VS.Net 2005 on Win XP SP2
I'm trying to add a web reference to an external SOAP application written in
RemObjects, but when I attempt to add the reference I get an error message
saying "The proxy settings on this computer are not configured correctly for
web discovery. Press F1 for more information". I am not using a proxy server
or behind a firewall. Other people are able to access the service (from
tools other than VS.Net), but I am not. However, I was able to access it
briefly last week, but now cannot again. I am able to create a web reference
to some other services, such as this:
https://adwords.google.com/api/adwords/v2/CampaignService?wsdl
http://lottoexchange.net/LottoDrawings.php?wsdl
http://www.claudehussenet.com/ws/services/Anagram.wsdl
http://www.dataaccess.com/webservicesserver/conversions.wso?WSDL
The one I'm trying to connect to is in this format:
http://myservice.mydomain.com/project/something.dll/soap
One of the common remedies touted for this problem is to uncomment this line
in machine.config:
<!--<add verb="*" path="*.vsdisco"
type="System.Web.Services.Discovery.DiscoveryRequestHandler,
System.Web.Services, Version=1.0.3300.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a" validate="false"/>-->
However, I do not have that line. If I were to add it, under what section
would it go? Since I am able to add a reference to some sites, and
occasionally to the target site, I presume this is not the issue.
*UPDATE:*
This would appear to be related to my ISP. If I put the web service address
in my browser bar I get "Page cannot be displayed", but when my friend who
has a different ISP does it, he sees the XML. I moved to his place and am
able to access it from here. The odd thing, again, is that I ~was~ able to
access it last week with the old ISP. My settings (as far as I can tell) are
the same. The old ISP denies that they are using a proxy server. Also, I was
able to access other web services even when I couldn't access the desired
one.
Any ideas? TIA.
[I initially posted this in ms.public.vsnet.general before I found this
group. Sorry for the cross-post]
Steven Cheng[MSFT] - 28 Apr 2006 03:43 GMT
Hi Monty,
Welcome to the MSDN newsgroup.
As for the VS IDE add webreference, it will just request the WSDL document
through http (if its a remote WSDL document over http), and then generate
the proxy code according to the downloaded WSDL document. As for your
scenario, you can not visit the WSDL document event through web browser, I
think this should be a internet connectivity issue. Also, you can try using
the command line tool (wsdl.exe) to create the webservice proxy externally,
and wsdl.exe tool support specify a web proxy for sending the http request
to the remote WSDL document.
#Web Services Description Language Tool (Wsdl.exe)
http://msdn.microsoft.com/library/en-us/cptools/html/cpgrfwebservicesdescrip
tionlanguagetoolwsdlexe.asp?frame=true
In addition, for generating webservice proxy, we can also first download
the WSDL document onto local disk, and Add webreference against the local
WSDL document in VS IDE. However, at runtime, we still need to connect to
the actual remote service. So I would suggest you change to use another
web proxy which can correctly connect to the remote service.
Regards,
Steven Cheng
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Signature
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Monty - 28 Apr 2006 14:29 GMT
Hi Steven,
Thanks for your reply. It would appear to be related to my ISP. When I try
it with Comcast, I get the error described above. When I try it with
BellSouth, it works fine. Comcast support flatly denies there is a proxy
server involved. The odd thing, of course, is that I am able to add a web
reference to some (like those listed previously), but not others. Are there
any other possibilities or factors that might cause this behavior?
Thanks again.
Steven Cheng[MSFT] - 01 May 2006 11:19 GMT
Thanks for your response Monty,
So currently the VS IDE behaves the same as the IE browser , yes? If so, I
think you can first try testing in IE first and then try making it work by
configure the web proxy used in IDE. And based on my understanding, VS IDE
will share the proxy setting in IE when we use the document explorer in VS
IDE to visit any external web resources.
Regards,
Steven Cheng
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Signature
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Carl Behrens - 24 Nov 2006 09:17 GMT
Hi
If you use an automatic config script for your proxy settings VS.net
runs into problems. You have to physically specify the proxy url and
port in your connection settings.
VS.net will not pick up an auto script