SQL Server Error Reference
SQL Server error messages are not always very helpful. Errors appearing in the error log and windows event log may not necessarily
be related to SQL Server but should still be investigated.
See this article
to find out why.
I regularly encounter error messages that subsequently lead me to spend hours tracking down the cause. The answer may be found in forums,
Books Online, technet, Microsoft support, or just plain old trial and error.
To save you from going through the same pain I have written articles on common errors and some not-so-common, explained the likely cause, and
given suggestions on how to troubleshoot them.
Please subscribe to my RSS feed for regular updates.
"Resolve Partial Assembly failed..."
is a fairly common error with a simple solution...
"SQLSCMControl() returned error 5040, 'The cluster node already exists.'"
is specific to a clustered instance of SQL Server 2005 SP2 when the build is 3179 or later...
"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections."
This article describes a methodical approach to diagnosing the cause of this error...
"FCB::Open failed: Could not open file <filename> for file number <filenumber>. OS error: 5(access denied)"
"The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs"
is a warning in the SQL Server error log that seems
to get a lot of interest in the forums...
Explains the warning "SQL Server has encountered n occurrence(s) of I/O requests taking longer than 15 seconds to complete on file fname in database dbname"
. Troubleshooting guide.