November 27, 2008 at 7:01 am
We have a clustered 64bit SQL server 2005 SP2 (active-active) cluster running on Windows 2003 Enterprise x64 Edition Service Pack 2.
But from time to time we receive this event 17187 (once every 3 or 4 days around 12:00 PM) stating that "SQL Server is not ready to accept new client connections.".
I have searched all over the internet for a reason for this and always came to the 2 following reasons:
1) SQL server version is lower than SP2 => not the case
2) The "portfast" option is not enabled on the CISCO switch => I had this verified by the network guys and it is enabled.
So I suppose that it must be a performance issue on the SAN drives.
Does any of you have the same problem and maybe know how to solve this, because during this little glitch it causes an application to crash. (Re-writing the application is not an option 😉 )
Kind regards,
Peter
November 27, 2008 at 7:41 am
Anything in the SQL error log from around the same time?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 27, 2008 at 8:04 am
In the SQL logs I only find the following warning, but this happens more often that the error in teh Eventviewer.
The example hereunder is for CPU1, I have the same for CPU's 3, 5 and 7)
Date11/26/2008 12:05:07 PM
LogSQL Server (Current - 11/27/2008 3:41:00 PM)
SourceServer
Message
The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply