I have a named instance of MSDE that works fine on Win2K, when i install MSDE with the same script on xp pro i cannot connect to it using ODBC or any of the third party MSDE administration programs.
Load the latest version of mdac.
Check the sql server service is running.
======================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
I have loaded the latest mdac and my instance mssql$wwagmsde is running in the services section.
If I look at the computer name it says w98bh6, but it belongs to a domain and the full computer name is w98bh6.mydomian.net. What server name do I use when referencing the named instance of msde, in this case, wwagmsde. I've tried every combination of servername\instancename that i can think of.
Could the problem be that I do not have a default instance of msde?
Do you have xp sp2 installed? Try turning off the firewall.
Not having a default instance shouldn't make any difference as they are independent.
======================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Tried the w98bh6\wwagmsde but that did not work. I only have sp1 installed and the firewall is turned off. You are talking about the firewall you get to from within the network connections, correct?
I actuall have two laptops and I cannot get msde to work on either. The one dual boots to win2k and that works fine.
Make sure you are using the version of MSDE with SP3 installed. I beleive that it is called MSDE 2000 (a). I beleive that the origional MSDE will not be able to listed for network connections on Windows XP just like Windows 2003 server unless SP3 is applied.
Denny
--Anything is possible. All it takes is a little research. (Me)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.