TCP connectivity after ESENT events
Tom
This is a troublesome problem. We recently started having trouble with a SQL
200 SP 4 server running on Win2k3 Server R2 Enterprise 32 bit SP 2.
SQL intermittently stops listening or responding to requests over TCP. We
can still telnet to 1433 from other sources but our application stops
working. We also cannot connect via SQL Manager over TCP. We can however
connect via SQL Manager on a remote server to the troubled server via named
pipes. SQL does not record any errors and never sees the connection attempts.
SQL never goes down. Windows Application and system logs do not show any
errors. So far the only way top solve the problem is to reboot the server.
Restarting SQL does not help. We have not seen anything meaningful monitoring
network traffic as well.
The only real clue we have is that preceding each incident, the event log
has an information notification form the source ESENT that svchost has
started the database engine 5.02.3790.3959 Event id 100. This is followed 5
minutes later by a shut down of the same database: event id 101.
I understand ESENT is used my Exchange, Windows Search, and AD and is used
to store DHCP and WINS databases. This server is not doing any of these
things.
Please help. This is causing much pain.
Thanks in advance