SQL Agent won''t start
-
After a failed MS Business Contact Manager attempt, both instances of SQL on my laptop appear to be running according to the SQL Service Manager, however I cannot connect to either and cannot start the SQL Server agent.
Any help in remedying this would be greatly appreciated.
"Some like to understand what they believe in. Others like to believe in what they understand."
--Stanislaus J. Lec -
What OS, service pack, SQL Server, service pack versions? Personal firewall in place? If so, what is it?
When you run a netstat -an from the command prompt, do you see the instances listening on their ports like they should? The default instance should listen on 1433 unless you've set it differently. you should see a line that has 0.0.0.0:1433 and the word LISTENING at the end of it.
Also, stop both instances. Check the error logs. You can find them typically at
Default instance:
C:\Program Files\Microsoft SQL Server\MSSQL\LOG
Named instance:
C:\Program Files\Microsoft SQL Server\MSSQL$\LOG
You're looking for ERRORLOG. This can be viewed with any text editor. The reason you stop the SQL Server instances is so you'll be able to open the ERRORLOG file.
What do they say?
K. Brian Kelley
@kbriankelley -
Brian,
Thanks for your help. I ran netstat -an, I did not see the sql server listening.
Here is a view of the log file for the primary server:
2005-03-16 09:36:35.62 server Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Personal Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2005-03-16 09:36:35.69 server Copyright (C) 1988-2000 Microsoft Corporation.
2005-03-16 09:36:35.69 server All rights reserved.
2005-03-16 09:36:35.69 server Server Process ID is 884.
2005-03-16 09:36:35.70 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2005-03-16 09:36:35.99 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2005-03-16 09:36:36.46 server SQL Server configured for thread mode processing.
2005-03-16 09:36:36.58 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2005-03-16 09:36:36.70 spid3 Starting up database 'master'.
2005-03-16 09:36:38.61 spid3 0 transactions rolled back in database 'master' (1).
2005-03-16 09:36:38.69 spid3 Recovery is checkpointing database 'master' (1)
2005-03-16 09:36:40.00 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-03-16 09:36:40.01 spid5 Starting up database 'model'.
2005-03-16 09:36:40.22 server SQL server listening on Shared Memory.
2005-03-16 09:36:40.24 server SQL Server is ready for client connections
2005-03-16 09:36:40.36 spid3 Server name is 'CALIBAN'.
2005-03-16 09:36:40.36 spid3 Skipping startup of clean database id 4
2005-03-16 09:36:40.36 spid3 Skipping startup of clean database id 5
2005-03-16 09:36:40.36 spid3 Skipping startup of clean database id 6
2005-03-16 09:36:40.36 spid3 Skipping startup of clean database id 7
2005-03-16 09:36:40.36 spid3 Skipping startup of clean database id 8
2005-03-16 09:36:40.36 spid3 Skipping startup of clean database id 9
2005-03-16 09:36:40.36 spid3 Skipping startup of clean database id 10
2005-03-16 09:36:40.36 spid3 Skipping startup of clean database id 11
2005-03-16 09:36:40.36 spid3 Skipping startup of clean database id 12
2005-03-16 09:36:41.45 spid5 Clearing tempdb database.
2005-03-16 09:36:45.21 spid5 Starting up database 'tempdb'.
2005-03-16 09:36:46.61 spid3 Recovery complete.
2005-03-16 09:36:47.20 spid3 Launched startup procedure 'smDEX_Build_Locks'
2005-03-16 11:07:02.68 spid3 SQL Server is terminating due to 'stop' request from Service Control Manager.
Hee is the log from the secondary server:
2005-03-16 09:36:34.06 server Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Personal Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2005-03-16 09:36:34.08 server Copyright (C) 1988-2000 Microsoft Corporation.
2005-03-16 09:36:34.08 server All rights reserved.
2005-03-16 09:36:34.08 server Server Process ID is 820.
2005-03-16 09:36:34.08 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL$WS2\log\ERRORLOG'.
2005-03-16 09:36:34.16 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2005-03-16 09:36:34.41 server SQL Server configured for thread mode processing.
2005-03-16 09:36:34.45 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2005-03-16 09:36:34.50 spid3 Starting up database 'master'.
2005-03-16 09:36:36.12 spid3 0 transactions rolled back in database 'master' (1).
2005-03-16 09:36:36.15 spid3 Recovery is checkpointing database 'master' (1)
2005-03-16 09:36:36.49 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-03-16 09:36:36.50 spid5 Starting up database 'model'.
2005-03-16 09:36:36.51 server SQL server listening on Shared Memory.
2005-03-16 09:36:36.51 server SQL Server is ready for client connections
2005-03-16 09:36:36.56 spid3 Server name is 'CALIBAN\WS2'.
2005-03-16 09:36:36.56 spid3 Skipping startup of clean database id 4
2005-03-16 09:36:36.56 spid3 Skipping startup of clean database id 5
2005-03-16 09:36:36.56 spid3 Skipping startup of clean database id 6
2005-03-16 09:36:36.56 spid3 Skipping startup of clean database id 7
2005-03-16 09:36:36.56 spid3 Skipping startup of clean database id 8
2005-03-16 09:36:37.29 spid5 Clearing tempdb database.
2005-03-16 09:36:43.08 spid5 Starting up database 'tempdb'.
2005-03-16 09:36:43.93 spid3 Recovery complete.
2005-03-16 09:36:44.28 spid3 Launched startup procedure 'smDEX_Build_Locks'
2005-03-16 11:07:08.87 spid3 SQL Server is terminating due to 'stop' request from Service Control Manager.
In the log files, I see where it reports that both servers are listening but I don't see it in the netstat -an return. I am not sure what port the second instance is using but I believe the first instance should be using 1433 since I did not alter that during the installation.
I am confused by the SQL Service Manager showing the servers running yet the netstat -an shows that they are not listening, what do I need to do to get the servers listening?
Thanks again for your assistance, I appreciate it.
"Some like to understand what they believe in. Others like to believe in what they understand."
--Stanislaus J. Lec -
These servers are only listening on shared memory. That means they can't be communicated with other than on the laptop. That also explains why you're not seeing an entry with netstat -an.
I noticed you are running Windows XP SP2 (Windows NT 5.1 - Service Pack 2). Do you have the firewall enabled? If so, you must enable the network ports to allow SQL Server to talk. You can find more here:
K. Brian Kelley
@kbriankelley -
Brian,
I tried the steps listed in the MS article w/o success. SQL still would not listen for the connection. I did come across the following article:
SQL Server Critical Update Wizard for Microsoft® SQL Server™ 2000 and Microsoft® SQL Server Desktop Engine (MSDE) 2000
The SQL Server Critical Update Wizard will scan Microsoft SQL Server 2000 and MSDE 2000 to help detect instances vulnerable to the "Slammer" worm, and will attempt to update the affected files.
from:
After running the tool, I can now connect to both instances. Thanks for your help.
Eric
"Some like to understand what they believe in. Others like to believe in what they understand."
--Stanislaus J. Lec
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply