Skip to main content
Post a question

Notifications

Community site session details

Community site session details

Session Id : ozF0VR7SYFksro0BvqIDhV
Microsoft Dynamics GP (Archived)

Workflow 2.0 error sending approval emails

Like (0) ShareShare
ReportReport
Posted on 1 Aug 2017 15:06:22 by

I have a client that upgraded to Dynamics GP 2016 (R2) build, 16.00.0579 running on SQL 2014 version 12.0.5203.0. They are now implementing PO Requisition workflow. The configuration and test approval emails processed without issue. When we attempted to send from a Windows 7 workstation, Dynamics GP returned the below error and the approval email was not sent.

workflow2.0.png

Subsequently all approval emails have stopped working. I followed the KB to drop the .Net assemblies and ran, exec wfDeployClrAssemblies to add them back. Running the deploy command returned the below top two lines and 44 warnings regarding the individual assemblies, and made no change in our results.

 

(1 row(s) affected)

Configuration option 'clr enabled' changed from 1 to 1. Run the RECONFIGURE statement to install.

Warning: The Microsoft .NET Framework assembly 'system.directoryservices, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.

 

The servers and SQL instance are on premise, but the warning message specifies hosted. Has anyone resolved this?

 

*This post is locked for comments

  • Suggested answer
    Beat Bucher  GP Geek  GPUG All Star Profile Picture
    28,058 Moderator on 28 Dec 2021 at 15:19:31
    RE: Workflow 2.0 error sending approval emails

    I know this was never answered, but I ran into this exact same error message after a customer was upgraded to the latest Fall 2012 release in GP, and workflows that used to work before, suddenly started to fail with the above error message.

    I had found this blog post from Microsoft (written by Dan Peletier back in 2016), but none of the errors listed would apply to this particular case.

    However, a comment left by a community member may lead to some solution, which I haven't yet tested, but asked the customer to check for in case they bump into the error again.

    community.dynamics.com/.../net-framework-errors-with-workflow-2-0

    I'll post back here in case of any update on this matter.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

🌸 Community Spring Festival 2025 Challenge 🌸

WIN Power Platform Community Conference 2025 tickets!

Jonas ”Jones” Melgaard – Community Spotlight

We are honored to recognize Jonas "Jones" Melgaard as our April 2025…

Kudos to the March Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 293,440 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 232,569 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,158 Moderator

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans
Loading complete