Can't Find (local) Server After Messing With SQL Server 2005 Betas 1

[BoulderBum]

I'm not sure exactly what happened, but all of a sudden I can't connect to my local instance of SQL Server (though I used to be able to just fine).

I'm not sure exactly when it happened, but I think it probably has something to do with me toying around with the SQL Server 2005 Betas which never quite worked right, and have since been uninstalled.

I've uninstalled SQL Server 2000, reinstalled it twice, and I still can't connect to it or even register it in Enterprise Manger.

Anyone know what might be going on?

PS- I also installed MySQL 5.0 around the same time, which may or may not have anything to do with it.

 

[mrdenny]

First take a look at the event log and the SQL ERRORLOG and see if there is anything in there.

Are you sure that SQL 2000 is starting correctly?

What method did you use to uninstall the SQL 2005 beta?

Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[BoulderBum]

The Visual Studio 2005 Beta 2/RC installer tried to install the Express Edition (and I later tried to install the full version beta) but it never quite installed right (a widespread bug Microsoft knew about). It also hosed me when trying to install the final release version until I cleaned a bunch of leftover programs off the system, but somewhere in all of that something got hosed.

I can see the SQL Server process is running, but I can't connect to the server at all yet.

Right now I'm thinking of wiping out the OS as that's something that is probably past due anyway, but I'd welcome any advice that might prevent me having to do that!

 

[mrdenny]

In the ERRORLOG from SQL 2000 it should say what ports and protocols it's listening on. What is it saying?

Are you able to connect with osql or isql?

Try connecting via machine name instead of (local).

Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[BoulderBum]

I tried that machine name thing and it didn't work.

Looks like port 1433, listening on TCP, Shared Memory, Named Pipes.

2005-11-24 02:53:53.62 server    Microsoft SQL Server  2000 - 8.00.194 (Intel X86) 
	Aug  6 2000 00:57:48 
	Copyright (c) 1988-2000 Microsoft Corporation
	Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)

2005-11-24 02:53:53.64 server    Copyright (C) 1988-2000 Microsoft Corporation.
2005-11-24 02:53:53.64 server    All rights reserved.
2005-11-24 02:53:53.64 server    Server Process ID is 1488.
2005-11-24 02:53:53.64 server    Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2005-11-24 02:53:53.71 server    SQL Server is starting at priority class 'normal'(1 CPU detected).
2005-11-24 02:53:54.62 server    SQL Server configured for thread mode processing.
2005-11-24 02:53:54.71 server    Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2005-11-24 02:53:54.76 server    Attempting to initialize Distributed Transaction Coordinator.
2005-11-24 02:53:55.48 server    Failed to obtain TransactionDispenserInterface: Result Code = 0x8004d01b
2005-11-24 02:53:56.28 spid3     Starting up database 'master'.
2005-11-24 02:53:58.31 server    Using 'SSNETLIB.DLL' version '8.0.311'.
2005-11-24 02:53:58.31 spid5     Starting up database 'model'.
2005-11-24 02:53:58.56 spid3     Server name is 'blahblah'.
2005-11-24 02:53:58.56 spid8     Starting up database 'msdb'.
2005-11-24 02:53:59.34 spid9     Starting up database 'pubs'.
2005-11-24 02:54:00.04 spid10    Starting up database 'Northwind'.
2005-11-24 02:54:02.24 spid5     Clearing tempdb database.
2005-11-24 02:54:03.96 server    SQL server listening on 127.0.0.1: 1433.
2005-11-24 02:54:04.68 server    SQL server listening on TCP, Shared Memory, Named Pipes.
2005-11-24 02:54:04.68 server    SQL Server is ready for client connections
2005-11-24 02:54:05.54 spid5     Starting up database 'tempdb'.
2005-11-24 02:54:05.71 spid3     Recovery complete.
2005-11-24 02:56:46.25 server    SQL Server terminating because of system shutdown.
2005-11-24 02:56:46.25 server    LogEvent: Failed to report the current event. Operating system error = 31(A device attached to the system is not functioning.).
2005-11-24 02:56:47.62 spid3     SQL Server is terminating due to 'stop' request from Service Control Manager.

 

[mrdenny]

OK, it looks like SQL isn't picking up your NIC's IP address for some reason (or you don't have a NIC in the machine).

Were you able to connect from osql or isql?

Looks like a drive letter that SQL is looking for isn't there any more either.

Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[BoulderBum]

I actually didn't try osql/isql, but I figured it was time for a fresh start anyway (I've been running the current OS for 3 years so it was past due anyway). I reinstalled the OS and about 16 gigs of server and development software and everything is getting along fine now.

That and my system is humming along now that I got all this cool system utility software at day after Thanksgiving sales!

Thanks a lot for your help, Denny.

 

[mrdenny]

no problem.

Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com