Let me introduce Steven Vlaanderen Oldenzeel, a consultant that works for Microsoft in The Netherlands. I have asked if he would write a blog and he was more than happy to do so. See the result below.
405 Method not allowed - The server might be down
This is the message I received during an Outlook client installation. To ensure it wasn't a server problem I performed some basic checks on the server. Like IP Address checking, Traceroutes, Installing ServicePacks and Rollup1, starting a webclient and more of those possible solutions. On the server everything worked perfectly, so I assumed that the problem must be somewhere on the client computer.
I got the error on more computers but the infrastructure at the clientside is loaded with accessrights and grouppolicies. I thought that those rights and policies were causing the same error on more computers. So I concentrated on differences between the infrastructure on the clientside and a standard installation. There were a lot of differences but they were not causing the problem.
A few day's later I installed the Data Migration Framework on the server because I had to migrate some data as well. And I got the same error on the server. So now the problem occured on the server as well. That was a change, because it had nothing to do with the infrastructure!
In the properties of the website MSCRMServices the property of the Server Response File wasn't there. So I had to add this property manually:
- On the Microsoft Dynamics CRM server, click Start, click Run, type inetmgr , and then click OK.
- In the Microsoft Internet Information Services (IIS) Manager dialog box, expand the server, expand Web Sites, expand Microsoft CRM v3.0, right-click MSCRMServices, and then click Properties.
- In the MSCRMServices Properties dialog box, click Configuration on the Virtual Directory tab.
- In the Application Configuration dialog box, click the Mapping tab, and then click Add.
- In the Add/Edit Application Extension Mapping dialog box, type the following in the Executable box:
C:\Program Files\Microsoft CRM\Server\bin\CrmIsapi.dll
- In the Extension box, type .srf . In the Limit to box, type GET, POST, HEAD .
- Click to select the Script engine check box and the Verify that file exists check box, and then click OK.
- Click OK two times to confirm the changes.
- Restart the Microsoft Dynamics CRM server, and then run the Rule Deployment Wizard.
Everything worked fine after these changes!
Steven Vlaanderen Oldenzeel - Microsoft Netherlands