Wrox Home  
Search P2P Archive for: Go

  Return to Index  

asptoday_discuss thread: ws working on localhost but not remotly?


Message #1 by "Chadrick Mahaffey" <chadm@d...> on Tue, 2 Jul 2002 18:51:18
I am just ftping my files over to the remote server. There must be 
something I am suppose to do to the files? I have put these files on the 
server in the root: .aspx - calls the ws function; .asmx - the web 
service; .dll - into the bin directory; .cs - put this over too (not sure 
why)

I'm assumming it has something to do with the proxy not working right 
because of the namespace or something?

Can you help me please...
Message #2 by "Gilles Muys" <gmuys@g...> on Tue, 2 Jul 2002 21:12:26
Have you tried to call the web service manually on your remote server? 
For example: http://www.mydomain.com/mywebservices/myservice.asmx

You should get a page giving you the list of methods supported by your 
web service, and you can manually invoke each of them.

Otherwise, deploying web services is similar to any other .NET 
deployment: XCOPY should do just fine.

You might want to verify that your ASP.NET page calls the web service on 
the remote server, not on your local domain. I believe that the proxy 
should be created with the remote address as well, not from the local one.

Let me know if the above helps. Thanks.

Gilles

> I am just ftping my files over to the remote server. There must be 
s> omething I am suppose to do to the files? I have put these files on 
the 
s> erver in the root: .aspx - calls the ws function; .asmx - the web 
s> ervice; .dll - into the bin directory; .cs - put this over too (not 
sure 
w> hy)

> I'm assumming it has something to do with the proxy not working right 
b> ecause of the namespace or something?

> Can you help me please...
Message #3 by "Chadrick" <chadm@d...> on Tue, 2 Jul 2002 16:16:44 -0400
I have tried to view the web service remotelty. It gives me the list of
web methods. I click on one and it gives me the error 404. My local
machine runs it fine.

What did you mean about the "proxy being created with the remote address
as well"? How do I go about doing this? I think I might have an idea -
so I'll give this a try.

-----Original Message-----
From: Gilles Muys [mailto:gmuys@g...] 
Sent: Tuesday, July 02, 2002 9:12 PM
To: ASPToday Discuss
Subject: [asptoday_discuss] Re: ws working on localhost but not remotly?

Have you tried to call the web service manually on your remote server? 
For example: http://www.mydomain.com/mywebservices/myservice.asmx

You should get a page giving you the list of methods supported by your 
web service, and you can manually invoke each of them.

Otherwise, deploying web services is similar to any other .NET 
deployment: XCOPY should do just fine.

You might want to verify that your ASP.NET page calls the web service on

the remote server, not on your local domain. I believe that the proxy 
should be created with the remote address as well, not from the local
one.

Let me know if the above helps. Thanks.

Gilles

> I am just ftping my files over to the remote server. There must be 
s> omething I am suppose to do to the files? I have put these files on 
the 
s> erver in the root: .aspx - calls the ws function; .asmx - the web 
s> ervice; .dll - into the bin directory; .cs - put this over too (not 
sure 
w> hy)

> I'm assumming it has something to do with the proxy not working right 
b> ecause of the namespace or something?

> Can you help me please...



Message #4 by "Gilles Muys" <gmuys@g...> on Tue, 2 Jul 2002 21:43:21
When you create the proxy, you need to indicate the URL for the web 
service. This URL should be the remote one, not the local one. If you 
create it with the local one, then when you upload to the server, it will 
look from the local host on the server and you probably will end up with 
a different but non-existant virtual directory. That would explain the 
404 error that you get. I have not verified what I just said, but it 
seems to make sense...

> I have tried to view the web service remotelty. It gives me the list of
web methods. I click on one and it gives me the error 404. My local
machine runs it fine.

What did you mean about the "proxy being created with the remote address
as well"? How do I go about doing this? I think I might have an idea -
so I'll give this a try.
Message #5 by "Chadrick" <chadm@d...> on Tue, 2 Jul 2002 16:56:04 -0400
I think I'm half way there. I created the proxy with the remote address
and that did work.

I tested the web service from the browser and the methods work. Now when
I go to my page that is suppose to consume the web service I'm getting
the 404 error on line 8 (I will show the code below)

How does the remote server see the namespace when I ran the compiler on
my local machine?

----------------------error
message----------------------------------------

Line 6:  	{
Line 7:  		AppService ws = new AppService();
Line 8:  		lblValue.Text = ws.GetAppState(txtSetting.Text);
Line 9:  	}
Line 10: </script>
 

Source File:
\\premfs2\sites\premium6\mdejeu\webroot\webservices\learning\appsettings
inf.aspx    Line: 8

---------------------------end
error--------------------------------------
-----------------------------code--------------------------------------

<%@ Page Language="C#" ContentType="text/html"
ResponseEncoding="iso-8859-1" Debug="true" %>
<%@ Import namespace="AppSettings" %>		//the namespace
	
//entered in the csc.
								//how
does remote server
								//see
this namespace?

<script language="C#" runat="server">
void GetSetting(System.Object sender, System.EventArgs e) //my web
method
	{
		AppService ws = new AppService();
		lblValue.Text = ws.GetAppState(txtSetting.Text);
	}
</script>

------------------------------end
code------------------------------------

-----Original Message-----
From: Gilles Muys [mailto:gmuys@g...] 
Sent: Tuesday, July 02, 2002 9:12 PM
To: ASPToday Discuss
Subject: [asptoday_discuss] Re: ws working on localhost but not remotly?

Have you tried to call the web service manually on your remote server? 
For example: http://www.mydomain.com/mywebservices/myservice.asmx

You should get a page giving you the list of methods supported by your 
web service, and you can manually invoke each of them.

Otherwise, deploying web services is similar to any other .NET 
deployment: XCOPY should do just fine.

You might want to verify that your ASP.NET page calls the web service on

the remote server, not on your local domain. I believe that the proxy 
should be created with the remote address as well, not from the local
one.

Let me know if the above helps. Thanks.

Gilles

> I am just ftping my files over to the remote server. There must be 
s> omething I am suppose to do to the files? I have put these files on 
the 
s> erver in the root: .aspx - calls the ws function; .asmx - the web 
s> ervice; .dll - into the bin directory; .cs - put this over too (not 
sure 
w> hy)

> I'm assumming it has something to do with the proxy not working right 
b> ecause of the namespace or something?

> Can you help me please...




  Return to Index