Filter
Top Products
Microsoft Dynamics CRM 4.0 Installing Guide
2-26
“One or more workflows could not be upgraded” message
received during upgrade
Because of changes in workflow and sales process functionality with Microsoft Dynamics CRM
4.0, some workflows cannot be upgraded. Although Setup indicates that the upgrade was not
successful, in most cases the rest of the Microsoft Dynamics CRM 4.0 application will function as
expected.
For a list of those workflows, including an explanation, see the server Setup log file. By default,
the log file is located at:
<systemdrive>:\Documents and Settings\<User>\Application
Data\Microsoft\MSCRM\Logs\crm40svrsetup.log
For more information about how workflows are upgraded, see “Chapter 4: Planning Deployment”
in the Microsoft Dynamics CRM 4.0 Planning Guide.
Sales processes are upgraded to workflows
In Microsoft Dynamics CRM 3.0, only sales processes could include stages, and they were only
able to take action on the Opportunity entity. In other words, sales processes were a special type
of workflow. In Microsoft Dynamics CRM 4.0, all workflows support stages on all types of entities.
Therefore, all Microsoft Dynamics 3.0 sales processes are converted to standard workflows
during the upgrade process. If the upgrade is successful, the underlying logic of the new workflow
is unaffected, including stages and the primary entity (Opportunity).
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 is invalid or does not exist on the server that is being upgraded, upgrade of that
workflow and all related workflow jobs will not succeed. The following list includes examples of
referenced objects that can cause a workflow upgrade to fail:
• Missing attachments
• Missing or invalid custom entities, attributes, and relationships
• Missing or invalid custom workflow activities (.NET 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 due to a missing or invalid
referenced object, open Workflow Manager, correct the problems described in the log file, and
continue the upgrade process. Specifically, remove or replace references to invalid, missing, or
unsupported objects and correct inconsistencies between owners and business units.
Server Setup fails with “The process cannot access the file
because it is being used by another process. (Exception from
HRESULT: 0x80070020)” error message
Microsoft Dynamics CRM Server Setup may fail with a “The process cannot access the file
because it is being used by another process. (Exception from HRESULT: 0x80070020)” error
message. This issue can occur when the following conditions are true: