| Author |
 Topic  |
|
|
X002548
Not Just a Number
15586 Posts |
 Posted - 04/19/2005 : 15:46:42
|
Ever since the started moving the servers over to "virtual" serves on blades, I been seeing weird problems.
No I can't get one to start
I get
quote:
Error: 17883, Severity: 1, State: 0
2005-04-16 21:49:05.37 server The Scheduler 0 appears to be hung. SPID 1, ECID 0, UMS Context 0x02554E88.
And a dialog error 1053 saying SQL Server Service could not be started in a timely manner.
ANY ideas are welcome
Brett
8-) |
|
|
eyechart
Flowing Fount of Yak Knowledge
USA
3575 Posts |
Posted - 04/19/2005 : 15:53:33
|
| what hardware are you using? |
 |
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 04/19/2005 : 16:06:56
|
IBM's EMC....I'm outta my depth here...
Brett
8-) |
|
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
USA
6997 Posts |
Posted - 04/19/2005 : 16:11:04
|
Maybe it is attempting to start before the network card is activated, and it fails because it can't reach a domain controller to login the SQL Server Service account.
CODO ERGO SUM |
|
|
|
eyechart
Flowing Fount of Yak Knowledge
USA
3575 Posts |
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 04/19/2005 : 16:17:05
|
This is the default instance...I have a named instance running...go figure....
Brett
8-) |
|
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 04/19/2005 : 16:55:45
|
My Director decide to sms into the box, copy the sqlservr.exe from the named instance that is running, and copied it to the default instance.
AND IT WORKED
I told him he was dangerous...
I also forgot to mention that the box to hit when the machine rooms power got hit and the box went dead...you would think the have UPS's on these things
I still can't beleive it....
I think a rebuild might be a good idea...
Brett
8-) |
|
|
|
eyechart
Flowing Fount of Yak Knowledge
USA
3575 Posts |
Posted - 04/19/2005 : 17:33:29
|
did you apply sp3a and ms03-031 to both instances? It sounds like maybe one instance was patched up higher than the other. Copying the sqlsrv executable over another one is definitely dangerous, especially if the other files that go along with it are not at the same level. If one file is out of date or corrupted, then there could be more.
I would doublecheck that instance to make sure that it is patched up properly.
-ec
|
|
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 04/20/2005 : 09:37:21
|
Thanks.
I plan on rebuilding the entire box
Brett
8-) |
|
|
| |
Topic |
|
SQL Server Service won't start on a blade
