Freitag, 11. Mai 2012

Fixed it! CRM 2011 404 Error Loading Web Resources

After installing Microsoft Dynamics CRM 2011 at a customer site today we get the follwoing issue. The CRM appeared to complete successfully, and if you didn’t look too close, the application seemed to be working fine.
But once we started to configure the queues, we noticed that there were form scripting errors all over the place. We usd fiddler to get more details on this issue.

As it turns out, the CRM was unable to load any of the Web Resources. 

Resolution 1 – URL Re-Write Rules Missing
In the CRM’s web.config (please make a backup copy of this file before working on it), there should be a <rewrite> section. If it is missing or doesn’t look like the XML below, then try updating it:
<rule name="ClientGlobalContextRule" stopProcessing="true">
<match url="/?([0-9a-zA-Z][^/]*)?/?((?:%7b|\{)[^/]*(?:%7d|\}))?/?(WebResources|Handlers)/ClientGlobalContext.js.aspx" />
<action type="Rewrite" url="/{R:1}/_Common/ClientGlobalContext.js.aspx" />
<rule name="WebResourcesRule" stopProcessing="true">
<match url="/?([0-9a-zA-Z][^/]*)?/?((?:%7b|\{)[^/]*(?:%7d|\}))?/?webresources/([^\\?]+)" />
<action type="Rewrite" url="/{R:1}/Handlers/WebResource.ashx?name={R:3}" />
<rule name="FederationMetadataRule" stopProcessing="true">
<match url="FederationMetadata/2007-06/FederationMetadata.xml" />
<action type="Rewrite" url="/Handlers/FederationMetadata.ashx" />

Note that if your <rewrite> section is missing altogether, then you should insert the snippet above between this:

and this:

After updating the web.config, you should do an IISRESET or reboot the server.
Resolution 2 – URL Re-Write Module is Corrupt
In our case, the <rewrite> section was ok, but it turned out that the IIS URL Re-Write Module was corrupt.

Open up Control Panel—>Programs. Select the Microsoft URL Rewrite Module from the list, and click the ‘Repair’ button. Or go ahead uninstall teh 1.1 URL Rewrite Module and install the 2.0 Version direcly. Will be required for CRM 2011 ADFS / IFD Deployments anyway.

IISRESET or reboot the server.

Fixed andcustomer happy!

Twitter Delicious Facebook Digg Stumbleupon Favorites More

Design by Free WordPress Themes | Bloggerized by Lasantha - Premium Blogger Themes | Free Samples By Mail