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

Tagged with: ,
Posted in CRM 4

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.

Tagged with: ,
Posted in CRM 4

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();

Posted in .NET

Unable to extract package error when trying to install CRM 2011 outlook client




You may receive an error when you try to install the outlook client for CRM 2011. When double clicking the installer files, it tells us that the package cannot be extracted.

Try entering the extract command manually in a command prompt window like this:
CRM2011-Client-ENU-i386.exe /extract:”c:\temp\”

Your files should now be extracted

Tagged with: , ,
Posted in CRM 2011

CRM Online: not able to login. LOGIN.LIVE.com keeps looping


You can’t log in to Microsoft Dynamics CRM Online. When you try logging in to CRM Online with your Windows Live ID (WLID) the screen goes blank, or partially loads, and then appears to be stuck in a loop of refreshing, reloading, or resetting. After about 5-10 seconds of reloading it shows the error message:

 

Windows Live ID is unavailable from this site for one of the following reasons:

  • This site may be experiencing a problem
  • The site may not be a member of Windows Live ID

 

This issue may be cause by the fact that not all of the web sites used to perform authentication are trusted.  This appears to be an issue with Internet Explorer

 

To solve it in Internet Explorer ( I’m using version 8 )

  • In the top menu click “Tools”
  • Select “Internet Options” from the dropdown menu
  • In the window that opens select the “Security” tab
  • Select the “Trusted Sites” checkmark
  • Click the “Sites” button
  • In the window that opens in the area that says “Add this website to the zone”
  • Close all open windows
  • Close and then open Internet Explorer

 

Tagged with: ,
Posted in CRM 2011, CRM 4

CRM 2011 Beta installation issues (Microsoft Dynamics CRM Reporting Extensions Setup)


We recently installed the CRM 2011 beta on a virtual server where there was already a SQL server installed.
The CRM server was supposed to be installed on a seperate instance so we created an instance called CRM.

Now there is a know issue when installing the Reporting Extensions on a named instance of SQL server.
This is an extract of the CRM 2011 beta readme:

An error occurs while installing Microsoft Dynamics CRM Reporting Extensions pointing to a named instance of SQL Server Reporting Services 2008 R2

An “Error| Check ReportServerValidator : Failure: Unable to validate SQL Server Reporting Services Report Server installation. Please check that it is correctly installed on the local machine.” error occurs when you install Microsoft Dynamics CRM Reporting Extensions pointing to a named instance of SQL Server Reporting Services 2008 R2. To work around this issue, install Microsoft Dynamics CRM Reporting Extensions by using a configuration file with the following tag appropriately defined:

<instancename>CRM</instancename>

After applying this to the install-config.xml of the reporting extensions we still received the error.

The exact message was:

Error installing Reporting Extensions Setup:
—————————
Microsoft Dynamics CRM Reporting Extensions Setup
—————————
Action Microsoft.Crm.Setup.Common.Analyzer+CollectAction failed.

Object reference not set to an instance of an object.
—————————
Retry   Cancel  
—————————

Digging into the installation logfiles I found the following entries:
Instance Name needs to be escaped. Management Exception: Invalid namespace

It was trying to find the instance named RS_MSSQLSERVER, which was the reporting services namespace for the default instance.

Looking arround on the net gave me some problem solutions but none of them fixed the issue.

The following steps may have (partially solved the issue)

  • There was  an “_” in the reporting services web URL (it was set to localhost/reportserver_crm)
  • The mof files of the report server pointed to the RS_<<instance name>> (check this post for more info)
  • the install-config.xml pointed to the wrong instance name (from the beta readme file)

None of the above fixed the problem. This got me looking even further and I tried to check both of the SSRS instances configurations.
It seemed the default instance was not yet configured. After configuring it, the Dynamics CRM Reporting Extensions Setup seemed to install successfully.

I still had one more issue because the reports were not published after the installation. But I think this was a problem with the beta setup.
When I created a new Organization AFTER the extensions were installed, all the reports were published successfully.

Tagged with: ,
Posted in CRM 2011

Plugin Images do not contain the name property for Lookups


When we register a plugin on the Pre-Create step, the Image does not contain the names for lookup controls.

The lookup properties in the image has a null value for the Name.

As a workarround, we always need to do a retrieve request to get the name of the lookup entity.

It would be usefull to always have the name for each lookup when working with plugin images.

Vote here to get it fixed:
https://connect.microsoft.com/dynamicssuggestions/feedback/details/585414/plugin-images-do-not-containt-the-name-property

Tagged with: ,
Posted in CRM 4
%d bloggers like this: