December 16, 2010 at 1:55 pm
We had a port failure on a prod box.
It caused our users to not be able to login to any of the db's. The server never re-booted.
Once the port failed we got this OS error - "[sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746; message = [Microsoft][SQL Native Client]TCP Provider: An existing connection was forcibly closed by the remote host.
"
then we got this OS error:
"SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again."
then (10 minutes later)?! everything is good...but I have to explain what happened to the bosses
any idea why a port failure would cause SQL to go into a re-intialize type of state?
December 16, 2010 at 9:17 pm
Check if your SQL Server has maximum connections number set. Possibly it reached this number and then when some sessions closed it returned to normal.
Also, if default trace for that day is available you can check if there is any additional information there.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply