Can't connect to new MSDE installation

I installed MSDE 2000 Release A as follows:

C:\MSDERelA>setup TARGETDIR="C:\MSDE" DATADIR="C:\MSDE_Data" INSTANCENAME="CPAPM
" SECURITYMODE=SQL SAPWD="MyPwd" /L*v msdelog.txt

Everything appears to install successfully.  In the msdelog.txt file, it says that the installation was successful at the end of the file.  I can start the service for this instance in services but I can't connect to it or see it from Enterprise Manager.

The code included is the test from the SQL server errorlog.  I've tried uninstalling, reinstalling, rebooting, removing registry settings, deleting the install folder, installing to a different folder, but whatever I do I run in to this same problem.  This is a relatively new server.  It does have SQL 2005 express installed for another app.  Can MSDE2000 and SQL 2005 express not coexist on the same server?
2009-05-20 22:08:31.37 server    Microsoft SQL Server  2000 - 8.00.760 (Intel X86) 
	Dec 17 2002 14:22:05 
	Copyright (c) 1988-2003 Microsoft Corporation
	Desktop Engine on Windows NT 5.2 (Build 3790: Service Pack 2)
 
2009-05-20 22:08:31.37 server    Copyright (C) 1988-2002 Microsoft Corporation.
2009-05-20 22:08:31.37 server    All rights reserved.
2009-05-20 22:08:31.37 server    Server Process ID is 1396.
2009-05-20 22:08:31.37 server    Logging SQL Server messages in file 'C:\MSDE_DataMSSQL$CPAPM\LOG\ERRORLOG'.
2009-05-20 22:08:31.37 server    SQL Server is starting at priority class 'normal'(1 CPU detected).
2009-05-20 22:08:31.57 server    SQL Server configured for thread mode processing.
2009-05-20 22:08:31.57 server    Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2009-05-20 22:08:31.61 spid3     Warning ******************
2009-05-20 22:08:31.61 spid3     SQL Server started in single user mode. Updates allowed to system catalogs.
2009-05-20 22:08:31.61 spid3     Starting up database 'master'.
2009-05-20 22:08:31.73 spid3     Server name is 'WGD04\CPAPM'.
2009-05-20 22:08:31.73 spid3     Skipping startup of clean database id 5
2009-05-20 22:08:31.73 spid3     Skipping startup of clean database id 6
2009-05-20 22:08:31.73 spid3     Starting up database 'msdb'.
2009-05-20 22:08:31.73 server    Using 'SSNETLIB.DLL' version '8.0.766'.
2009-05-20 22:08:31.78 spid5     Starting up database 'model'.
2009-05-20 22:08:31.84 server    SQL server listening on Shared Memory.
2009-05-20 22:08:31.84 server    SQL Server is ready for client connections
2009-05-20 22:08:31.87 spid5     Clearing tempdb database.
2009-05-20 22:08:31.92 spid5     Starting up database 'tempdb'.
2009-05-20 22:08:31.93 spid3     Recovery complete.
2009-05-20 22:08:31.93 spid3     SQL global counter collection task is created.
2009-05-20 22:08:31.96 spid3     Warning: override, autoexec procedures skipped.
2009-05-20 22:08:41.90 spid51    Error: 15457, Severity: 0, State: 1
2009-05-20 22:08:41.90 spid51    Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install..
2009-05-20 22:08:41.95 spid51    Error: 15457, Severity: 0, State: 1
2009-05-20 22:08:41.95 spid51    Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install..
2009-05-20 22:08:41.99 spid3     SQL Server is terminating due to 'stop' request from Service Control Manager.

Open in new window

LVL 3
FWestonAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Brian PringleSystems Analyst II, SCM, ERPCommented:
They can exist on the same server as long as they do not use the same instance name.  

How are you trying to connect?  Are you trying to connect from the command line or from the  Management Studio?

Try this command to see if you can get in at a command prompt.

osql -E -S servername\CPAPM

Replace servername with the actual name of the server -- not "localhost".  If you get a "1>" prompt, then you are in.

