Open Forum

  • 1.  Failing WF submission after 18.4 upgrade with error on "SendWorkFlowAssignmentEmail" ?

    GPUG ALL STAR
    Posted 13 days ago
    This question is for the more technical Admins here that might have run into this in the past..
    One customer is receiving this after their GP got upgraded from 18.3 to 18.4.1361. Before upgrade the WF submission was working fine with e-mail notifications, after the upgrade that started getting this error message every time a WF was submitted which includes an E-mail notification to be sent out (not all of them do have that, but most) and it took some time to realize the check box in the WF setup for e-mailing was the trigger..


    I found multiple recommendations and MS blog posts about this specific error message and re-ran the script "wfDeployClrAssemblies" against the system DYNAMICS DB, but it didn't changed anything. I've been trying to check for various event logs entries related to .NET libraries, but with no success. Only GP was upgraded on that site, nothing was updated on the Windows side or .NET (which is at version 4.7.xxx)

    Any ideas where else I can look for a fix ?

    ------------------------------
    Beat Bucher
    Business Analyst, Dynamics GP SME
    Montreal QC/Canada
    @GP_Beat http://www.gp-geek.com
    Montreal QC GPUG Chapter Leader
    MBS MVP (2015-2018)
    All-Star 2013
    ------------------------------
    Academy - Online Interactive Learning from Experts


  • 2.  RE: Failing WF submission after 18.4 upgrade with error on "SendWorkFlowAssignmentEmail" ?

    Posted 12 days ago
    i would still check the event viewer for SQL client errors and not necessarily .NET.  The error is being raised within .NET but from the SQL client 11 software,  If i were a betting man, I would say you need to reinstall the sql 11 native client and check to see if your system has the SQL 10 native client.  Also, as you know these are 32 bit odbc components so make sure you have those two pieces of software installed as 32 bit odbc drivers and that you can even create 32 bit odbc connections to your database.  If you cannot create the connections i have mentioned, start there and make sure these things are being installed on your workstations and your sql server.  You might want to be sure that you install GP on the server, since this is not an sql object , but rather a user object that MS must use for their workflows to send email, if you don't have the GP software installed, the sql server may not have had .net properly updated to use the referenced object causing your error.

    Something else to check, i noted that on another blog post it seems you might have a user who is set in order to send messaged to users on their behalf.  This setting which called  mail.from.enabled=false is set to false. locate your config files on your workflow setup config files.   good luck, let us know the eventual answer really is.

    ------------------------------
    Tracy Hipps
    TD Carpenter & Associates, Inc.
    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 3.  RE: Failing WF submission after 18.4 upgrade with error on "SendWorkFlowAssignmentEmail" ?

    GPUG ALL STAR
    Posted 12 days ago
    Hi Tracy,
    Thanks for your input.. Most of that was already validated as the SQL server has the same GP client setup as the Terminal Server side.. SQL client hasn't changed and the odbc is configured by using the SQL client 11.0.
    Oddly enough, the client wrote this morning that the WF submission had started working again and the users received the notifications in the mailbox. I suspect something had to be checked on the Exchange side by them, but didn't got a confirmation about that yet.
    There was also those WF's that were pending from before the upgrade and I told the client that those would likely to fail and it would indeed. Microsoft does recommend as part of the upgrade checklist to not have any pending WF's awaiting approval, likely for good reasons. I recommended they create a new batch and transfer the transaction into that new batch, then try to submit again. That seem to have been doing the trick.
    I haven't checked the "on behalf" option, but I don't think that would have been the case here.
    Thanks anyway and I'll follow-up if I get more on the resolution side.

    ------------------------------
    Beat Bucher
    Business Analyst, Dynamics GP SME
    Montreal QC/Canada
    @GP_Beat http://www.gp-geek.com
    Montreal QC GPUG Chapter Leader
    MBS MVP (2015-2018)
    All-Star 2013
    ------------------------------

    Academy - Online Interactive Learning from Experts


If you've found this thread useful, dive deeper into User Group community content by role