Check the SQL server Client Network Utility to see if it is configured corerctly on your development machine.
Main Topics
Browse All TopicsI am having some connectivity issues with a new install of MSDE Service Release A. The Server has all updates from Microsoft as well as MDAC 2.8.
First I installed a named Instance of MSDE (Instance1). After installing and rebooting the server I attempted to register the instance using Enterprise Manager on my development workstation. I received the error message "SQL Server does not exist or access denied".
Also after rebooting the Server I did not have a green arrow inside the White circle of the Server Manager app running in the sys tray. If I opened Server Manager the named instance did not appear in the drop-down box. If I manually typed in the \\servername\instancename,
After several attempts to comminucate with the named instance of SQL Server on the Server, I installed a default instance of SQL Server.
Now when the server is rebooted Server Manager does display the default instance running, but still does not show the named instance in the drop-down box (I have to type it in manually).
I still can not register either the named or default instance on my workstation using Enterprise Manager. I also tried to create an ODBC connection to both the default and named instance to no avail.
However ODBC connections on the Server will commincuate with both instances (named and default).
I have seen several posts on the web refering to Server Utilities and Client Utilities but with very little information on how to use these tools. If these tools are needed to resolve the issue please include information (or link to information) on how to use them.
thanks,
matchbx.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
PROBLEM SOLVED:
adwiseman you were close.... I had to enable protocols on the Server not my development machine. As it turned out the Network Admin's who set the Server up did not make sure it was logging into the domain. Instead I was logging in to the local machine. I am assuming that since I installed MSDE being logged in this way no protocols were enable by default. Once I enabled the protocols and logged into the domain everything worked....
P.S To enable protocols on a MSDE installation navigate to "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\svrne
Business Accounts
Answer for Membership
by: adwisemanPosted on 2004-02-09 at 11:46:17ID: 10313571
the problem might be stemmin from the port that this named instance is running on. The standard SQL server port is researved for the "localhost" instance, or the instance that shares it's name with the machine name. When other instances are added, they must utalize alternative ports and the connecting machine must know to look for these ports. Let me dig for a sec...