Could not load all ISAPI filters for site/service. Therefore startup aborted.

You may receive a “Service Unavailable” error when opening CRM in IE. Looking at the eventlog of the CRM server, it seems that Worker Process could not start correctly and show the following entry:

ISAPI Filter ‘C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_filter.dll’ could not be loaded due to a configuration problem. The current configuration only supports loading images built for a AMD64 processor architecture. The data field contains the error number. To learn more about this issue, including how to troubleshooting this kind of processor architecture mismatch error, see http://go.microsoft.com/fwlink/?LinkId=29349.

This occurred on the CRM server for one of our customers after they installed a 32-bit application which also required a website in IIS called SolarWinds-Orion-NPM.
We are not sure if the installer reconfigured the IIS website, or the sysadmin did J

For IIS 6.0, it is not possible to run both 32-bit an 64-bit worker processes.

This is stated here on the MS website: http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/13f991a5-45eb-496c-8618-2179c3753bb0.mspx?mfr=true
On 64-bit Windows, the World Wide Web Publishing service does not support running 32-bit and 64-bit worker processes concurrently on the same server.

Anyway, switching the IIS website back to x64 mode solved our problem.

To do this for IIS6.0, run the following script in a Command Prompt:

// this will disable 32-bit mode on IIS
cscript.exe C:\inetpub\adminscripts\adsutil.vbs set W3SVC/AppPools/Enable32BitAppOnWin64 “false”

// this will register the .NET framework assemblies in 64-bit mode for IIS
C:\Windows\Microsoft.NET\Framework64\v2.0.50727> aspnet_regiis.exe –i        

Your CRMAppPool should now start correctly

 

Action Microsoft.Crm.Config.Client.InstallPstAction failed when configuring CRM for Outlook

I received this error when I was trying to configure the outlook client for CRM 4.0. It seems that the user had first installed the CRM 2011 client and removed this one to install the 4.0 client.

Uninstalling the CRM 2011 client however leaves some 5.0 files on the machine, causing the 4.0 config to crash.

To resolve this issue according to Microsoft KB follow these steps:

1. Navigate to C:\Program Files\Microsoft Dynamics CRM\Client\ConfigWizard directory or C:\Program Files (x86)\Microsoft Dynamics CRM\Client\ConfigWizard directory.

2. Delete the CRMForOutlookInstaller.exe file.

3. Do one of the following options:

• Replace the CRMForOutlookInstaller.exe from the 4.0 client install bits.
  
• Run a repair on the Dynamics CRM 4.0 Client for Microsoft Office Outlook installation.
  

4. Run the Configuration Wizard.

 

Exporting a CSV file from ASP.NET with special characters

When you try to export a CSV file from ASP.NET that contains special characters like é å æ É à you may experience the following:

• Opening the file in Notepad shows the correct characters
  
• Opening the file in Excel, it shows characters like é Ã¥ æ É Ã

This also causes problems when you try to import this file in to CRM using the standard data imports.

To solve this issue you will have to use the correct encoding during the export of the file.

Imagine you have used a StringBuilder to generate the CSV file content.

Response.ContentType = “application/csv”;

Response.Charset = “”;

Response.AddHeader(“Content-Disposition”, “attachment;filename=queue-errors.csv”);

 

Response.ContentEncoding = Encoding.Unicode;

Response.BinaryWrite(Encoding.Unicode.GetPreamble());

 

Response.Write(sb.ToString());

Response.End();