Welcome to my knowledgebase, which contains snippets of information that I find (mostly about Microsoft Dynamics CRM) and then forget.

You are most welcome to browse and if any of the information helps you in your work with Microsoft Dynamics CRM then that is great.

Use the search box or the tag links to search for articles.

About Me

I’m an experienced Microsoft Dynamics CRM Consultant and Microsoft Certified Trainer. Find out more at

Recently updated articles

Installing CRM 4.0 on SQL Server 2008

29 Oct 2012

CRM 4.0 can be installed on SQL Server 2008.

Refer to for more details and specific workarounds that may be needed.


Connect to Existing Deployment or Install New Deployment

29 Oct 2012

When installing CRM 4.0 you have the option to connect to an existing deployment. This option is for adding new CRM 4.0 servers to an existing deployment and not for connecting to an existing database following a server or domain migration.

For an existing database that has been moved to a new domain, use a new installation, create a new (temporary) organization. Then use Deployment Manager to import the existing database and then delete the temporary organization.


CRM 4.0 Workgroup Edition may be installed on any server

29 Oct 2012

CRM 4.0 Workgroup Edition does not have to be installed on a Small Business Server. The Purchase Usage Rights document from Microsoft does not detail any such restriction.

Problems when using Host Headers

29 Oct 2012

If host headers are used for the CRM web site a number of problems may occur including, workflows stuck at waiting, duplicate detection rules not working, Outlook configuration not working and so on. The issue appears to be how rows in the DeploymentProperties table in MSCRM_CONFIG are configured.

To check whether this is the issue, run the following SQL statements against the MSCRM_CONFIG database:


SELECT NVarCharColumn
FROM deploymentproperties
WHERE columnname = 'AsyncSdkRootdomain'

CRM 2011 Client for Outlook- problem communicating with server

29 Oct 2012

The installating guide for CRM 2011 strongly recommends that a low privilege domain account is used for the CRM and ASP.NET services.

Having followed this advice I found I was unable to configure the Outlook Client to connect to the CRM server. The error I got was "there is a problem communicating with the server". Examining the log file, Crm50ClientConfig.log, revealed the following error:

Security groups required by Microsoft Dynamics CRM 4.0

29 Oct 2012

Microsoft Dynamics CRM uses several security groups in Active Directory.

Kernel-mode authentication for CRM 2011 Website

29 Oct 2012

Following a CRM 2011 installation that seemed to work, users were getting 401.1 unauthorized errors when connecting to the CRM server from their PCs.

However, everything worked fine when connecting to CRM from the server.

The problem was found to be that kernel-mode authentication was not enabled on the CRM website. To resolve the issue, complete the following steps:

Service Unavailable error for CRM Federation Metadata

29 Oct 2012

I came across an error when configuring claims-based authentication for Microsoft Dynamics CRM 2011. The error, Service is Unavailable was returned when browsing to the CRM metadata URL.
In this installation, something was wrong with URL rewriting. Following the steps in this article resolved the issue:

Buying Microsoft Dynamics CRM Workgroup Edition

29 Oct 2012

Microsoft Dynamics CRM Workgroup Edition is best purchased under an Open Value licence. Open Value includes the option to buy a step-up to Server Edition thus preserving the initial investment in the Workgroup edition licence.
An Open Value licence also means that you can spread payments over 3 years.

Clearing Workflow History

29 Oct 2012

There is no way to bulk clear out workflow history via the CRM application. It is possible to delete entries under Settings | System Jobs but that is restricted to a set number of records at a time (i.e. the number of records shown in a list view).

In Microsoft Dynamics CRM 4.0 workflow history is stored in two tables called asyncoperationbase and workflowlogbase. Details of all jobs that have run (whether workflow initiated or not) are stored in the asyncoperationbase table. For workflows, asyncoperationbase has one entry.