October 20, 2005 at 9:07 am
I am a new admin to an e-commerce company and twice I have tried to access properties of our production server using Enterprise Manager (SQL Server 2000) and both times it has caused SQL Server to stop working and we have had to have our server rebooted (it is remotely administered). During reboots SQL Server hangs up and it is taking quite a lot of time to get it to restart. These may be two separate issues. Our server is running Windows Server 2000, IIS 5.0, SQL Server 2000, and IMail as our mail server. I suspect a conflict on restart, but everything I see says that these are all compatible. Any help would be appreciated.
October 20, 2005 at 9:53 am
Are there any applicable errors in any of the following:
(1) OS Application Event Log
(2) OS System Event Log
(3) SQL Server log
Also, when you try and check on any of the properties through another mechanism, say through Query Analyzer and using sp_configure, do you see a similar lock-up?
K. Brian Kelley
@kbriankelley
October 20, 2005 at 10:22 am
There were no errors reported before the incident. The Server had backed up as normal an hour earlier. The next log in SQL log is that the Server was shutting down due to system shut down.
The application log and the system log are also void of information before the problem. The application log records when I tried to stop and restart SQL Server Agent, but this was after the database hung up.
Afterwards I found errors Event ID 61 on both dates (the only messages found on both those dates). They concern KB266416. Can problems with performance counters cause the Properties in Enterprise Manager to be inaccessible? I was just trying to look at Server Properties.
Other messages, and they are all on restart after the initial problem, were
Event ID 1010, and 1016 (just a warning message). But these only appear after the most recent incident, not the one just prior.
October 20, 2005 at 11:37 am
How many databases do you have on the server?
When EXACTLY does it hang up in EM?
October 20, 2005 at 12:13 pm
Jeff,
Lets start with startup.
1.Get us any messages after the server is coming up from application, security and system logs that are errors or warnings. The moment the server is coming up could be looked up in the system log. There should be 3 messages with the source of eventlog (open each one by double-clicking on it): 1. Event log service was stopped 2.Microsoft Windows..... 3. Event Log Service was started. These 3 messages are the indicator when the server is going down and up again. There will be records after them from different applications including SQL Server. We are most interested in any messageg from Service Control Manager. They can contain the info what is wrong on startup.
2. Get us messages from SQL Server log, the one that starts after the machine was just rebooted. Default Directory is <Your SQL Server Install location for Data>\MSSQL\LOG like: C:\Program Files\Microsoft SQL Server\MSSQL\LOG. File name is Errorlog or ErrorlogX where X is a number. Check system log when the machine was restarted, open logs in Notepad and check the time there. The new log is open each time SQL Server is starting, but you may restart SQL without restarting the server, so search for the one that correspond to the server restart.
Yelena
Regards,Yelena Varsha
October 20, 2005 at 12:36 pm
Thank you for your efforts. We have two databases running on the same instance of SQL Server. They are not very large with plenty of free space.
The Error messages after restarting are:
Event ID: 7001
Service Control Manager
The SQLSERVERAGENT service depends on the MSSQLSERVER service which failed to start because of the following error: %%0
Event 26
Application popup: Service Control Manager : At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details.
The SQL Server logs say nothing outside of normal start up.
October 20, 2005 at 1:06 pm
This is certainly a descriptive error message (did you remember this joke about the young man who writes error messages for Microsoft?)
The SQL Agent error message on startup is OK, it is normal when SQL Server can not start. I wonder why there was no messages why it could not be started for the first place.
In my practice there could be several reasons: we do remember that SQL Server starts eventually. Those reasons are:
1. SQL Server tries to startup on the Domain startup account that is not accessible yet and can not use cached credentials because nobody logged in interactively on the server for some time with this account.
Check if domain is accessible.
2. Some permissions or policies prevent access to SQL Server executables to the startup account. I had 2 cases when it was Local System account that was removed from ACL (access control list) of SQL folders. The permission is somehow gained later.
3. Had this case with SQL Server 6.5 several times: as soon as the server is shutting down, SQL Server database files are released to OS and on the startup they are grabbed by Norton or Backup utility. Happed when those utilites supposed to be running in the early hours and one of the users used to work during early hours and rebooted the server.
Did you check the Security log for the startup times?
Another idea: set SQL Server startup type to Manual, reboot the server, log in as yourself, not SQL Server startup account and try to start SQL Server manually. See what happens or any pop up messages. What is the startup account anyway? Domain or local? Check that account is not locked and password did not expire.
Yelena
Regards,Yelena Varsha
October 20, 2005 at 1:10 pm
Not the issue: SQL Server restarted and our web sites are running now. I am trying to find out how to prevent this from happening again.
November 30, 2005 at 5:50 pm
Can you please post the solution/resolution to this problem?
I am having a similar problem except it is not while running Enterprise Manager..it is occurring
at boot time.
Win2k Server SP4 - SQLServer 2000
System Event Log:
Event ID: 7022
Source: Service Control Manager
Description:
The MSSQLSERVER service hung on starting
Then of course sqlserveragent fails because it depends on mssqlserver.
Application Event Log:
Warning
Event ID: 19011
Source: MSSQLServer
Description:
SuperSocket info: (SpnRegister): Error 1355.
The odd thing is after 10 minutes of trying to start mssqlserver, it gives up and I can
then remote desktop to the server. If I use task manager to kill sqlservr.exe, I can then
use the Services manager to start MSSQLServer service just fine. At that point messenger and sqlagent
and Windows Install Service all fire up immediately.
Other pertinent info:
Does NOT Log on as a Local System Account.
Using visnetic Firewall...but the same problem occurs with it enabled or disabled.
Viewing 9 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply