MSDE on Win 2003 - unable to connect
-
Hello, all. I'm beating my head against this one. I have an MSDE SP3 installed on a Win 2003 server. The protocols are enabled (checked using svrnetcn.exe) and both Named Pipes and TCP/IP are enabled. The user is running a setup routine on the server via remote desktop and it keeps failing with the unable to connect message.
The MSDE is in SQL Mixed Mode and we are able to connect via OSQL using the sa password.I've run into this once or twice when I have been totally unable to diagnose the problem and the user finally chose another server and I really want to figure out what's happening here. Most of the time I don't have any problems with installations on Win 2003 servers but there are exceptions.
Any ideas?
Thanks!
Don
-
This was removed by the editor as SPAM
-
What is the exact command you were running to install service pack?
As far as i understand, it is failing during "configuing server".
If you have verbose log output with you, please paste in your next post.
Also, there should be a file called cnfgsvr.out. please paste the content of that file as well.
-
Sorry for the delayed reply. I was not talking about installing a service pack, I was talking about installing databases via an InstallShield front end. The front end invokes OSQL to create the databases and database objects. That is the point of failure. As far as I can tell, when OSQL attempts to log on it either can't find the default instance of SQL or the logon itself is failing.
I did find a posting from someone else where they can't log on to a named instance of SQL and it led me to a couple of MS knowledge base articles that might provide the answer. Yesterday I went to the client site and found that there was a named instance in addition to the default instance of SQL running on the server. I stopped the named instance and, voila, the installer was able to connect. I suspect that the named instance was interfering in some obscure way. I plan to follow up based on what I read in the MS articles.
Thanks for the response. If I find an answer I'll post it.
Don
-
Hi there,
I have a somehwat similar problem, and decided to reply to your post after searching the forum and finding it.
I also have MSDE installed on Windows Server 2003, with TCP/IP and Named Pipes, and with Mixed Mode authentication. The server has not been set up as a domain controller. I can log in using osql and the sa user name, but I can't connect to the SQL Server from a client computer on the network.
There is only the default instance installed on the server, no named instance. What could be the problem?
Any ideas welcome, thanks
Daniel
-
"I can log in using osql and the sa user name, but I can't connect to the SQL Server from a client computer on the network.
There is only the default instance installed on the server, no named instance. What could be the problem?"
Hi, Daniel. I apologize for taking so long. I'm WAY behind on my SQL Server Central reading.
I assume you checked all the protocols using the svrnetcn.exe utility. Have you checked the client workstation using the cliconfg.exe utility? Occasionally I have seen problems of this nature where the netwdblib.dll was not referenced properly on the DB-Library Options tab.
Don
-
Hi Donald,
Sorry for my own late response to the previous suggestion, the installation was in another part of the country. I just got back from there, and I tried the svrnetcn.exe utility, enabled TCP/IP and Named Pipes, and I'm glad to report that it worked!
Thanks a lot for the help!
Daniel
-
Daniel, I'm glad that did the trick. Win 2003 can be a real pain in the neck with SQL installs. The improved security comes with a price.
Don
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply