Problems getting web service applications to work in IIS

[gdodd10]

Greetings.
I have an application that I am building in C#. Basically I have 5 web

service applicationsthat run with a client and a socket adapter.
Everything connects and works fine when I run the web service
applications in the cassini web server form. However, when I try to
use them running in IIS, they no longer connect with my client and
socket adapter. Is there a known problem with IIS and web service
applications. Do I need to keep my web services as the standard web
service, or does converting them to web service applications not have
anything to do with this?

Thanks

 

[Marc Gravell]

Not a lot of info here...

The first things to check is whether you are hitting the correct end-point,
and if that end-point is alive; in IIS, navigate to your asmx, right click
and select browse. This should should display the contract information about
the web-service; if it returns a 404, a "Service Unavailable", an ASP.Net
error, access denied etc, then that's the problem.

Is an IIS application set at the correct level? For IIS6 this would be a cog
icon at the same level as web.config. Is it running in the correct identity
(app-pool identity in IIS6).

That done, look at the url in the top of IE; allowing for the localhost ->
someserver substitution, is this the end-point that your client is trying to
connect to? If not, fix it.

Go to the client - can that machine (via IE) reach the end-point you were
just looking at? There might be firewall or other security blocks.

Any of that help?

Other notes; if you code is going to run under IIS, then I strongly advise
developing it under IIS; this gives you the least suprises later on. If you
want hints on setting this up (assuming IIS is installed on the development
machine) then let me know.

Marc