Microsoft Dynamics CRM 4.0

You cannot upgrade Microsoft Business Solutions CRM 1.2, or any pre-release version of Microsoft Dynamics CRM 4.0, to the final release of Microsoft Dynamics CRM 4.0.

However, Microsoft Dynamics CRM 3.0 is supported for upgrade.

Upgrade Known Issues

This section describes known issues that may occur when you upgrade Microsoft Dynamics CRM 3.0 Server to Microsoft Dynamics CRM 4.0 Server.

Stop all instances of the Microsoft Dynamics CRM Workflow service before running Setup

If you have multiple Microsoft Dynamics CRM 3.0 servers running multiple instances of the Microsoft Dynamics CRM Workflow service, you must stop all the Microsoft Dynamics CRM Workflow services before you run Setup. If you do not stop all the services, workflow jobs that are running may be lost.

Workflow rules and workflow instances on additional servers are not upgraded to Microsoft Dynamics CRM 4.0

In a multi-server configuration of Microsoft Dynamics CRM 3.0, it is possible to have unique workflow rules and workflow assemblies on each server. Similarly, each server may have active workflow instances. However, the upgrade process for Microsoft Dynamics CRM 4.0 only upgrades workflow rules, workflow assemblies, and workflow instances for one server.

To make sure that there are no active workflow instances on these additional servers during the upgrade process, shut down the additional servers before you start the upgrade to Microsoft Dynamics CRM 4.0. To make sure that any unique workflow rules or workflow assemblies are also upgraded, copy them from the additional servers to the primary server that will be upgraded.

Notes with over 100,000 characters will be truncated in records

During a Microsoft Dynamics CRM Server upgrade, records that have notes with more than 100,000 characters will be truncated. When this occurs, any text that follows the 100,000th character is not included in the record after the upgrade is complete.

Environment Diagnostics Wizard warning: Indexes on the Microsoft Dynamics CRM database are not consistent with Microsoft Dynamics CRM 3.0 indexes

If you continue with the upgrade after you receive this warning, Microsoft Dynamics CRM may not install successfully, unless the added indexes are removed and any modified indexes are replaced by the original Microsoft Dynamics CRM 3.0 database indexes. For detailed information about the indexes that are not consistent, view the Server Setup log (crm40svrsetup.log). By default, this log is located in the %appdata%\Microsoft\MSCRM\Logs\ folder. If you need help resolving this problem, contact Microsoft Customer Support Services.

Environment Diagnostics Wizard warning: Statistics were detected on the Microsoft Dynamics CRM database that are not consistent with the Microsoft Dynamics CRM 3.0 database

Although the Environment Diagnostics Wizard Help indicates that Setup should complete successfully, if you continue with the upgrade after you receive this warning, Microsoft Dynamics CRM may not install successfully. We recommend that you remove the statistics before you continue. For detailed information about this issue, view the Server Setup log (crm40svrsetup.log). By default, this log is located in the %appdata%\Microsoft\MSCRM\Logs\ folder. If you need help resolving this problem, contact Microsoft Customer Support Services.

'OutOfMemoryException' error message during Microsoft Dynamics CRM Server upgrade

This error can occur when the Microsoft Dynamics CRM Server Setup program has insufficient memory to run. To work around this issue, you can reduce how much memory the instance of Microsoft SQL Server is using. For more information about how to configure SQL Server memory, see the SQL Server Help.

Some Microsoft Dynamics CRM 3.0 reports cannot be upgraded

Because of changes to the reporting feature, some Microsoft Dynamics CRM 3.0 reports cannot be upgraded to Microsoft Dynamics CRM 4.0 reports. For those reports that cannot be upgraded, Microsoft Dynamics CRM 4.0 provides reports that are similar in functionality. During the upgrade process, the following known reporting upgrade failures will appear in the <systemdrive>:\Documents and Settings\<User>\Application Data\Microsoft\MSCRM\Logs\crm40svrsetup.log:

· Unable to preserve expression link from parent report 'Neglected Cases Detail' to child report '="Neglected Cases Detail"'

· Unable to preserve expression link from parent report 'Campaign Performance Sub-Report' to child report '= IIF(Fields!category.Value = "Orders Placed", ReportItems!txtCampaignPlacedOrderDetail.Value, IIF(Fields!category.Value = "Opportunities Realized", ReportItems!txtCampOppRealizedRevenueDetail.Value, IIF(Fields!category.Value = "Opportunities Estimated",ReportItems!txtCampOppEstimatedRevenueDetail.Value, System.dbnull.value )))'

· Unable to preserve expression link from parent report 'Account Summary Sub-Report' to child report '="Account Summary Sub-Report"'

· Unable to preserve expression link from parent report 'Top Knowledge Base Articles Detail' to child report '="Top Knowledge Base Articles Detail"'

· Unable to preserve expression link from parent report 'Neglected Leads Detail' to child report '="Neglected Leads Detail"'

· Child report has multiple parents. Unable to preserve link from parent report 'Campaign Comparison' to child report 'Campaign Performance Sub-Report'

· Circular parenting detected. Unable to preserve link from parent report 'Neglected Cases' to child report 'Neglected Cases Detail'

· Circular parenting detected. Unable to preserve link from parent report 'Competitor Win Loss' to child report 'Competitor Win Loss Details'

· Circular parenting detected. Unable to preserve link from parent report 'Neglected Leads' to child report 'Neglected Leads Detail'

· Circular parenting detected. Unable to preserve link from parent report 'Top Knowledge Base Articles' to child report 'Top Knowledge Base Articles Detail'

Workflows that include references to objects that are invalid or do not exist cannot be upgraded

If a Microsoft Dynamics CRM 3.0 workflow references a record, entity, attachment or other type of object that does not exist on the server that is being upgraded, upgrade of that workflow and all related workflow jobs will fail. The following list includes examples of referenced objects that can cause a workflow upgrade to fail:

Missing attachments
Missing or invalid custom entities, attributes, or relationships
Missing or invalid custom workflow activities (Microsoft .NET Framework assemblies or .NET methods)
Unsupported attributes (attributes that have been deprecated since the previous release)
Inconsistencies between the workflow owners and the business units to which they belong

If any workflows or workflow jobs are not successfully upgraded because of a missing or invalid referenced object, open Workflow Manager, correct the problems described in the log file, and continue the upgrade process. Remove or replace references to invalid, missing, or unsupported objects, and correct inconsistencies between owners and business units.

Some workflow jobs are no longer visible to the users who owned them in Microsoft Dynamics CRM 3.0

In Microsoft Dynamics CRM 3.0, workflow jobs were owned by the users who owned the records that the workflow job was taking action on. However, in Microsoft Dynamics CRM 4.0, workflow jobs are owned by the user who owns the workflow that started the workflow job. For example, a sales process that is running on an opportunity in Microsoft Dynamics CRM 3.0 would be visible to the user who owned the opportunity record. However, because of improved security features in Microsoft Dynamics CRM 4.0, workflow jobs may no longer be visible under certain circumstances. Specifically, if the user who owns the upgraded workflow differs from the user who owns the record, the workflow jobs taking action on the record will not be visible to the record owner.

If you want workflow jobs to be visible to users in your organization, increase the access level for the Workflow and System Job entities (workflow jobs are a special type of system job). For example, increase the access level for these entities from User to Business Unit.

Some attributes supported by workflow rules in Microsoft Dynamics CRM 3.0 are not supported by workflows in Microsoft Dynamics CRM 4.0

Although many new attributes are available to workflows in Microsoft Dynamics CRM 4.0, support for some attributes has been deprecated. The attributes in the following table are no longer supported.

Entity Name	Attribute Name	Entity Name	Attribute Name
Account	importsequencenumber	Lead	customeridtype
Account	owneridtype	Lead	importsequencenumber
Appointment	importsequencenumber	Lead	owneridtype
Appointment	isbilled	Letter	importsequencenumber
Appointment	isworkflowcreated	Letter	isbilled
Appointment	owneridtype	Letter	isworkflowcreated
Appointment	owninguser	Letter	owneridtype
Appointment	regardingobjecttypecode	Letter	owninguser
Campaign	importsequencenumber	Letter	regardingobjecttypecode
Campaign	owneridtype	Marketing List	importsequencenumber
Campaign Activity	importsequencenumber	Marketing List	owneridtype
Campaign Activity	owneridtype	Marketing List	statuscode
Campaign Activity	regardingobjecttypecode	Opportunity	customeridtype
Campaign Response	importsequencenumber	Opportunity	importsequencenumber
Campaign Response	originatingactivityidtypecode	Opportunity	owneridtype
Campaign Response	owneridtype	Phone Call	importsequencenumber
Campaign Response	regardingobjecttypecode	Phone Call	isbilled
Contact	importsequencenumber	Phone Call	isworkflowcreated
Contact	owneridtype	Phone Call	owneridtype
Contact	parentcustomeridtype	Phone Call	owninguser
Contract	billingcustomeridtype	Phone Call	regardingobjecttypecode
Contract	customeridtype	Product	importsequencenumber
Contract	importsequencenumber	Quote	customeridtype
Contract	owneridtype	Quote	importsequencenumber
E-mail	compressed	Quote	owneridtype
E-mail	importsequencenumber	Order	customeridtype
E-mail	isbilled	Order	importsequencenumber
E-mail	isworkflowcreated	Order	owneridtype
E-mail	messageid	Service Activity	importsequencenumber
E-mail	owneridtype	Service Activity	isbilled
Email	owninguser	Service Activity	isworkflowcreated
E-mail	regardingobjecttypecode	Service Activity	owneridtype
E-mail	sender	Service Activity	regardingobjecttypecode
E-mail	torecipients	Subject	createdby
Fax	importsequencenumber	Subject	createdon
Fax	isbilled	Subject	description
Fax	isworkflowcreated	Subject	importsequencenumber
Fax	owneridtype	Subject	modifiedby
Fax	owninguser	Subject	modifiedon
Fax	regardingobjecttypecode	Subject	parentsubject
Case	customeridtype	User	importsequencenumber
Case	importsequencenumber	User	isdisabled
Case	owneridtype	Task	importsequencenumber
Invoice	customeridtype	Task	isbilled
Invoice	importsequencenumber	Task	isworkflowcreated
Invoice	owneridtype	Task	owneridtype
		Task	regardingobjecttypecode
		Territory	importsequencenumber

