web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

A.NET Framework error

(0) ShareShare
ReportReport
Posted on by

Microsoft SQL Server Native Client 11.0 SQL Server A.NET Framework error occurred during execution of user-defined routine or Aggregate "SendWorkflowCompletionEmail" System.IO.FileLoadException:  Could not load file or assembly 'System.DirectorySer{

HELP - no idea where to go or how this happened.

Only thing done in the workflow process was to change the email to send notifications to a different person.

Now this happens when entering PO's

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Peter Muchira Profile Picture
    1,912 on at

    Hello,

    Run this against your Dynamics(system) database:

    exec wfDeployClrAssemblies

    Check this link for more discussions, and see if it helps:

    community.dynamics.com/.../138112

  • Community Member Profile Picture
    on at

    Yeah - that worked!

  • Derek Albaugh Profile Picture
    Microsoft Employee on at

    I also wanted to mention that we've seen a couple of support cases in the last day or so, that having the 'KB 3102467' .NET Framework patch installed has been seen to 'break' Workflow 2.0 as well. The patch has been out for a while, so odd that we're starting to see it just recently.

    Also, this patch doesn't necessarily break it on all machines, as we've installed it on machines of our own and it has no issues with Workflow 2.0.

    This being said, running the 'Exec wfDeployClrAssemblies' script against the DYNAMICS/system database for Dynamics GP resolves the issue. I just wanted to put this information out here as well.

    We did see one customer on Dynamics GP 2013 R2 where this didn't work so they had to uninstall the KB 3102467 patch and that fixed the issues. Our thinking is that for GP 2013 issues, we may need to manually drop the functions, procedures and assemblies the wfDeployClrAssemblies procedure creates and that will resolve it.

    Thank you

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
HP-11021721-0 Profile Picture

HP-11021721-0 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans