Forum Moderators: open

Message Too Old, No Replies

SQL not loading correctly lately

on NT4

         

SEOMike

9:48 pm on Jul 17, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



We have been having SQL server agent crash lately on a server running NT4. The error is:

SQL server agent could not be started (reason: Unable to connect to server (local); SQL server can not start).

Any ideas? I'm freakin stumped.

encyclo

10:03 pm on Jul 17, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I've got a Windows sysadmin visiting today, so I've just asked. He says to ask whether you've changed any on the login names or passwords, especially for the Administrator accounts, as SQL server uses Builtin/Administrator to start. Otherwise, go to the "SQL Server Agent" and check properties for the login info and make sure it is for an Administrator account.

If it's not that, I don't know, because I only know about Linux servers!

SEOMike

2:28 pm on Jul 18, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Thanks for the tip. I will definately check that. Trouble is... sometimes it loads just fine, then after a few days, it tanks.

The hunt countinues. However, it's too important to chase for long. I might go WIN2k server on it pretty soon if I can't chase this thing down.

JuniorHarris

3:21 pm on Jul 18, 2004 (gmt 0)

10+ Year Member



That's a weird message to get from an already running process. The could not be started message sounds like one from boot/startup process.

If you haven't already done so, double check and apply any service paks for sql server...

digitalv

3:58 pm on Jul 18, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Is this happening on BOOT or when you do it manually? If it's on boot, it could be happening because SQL Agent is trying to start before SQL Server loads or before SQL Server *finishes* loading. That would throw that error back to Agent.

Also what is the load like on your server at the time agent is trying to start? If the SQL Server is doing something that can tie it up and prevent it from responding to queries (like rebuilding indexes or pulling down replicated data) SQL Agent will time out waiting for the server to respond and will throw back a "can't connect to server" error of some sort.

If SQL is already running (and I mean running for a few minutes without being overloaded) what happens if you start agent manually or if it's running STOP it and start it back up?

macrost

10:21 pm on Jul 19, 2004 (gmt 0)

10+ Year Member



I have one question.. I have sql running and when I change my admin password, then of course sql won't start. How can I change that?

digitalv

10:42 pm on Jul 19, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Hit the SERVICES icon in your control panel / administrative tools.

You probably have the service starting as administrator instead of system. Change this to system account, or change the password here and that will solve your problem.