Workflows can be started on changes to Status Reason values in addition to Status values

In Microsoft Dynamics CRM 3.0, workflows could not be started by changes to the values in a record’s Status Reason field. However, in Microsoft Dynamics CRM 4.0, changes to status reasons are now supported as attribute changes. Because status reasons are tied to specific statuses, a workflow that started automatically when a status changed may now start when the associated status reason changes.

If your implementation of Microsoft Dynamics CRM 3.0 included logic to detect changes to the status of a record, review the upgraded workflow in Microsoft Dynamics CRM 4.0 to make sure that the new logic starts the workflow based on the correct combination of status and status reason.

Setup Known Issues

This section is a description of known issues that may occur when you install Microsoft Dynamics CRM 4.0 Server.

License key

If you purchase Microsoft Dynamics CRM through a Microsoft Volume Licensing program, the license key is provided in the license.txt file. The license.txt file is included in the Microsoft Dynamics CRM installation files.

Environment Diagnostics Wizard message: Database version is later (or earlier) than expected; Help topic is incomplete

During Setup when you select to connect to an existing deployment, or when you use Deployment Manager to import an organization, you may receive an Environment Diagnostics Wizard message that the database is a later version or an earlier version. When you click Help, the help topic describes the message as a warning, but in some cases when the database major version is later, this message is actually an error and Setup cannot continue. The database version is determined as MajorVersion.MinorVersion.BuildVersion.Revision, such as 4.0.7333.03.

Method not found: 'Microsoft.Crm.CrmKeySetting Microsoft.Crm.CrmKeySetting.CreateKeySetting (Microsoft.Crm.CrmKeyType, Microsoft.Crm.SharedDatabase.ConfigSku)' error message when you run Microsoft Dynamics CRM 4.0 Server Setup

You may receive this error message when you run Microsoft Dynamics CRM 4.0 Server Setup on a computer that has Microsoft Dynamics CRM “4” Community Technology Preview (CTP) 3 Server installed. To avoid this problem, use Add or Remove Programs to remove Microsoft Dynamics CRM “4” CTP 3 Server before you run Microsoft Dynamics CRM 4.0 Server Setup. Notice that, after you experience this problem you cannot use Add or Remove Programs to remove Microsoft Dynamics CRM “4” CTP 3 Server.

Administrator Applications Known Issues

This section describes known issues that may occur when you use specific Microsoft Dynamics CRM administrator applications, such as Deployment Manager.

'Cannot open service control manager on computer 'ServerName'. This operation might require other privileges.' error message when using the Server Manager area in Deployment Manager

This error message can occur when the Deployment Manager application is open for a long time, or several operations have been performed. To resolve this problem, start the application again.

Web Application Known Issues

This section has a known issue that may occur when you use the Microsoft Dynamics CRM Web application.

Users cannot connect to other organizations in the deployment after the default organization has been disabled

Users cannot connect to an organization when the following conditions are true:

· You have multiple organizations in the deployment and you disable the default organization. Notice that, the default organization appears in Deployment Manager as OrganizationName (Default), where OrganizationName is the name of the organization. You can disable the default organization in Deployment Manager or by using the methods that are described in the Microsoft Dynamics CRM 4.0 Software Development Kit (SDK).

· You restart Internet Information Services (IIS) services.

To work around this problem, select one of the following options:

· Change the default organization to a different organization that is enabled. To do this, start Deployment Manager, click Organizations, right-click an enabled organization that you want to set as the new default organization, and then click Set as Default Organization.

· Enable the default organization. To do this, start Deployment Manager, click Organizations, right-click the default organization, and then click Enable.

Activity parties are granted read privileges to appointment activities

When you add a required, or optional, party to an appointment activity, all activity parties are granted read-only access. This behavior occurs because Microsoft Dynamics CRM 4.0 grants only read access to activity parties to help make appointment data more secure. Earlier versions of Microsoft Dynamics CRM granted all access. Because of this design, activity parties can no longer modify the appointment record.

Import Wizard cannot import an exported file

When you try to import a comma separated values (CSV) file, the import may fail. This can occur when the following conditions are true:

· The file that you are trying to import is created from an export, such as an exported list of “My Active Accounts.”

· The list includes e-mail addresses.

To work around this issue, you can remove the E-mail (Primary Contact) column before you import the file.

Custom entity cannot be imported to a new system when duplicate detection has been enabled and then disabled

The error message that you may receive is "Either the file could not be uploaded or Import failed.” An additional message contains a reference that includes the name of the custom entity and the text "A SQL Server error occurred.” This error will occur when you try to import a custom entity into a new system if the custom entity had had duplicate detection enabled but now has duplicate detection disabled. To work around this issue, turn duplicate detection on for the custom entity before you export it. After the custom entity is imported to a new system, disable duplicate detection for the custom entity.

Moving a user from one business unit to another causes organization-level workflows, owned by that user, to stop running

In Microsoft Dynamics CRM 3.0, workflow rules were associated with the organization. Even when the administrative user who owned the workflow was moved between business units, a workflow rule owned by that user would continue to run. In Microsoft Dynamics CRM 4.0, workflows are owned by individual users. A workflow’s scope limits the records on which workflow jobs can take action. Because of this change in behavior between Microsoft Dynamics CRM 3.0 and 4.0, workflows with an organization scope, owned by a specific user, will stop working when that user is moved from the current business unit to another business unit.

Before moving a user between business units, determine whether the user owns any organization-level workflows and reassign any workflows of this type to a user who will remain in the first business unit.

Changes to Opportunity form labels due to changes in workflow functionality

The display labels for the stepname and salesstagecode attributes of the Opportunity entity have been changed to reflect updates in workflow functionality in Microsoft Dynamics CRM 4.0. The following table lists those changes.

Attribute Name	Label in 3.0	Label in 4.0	Description
stepname	Step Name	Pipeline Phase	Current phase in the sales pipeline for the opportunity. To be updated by using workflows.
salesstagecode	Sales Stage	Process Code	Customizable code that represents the current stage of an opportunity in a manual sales process. This supports manual sales processes upgraded from earlier versions of Microsoft Dynamics CRM.

In Microsoft Dynamics CRM 3.0, the stepname attribute was controlled by the default sales process (a special type of workflow for opportunities). Because more than one workflow can take action on an opportunity in Microsoft Dynamics CRM 4.0, this field no longer automatically displays the current stage of a workflow job that is active on that opportunity. If you want to update this attribute by using one or more workflows, you must add logic to your workflow to do this.

In Microsoft Dynamics CRM 3.0, the salesstagecode attribute was not controlled by sales processes; this supports manual sales processes through client-side scripting. If any custom drop-down list (picklist) values were present for the salesstagecode attribute in Microsoft Dynamics CRM 3.0, both the list values and the scripts will be retained during the upgrade to Microsoft Dynamics CRM 4.0. However, customers are encouraged to use the new workflow feature in Microsoft Dynamics CRM 4.0 to implement more robust behavior.

Microsoft Dynamics CRM Documentation

Microsoft Dynamics CRM Implementation Guide

The Microsoft Dynamics CRM Implementation Guide is available for download. This guide has the system requirements and installation instructions to install Microsoft Dynamics CRM 4.0.

This implementation guide is written for those responsible for deploying Microsoft Dynamics CRM 4.0.

Microsoft Dynamics CRM SDK

The Microsoft Dynamics CRM Software Development Kit (SDK) for developers, system customizers, and report writers is available for download. The SDK package covers the following topics:

Supported extension mechanisms
Architectural overview of Microsoft Dynamics CRM
Entity model
Security model
Web services
Coding for the server and for the client
Plug-ins
Data migration
Custom workflow activities
Forms scripting
Integration of custom Web pages and other UI elements
Customizing online help

Additionally, you’ll find a user interface style guide, walkthroughs, tools for registering plug-ins and custom workflow activities, and lots of sample code. The documentation also is posted live on the Microsoft Dynamics CRM Developer Center, along with other helpful links for developers and system customizers.

Documentation Feedback

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

Copyright

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

Microsoft, Microsoft Dynamics, Active Directory, Outlook, SQL Server, and Visual Studio are trademarks of the Microsoft group of companies.

All other trademarks are property of their respective owners.