Sign in

Microsoft.com

Microsoft

Remove From My Forums

MSCRM Migration 3.0 to 4.0 failure with exception "Microsoft.Crm.Setup.Server.WorkFlowUpgradeAction" failed.

Question
0

Sign in to vote

I am working on migartion from MSCRM 3.0 to 4.0 version by running MSCRM 4.0 upgrade over existing 3.0 installation. I am facing a sever problem in migration of workflows and migration wizard is not reaching successful stage. Migration ran for more than 20 hrs but didn't succeed. For Initial 2 hrs wizard completed few of activities and reached the Workflow migration stage and after 18 hrs finally thrown the error message - "Microsoft.Crm.Setup.Server.WorkFlowUpgradeAction" failed.

I followed the whitepaper published by MS on CRM Optimizing Performance page 16-18 at location http://www.microsoft.com/downloads/details.aspx?FamilyID=6B32E0B3-5520-48A7-B3CD-D8477D084821&displaylang=en.

Originally there were 400000 records in wfprocessInstance table which got reduced to 60,000 after we ran the query to purge old workflow log records with the exception of sales process log information.

No of records in WFlowProcessInstance - 59,256

· No of records in wfRuleLog - 124508

· No of records in wfActionLog - 585586

Total size of CRM database – 12GB.

Disk space available on CRM database drive – 65 GB.

Disk Space available on TempDb database is 30 GB.

Available RAM - 16GB

Please let me know if anyone faced such a problem and how to handle this situation.

Appreciate help.

Thanks,

Vijayendra

Tuesday, August 5, 2008 8:38 PM

Answers

0

Sign in to vote
There's another thread on this topic: http://forums.microsoft.com/Dynamics/ShowPost.aspx?PostID=3521181&SiteID=27

The thread indicates that you can safely ignore workflow conversion errors. That's my belief as well. I've upgrade several 3.0 systems to 4.0 and often run into the error you mentioned.

The CRM 4.0 setup application upgrades workflow instances after all other upgrade tasks; there's nothing significant that occurs after workflow upgrades. Thus, you can ignore the error and then manually start workflows if necessary. Of course, it's best to upgrade without seeing any errors but at least this is one that you should be able to work around.

-Tim
- Marked as answer by Jim Glass Jr Tuesday, June 23, 2009 8:48 PM
Wednesday, August 6, 2008 11:15 PM

All replies

0

Sign in to vote

did you stop the workflow while upgradation?

For More see MS CRM Support section

http://support.microsoft.com/ph/12976

Regards,
Imran

http://www.crmxperts.com

Wednesday, August 6, 2008 12:45 PM

Moderator
0

Sign in to vote
There's another thread on this topic: http://forums.microsoft.com/Dynamics/ShowPost.aspx?PostID=3521181&SiteID=27

The thread indicates that you can safely ignore workflow conversion errors. That's my belief as well. I've upgrade several 3.0 systems to 4.0 and often run into the error you mentioned.

The CRM 4.0 setup application upgrades workflow instances after all other upgrade tasks; there's nothing significant that occurs after workflow upgrades. Thus, you can ignore the error and then manually start workflows if necessary. Of course, it's best to upgrade without seeing any errors but at least this is one that you should be able to work around.

-Tim
- Marked as answer by Jim Glass Jr Tuesday, June 23, 2009 8:48 PM
Wednesday, August 6, 2008 11:15 PM
0

Sign in to vote

Tim,

I am trying to migrate a MS CRM 3.0 implementation to MS CRM 4.0, with little success. The 3.0 system uses a lot of customisation including Javascript, Custom forms/entities, workflows, call outs and mail merge. Can you please share your experience/ approach(s) to successfully migrate the system? Any help on this will be most appreciated.

Regards

Abhishek P.

Monday, December 1, 2008 7:02 AM