posted on Wednesday, October 26, 2005 6:59 PM
by
BayerWhite
The request failed with HTTP status 405: Method Not Allowed
Calling my web service like a do everyday fails with, “The request failed with HTTP status 405: Method Not Allowed.”
SOLUTION :
Check that our IIS Extensions for .wsdl have not been removed from your server! Read on if you want to hear about my experience.
My Project Server WorkFlow application was having some problems today, accessing the PDS WebService it uses as Project Server’s recommended API. I thought it might be useful to post what I found because it has happened to me numerous times and I keep forgetting!
There was some work done on our development server today and I was not made aware which is no big deal because it is development right? Well when I am trying to develop, I need to know so I do not work all day trying to figure out what I did wrong with my code. I call our Infostructure group in another state and ask if any changes have taken place and of course some changes have been made. Once we agreed that any database maintenance is not the issue we focus on what might have changed to IIS since the error is IIS based. Once I had heard that a tool was used to change the sites extensions I knew we had a contender.
Quick instructions :
- Open IIS
- Right click on your site and select properties
- Select the ‘Home Directory’ Tab
- On the bottom right, click the ‘Configuration’ button
- Click the add button
- Execute path for me was "C:\Program Files\Common Files\MSSOAP\BINARIES\SOAPIS30.DLL" but you can browse
- Extension is “.WSDL”
- Limit To "Get,Post"
- Check “Script Engine” and “Verify That File Exists”
- Click “OK” and it should work!