January 7, 2005 at 11:33 am
Alright, I have MSDE setup in many places in my environment. Until recently, it has always been MSDE 2000 on Win2K Server. For whatever reason, I have always (and can still) connect to these MSDE instances using both Analyzer and SEM, even though I have been told I shouldn't be able to.
Now, I have a new Win2003 server with MSDE 2000 and BizTalk 2004 and I can NOT manage MSDE using Analzyer or SEM. In fact, I can only connect to MSDE using OSQL directly on the server itself.
Needless to say, I am a fish out of water. Does anyone know why I cannot connect to this server with a management tool. Does anyone have any suggestions on how to manage this server?
I have some SQL / BizTalk issues in the log and it is driving me nuts not to be able to see my DB's, configs, etc.
Thanks in advance!
Ryan Hunt
January 10, 2005 at 8:00 am
This was removed by the editor as SPAM
January 10, 2005 at 9:52 am
Did you install msde with SP3A on the new server? If so, did you set DISABLENETWORKPROTOCOLS=0?
If you did not set it to 0 (for sp3a) it defaults to 1 then the net-libraries are disabled.
January 10, 2005 at 1:55 pm
No, the MSDE instance was installed with default params. Is there a way to set this parameter after install?
January 10, 2005 at 2:14 pm
I found the answer. C:\Program Files\Microsoft SQL Server\80\Tools\Binn\SVRNETCN.exe
This is the server network utilities. I had to enable Named Pipes and TCP/IP - now I can connect to it.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply