chome81
asked on
Error when upgrading from CRM 3.0 to CRM 4.0. "Action Microsoft.Crm.Setup.Common.RegisterAsyncServiceAction failed"
Hello,
We've been working on our CRM upgrade for the last two days and we're at a stopping point with this latest error.
"Action Microsoft.Crm.Setup.Common
There seems to be a lot of info online regarding this error, but so far nothing has worked. We tried uninstalling/reinstalling .net framework. We tried following this KB http://support.microsoft.com/kb/949092. Tried changing the Async Service to start as a domain account rather then the network service. Nothing is fixing our issue. Any ideas on how to fix this? Seems like there much be a logical explanation... Any help is appreciated.
Thanks!
image.jpg
We've been working on our CRM upgrade for the last two days and we're at a stopping point with this latest error.
"Action Microsoft.Crm.Setup.Common
There seems to be a lot of info online regarding this error, but so far nothing has worked. We tried uninstalling/reinstalling .net framework. We tried following this KB http://support.microsoft.com/kb/949092. Tried changing the Async Service to start as a domain account rather then the network service. Nothing is fixing our issue. Any ideas on how to fix this? Seems like there much be a logical explanation... Any help is appreciated.
Thanks!
image.jpg
Aftab_Khateeb
can you please provide me the log file for this install. it would be found at location C:\Documents and Settings\{username}\Applic
ASKER
Actually it appears that we were able to get thru this portion of the install without error today. We reverted back to our 3.0 snapshots and started from scratch. We took two actions.
One, we ran a fresh windows update to get any of the latest .NET Framework Service Packs and potentially fix any .NET files issues.
Two, we ran lodctr /r to reload any counters. We did this previously, but this time it wasn't after manually clearing out many reg keys from the MS KB.
Our install isn't complete yet, but it did get past that stage. Currently is 3 hours into the Workflow Upgrade portion.
One, we ran a fresh windows update to get any of the latest .NET Framework Service Packs and potentially fix any .NET files issues.
Two, we ran lodctr /r to reload any counters. We did this previously, but this time it wasn't after manually clearing out many reg keys from the MS KB.
Our install isn't complete yet, but it did get past that stage. Currently is 3 hours into the Workflow Upgrade portion.
ok let me know if you have any issues with it
ASKER
Any guess on how long (worst case scenario) I'll have to wait on this Workflow Upgrade portion? Going on 3.5 hours. It it doesn't finish soon, I'll have to abort the upgrade.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ended up aborting and reverting to my 3.0 snapshot. Will have to kick it off again on a Friday evening so I have more time to let it run. This time I'll delete the workflow logs prior to kicking it off.