Valdar729
asked on
405 method not allowed when calling ASP web service
I have an application that runs fine on my development machine locally that consists of a web service and a client application calling the web service.
When I move the client portion to another machine and use my dev machine (Windows XP Pro SP2, IIS 5.1) for the web service I get an error on the client app stating
"405 method not allowed" when attempting to call the web service.
I can pull up the web service web page and test it fine from the client machine, but when I run the client application I get this error.
I've searched for many fixes and already added POST and GET configs to the web.config file. Also, I've re-installed ASP .Net on my dev machine through the aspnet_regiis -i. My persmission are set to allow anonymous access and scripts are allowed to run. I'm not sure what other security setting I can change.
Thanks for any help.
When I move the client portion to another machine and use my dev machine (Windows XP Pro SP2, IIS 5.1) for the web service I get an error on the client app stating
"405 method not allowed" when attempting to call the web service.
I can pull up the web service web page and test it fine from the client machine, but when I run the client application I get this error.
I've searched for many fixes and already added POST and GET configs to the web.config file. Also, I've re-installed ASP .Net on my dev machine through the aspnet_regiis -i. My persmission are set to allow anonymous access and scripts are allowed to run. I'm not sure what other security setting I can change.
Thanks for any help.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'm an idiot, I had the client app referencing the web app correctly, but there is a class that I didn't have set correctly to reference the web service. Thanks for the help.
ASKER
I'm not sure where I would find that.
The web services are referenced through my dev machines name so when deploying the client it should be calling it by name and not ip or loopback. I can ping my dev machine and run it through the test page fine, using the machine name.
Also, I would get a 404 error if I didn't have it set correctly, right?