Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > ASP .Net > ASP .Net Web Services > WSDL Proxy class cannot connect to Web Service

Reply
Thread Tools

WSDL Proxy class cannot connect to Web Service

 
 
Chris Wallis
Guest
Posts: n/a
 
      10-14-2003
We are using a third party Document Management System
which has a number of web services. I have created c#
proxy classes using WSDL.exe for each of the wsdl files
provided, and calls to the web service work fine when I
run them on my XP development machine.

However, when I publish the project to one of our
Production servers each call to a web service results in
the error

"The underlying connection was closed. The remote name
could not be resolved".

This looks similar to the problem fixed by Knowledgebase
article 819450 but I do not see how to fix it when I am
not using a web service as a Web Reference but rather via
the proxy class created by wsdl.exe.

Of course this might be a red herring, since I really
cannot understand why it works from my XP box but not the
server?

Note: I had to copy the wsdl files to my XP box before
running wsdl.exe because there was security on the web
service web site which I was unable to get around using
wsdl.exe. I assume this will make no difference to the
proxy c# class created.
 
Reply With Quote
 
 
 
 
Dino Chiesa [Microsoft]
Guest
Posts: n/a
 
      10-16-2003
can you resolve the name of the target server, fom the "production server"
?


"Chris Wallis" <chris@nospam> wrote in message
news:0a3e01c3927e$fc9e8e50$(E-Mail Removed)...
> We are using a third party Document Management System
> which has a number of web services. I have created c#
> proxy classes using WSDL.exe for each of the wsdl files
> provided, and calls to the web service work fine when I
> run them on my XP development machine.
>
> However, when I publish the project to one of our
> Production servers each call to a web service results in
> the error
>
> "The underlying connection was closed. The remote name
> could not be resolved".
>
> This looks similar to the problem fixed by Knowledgebase
> article 819450 but I do not see how to fix it when I am
> not using a web service as a Web Reference but rather via
> the proxy class created by wsdl.exe.
>
> Of course this might be a red herring, since I really
> cannot understand why it works from my XP box but not the
> server?
>
> Note: I had to copy the wsdl files to my XP box before
> running wsdl.exe because there was security on the web
> service web site which I was unable to get around using
> wsdl.exe. I assume this will make no difference to the
> proxy c# class created.



 
Reply With Quote
 
 
 
 
Chris Wallis
Guest
Posts: n/a
 
      10-21-2003
Web services are actually a red herring here because as
part of my investigations I build a text page which
literally created an XmlDocument and used the Load method
pointed to a htm file on the Server.

Again this worked fine from my XP box but failed with
the "The underlying connection was closed. The remote name
could not be resolved" error when the code is installed on
a Production Web server.

Interestingly, when I use the Production Server of the
Document Management System rather than the Dev box, both
the web services and the XmlDocument.Load work from both
the XP box and the Production Web Server.

In Summary, I can reach the Production Document Management
Server from both my XP box and our Production Web Server,
but I can only reach the Development Document Management
Server from my XP box.

For now I am having to continue development on the
Production Document Management Server which is far from
ideal, but I really have no idea why I cannot connect to
the Development Document Management Server from our
Production Web Servers.

Any other ideas would be most welcome.

>-----Original Message-----
>can you resolve the name of the target server, fom

the "production server"
>?
>
>
>"Chris Wallis" <chris@nospam> wrote in message
>news:0a3e01c3927e$fc9e8e50$(E-Mail Removed)...
>> We are using a third party Document Management System
>> which has a number of web services. I have created c#
>> proxy classes using WSDL.exe for each of the wsdl files
>> provided, and calls to the web service work fine when I
>> run them on my XP development machine.
>>
>> However, when I publish the project to one of our
>> Production servers each call to a web service results in
>> the error
>>
>> "The underlying connection was closed. The remote name
>> could not be resolved".
>>
>> This looks similar to the problem fixed by Knowledgebase
>> article 819450 but I do not see how to fix it when I am
>> not using a web service as a Web Reference but rather

via
>> the proxy class created by wsdl.exe.
>>
>> Of course this might be a red herring, since I really
>> cannot understand why it works from my XP box but not

the
>> server?
>>
>> Note: I had to copy the wsdl files to my XP box before
>> running wsdl.exe because there was security on the web
>> service web site which I was unable to get around using
>> wsdl.exe. I assume this will make no difference to the
>> proxy c# class created.

>
>
>.
>

 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Creating a Web Service (Service, not Client) from WSDL Bert Leu ASP .Net 1 11-23-2007 08:29 PM
Creating a Web Service (Service, not Client) from WSDL Bert Leu ASP .Net Web Services 1 11-23-2007 07:59 PM
Web Service Client Cannot Connect to Web Service From Some Machine EagleRed@HighFlyingBirds.com ASP .Net Web Services 0 10-10-2005 11:15 PM
WSDL file produces useless class when imported with WSDL.exe RH ASP .Net Web Services 1 05-27-2004 09:40 PM
PLEASE HELP: incompatible wsdl proxy class with the .NET compact framework amine ASP .Net 0 10-19-2003 07:53 PM



Advertisments