I’ve assisted a few clients to upgrade to Microsoft Dynamics GP 2018 recently and have seen two different errors cause problems with Workflow.
As part of the upgrade process, database objects are deployed and various scripts run against them. This includes the wfdeployclrassemblies stored procedure which deploys the .NET Assemblies required by Workflow for such tasks as AD lookups and sending of emails.
However, I’m going to make the running of this stored procedure a standard, manual, part of the upgrade as I am finding that if it isn’t run after the upgrade is complete, that AD lookups don’t work until it is (this usually manifests in approvals failing to find a user to email or approvals failing if the user had the email from before the upgrade). I might was preempt and do it manually every time in order to give clients a smoother process. To run the stored proc, open SQL Server Management Studio and, against the system database, typically called DYNAMICS run the following (it’ll take a few minutes):
exec wfdeployclrassemblies
The other issue I’ve now seen more than once (and have also seen when upgrading some clients to prior versions), is that during the upgrade the Workflow managers are lost:
The manager being missing results in a request error:
Selecting a workflow manager again, resolves the problem and users are able to approve (or reject) documents.
What should we write about next?
If there is a topic which fits the typical ones of this site, which you would like to see me write about, please use the form, below, to submit your idea.
2 thoughts on “Workflow Approval Request Error After Upgrade”