Default instance stuck on starting

Question

Post reply

Default instance stuck on starting

Adam Bean

One Orange Chip

Points: 26631
More actions
October 16, 2009 at 10:39 am

#103840

Hey all,
Have a server that has a default instance of SQL 2000 SP3A Enterprise that when starting the service, it just sits on starting. Nothing in the application/system logs, nor does a new error log get created for SQL. I have restarted the server to no avail.
I've tried running the service under a local account, domain account, and even a domain admin, no change. The server houses another instance (SQL2000 MSDE, but I can't connect to it because it's only running on shared memory) which is up and running.
I've tried to install SP4, but when running the install, it simply returns a "setup has finished installing an instance of service pack 4" after a couple minutes. Now granted, I haven't done a SQL2000 SP4 install in awhile, I do remember it taking longer and giving more detail.
Any thoughts here?
Thanks

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply

Adam Bean One Orange Chip Points: 26631 More actions · Answer 1

Hello all, haven't had much luck on this issue and was hoping to catch someone's attention today.

Thanks

Steve Jones - SSC Editor SSC Guru Points: 736544 More actions · Answer 2

It sounds like something is messed up. The MSDE isn't a default as well by any chance, is it?

I know SP4 was quick, but not that quick. Does SP4 ask for an instance?

Adam Bean One Orange Chip Points: 26631 More actions · Answer 3

Steve Jones - Editor (10/19/2009)
It sounds like something is messed up. The MSDE isn't a default as well by any chance, is it?
I know SP4 was quick, but not that quick. Does SP4 ask for an instance?

Hey Steve. No, the default instance is indeed enterprise edition. Agreed, it is not that quick ... at least if memory serves correct. Negative, it does not ask for an instance.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 4

What happens if you try and start SQL from the command line? For the default instance, go to the directory with the executable and just run sqlservr.exe

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Adam Bean One Orange Chip Points: 26631 More actions · Answer 5

GilaMonster (10/19/2009)
What happens if you try and start SQL from the command line? For the default instance, go to the directory with the executable and just run sqlservr.exe

Hi Gila. It simply responds saying the service could not start. Yet when viewing the services, you'll see it sitting on "starting". Crazy huh?

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 6

Adam Bean (10/19/2009)
GilaMonster (10/19/2009)
What happens if you try and start SQL from the command line? For the default instance, go to the directory with the executable and just run sqlservr.exe
Hi Gila. It simply responds saying the service could not start. Yet when viewing the services, you'll see it sitting on "starting". Crazy huh?

You're getting that when you start SQL as a standalone executable? did you use any command line switches when you ran sqlservr.exe?

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Adam Bean One Orange Chip Points: 26631 More actions · Answer 7

GilaMonster (10/19/2009)
Adam Bean (10/19/2009)
GilaMonster (10/19/2009)
What happens if you try and start SQL from the command line? For the default instance, go to the directory with the executable and just run sqlservr.exe
Hi Gila. It simply responds saying the service could not start. Yet when viewing the services, you'll see it sitting on "starting". Crazy huh?
You're getting that when you start SQL as a standalone executable? did you use any command line switches when you ran sqlservr.exe?

Actually, I had not tried callings sqlservr.exe until now. I just did (c:\program files\microsoft sql server\mssql\binn\sqlservr.exe) and got the following:

"SQL Server could not find the default instance (MSSQLSERVER) - please specify the name of an existing instance on the invocation of sqlservr.exe. if you believe that your installation is ocrrupt or has been tampered with, uninstall then re-run setup to correct this problem."

Adam Bean One Orange Chip Points: 26631 More actions · Answer 8

Now to add to the mystery of this default instance ... when using the server network utility, the default instance does not appear in the "instances on this server" drop down, just a secondary MSDE sharepoint instance (i have another thread going for this).

Jan Vrubel Valued Member Points: 62 More actions · Answer 9

Hi,

as in most of the times, it's not necessary to reinstall...in this case often the problem lies in not sufficient registry permissions of the SQL Server service account.

Eg. in my case this was that the SQL Server account didn't have full control on HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\MSSQLServer ...