September 23, 2011 at 7:58 am
Twice a day, SQLSERVER becomes unresponsive and I will have to stop TCP, SQLSERVER, and SQLSERVER Agent, then restart to connect to my sqlserver.
OS=2008 R2 Server SP1
SQL=2008 Enterprise SP2
Error Log:
September 23, 2011 at 8:01 am
Your post is cut off.
September 23, 2011 at 8:08 am
Error Log
September 23, 2011 at 8:10 am
Error [298] sqlserver Error: 258 TXP provider: Timeout error [258].
Error [165] ODBC error: Login timeout expired
Error [298] Sqlserver error: 258 Unable to complete login process due to delay in prelogin response
September 23, 2011 at 8:58 am
Do you have login triggers?
September 23, 2011 at 9:16 am
No, I don't have login triggers
Shelley
September 23, 2011 at 9:28 am
Can you define what unresponsive means? Are you sure it's the server and not your client?
The inability to process a login usually means there are DDL triggers in place or a resource governor classifier that is delaying things. It could be memory as well. Is the server under load when this happens? Have you traced back through the error log before these messages to see what might be logged? Or maybe run a trace to track activity/performance monitor to track load before this happens?
September 25, 2011 at 5:55 am
It sounds like something is pegging the resources. Do you have scheduled events in SQL Server? How about in the OS? Do you have any form of monitoring in place so that you can observe the behavior of the server over time, see what's happening before it becomes unresponsive?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
September 25, 2011 at 11:49 am
what other software runs on this server?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
September 25, 2011 at 8:09 pm
Shelley Allen (9/23/2011)
Twice a day, SQLSERVER becomes unresponsive and I will have to stop TCP, SQLSERVER, and SQLSERVER Agent, then restart to connect to my sqlserver.OS=2008 R2 Server SP1
SQL=2008 Enterprise SP2
Error Log:
Does it happen at approximately the same time every day?
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply