15 November,2012 by Jack Vamvas
SQL Server exists within a complex IT ecosystem – disk , svc controllers, routers, networks, domain controlers, hardware through to user queries. It is not unusual for a problem in the wider sphere to result in a negative impact to SQL Server. Organising engineers from other areas such as storage or networks is not always straightforward.
When a system performance issue occurs, they’re probably receiving requests from other technology areas – and are overwhelmed by the mounting management pressure to resolve the issue.
Recently the following error message appeared on a server restart “This computer was not able to set up a secure session with a domain controller in domain xxxxxxxxxxx due to the following:
There are currently no logon servers available to service the logon request. “ This stopped SQL Server starting as the Long Account is a domain account.
My immediate questions were :
a) has the command hit the logon server and been rejected ?
b) has the command not hit the logon server?
Unless you are a supertech – this root cause analysis may require the assistance of other experts , in this case : Server Administrator and Network Administrator.
How do you get other engineers and administrators to focus on your problems?
1) Document clearly as possible every test you’ve completed. Is the problem repeatable?
2) Document every log message
3) Have you checked the Change request system to ensure no recent changes have occurred?
4) Have you checked recent patches ? Use Powershell List all Patches Updates on a Server - SQL Server DBA
5) Facts speak louder then complaining. Ultimately most IT based technical problems have a logical explanation , maintain a logical approach.
6) Last resort: outline risk to management. Management can assist in creating priorities for the organisation