There are some other considerations, such as network protocols being disabled by SQL 2005 being installed.  Use the Configuration Manager (I can't remember the exact name right now) and on the left-hand side, select Network Protocols.  Enable TCP/IP and Named Pipes (the first three should be enabled).  Restart the SQL services and try again.
0
Brian PringleSystems Analyst II, SCM, ERPCommented:
Just noticed... is that a space after CPAPM (inside the quotes)?
0
FWestonAuthor Commented:
No space.  I tried what you suggested from the command line and got in.  I had been trying to connect using Enterprise Manager from another server that has SQL 2000 installed.  I'm going to install the SQL 2000 management tools on this server to see if I can get connected that way.  I figure if named pipes and tcp/ip are disabled, I should still be able to get in from the local machine.
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Brian PringleSystems Analyst II, SCM, ERPCommented:
Not necessarily.  You can use Enterprise Manager from another server.  When it asks for the name of the SQL server, type the servername\CPAPM, just like you did from the command line.
0
FWestonAuthor Commented:
I tried that previously.  I installed Enterprise Manager on the local server and added the instance of MSDE to it.  When I browsed for an instance to add, it didn't show up, but when I typed it in manually it registered successfully.  I changed the network protocols to enable tcp/ip and named pipes, then the restarted the service.  Now it doesn't want to connect in Enterprise Manager again.  I've checked the event log and now I see a message there saying that the configuration for the SQL 2005 instance is invalid, so I've uninstalled that and am waiting for an opportunity to bounce the server.
0
Brian PringleSystems Analyst II, SCM, ERPCommented:
I just realized that you installed Enterprise Manager on the same server with SQL 2005.  While SQL 2000 instances can co-exist with SQL 2005 instances, you cannot (or shouldn't) install Enterprise Manager and SQL Management Studio on the same server.  

Use SQL 2005 Management Studio Express -- even for SQL 2000 databases.  It is a much better program, works with both version, and is easier to use (for most functions)
0
FWestonAuthor Commented:
Sorry for the delay, I haven't had access to the server until yesterday.  I created a new Windows 2003 SP2 virtual machine, and installed MSDE as follows:

setup INSTANCENAME="CPAPM" SECURITYMODE=SQL SAPWD="mypwd" /L*v C:/MSDELog.log

The install completed and the logfile indicated everything was successful.  I started the MSSQL$CPAPM service and tried to connect using Enterprise Manager from my computer, but it wouldn't establish a connection.

I installed Enterprise Manager on the server running MSDE and was able to connect to the instance by typing the name in manually in the register new server wizard.

I opened the properties of the server in EM, went to network configuration and enabled named pipes and tcp/ip.  I then restarted the service and verified I could still connect using EM from the local server.

I tried connecting using EM from a remote computer and it still wouldn't connect.

I installed Wireshark on the server running MSDE and tried to connect using EM from a remote computer.  I saw traffic coming in on tcp/1433 but didn't see anything going back.

I tried registering the server in EM from a remote computer using intentionally invalid login info to see if it would at least tell me the login was invalid, but it just sits there and eventually times out with "SQL server does not exist or access denied".

I tried telnetting to port 1433 on the MSDE server but couldn't establish a connection.  Then on the MSDE server, I ran "netstat -o" and it doesn't even list any process listening on port 1433, so for some reason even though I've enabled tcp/ip in EM, the instance isn't actually listening.
0
Brian PringleSystems Analyst II, SCM, ERPCommented:
Do you have a firewall running on either of the servers?
0
FWestonAuthor Commented:
There are no firewalls running and both servers are on the same subnet.
0
Brian PringleSystems Analyst II, SCM, ERPCommented:
FWeston,

Sorry, but I am at a loss as to why you cannot access it.
0
Steve BinkCommented:
>>> 2009-05-20 22:08:31.61 spid3     SQL Server started in single user mode. Updates allowed to system catalogs.

Are you using (or have you not disabled) the SQL Server Agent?  If your db is starting in single-user mode, the agent will take up the single connection allowed, thus blocking any of your attempts.

0
FWestonAuthor Commented:
The original server I installed MSDE on did have the SQL Agent installed, but the new virtual machine I created to get a clean test environment does not.

I've come back to this after a few days and noticed that I can now telnet to port 1433 on the MSDE server from the server itself and from a remote server.  However, I still can only connect using Enterprise Manager from the local server, when I try to connect from a remote server, it tells me "SQL Server does not exist or access denied".  I've tried disconnecting everything, restarting the MSDE service, and then trying to connect from a remote server (thinking perhaps an existing connection was interfering with the connection), but still no dice.
0
FWestonAuthor Commented:
Gave up on this and did a physical to virtual migration of the machine this was intended to replace.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.