Re: SQL Server stops responding
From: Anthony Thomas (ALThomas_at_kc.rr.com)
Date: 02/18/05
- Next message: Anthony Thomas: "Re: Disk Queue Length counters not meaningful in SQL 2000?"
- Previous message: Anthony Thomas: "Re: Login/connection problem"
- In reply to: Jonathan S: "SQL Server stops responding"
- Next in thread: scott mackie via SQLMonster.com: "Re: SQL Server stops responding"
- Reply: scott mackie via SQLMonster.com: "Re: SQL Server stops responding"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 17 Feb 2005 21:08:04 -0600
Not to mention that it sounds like the box is WAAAAYYY too busy. SQL Server
should be deployed to a dedicated server for best usage. Anywhere else
requires a LOT of fine tuning to get all of the applications function
cooperatively together.
Sincerely,
Anthony Thomas
-- "Jonathan S" <JonathanS@discussions.microsoft.com> wrote in message news:D3A9594F-32D4-40C3-A027-DF9CD5D14EED@microsoft.com... Hi, here is another 'stops responding' problem and I cannot find the problem (and therefore the solution!). SQL Server 2000 with sp3a running on Windows 2000 sp4. One database is being replicated using snapshot replication. Since last week, on several occasions SQLServer simply stopped responding. Services showed that the SQLServer and SQLServerAgent were both running but I could not connect at all (using Enterprise Manager, Profiler, Query Analyser and even osql). Could not manually restart the services using the control panel Services applet and command line NET STOP MSSQLSERVER did not work either. The only way to get it working again was to reboot the box. Nothing was recorded in the event logs. In the SQLServer error logs occasionally there is the entry 'LogEvent: Failed to report the current event. Operating system error = 31(A device attached to the system is not functioning.).' and this tended to be recorded just prior to a system shutdown (ie restarting the box). Also I am getting several errors in the exception.log file similar to: '02/01/05 18:31:39 spid 0 Exception 0xc0000005 EXCEPTION_ACCESS_VIOLATION at 0x39D9E751', all of these errors caused by SPID 0. And finally, here is another extract from an SQLServer error log: 2005-02-01 18:18:49.50 spid3 Launched startup procedure 'sp_MSrepl_startup' 2005-02-01 18:18:55.70 spid52 Using 'xpsqlbot.dll' version '2000.80.194' to execute extended stored procedure 'xp_qv'. 2005-02-01 18:18:58.57 spid52 Using 'xpstar.dll' version '2000.80.194' to execute extended stored procedure 'xp_sqlagent_monitor'. 2005-02-01 18:31:39.85 server Using 'sqlimage.dll' version '4.0.5' Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL\log\SQL00109.dmp 2005-02-01 18:31:39.89 server process_commands: Process 1868 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process. SQLServer then performs a stack dump. I have also been running a Profiler trace over the past week and nothing unusual was recorded prior to any of these unresponsive sessions. Since the box is also used to authenticate users, acts as a print server and runs some other client server database (Pegasus accounting stuff) I simply cannot keep rebooting the box every time SQLServer gives up. Sadly I don't know enough to fix this problem, but I need to find a solution before I get lynched! Thanks in anticipation for any help. -- Jonathan S
- Next message: Anthony Thomas: "Re: Disk Queue Length counters not meaningful in SQL 2000?"
- Previous message: Anthony Thomas: "Re: Login/connection problem"
- In reply to: Jonathan S: "SQL Server stops responding"
- Next in thread: scott mackie via SQLMonster.com: "Re: SQL Server stops responding"
- Reply: scott mackie via SQLMonster.com: "Re: SQL Server stops responding"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
