April 15, 2002 at 12:10 pm
I have 6 Instances installed. The services for each are set to automatically start.
But only 2 Instance's services start.
Event Viewer - system log:
The MSSQL$DEV service hung on starting.
--------------------
The SQLAgent$DEV service depends on the MSSQL$DEV service which failed to start because of the following error:
After starting, the service hung in a start-pending state.
ANY IDEAS ?
April 15, 2002 at 12:54 pm
-> SQL Server 2000 Enterprise Edition that is, on Windows 2000 Advanced Server with 2Gb RAM.
April 15, 2002 at 3:27 pm
Try setting all to manual then start each one independently. Each instance wants to launch a copy of SQL in memory and they may be tying each other up to log for the service to complete or even trying to access dll and causing a deadlock type situation based on sequence of access. By doing manual you should be able to get all up and running.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
April 17, 2002 at 8:31 am
But Manual is not good if the box reboots in the middle of the night and when it comes back the services are not started.
April 17, 2002 at 11:09 am
Haven't tried this in dealing with instances but have with Service apps that need SQL up and ready to receive when reboot occurrs. Set 1 instance to automatic, then create a job with Operating System Command task to start the next server and it's agent scheduled for when SQL Server Agent Starts. On the next server (set to manual) do the same for the next. In effect daisy chaning the starts and allowing one to finish before the next. But this still does not guarantee will occurr. I would look at seperating them to different boxes to be sure, if at all possible. Or put all under one instance and deal with differently.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply