Have you ever seen errors like these?
"Could not create SSPI context."
"No server principal name found."
There are literally dozens of variations, and the most common resolution is to
ensure that a Service Principal Name (SPN) gets created in Active Directory. If you see
these errors, just check the Microsoft Knowledge Base; you??™ll get a hit right away with
directions on troubleshooting the issue.
Power
Often an overlooked hardware gremlin, power issues can present themselves in a variety
of seemingly unrelated events. Random reboots, network hiccups, and even corrupt
backups can be the result of an inconsistent power supply. Some power problems can be
handled by simply installing redundant power supplies. Sometimes there??™s nothing you
can do to protect against power issues.
Power Surges/Lapses
I recently encountered a mission-critical server that was disabled by a lightning strike.
It had surge protection and a basic Uninterruptible Power Supply (UPS). Apparently,
neither was sufficient. Considering the massive amount of power a lightning strike can
generate, it??™s hard to conceive of any sort of protection being sufficient in the event of
a direct strike.
Pages:
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484