SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Default instance stuck on starting


Default instance stuck on starting

Author
Message
Adam Bean
Adam Bean
SSC-Insane
SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)

Group: General Forum Members
Points: 24330 Visits: 2222
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

---
SQLSlayer
Making SQL do what we want it to do.
Adam Bean
Adam Bean
SSC-Insane
SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)

Group: General Forum Members
Points: 24330 Visits: 2222
Hello all, haven't had much luck on this issue and was hoping to catch someone's attention today.

Thanks

---
SQLSlayer
Making SQL do what we want it to do.
Steve Jones
Steve Jones
SSC Guru
SSC Guru (609K reputation)SSC Guru (609K reputation)SSC Guru (609K reputation)SSC Guru (609K reputation)SSC Guru (609K reputation)SSC Guru (609K reputation)SSC Guru (609K reputation)SSC Guru (609K reputation)

Group: Administrators
Points: 609479 Visits: 21159
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?

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Adam Bean
Adam Bean
SSC-Insane
SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)

Group: General Forum Members
Points: 24330 Visits: 2222
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.

---
SQLSlayer
Making SQL do what we want it to do.
GilaMonster
GilaMonster
SSC Guru
SSC Guru (908K reputation)SSC Guru (908K reputation)SSC Guru (908K reputation)SSC Guru (908K reputation)SSC Guru (908K reputation)SSC Guru (908K reputation)SSC Guru (908K reputation)SSC Guru (908K reputation)

Group: General Forum Members
Points: 908901 Visits: 48838
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
Adam Bean
SSC-Insane
SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)

Group: General Forum Members
Points: 24330 Visits: 2222
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?

---
SQLSlayer
Making SQL do what we want it to do.
GilaMonster
GilaMonster
SSC Guru
SSC Guru (908K reputation)SSC Guru (908K reputation)SSC Guru (908K reputation)SSC Guru (908K reputation)SSC Guru (908K reputation)SSC Guru (908K reputation)SSC Guru (908K reputation)SSC Guru (908K reputation)

Group: General Forum Members
Points: 908901 Visits: 48838
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
Adam Bean
SSC-Insane
SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)

Group: General Forum Members
Points: 24330 Visits: 2222
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."

---
SQLSlayer
Making SQL do what we want it to do.
Adam Bean
Adam Bean
SSC-Insane
SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)

Group: General Forum Members
Points: 24330 Visits: 2222
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).

---
SQLSlayer
Making SQL do what we want it to do.
Jan Vrubel
Jan Vrubel
Valued Member
Valued Member (62 reputation)Valued Member (62 reputation)Valued Member (62 reputation)Valued Member (62 reputation)Valued Member (62 reputation)Valued Member (62 reputation)Valued Member (62 reputation)Valued Member (62 reputation)

Group: General Forum Members
Points: 62 Visits: 19
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 ...
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search