September 27, 2001 at 12:04 am
Here is a gotcha.
If stopping and restarting the MSSQLServer service. Leave some time between the stop and the start. Also check the errorlog to see that TCP port has been bound (if using TCP as one of the protocols).
Sometimes the port (default = 1433) has not been released by the service shutting down when the time the service is starting up again occurs.
If the port is unavailable and therefore not bound during SQL recovery, any TCP/IP connections to SQL will fail.
It can be confounding if you use named pipes as well because there will be some clients that fail authentication and others working without problems.
September 27, 2001 at 5:12 am
I've seen this - it does show up in the error log, so at least once you start looking for a problem there is a clue left!
Andy
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply