Troubleshoot

This seciton is for CRM Together staff to help troubleshoot product installs

1. Client toolbar only half lights up and Outlook when starting always asks to reconnect to CRM.

Check the Server error log. If you see 500 errors there is a chance that the server request (which is made within the iis process) is not allowed and so is returning 500 errors.

To resolve this open the web.config file and set the CRMCodedPath setting to be something like "http://servername/CRM/". (Note: you may need to add this setting)

For example

   <add key="CRMCodedPath" value="http://localhost/crm/"/>

This can happen to any application written in Titan so this applies to all products.

2. NT Authenication Error

Depending on the IIS setup you may need to add in a windows users details to the web.config file. This usually occurs when IIS requires authentication.

Set the following values to be a relevenat user. It is best to ensure that the users password does not expire.

   <add key="CRMNetworkUser" value=""/>
   <add key="CRMNetworkUserPassword" value=""/>
   <add key="CRMNetworkDomain" value=""/>

(Note: you may need to add these settings)

3. Fiddler is a great tool for debugging HTTP requests.

One thing to remember is..

Important: Regardless of other settings, .NET will always bypass the Fiddler proxy for URLs containing localhost. So, rather than using localhost, change your code to refer to the machine name. For instance:

   Does not show in Fiddler: http://localhost/X509SignCodeService/X509SigningService.asmx

   Shows in Fiddler: http://mymachine/X509SignCodeService/X509SigningService.asmx

4. Parameter name cannot be zero

This is an error on the Accelerator license. Something has changed or broken the license. Should be fixed in an upcoming release (after Jan 2012)

5. 500.21 (pagehandlerfactory integrated has a Bad Module)

http://blogs.microsoft.co.il/blogs/gadib/archive/2010/10/26/iis-error-handler-pagehandlerfactory-integrated-has-a-bad-module-managedpipelinehandler-in-its-moudle-list.aspx

it seems .net 4.0 might not be installed .

see also

http://www.compdigitec.com/labs/2010/07/12/solving-handler-pagehandlerfactory-integrated-has-a-bad-module-managedpipelinehandler-in-asp-net-4-0/