Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics GP (Archived)

Workflow 2.0 error sending approval emails

(0) ShareShare
ReportReport
Posted on by Microsoft Employee

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
    Beat Bucher GP Gee... 28,054 Super User 2024 Season 1 on at
    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

Congratulations 2024 Spotlight Honorees

Kudos to all of our 2024 community stars! 🎉

Meet the Top 10 leaders for December

Congratulations to our December super stars! 🥳

Start Your Super User Journey

Join the ranks of our community heros! 🦹

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,711 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,458 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans