Microsoft Dynamics CRM 2011 Beta Readme

September 2010

This document provides important, late-breaking information about Microsoft Dynamics CRM 2011. You will find information about upgrading from previous versions, prerequisites for this release, and descriptions of known issues. Where possible, workarounds are provided for the known issues.

This is version 1.0 of this readme.

Microsoft Dynamics CRM 2011 Download Contents

The following table lists the contents of the Microsoft Dynamics CRM 2011 download.

Name

Contents

Microsoft Dynamics CRM 2011
  • Microsoft Dynamics CRM 2011 Server and Microsoft Dynamics CRM Fetch Extension Setup (32-bit)
  • Microsoft Dynamics CRM E-mail Router Setup
  • Microsoft Dynamics CRM for Microsoft Office Outlook

Documentation

Microsoft Dynamics CRM 2011 Installation Guide

The Microsoft Dynamics CRM 2011 Beta Implementation Guide is available for download. This document provides the system requirements and installation instructions to use to install Microsoft Dynamics CRM 2011.

Microsoft Dynamics CRM SDK

The Microsoft Dynamics CRM SDK contains documentation and a readme, sample code and tools for developers, system customizers, and report writers.

Software Upgrade

Applications that do not support upgrade

Although Microsoft Dynamics CRM 2011 Server can be upgraded from Microsoft Dynamics CRM 4.0 versions, the following applications do not support upgrade for this release. You must uninstall the previous version of the application (using the Microsoft Windows Control Panel "Uninstall or change a program feature") before you run Setup:

After upgrading the server, you can then install the Microsoft Dynamics CRM 2011 Server version of the applications.

Microsoft Dynamics CRM 2011 Server beta is shipped with English (1033) as the only base language

Microsoft Dynamics CRM 2011 Server beta is shipped with English (1033) as the only base language. If you want to import and upgrade a Microsoft Dynamics CRM 4.0 organization with a non-English base language into the Microsoft Dynamics CRM 2011 beta deployment, you must first install the Microsoft Dynamics CRM 2011 Language Packs for that non-English base language.

Upgrading Microsoft Dynamics CRM Language Packs

You can upgrade from Microsoft Dynamics CRM 4.0 to Microsoft Dynamics CRM 2011 Server without uninstalling the Microsoft Dynamics CRM Language Packs. However, after upgrading, you should still uninstall the Microsoft Dynamics CRM 4.0 Microsoft Dynamics CRM Language Packs, and then install the Microsoft Dynamics CRM 2011 Server version of the Language Packs.

If you do not manually upgrade the Language Packs, you will encounter the following error:

Base language overwrites language pack labels after organization import and upgrade

This issue occurs when you upgrade the server from Microsoft Dynamics CRM 4.0 to <crm5_Server> but do not manually upgrade the Language Packs, leaving the Microsoft Dynamics CRM 4.0 Language Packs installed with the <comp5_Server, and then you import a Microsoft Dynamics CRM 4.0 organization into the Microsoft Dynamics CRM 2011 deployment.

For example, the issue will occur if you do the following

  1. Install Microsoft Dynamics CRM 2011 Server, setting the base language to English (1033).
  2. Do not manually upgrade the Microsoft Dynamics CRM 4.0 Japanese Language Pack (1041) to the Microsoft Dynamics CRM 2011 Language Pack.
  3. Import and upgrade a Microsoft Dynamics CRM 4.0 organization that has the the Japanese Language Pack (1041) enabled.
  4. After the organization import and upgrade is complete, when a user selects to view theMicrosoft Dynamics CRM user interface in Japanese (1041), the some of the organization’s labels may still display in the base language that Microsoft Dynamics CRM 2011 Server was installed in, in this example U.S. English (1033).

If the max length of a Subject field on an Activity entity is greater than 500, upgrade could fail.

The workaround is to set the maximum length property of all Subject fields on all Activity entities to 500 or lower.

Prerequisites for Computers That Have a Prerelease Version of Microsoft Dynamics CRM 2011 Installed

We recommend that you install Microsoft Dynamics CRM 2011 on a computer that does not have a prerelease version of Microsoft Dynamics CRM 2011 installed, such as Microsoft Dynamics CRM "5" CTP3. Or install to a computer that has had its hard disk recently reformatted. However, if you must install Microsoft Dynamics CRM 2011 on a computer that has a prerelease version of Microsoft Dynamics CRM 2011 installed, follow these steps:

  1. Uninstall any previous Microsoft Dynamics CRM 2011 prerelease version, such as Microsoft Dynamics CRM "5" CTP3.
  2. If installed, uninstall Microsoft .NET Framework 4.0 prerelease.
  3. If installed, uninstall Microsoft Visual Studio 2010 prerelease.
  4. After Setup is complete, if you are using the same Microsoft Dynamics CRM Web site that was used with an earlier Microsoft Dynamics CRM prerelease version, follow these steps to change the handler mappings:
    1. Start Internet Information Services (IIS) Manager.
    2. Expand the Web site, expand the Sites folder, and then click Microsoft Dynamics CRM.
    3. In the right pane, double-click Handler Mappings.
    4. Modify the path of the executable for all Microsoft .NET Framework 4.0 mappings to point to the location of the new .NET Framework 4.0 assemblies. The .NET Framework 4.0 handler mappings will all end in -4.0_64bit.
    5. Click Yes at the prompt to allow for the ISAMPI extension.
  5. To upgrade Microsoft Dynamics CRM document management, follow these steps:
    1. Install and activate the Microsoft Dynamics CRM List component for Microsoft SharePoint. To do this, follow these steps:

      Start Internet Explorer, and then open the SharePoint site collection, for example http://crmsp/sites/crm.

      Click Select Site Actions, and then click Site Settings.

      Under Galleries, click Solutions.

      On the Solutions tab, in the New group, click Upload Solution.

      Click Browse, locate the crmlistcomponent.wsp file, and then click OK.

      On the Solutions tab, in the Commands group, click Activate.

    2. If you are using Microsoft SharePoint Server 2010 (On-Premises), you must add .htc extensions to the list of allowed file types:

Product Key

The following product keys are available for this release:

Microsoft Dynamics CRM 2011 Server Beta Prerequisites

Microsoft .NET Framework 4.0 RTM is required

The RTM version of Microsoft .NET Framework 4.0 is required.

To use the Microsoft Dynamics CRM documentation management feature with Microsoft SharePoint Server 2010, Microsoft SharePoint Server 2010 must be installed and running

To use the optional Microsoft Dynamics CRM 2011 functionality for Microsoft SharePoint Server 2010, Microsoft SharePoint Server 2010 must be installed, configured, and available. Microsoft SharePoint Server 2010 is available to download at the Microsoft SharePoint Server 2010 Web page.

Important

For additional prerequisites and system requirements, see the Microsoft Dynamics CRM 2011 Implementation Guide.

Setup and Deployment Known Issues

Microsoft Internet Explorer 9 beta is not supported with Microsoft Dynamics CRM 2011

The Internet Explorer 9 beta version is not supported and will not work with Microsoft Dynamics CRM 2011.

“Action Microsoft.Crm.Tools.Admin.UpgradeWorkflowInstancesAction failed. Timeout expired.” error message occurs when you upgrade a previous Microsoft Dynamics CRM Server version to Microsoft Dynamics CRM 2011 Server Beta

To work around this issue, add the OLEDBTimeout and the ExtendedTimeout registry subkeys to increase the time-out values as described in http://support.microsoft.com/kb/918609, and then click Retry in the Setup error message dialog box.

“Microsoft.Crm.Tools.Admin.ConvertIsvConfigToRibbonAction failed” error message during organization upgrade

Organizations with ISV configuration customizations may receive this error during organization upgrade. To work around this issue, click Ignore when you are prompted during the upgrade. The ISV configuration customizations will not be converted into Microsoft Office customizations, but the rest of the organization upgrade should complete successfully. This issue will be addressed in a future release.

Some Microsoft Dynamics CRM 4.0 organizations cannot be upgraded to Microsoft Dynamics CRM 2011

Organizations that were migrated to Microsoft Dynamics CRM 4.0 on-premises editions from Microsoft Dynamics CRM Online March 2009 Service Update or a later Microsoft Dynamics CRM Online release cannot be successfully upgraded to Microsoft Dynamics CRM 2011.

Organization upgrade fails during the UpgradeDatabaseAction Cannot drop procedure 'procedure_name' because it is referenced by plan guide 'plan_guide_name'

This issue can occur if you have an organization database that contains one or more Microsoft SQL Server plan guides. To work around this issue, drop the plan guide and then try the upgrade again.

After upgrade custom menus and buttons do not display for Microsoft Office Outlook 2003 and 2007

ISV.Config definitions for custom menus and buttons in Microsoft Dynamics CRM 4.0 are not correctly converted into the correct RibbonDiffXml to display in versions of Microsoft Office Outlook that do not use the ribbon.

Microsoft Windows Azure Platform AppFabric integration

Enabling Windows Azure Platform AppFabric integration in Microsoft Dynamics CRM is a post setup action. See the Microsoft Dynamics CRM SDK for instructions about how to enable it. This feature lets Microsoft Dynamics CRM 2011 post messages to the services hosting endpoints on the Windows Azure Platform AppFabric service bus.

Prerequisites for Microsoft SharePoint and Windows SharePoint Services

  1. SharePoint must be installed before installing the Microsoft Dynamics CRM List component.
  2. The Microsoft Dynamics CRM List component must be installed on the server that is running SharePoint by a Microsoft Dynamics CRM administrator who has site collection permissions on the SharePoint server. The administrator must uninstall the old version of the Microsoft Dynamics CRM List component and install the new component because component upgrade is not supported.

    To install the Microsoft Dynamics CRM List component:

    1. Go to the Microsoft Dynamics CRM List Component for SharePoint Download page.
    2. Click Download, and save the file to the desired location.
    3. Open your browser.
    4. In the address bar, type the URL of the site collection on which you want to install the Microsoft Dynamics CRM List component.
    5. Click Site Actions, and then click Site Settings.
    6. Under Galleries, click Solutions.
    7. On the Solutions tab, in the New group, click Upload Solution.
    8. Click Browse, locate the crmlistcomponent.wsp file, and then click OK.
    9. On the Solutions tab, in the Commands group, click Activate.

    If you are using Microsoft SharePoint Server 2010 (On-Premises), you must add .htc extensions to the list of allowed file types:

    1. Copy the AllowHtcExtn.ps1 script file to the server that is running Microsoft SharePoint Server 2010.
    2. In the Windows PowerShell window or in the SharePoint Management Console, run the command: AllowHtcExtn.ps1 <Web Application URL>.

      Example: AllowHtcExtn.ps1 http://servername

      For more information, see the Microsoft Dynamics CRM List Component for Microsoft SharePoint Server 2010 Readme on the Microsoft Dynamics CRM List Component for Microsoft SharePoint Server 2010 Download page.

Import organization fails with Microsoft Dynamics CRM 4.0 organization database when running on Windows Server 2008 R2

When you run the Import Organization Wizard in Deployment Manager to import and upgrade a Microsoft Dynamics CRM 4.0 organization, you may receive an error message that resembles the following message, and the import does not complete:

System.Data.SqlClient.SqlException (0x80131904): The login already has an account under a different user name.

This issue occurs only when you run Microsoft Dynamics CRM 2011 Server on Windows Server 2008 R2. To work around this issue, install Microsoft Dynamics CRM 2011 Server on a computer that is running the original release of Windows Server 2008, and then try the import organization operation again.

Issues and limitations when using claims-based authentication

When you use claims-based authentication, the following limitations apply:

Cannot access Microsoft Dynamics Marketplace

If you deploy Microsoft Dynamics CRM 2011 Server on premises and you use a proxy server to manage Internet access, you will not be able to access Microsoft Dynamics Marketplace data. To work around this issue, you must set the proxy URL property for Microsoft Dynamics Marketplace in the configuration database. To do this, run the following T-SQL against the Microsoft Dynamics CRM 2011 configuration database (MSCRM_CONFIG), where http://myproxy.url.com is the URL of the proxy server:

insert into deploymentproperties (id, columnname, nvarcharcolumn)

(select top 1 id,'InternetConnectionProxyEndpoint','http://myproxy.url.com from deploymentproperties)

Setup fails during UpdateWebsiteRegistryAction

When you install Microsoft Dynamics CRM 2011 Server on a Windows 2008 R2 computer with no Windows Role Services previously configured on it, Setup fails during UpdateWebsiteRegistryAction with the following error:

5:54:08| Error| System.Exception: Action Microsoft.Crm.Setup.Server.UpdateWebsiteRegistryAction failed. ---> System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Web.Administration, Version=7.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

at Microsoft.Crm.Setup.Server.Utility.WebServerSettings.get_Url()

at Microsoft.Crm.Setup.Server.UpdateWebsiteRegistryAction.WriteRegistrySettings(ServerInstallInfo installInfo)

at Microsoft.Crm.Setup.Common.CrmAction.ExecuteAction(CrmAction action, IDictionary parameters, Boolean undo)

.--- End of inner exception stack trace ---, Error, RetryCancel, Option1

To work around this issue, install any Web server role service on the computer so that the Microsoft.Web.Administration.dll file is registered in the GAC.

Microsoft Dynamics CRM Server cannot be uninstalled, configured, or repaired by using Programs and Features

You receive an error message when you perform a maintenance operation by using Programs and Features for Microsoft Dynamics CRM 2011 Server, such as uninstall, configure, or repair.

This issue can occur when the following are true:

To work around this issue, perform the maintenance operation by running Microsoft Dynamics CRM Server Setup at the command line:

  1. On the computer where Microsoft Dynamics CRM Server is installed, open a command prompt: Click Start, type cmd, and then press ENTER.
  2. Move to the Microsoft Dynamics CRM 2011 program files folder. By default, the location is C:\Program Files\Microsoft Dynamics CRM.
  3. Type Microsoft.Crm.Setup.Server.exe, and then press ENTER.
  4. In the Microsoft Dynamics CRM Setup dialog box that opens, select the maintenance task that you want, and then follow the instructions that are on your screen.

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>

Report Authoring in Microsoft Dynamics CRM

To author custom Fetch-based reports for Microsoft Dynamics CRM, you must install Microsoft Dynamics CRM Fetch Extension. For more information, see the Microsoft Dynamics CRM Fetch Extension Download page.

Feature Area Known Issues

‘Add New’ on specific activity toolbars, such as Tasks, sets the regarding object id rather than the look-up id

‘Add New’ sets the regarding object id rather than the look-up id, a known issue for this release. There is no workaround at this time.

Bulk activity buttons are not on the toolbars

The absence of the bulk activity buttons on the toolbars is a known issue for this release. There is no workaround at this time.

Canceled and expired contracts cannot be deleted

Contracts that are canceled or expired cannot be deleted in Microsoft Dynamics CRM. This is by design and is not a change for Microsoft Dynamics CRM 2011. However, in Beta, this means you cannot delete the contracts that are sample data or any contracts you imported, unless they are in the draft state.

Some mobile devices cannot sign out from Mobile Express

On some devices you will see a blank page after signing out. Close all browser sessions to sign in again.

A 404 error occurs after a mobile device running Microsoft Dynamics CRM times out

Clear the Internet cache or close all browser sessions. If the error still occurs, restart the device.

Some mobile devices show a blank screen after signing in to Microsoft Dynamics CRM

Navigate back to the sign in page and try to sign in again. If this fails, there is no other workaround.

Data import to a field of PartyList type is not supported

Maps with lookup mapping nodes that make references to a field of PartyList type will not be imported. The data that has lookup references to a field of PartyList type will also fail to import.

Import job cannot be created when old maps (maps that existed prior to the Microsoft Dynamics CRM upgrade) are used for an import through the Import Data Wizard

A data map that existed prior to the upgrade cannot be exported and cannot be used to import data through the Import Data Wizard. These old maps will not appear in the list of maps in the Import Data Wizard if a .zip file is uploaded for import. To work around this, export all the maps before starting the upgrade and then import the maps back into Microsoft Dynamics CRM after the upgrade is complete.

Out-of-box data maps are available only in English

In Microsoft Dynamics CRM Beta release, the out-of-box data maps in the Import Data Wizard, such as data maps for Salesforce.com, are not localized and hence are available only in the English language. Because of this, if your source data is localized (in other languages), you will need to manually map your data during import.

Import fails with an "Id is missing" error on import of the Account entity (upgraded entity)

If you have customized the Account form in Microsoft Dynamics CRM 4.0 and then upgraded to Microsoft Dynamics CRM 2011, and the Microsoft Dynamics CRM 2011 Account form XML contains the <header> element, you are unable to import any managed solution that customizes the Account entity. The import will fail with the error 'id is missing'.

The workaround for this is to remove the following lines from the form header XML:

<cell>
<labels/>
<cell>

To do that, export an unmanaged solution that contains an Account entity, remove those lines of code from the form XML, and then reimport the unmanaged solution.

Opening a Data Import template or XML Spreadsheet 2003 files for reimport fails with Microsoft Excel 2010

The Data Import templates and files configured for reimport (using Export to Excel) are in XML Spreadsheet 2003 format. Opening an XML Spreadsheet 2003 file that has data validation fails with Excel 2010. This is a known issue with Excel 2010. The issue will be addressed in the Excel 2010 Service Pack 1 release in February 2011. To work around this issue, save the file before you open it. This issue is not observed when the files are opened with Microsoft Office Excel 2007.

Automatic field width customization during import is not supported

If a column has data that exceeds the specified limit for the field, the field width is not changed automatically during import and the import fails.

Workflow fails because of import error

If you import a workflow that refers to an attribute that does not exist in your Microsoft Dynamics CRM system, the error message that should result is broken. Therefore, you are not informed of the mistake. Instead, when you try to run the workflow, it fails. You are also unable to open the workflow in order to edit it.

Start Dialog button not available on ribbon for a sub-list in a record

A record that has a sub-list, such as Contract Lines for a contract, has dialogs available to be started for it. However, the sub-list does not display the Start Dialog button in the ribbon.

To work around this issue, click the main tab for the record, such as the Contract tab for a contract. The Start Dialog button is available and you can click it to start a dialog. You can also start the dialog from the main area for the entity where the records are listed.

Hyperlink in dialog causes HttpException at runtime

A hyperlink inserted in the prompt or tip text for a prompt-and-response step will cause an HttpException error similar to the following when you run the dialog and click the hyperlink:

HttpException: A potentially dangerous Request.Path value was detected from the client (:).]
at System.Web.HttpRequest.ValidateInputIfRequiredByConfig()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

The Microsoft Dynamics CRM 2011 beta release does not support using hyperlinks in the prompt or tip text in a dialog. To work around this issue, remove any hyperlinks in the prompt or tip text in your dialog.

Cannot sign out from IFD Microsoft Dynamics CRM using some mobile devices

On some devices you will see a blank page after sign out. You may need to close all browser sessions in order to sign in again.

404 error occurs after a mobile device running Microsoft Dynamics CRM times out

Clear the cache or close all browser sessions. Some devices will require a restart of the device.

IFD Login pages not mobile friendly

Some devices require a mobile-friendly login page. To make the pages mobile friendly, please add the following line of code to masterpage.master under inetpub\adfs\ls\MasterPages\:

<%@ Master Language="C#" AutoEventWireup="true" CodeFile="MasterPage.master.cs" Inherits="MyMasterPage" EnableViewState="false" %>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" dir='<%$ Resources:CommonResources, LanguageDirection%>' runat="server">

<head runat="server">

    <meta http-equiv="X-UA-Compatible" content="IE=8" />

    <title>AD FS 2.0 Authentication Web site</title>

    <link rel="stylesheet" type="text/css" href="StyleSheet.css" />

    <meta name="robots" content="noindex, nofollow" />

    <meta name="viewport" content="width=device-width" />

</head>

 

…

Some mobile devices show a blank screen after signing in to Microsoft Dynamics CRM

There is no known work around at this time.

Import of new security roles fails with an error "An item with the same key has already been added."

If you import a solution that includes new security roles and if auditing is enabled on the Security Role entity, the error "An item with the same key has already been added." occurs. To work around this, disable auditing on the Security Role entity before you import the solution. You can enable auditing after the import is successful.

Microsoft Dynamics CRM for Outlook Known Issues

Cannot upgrade from CTP4 build to Beta build

First uninstall CTP4 and then install Beta. Beta is compatible with Microsoft Outlook 2007 and Microsoft Outlook 2010.

You can download Microsoft Dynamics CRM for Microsoft Office Outlook

Download Microsoft Dynamics CRM for Outlook. Downloads are available for 32-bit and 64-bit platforms, and from data centers in Asia, Europe, or North America. You can also download corresponding language packs for the following languages: French, German, Hebrew, Italian, Japanese, and Spanish.

Setup does not complete after restarting your computer

If, after restarting your computer, you see an error message that indicates that setup cannot complete because some files are missing, go to the location where you downloaded the setup files. Double-click the program with the .exe filename extension to restart the setup program.

Configuration of Microsoft Dynamics CRM for Outlook fails if you are using the 64-bit version of Office

Before you can configure Microsoft Dynamics CRM for Outlook, you must install both the 32-bit and 64-bit versions of Microsoft SQL Server Compact Edition, which is a prerequisite for Microsoft Dynamics CRM for Outlook. First, install both the 32-bit and 64-bit versions of SQL Server CE, and then install Microsoft Dynamics CRM for Outlook again.

Click the following 32-bit and 64-bit links to download and install SQL Server CE in the language that you are using:

Script error occurs when you click certain links in the Get Started pane in Outlook

Some of the links that are used to open a dialog box or start an action in the Get Started pane in Outlook display a script error. The script error prompts you about whether you want to continue running scripts on the page. Click Yes or No to close the message.

To open the dialog box or start the action described in the link, follow the instructions in the tip that is displayed when you hover over the text.

Credentials are not deleted

The Sign Out and Forget Me command is supposed to log off a user and delete the credentials (user name and password) that were used to connect to the Microsoft Dynamics CRM server. Even though you click the Sign Out and Forget Me command, your credentials are saved. If you sign on to the server, you are not prompted for credentials.

Your Microsoft Dynamics CRM credentials are also still stored in the Credentials Manager, even though Microsoft Dynamics CRM for Microsoft Office Outlook is uninstalled.

List of recently used records is not saved

When you close Outlook, the list of most recently used records is deleted.

Changes to views are not saved

Personalization of views, such as added or removed columns, and arrangements or sorts of the information are not saved along with the view.

Folders open slowly initially

The first time you open folders, they open slowly.

Cannot go offine if the language for Microsoft Dynamics CRM for Outlook is different than the language for the Microsoft Dynamics CRM server

If the selected language of the Microsoft Dynamics CRM server and Microsoft Dynamics CRM for Outlook are different, they will function properly until you try to go offline. For example, going offline will not work if the language of the Microsoft Dynamics CRM server is English, but the Microsoft Dynamics CRM for Outlook is French.

Install the Microsoft Dynamics CRM for Outlook language pack from the Microsoft Download Center Web site: Download Beta Language Packs

Folders of a second organization do not display correctly when organizations use different languages

If you are using more than one organization, be sure to use the same language for all of them.

Non-owner of records cannot track e-mail messages when offline

When offline, only the owner of the recipient record can track e-mail messages.

Outlook may hang the first time you go offline if a custom entity contains follow-up flags

If Outlook hangs while going offline, restart Outlook.

Entity privileges to synchronize with the Microsoft Dynamics CRM Address Book are not revoked

Turning off Address Book synchronization does not turn it off for each entity. To turn off Address Book synchronization, you must turn it off for each entity that you do not want to synchronize.

Recurring appointments are not synchronized between Outlook and Microsoft Dynamics CRM

If you update or delete a single occurrence of a tracked appointment, it may not synchronize between Outlook and Microsoft Dynamics CRM.

Microsoft Dynamics CRM for Outlook does not start

If your security role is changed or was removed in Microsoft Dynamics CRM, Microsoft Dynamics CRM for Outlook will not start.

If your security role was changed, close Outlook, and then use the Microsoft Dynamics CRM Configuration Wizard to connect to the Microsoft Dynamics CRM server again.

  1. To start the Configuration Wizard, click Start, point to All Programs, click Microsoft Dynamics CRM 2011, and then click Configuration Wizard.
  2. Click Delete to remove the server URL.
  3. Click Add. Type the server URL, and then click Test Connection. Click the name of the organization, and then click OK.

Charts feature does not work correctly in Microsoft Dynamics CRM for Outlook

The following features of charts do not work correctly in Microsoft Dynamics CRM for Outlook:

Chart selector appears blank in a few cases in Microsoft Dynamics CRM for Outlook

In Microsoft Dynamics CRM for Outlook, navigating to the same entity from a different folder hierarchy causes chart pane and list to become blank. For example, navigating to the Lead entity from Marketing, and then from the Sales area can cause this problem. In such cases, restart Outlook.

Reporting Known Issues

Installing Microsoft Dynamics CRM Reporting Extensions without the SQL Data Processing Extension may lead to errors

You have the option to not install the SQL Data Processing Extension during Microsoft Dynamics CRM Reporting Extensions Setup. However, SQL Data Processing Extension is going to be made mandatory, and installing Microsoft Dynamics CRM Reporting Extensions without SQL Data Processing Extension would give unexpected errors. To avoid this, install both Fetch and SQL Data Processing Extensions as part of Microsoft Dynamics CRM Reporting Extensions installation.

Installing language pack does not upgrade Report Wizard reports

When you are upgrading Microsoft Dynamics CRM 4.0 to Microsoft Dynamics CRM 2011, Report Wizard reports of non-base languages will not get updated when the upgrade happens or when a language pack is installed. To work around this, edit the report by using the Report Wizard, and walk through it without making any changes. This will upgrade the report.

Dependencies between Report and Report Entity not shown correctly

In Solutions Explorer, the dependencies between Reports and ReportEntity/ReportCategory are not shown correctly. This can be observed when you click Show Required Components, or when you export or import a solution with a missing dependency.

Data source of parent report not set to the shared data source during customization of child report

When a child default (out-of-box) report is customized, the parent report is also customized and both reports are copied to the Custom Reports folder. The data source for the child report is correctly set to the shared data source but the data source of the parent report is not set. To work around this, manually set the parent report's data source on SQL Server Reporting Services or make superficial customizations (like changing report name) to the parent report.

Parent report customization does not customize the child report

If a default (out-of-box) parent report is customized, the child report does not get customized. Running the parent report will give a missing child report error. To work around this, make superficial customizations (like changing the report name) to the child report.

Drilling down in default (out-of-box) reports or Report Wizard reports to Microsoft Dynamics CRM entity forms does not work correctly

When drilling down in default (out-of-box) reports or Report Wizard reports to Microsoft Dynamics CRM entity forms in deployments that use HTTPS (HTTP Secure), the drill down page does not open and the user is redirected to a sign-in page or a Page not found page. This happens on some of the Services Provider License Agreement (SPLA) deployments that use HTTPS and all Microsoft Dynamics CRM Online production deployments. To work around this, cancel the navigation of the drill-down page and replace http with https in the URL and navigate to that URL.

Reports scheduling or snapshots may fail for some Microsoft Dynamics CRM users

In some deployment configurations, only the Microsoft Dynamics CRM user who is running the CRMAppPool application pool will be able to schedule reports or create snapshots in the Microsoft Dynamics CRM Beta release.

Visualization/Charts Known Issues

Charts that use associated views may show wrong data

A chart added to an associated list may show incorrect data if the chart uses an associated view. That is, the chart may show data that is inconsistent with the data in the list of records.

Charts do not work properly in Internet Explorer 9

Charts are not working properly when opened in Internet Explorer 9.

Error occurs in the chart pane when activity type is changed from the view selector

If you change the view to show records of a different activity type, an error occurs while rendering the chart.

E-mail Router Known Issues

After upgrade to Microsoft Dynamics CRM 2011, e-mail messages won't be processed on accounts that used Exchange Online as E-mail Server Type in Microsoft Dynamics CRM 4.0

You may have created incoming or outgoing configuration profiles for use by the E-mail Router for Microsoft Dynamics CRM Online. In configuration profiles that specify Exchange Online as the E-mail Server Type, the protocol is automatically changed to WebDAV for Microsoft Exchange Server 2003 after you upgrade to the Microsoft Dynamics CRM 2011 E-mail Router. After this conversion, the E-mail Router will not process e-mail messages for the accounts that use these configuration profiles.​

After you upgrade to the Microsoft Dynamics CRM 2011 E-mail Router, do the following for each Exchange Online configuration profile:

  1. Change the value of the E-mail Server Type to Exchange Online from Microsoft Exchange Server 2003. This forces the protocol to change from WebDAV to Exchange Web Services.
  2. Save the changes to the profile.
  3. Run Test Access to verify that the profiles are functional.
  4. Publish changes.

Installations without users or queues configured will fail on upgrade

If you have not configured any users or queues in your installation of the Microsoft Dynamics CRM 4.0 E-mail Router, an attempt to upgrade to the Microsoft Dynamics CRM 2011 E-mail Router will fail when the system requirements are checked. In your installation of the Microsoft Dynamics CRM 4.0 E-mail Router, configure at least one user or queue with an incoming or outgoing profile before you upgrade to the Microsoft Dynamics CRM 2011 E-mail Router.

You cannot configure the E-mail Router to work with Microsoft Dynamics CRM Online

To connect the E-mail Router to Microsoft Dynamics CRM Online, you must edit a specific configuration file as follows:

To set the E-mail Router to work with Microsoft Dynamics CRM Online

  1. On the computer where the E-mail Router was installed, open the Service folder in the E-mail Router installation folder. If you chose the default installation folder during Setup, this is: C:\Program Files\Microsoft CRM Email\Service
  2. Open the file Microsoft.Crm.Tools.Email.Management.config file for editing.
  3. Remove the XML comments (<!-- and -->) from around the following statement: <add key="DiscoveryUrl" value="https://dev.crm.dynamics.com" />
  4. Save the file.
  5. Start the E-mail Router Configuration Manager.

In e-mail messages that you receive, the names and contents of attachments are not displayed correctly if the names of those attachments contain Unicode characters

No resolution is currently available for this issue.

The E-mail Router fails to process outgoing e-mail if the user account is not a member of the PrivUserGroup CRM security group

Note

This issue and resolution apply only to users of Microsoft Dynamics CRM (On-Premises Edition).

  1. Start the E-mail Router Configuration Manager, and then click Deployments.
  2. Determine the accounts that are specified in the listed deployments. (To open a deployment, select the deployment and click Modify.)
  3. Add each account to the PrivUserGroup CRM security group in Active Directory.
  4. Restart Internet Information Services (IIS) Manager. For more information, see Load Data Troubleshooting in the Load User, Queue, and Forward Mailbox Data section of the E-mail Router Help.

The Rule Deployment Wizard cannot connect to a deployment of Microsoft Dynamics CRM (On-Premises Edition)

Note

This issue and resolution apply only to users of Microsoft Dynamics CRM (On-Premises Edition).

To connect the Rule Deployment Wizard to a deployment of Microsoft Dynamics CRM (On-Premises Edition)

  1. Start the Rule Deployment Wizard.
  2. On the welcome page of the Rule Deployment Wizard, click Add Contacts.
  3. On the Select a Deployment page, under Deployment, select An online service provider.
  4. Under Access Credentials, provide the credentials of the Microsoft Dynamics CRM (On-Premises Edition) server in the User Name and Password fields.

Document Management Known Issues

User code service does not work correctly if SharePoint is installed on an Active Directory service domain controller

If SharePoint Server is installed on an Active Directory Service domain controller, the User code service does not work correctly. To work around this, run the following Windows PowerShell script:

$acl = Get-Acl HKLM:\System\CurrentControlSet\Control\ComputerName

$person = [System.Security.Principal.NTAccount]"Users"

$access = [System.Security.AccessControl.RegistryRights]::FullControl

$inheritance = [System.Security.AccessControl.InheritanceFlags]"ContainerInherit, ObjectInherit"

$propagation = [System.Security.AccessControl.PropagationFlags]::None

$type = [System.Security.AccessControl.AccessControlType]::Allow

$rule = New-Object System.Security.AccessControl.RegistryAccessRule($person, $access, $inheritance, $propagation, $type)

$acl.AddAccessRule($rule)

Set-Acl HKLM:\System\CurrentControlSet\Control\ComputerName $acl

Documents for duplicate records for the same record type will be shown from the same SharePoint location

If there are duplicate records for the same record type, the documents will be shown from the same SharePoint location.

New Document action does not save the document

The New Document action saves the document locally and not on SharePoint server if the operating system is Windows Vista or Windows Server 2008.

Limitations in performing actions related to SharePoint Document Management in the Microsoft Dynamics CRM list

You will not be able to perform any actions related to SharePoint Document Management in the Microsoft Dynamics CRM list if .htc extensions are not added to the list of allowed file types on SharePoint. To work around this, add .htc extensions to the list of allowed file types:

  1. Copy the AllowHtcExtn.ps1 script file to the server that is running Microsoft SharePoint 2010.
  2. In the Windows PowerShell window or in the SharePoint Management Console, run the command: AllowHtcExtn.ps1 <Web Application URL>.

    Example: AllowHtcExtn.ps1 http://servername

    Alternatively, in SharePoint, set Browser File Handling to Permissive.

Microsoft Dynamics CRM List component tries to open WAC even when WordViewer.aspx is not available

By default in SharePoint, the Document Open setting is set to Open in Browser, and if Office Web Application Companion (WAC) is not installed on the SharePoint server, SharePoint opens the documents in the Office clients. In the Microsoft Dynamics CRM Beta release, even if WAC is not installed, the List component tries to open documents in WebViewer and fails. To work around this:

  1. Start Internet Explorer, and then open the SharePoint site collection.
  2. Click Site Actions, and then click Site Settings.
  3. Under Site Collection Administration, click Site Collection features.
  4. For Open Documents in Client Application by Default, click Activate.

Automatic creation always occurs in the document library with a name the same as the entity schema name

The automatic creation of the folders always occurs in the document library with the name the same as the schema name of the entity. For example, if the folder is being created for an account, the folder will always be created in the document library with the name account, which is the schema name of the Account entity in Microsoft Dynamics CRM. It is not possible to configure auto-creation of folders in another document library, such as customer. However, as a workaround, you can manually add a different document library from the SharePoint Document Locations (in the Navigation Pane, click Settings, click Document Management, click SharePoint Document Locations), and then select this document library in the Add Document Location dialog box. For more information, see the Microsoft Dynamics CRM List Component for Microsoft SharePoint Server 2010 Readme on the Microsoft Dynamics CRM List Component for Microsoft SharePoint Server 2010 download page.

An unhandled exception occurs when you try to enable Document Management if there are two entities with the same display name

In the Beta release, an unhandled exception occurs when you try to enable document management from the Document Management area and if there are two entities with the same display name.

You will not be able to enable Document Management for other entities except for the selected default (out-of-box) seven entities. In this case, automatic creation of folders will also not occur because you will not be able to specify the SharePoint site URL in the Document Management Settings dialog box. To work around this issue, change the display name of the entities to make sure that no two entities have the same name. There is no workaround to enable automatic creation in this case.

Customization and Solutions Known Issues

When you import translations, the dialog box for the import stays open indefinitely

The translation import works correctly, but you must manually close the progress dialog box for the import.

HTML is corrupted when you create a new HTML Web resource, and then open the Text Editor and view the Source tab

The workaround is to not use the Text Editor if Microsoft Silverlight objects are embedded in the HTML. Use an external text editor and upload to Microsoft Dynamics CRM.

Form Editor preview does not show unpublished changes to Web resources

To see the latest changes to Web resources using the Form Editor preview, you must first publish the Web resource.

N:N (Many-to-Many) entity relationships are not exported in a solution

For an N:N (Many-to-Many) entity relationship to be exported in a solution, both entities must be exported together.

Publishing an entity form does not publish required components

This issue may occur when a Web resource used by the form is edited from the Form Editor where there is no opportunity to publish the edited Web resource.

To make sure that all required components are published, publish them individually or use the Publish All action.

Managed solution components related to reused field security profiles cannot be uninstalled

Do not reuse existing security profiles in a managed solution.

Managed solution deletion (uninstall) fails because data in the solution entities cannot be deleted

Delete all data from managed solution entities before uninstalling the managed solution. For example, if your solution includes a School entity and if there are any School records on the system, delete all School records first, then delete the solution.

When upgrading to Microsoft Dynamics CRM 2011, unpublished OrganizationUI rows are not upgraded, and you lose unpublished customizations

The loss happens without any catastrophic failure during upgrade or run-time, and the overall upgrade process completes normally.

After upgrading to Microsoft Dynamics CRM 2011, the User entity form editor shows the Microsoft Dynamics CRM 4.0 version of the form and throws an exception when you try to publish the form

To avoid this, publish all your customizations before you upgrade to Microsoft Dynamics CRM 2011.

After upgrading to Microsoft Dynamics CRM 2011, the User entity form doesn't have Account Information and User Information sections

After upgrade, a system customizer can modify the user form so that the Account Information section that contains the User Name field is the first section of the first tab, and so that the Account Information section that contains the Windows Live ID field is the second section on that tab. The workaround succeeds because it puts the sections in the places where the form script expects them.

Form scripts for certain entity forms are not upgraded correctly

Form scripts are not updated correctly for entities that have a Service Calendar form. When the Service Calendar form loads, it might call a function designed for the entity main form, thus causing an error. The entities affected are:

When you customize one of these entities in Microsoft Dynamics CRM 4.0 and then upgrade to Microsoft Dynamics CRM 2011, a Web resource file named xxxx_main_library is created. The workaround is to open the form editor and fix this JScript library Web resource. They have to be split into individual files and functions manually.

When you upgrade to Microsoft Dynamics CRM 2011, a standard view on business entities and custom entities has the IsCustomizable property set to false

This happens for entity views that were customized in Microsoft Dynamics CRM 4.0. To workaround this issue, manually set the IsCustomizable property to true before exporting the view as part of a managed solution.

After upgrade a script error occurs when buttons configured using ISV.Config attempt to open a URL

If ISV.Config was used to add a custom button that opens a URL in Microsoft Dynamics CRM 4.0, and the entity does not use the ribbon in Microsoft Dynamics CRM 2011, a script error will occur when the button is used after the organization is upgraded to Microsoft Dynamics CRM 2011.

Error when importing a large solution can cause CPU utilization at 100 percent and cause the organization to become unusable

This is related to the issue described in KB 978430. To address the issue, you must request the Cumulative update package 7 for SQL Server 2008 Service Pack 1. Note that this patch applies only to SQL Server 2008 and not to SQL Server 2008 R2.

Import of a solution fails

Import of a solution with a large number of custom relationships might fail because it times out. The workaround is to split the large, failing solution into two or more smaller solutions.

After you import a solution, custom status reason values are not created correctly

The workaround is to import the solution twice. The second import will force an update, which will create the status reason values correctly. The exception is for custom activities, for which there is no workaround.

Users are unable to create or update records in a custom entity

When two managed solutions share a custom entity and they are both installed in the same organization, uninstalling the base solution (the solution that was installed first) leaves shared entities in an unusable state.

The workaround is to avoid uninstalling any of the solutions.

Your solution import fails, with the error "Cannot import component Attribute"

This happens when you import an updated solution that contains one or more custom activities. The workaround is to remove or comment out the ActivityId attribute in the customizations.xml file, and then try the import again.

International Known Issues

Microsoft Dynamics CRM 2011 Beta supports only 8 languages

The Beta release of Microsoft Dynamics CRM 2011 supports only the following 8 languages (with locale ID codes in parentheses): English (1033), French (1036), Italian (1040), German (1031), Spanish (3082), Japanese (1041), Chinese (Simplified) (2052), and Hebrew (1037).

Similarly, the base language of the server installation must be English (1033) for this release. After installing language packs for the additional supported languages, however, you can create organizations in any of these languages.

Support for additional languages is planned for the final release of Microsoft Dynamics CRM 2011.

Some English text or translated text from previously released versions of Microsoft Dynamics CRM may appear as placeholder text

The text displayed in the user interface for languages other than English may include some English text or translated text from previous versions of Microsoft Dynamics CRM as placeholder text. This placeholder text will be replaced with fully localized text for the final release of Microsoft Dynamics CRM 2011.

Document lists for items hosted on Windows SharePoint do not display in non-English languages

Integration between Microsoft SharePoint and Microsoft Dynamics CRM includes lists of documents hosted on the Windows SharePoint server. Users in organizations with base languages other than English will not be able to view document lists.

Data import mapping files for SalesForce.com are available only in English

The data import mapping files SalesForce.xml and SalesForceCustomizations.xml are available only in English.

To import data into Microsoft Dynamics CRM from SalesForce.com, switch your user interface language selection to your organization's base language.

Sample data for goals fails to import in localized languages

Sample data failing to import for the Goal entity is a known issue for this release. There is no workaround at this time.

Help, Resource Center, and other content areas are not localized for Microsoft Dynamics CRM 2011 Beta

Content areas that support Microsoft Dynamics CRM 2011 Beta, including Help and the Resource Center, have not been localized for this release. Until the final release of Microsoft Dynamics CRM 2011, these content areas will be available only in English.

Documentation Feedback

The Microsoft Dynamics CRM Documentation Team welcomes your suggestions and comments about the documentation. You can quickly and directly send e-mail feedback to Documentation Feedback. All feedback must be in English. Your feedback will be used to make improvements to the content.

Copyright

This document is provided "as-is". Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it.

Some examples depicted herein are provided for illustration only and are fictitious.  No real association or connection is intended or should be inferred.

This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes.

© 2010 Microsoft Corporation. All rights reserved.

Microsoft, Active Directory, Azure, Excel, Internet Explorer, Microsoft Dynamics, Outlook, SharePoint, Silverlight Windows, Windows Live, Windows Vista, and Visual Studio are trademarks of the Microsoft group of companies.

All other trademarks are property of their respective owners.