Problem Fixes for Plugins

KB 950542 : Synchronous plug-ins do not respond to the events that are triggered in Microsoft Dynamics CRM 4.0

When you deploy synchronous plug-ins in a Microsoft Dynamics CRM 4.0 server that is configured to use a host header, the synchronous plug-ins do not respond to the events that are triggered in Microsoft Dynamics CRM 4.0.

KB 948746 : Error message when you execute a plug-in on a nondefault organization instance in Microsoft Dynamics CRM 4.0: "The request failed with HTTP status 401 unauthorized".

The default behavior for ICrmService object is that the organization name is the organization friendly name without spaces.  It is not so in many cases. There is a fix for that. The KB also instructs how to change the friendly name if this is the choice.

Logging Usage and Displaying Summary

Blog entry named CRM Usage Reporting Unleashed telling how to set IIS log to a database table and create reports on that table.

Can not Load Plugin Assembly error in Offline Client

The Outlook offline does not regiter plugin assemblies correctly. This may happen when uninstalling and re installing the Offline client.
To fix this, you need to write the Assembly Public Key token in the registery as a new key under ther "HKEY_CURRENT_USER\Software\Microsoft\MSCRMClient\AllowList" Key.
Getting the key can be done by executing sql query "select * from PluginAssemblyBase" in the organization database.
This is from KB 949088 by microsoft, can be found on KBAlertz here.
The title for the KB is :
Error message when you start a plug-in assembly in the Microsoft Dynamics CRM 4.0 client for Outlook: "Unable to load plugin assembly"

Problem Installing Outlook Offline client with MSXML 6 installation failure

MSXML 6 installation recognizes newer versions and reports a failure when executed. The SQL Express installation does not recognize the newer version and executes the 6 installtion which in its turn retruns a failure. After that the SQL Express installation will not continue and the CRM Outlook clinet will not be installed too.
Aaron Bertrand writes about this in his blog here and includes a solution. The solution includes installing the Windows Installer Cleanup Utility.