You are here


Minimum permissions needed for a deployment administrator

In CRM 4.0 a deployment administrator is used to manage organizations. The user that installs CRM is created as a deployment administrator. Further users may bee added as deployment administrators using Deployment Manager.

Forcing CRM to clean up deleted records

CRM 4.0 tidies up deleted records via the asynchronous service every 24 hours. To force an immediate cleanup follow the steps:

1. Mark the database to run the deletion tidy up immediately by running the following SQL commands. Take care to update the correct deletion service if your CRM server hosts multiple organizations.


Tables involved in Workflow and Workflow history

This article  details how to clear up the AsyncOperationBase and WorkflowLogBase tables

Relevant Tables

Modifying Queue Views

Modifying a queue view is not directly supported in the CRM Application. However it is supported as described in this post:


Deleting workflow logs using the SDK

To delete workflow logs using the SDK use the RetrieveMultiple and Delete messages.

Set up a query expression that defines which workflow logs to delete. For example, to delete workflow logs older than a certain date:

// set the columns to be returned
ColumnSet cols = new ColumnSet();
cols.Attributes = new string[] { "createdon", "description" };

// Create the on or before condition
ConditionExpression dateCondition = new ConditionExpression();
dateCondition.AttributeName = "createdon";

Sending Direct E-mail to Contact requires permission on parent account

Using Direct E-mail to send to a contact requires at least read access on the Parent Customer record.

Quite why this is needed is a mystery. Possibly a bug.

Sending Direct E-mail to members of a marketing list

In Microsoft Dynamics CRM 4.0, there is no obvious way in the application to send direct e-mail to members of a marketing list.

Here is a way of doing just that:

Exported isv.config is empty

In CRM 4.0, in order to customize the application the isv.config file has to be exported. On some systems I've noticed that the exported file does not have the sample customizations.

The sample customizations can be added from the sample isv.config from the SDK.

Problem configuring Outlook Client when host headers are used

If host headers were used to install the CRM web site on the web server then you may run into problems when configuring the CRM Client for Outlook.

During configuration you may get errors saying that the CRM web site cannot be contacted (even though you can in Internet Explorer).

The solution is to follow the steps in this article:

Installing CRM 4.0 in Windows Server 2008

CRM 4.0 can be installed on Windows Server 2008.
Refer to for more details and specific workarounds that may be needed.



Subscribe to 4.0