Add Web Reference Issue

[Guest]

Hi

I've checked the other posts on this topic but haven't been able to resolve it so far
-I have a working web service, that is to say I can view it/run it from a web browse
-From VS.Net I can use the Add Web Reference dialog and add this referenc
-However, from VS.Net 2003 the same localhost URL does not resolve and I get the "The proxy settings on this computer are not configured correctly for web discovery." message in the 'Web Services Found at this URL' box

So far I have
-Messed around with proxy settings to no avai
-Modified the machine.config file for the VSDisco dynamic discover
-Attempted to use WSDL.exe and Disco.exe from the command prompt to manually create a reference

Any thoughts or advice would be greatly appreciated.

 

[bruce barker]

you have to set the proxy setting in the web request with code or in the
web.config, as the web service does not have a profile, and will not pick up
proxy settings entered into internet explorer.

-- bruce (sqlwork.com)

Hi,

I've checked the other posts on this topic but haven't been able to resolve it so far.
-I have a working web service, that is to say I can view it/run it from a web browser
-From VS.Net I can use the Add Web Reference dialog and add this reference
-However, from VS.Net 2003 the same localhost URL does not resolve and I

get the "The proxy settings on this computer are not configured correctly
for web discovery." message in the 'Web Services Found at this URL' box.

 

[Steven Cheng[MSFT]]

Hi,

Thanks for posting in the community!
From your description, you encountered the following error:
"The proxy settings on this computer are not configured correctly for web
discovery." message in the 'Web Services Found at this URL' box when trying
to add a web service as webreferencein a ASP.NET web app? And this works
well in VS.NET?

As for this problem, I'd like to confirm some certain things:
1. Does the problem occurs on every webservice? You may try creating a
simple webservcie and then try to generate the client proxy via both
VS.NET2003 and wsdl.exe to see whether this problem remains.

2. Also, have you tried use a winform application to add the web reference
to see whether the problem remains?

In addtion, since you said that you failed to add the web reference via the
localhost url, are you able to generate the client proxy class via "machine
name" or the physical address ? Also, sometimes the default namespace of
the webservide class may also cause the problem, try specfying a differernt
custom namespace via the WebServiceAttribute as below:

[ WebService(Description="Common Server
Variables",Namespace="http://www.mydomain.com/")]
public class ServerVariables: WebService {
................

Please check out the above items. If you have any new findings or update.
Please feel free to post here.


Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx

 

[Steven Cheng[MSFT]]

Hi Morgan,

Have you got any progress or new findings on this issue? If you need any
assistance, please feel free to post here.


Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx

 

[Guest]

Hi Steven

Thanks for the reply. So far I haven't been able to resolve it. I know it's a common problem based on all the posts I've read

Again, all works well in VS.Net as far as referencing web services. The problem is only in VS.Net 2003
-Yes, this occurs on every web service. Created a simple HelloWorld web service. Opened up another VS.Net 2003 and created a windows app. Tried to set a reference to the previous web service. The service information shows up in the left hand pane but Add Reference is disabled and the message, "The proxy settings on this computer..." shows up

-Same issue regardless of my using the physical address or machine name. I have a unique namespace for the web service

- I ran WSDL.exe from the .Net prompt: Error message as follows
Unhandled Exception: System.TypeInitializationException: The type initializer f
r "System.Net.Sockets.Socket" threw an exception. ---> System.Net.Sockets.Socke
Exception: An operation on a socket could not be performed because the system l
cked sufficient buffer space or because a queue was ful
at System.Net.Sockets.Socket.InitializeSockets(
at System.Net.Sockets.Socket..cctor(
--- End of inner exception stack trace --
at System.Net.Connection.StartConnectionCallback(Object state, Boolean wasSi
nalled

NOTE: If I am working from a seperate machine I am able to set a web reference. This problem only seems to occur if I am setting a reference on the same machine where the web service resides

Thank you for your help so far. Any additional help is greatly apprciated
Sincerely

Morgan

 

[Felix Wang]

Hi Morgan,

I believe the following 2 articles addresses the issue:

BUG: You receive a "The operation has timed-out" error message when you
access a Web service or when you use the IPAddress class
http://support.microsoft.com/?id=815209

FIX: Socket Initialization Does Not Succeed if Your Computer Has More Than
50 Network Bound Protocols
http://support.microsoft.com/?id=826757

To confirm the point, you may try the "enum.exe" mentioned in the article
Q815209. If it does apply to your situation, you may contact our product
support service for the hotfix mentioned in Q826757. It should be free of
charge.

If you refer my name (Felix Wang) when submitting the service request, I
will be happy to work with you in the support case :=)

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.

 

[Guest]

Hi Felix

Thank you for the advice. Unfortunately it did not resolve my issue. I only have one network connection and it has only 4 protocols (Client For MS Networks, File and Printer Sharing for MS Networks, Reliable Multicast Protocol, and Internet Protocol (TCP/IP)

I'm still looking for feedback and advice to resolve this. For now my workaround has been to load up the client application on a seperate machine with VS.Net 2003 installed. Set the web reference from that machine. And finally, copy and paste the client project back on to my development machine. Once there the web reference shows up in the project and I'm able to run both the web service and the client on the same machine to debug

Take Care
Morgan

 

[Felix Wang]

Hi Morgan,

Have you tried the "enum.exe"? Based on my past experience, sometimes there
are more protocols than we expect.

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.

 

[Felix Wang]

Hi Morgan,

The protocols mentioned in the KB article are not the same as the protocols
as we see in the LAN Properties Window. For example, we may have the
following:

MSAFD Tcpip [TCP/IP]
MSAFD Tcpip [UDP/IP]
MSAFD Tcpip [RAW/IP]
RSVP UDP Service Provider
MSAFD NetBIOS
...

I would just like to make sure that your issue is not caused by the problem
mentioned in the KB articles.

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.

 

[Guest]

Thank you Felix

Unfortunately enum.exe did not uncover any additional protocols. For now my work around will suffice. Once I have the reference set I have no problems. I just have to set it using a different machine and then copy the project back over. It's not too bad

Thanks again
Morgan

 

[Guest]

I am having the same problem. I created the web service in one VS2003 project. Then I created a winform project and accessed the service using the Add Web Service/Web Services on Local Machine. It works fine

Then I copied it up to our ISP and tried to reference it and I get the Proxy error. I typed this in and got the error. I also get it as soon as I click on the UDDI Directory or Test Microsoft UDDI Directory.

I'm on a Toshiba laptop with 2 network cards. The ethernet card is currently unplugged. It is set to a fixed IP for my primary client's network. I was connecting using the built in wireless card. I have a firewall but turning it off had no effect. I'm running W2K professional with the latest service packs and I run both Ad-aware and SpyBot S&D scans weekly (I'm a fan of paranoid computing!).

I look forward to a quick resolution

Regards

Ross

 

[Felix Wang]

Hi Morgan,

Thanks for your update. I am sorry to hear that the issue is still not
resolved. To further track it, you may need to submit a service request to
our Product Support Service. We may do some dump analysis on it and see why
the exception happens.

Should you have any further concerns or new findings, please let me know.

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.

 

[Felix Wang]

Hi Morga,

I have one additional suggestion. Have you checked the <defaultProxy>
setting in your .Net 1.1's machine.config?

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.