MSDE 2000 and VS.NET 2003

Sorry about having to send this again but I did not get an 
answer from MS within two days as I am a subscriber!

I have MSDE 2000 set up with the default instance on my 
Win 2000 workstation system along with VS.NET 2003 EA. 
When I try to see the servers with the Server Explorer, I 
get an error:

The type initializer for "System.Net.Dns" threw an 
exception.

The type initializer for "System.Net.Sockets.Socket" threw 
an exception.

I have another similar setup on an XP Pro machine and it 
has no problem and can see the MSDE 2000 on the Win2K 
system also. I have done a repair or reinstall of MSDE 
2000 and VS.NET 2003 EA to no avail. Does anyone know what 
my problem might be?

Ray Stevens

Hi Ray,

Thanks for posting. In fact I replied your previous post last Friday. The 
following was my reply:

Can you connect to the MSDE with code? I mean that we write some code to 
test the connection and bypass the server explorer here.

We have encountered a very similar issue before. It was caused by that too 
many protocols were bound and was resolved by the following article:

BUG: "The Operation Has Timed-Out." Error Message May Occur When You Add a 
Web Service Reference
 http://www.**--****.com/ ;en-us;815209

Please have a check and see whether this applies to your situation. I hope 
the information is useful to you.

Regards,

Felix Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Hi Felix,

I didn't reply before because you are not aswering my 
question. What causes the error so that I can fix it? 
Since you replied, no one that has an answer will reply 
now. None of your suggestions pertain to my problem. Yes, 
I can connect with code but that leaves me with the same 
problem: I can't look at the servers and their databases 
not to mention something is still broken! I'm sorry for 
being so terse but I am very upset by the stupid error 
message from the ide which makes no sense since other 
programs that use sokets seem to be working. I have since 
found out that other people are having the same problem 
and no one at MS seems to know that there is anything 
wrong.

Ray Stevens

Hi Ray,

I am so sorry that you do not need my help. I was trying to answer your 
question. The issue I mentioned is a bug on Microsoft Web Services included 
with the .NET Framework 1.1 only. It does not affect other applications. 
The solution is also given in the KB article. Please have a check.

I asked you to try connecting MSDE using code, because I would like to 
figure out whether the issue is on MSDE or VS.Net Server Explorer. Usually 
it is not possible for me to deliver a definite answer without any 
troubleshooting process. We only promise that "MSDN Subscribers can receive 
responses in 2 business days". We can never promise that we are able to 
deliver a definite answer or solution within two days. For detailed 
information, you may refer to the following site:

 http://www.**--****.com/ 

I hope you can understand my concerns here. Satisfied customers are our 
first priority. If you think it is appropriate, you may re-post your 
question here and I will not answer it this time.

Regards,

Felix Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Hello Ray,

As I understand the issue correctly, you are having problems to connect to 
MSDE2K default instance on Win2K machine having VS.NET2003 installed 
on it.

Please follow the steps below and check if you are able to connect,

- Check in Services to verify the SQL Server is running
- In the Server Explorer, right click on the 'data connection' and select 
'add new connection'
- You will see, the Data Link Properties Window. In the Provider tab , make 
sure that you have OLE DB for SQL Server selected.
- In the Connection Tab, type the name of the MSDE (machine name)
- Use Windows Authentication or use Username/password (if Mixed mode is 
Enabled for MSDE)
- If you still get the Error, please carefully go over the instruction in 
the following article,

HOW TO: Connect to Microsoft Desktop Engine
 http://www.**--****.com/ ;en-us;319930

The above article, describes diff reasons for msde connection problems and 
does have "connection verification and troubeshooting" steps which would be 
helpful 
in your case.

Please let us know if you need any further assistance on this issue.

Thanks for using MSDN Managed Newsgroup.

Vikrant Dalwale 

Microsoft SQL Server Support Professional


Microsoft  highly recommends to all of our customers that they visit the 
 http://www.**--****.com/ 
steps listed to improve your computer security."
This posting is provided "AS IS" with no warranties, and confers no rights. 

 

--------------------
< XXXX@XXXXX.COM >