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?
Making SQL do what we want it to do.