Installing MSDE 2000 on Server with SQL 2005 Express

Can anybody help?

I have a Windows XP and 2003 server; we have installed SQL 2005 Express on it but have an application that installs MSDE 2000 to connect to an application. After the MSDE 2000 is installed we can no longer see the instance across the network. If we uninstall the SQL 2005 express version we can see the Instance in MSDE 2000.

Is there any compatibility issue with install MSDE 2000 after SQL 2005 has been installed.

Many Thanks in advance

David

In general, this should work. There are specific limitations, which I think are well spelled out in BOL. Here's a copy and paste; hopefully this will describe your issue:

In SQL Server 2000, the identification of the server connection endpoints was performed by the SQL Server service. SQL Server 2005 replaces that function with the SQL Server Browser service. If you install SQL Server on a computer that is also running SQL Server 2000 or MSDE, you must ensure that SQL Server 2000 or MSDE is upgraded to Service Pack 3 (SP3) or later. Versions prior to SP3 do not properly share port 1434 and may not make your SQL Server instances available to requesting client applications. Although you can change the services startup order so that the SQL Server Browser service starts before SQL Server 2000 or MSDE, the recommended resolution is to update all older versions of SQL Server to the latest service pack.

When an instance of SQL Server 2000 is installed on the computer, if the SQL Server Browser is not running, the SQL Server 2000 listener service starts. If SQL Server Browser starts after the listener service, it waits 5 seconds for SQL Server 2000 to give up port 1434. If that does not occur, SQL Server Browser fails to start. To resolve this problem with versions of SQL Server 2000 prior to service pack 3, stop SQL Server 2000, start SQL Server Browser, then restart SQL Server 2000. The SQL Server 2000 listener service continues to attempt to start on port 1434, so the SQL Server 2000 instance should be upgraded to service pack 3 as soon as possible.

SQL Server 7.0 had no similar capabilities and has no conflicts with SQL Server Browser.