Thursday, June 5, 2014

Dynamics GP 2013 R2 upgrade: The following SQL statement produced an error: exec wfDeployClrAssemblies

During the upgrade process to Dynamics GP 2013 R2 with one of my customers we got the error in the subject, the issue is with dropping one of the SQL level Assemblies called “System.DirectoryServices” that been used by “Microsoft.Dynamics.GP.WorkflowGP.WorkflowEngine”.

The "System.DirectoryServices" assembly is being used by the Workflow module in Dynamics GP, if you have workflow installed you will not be able to drop this reference as you will be having another assembly depending on this and the other assembly is being used by 7 functions and stored procedures.

This assembly basically is used to connect your active directory and get the needed details that are being used by the system, dropping all these objects is safe as the upgrade process will automatically create them back for you.

To resolve the issue, first find the following functions and stored procedures, right click them one by one and hit drop:


Go to DYNAMICS database and navigate “Programmability>> Assemblies” and find “Microsoft.Dynamics.GP.WorkflowGP.WorkflowEngine”, right click the assembly and hit drop and then drop “System.DirectoryServices”:


Reinitiate Dynamics GP Utilities and and the upgrade will proceed safely, don’t worry about the deleted objects as the upgrade will recreate them all.

Hope that this helps.


Mohammad R. Daoud MVP - MCT
+962 - 79 - 999 65 85


SQL Training said...

Such a nice post on SQL Training. I found it very useful for me. Thanks for sharing such an informative post.

Bruce Bowsher said...

Worked for me. Thank you!

Unknown said...

Please help me, I cannot find the GetAssignedUsers or the sendworkflow*.* statements.

I have a client waiting to get their year end update done on this and am stressed out....

Ginger Knott

Tallguy said...

Thank you, thank you , thank you. I don't know how we would survive without these valuable posts....

Sean Y said...

For me it had something to do with the affinity checkbox for CPUs. On the SQL Studio I had my CPU affinity manually checked and I changed it to automatic then ran the setup again. It worked.

Related Posts:

Related Posts with Thumbnails