Open Forum

Expand all | Collapse all

procedure trigger registration failed on script SOP_DP_Run_Reports

  • 1.  procedure trigger registration failed on script SOP_DP_Run_Reports

    Posted 9 days ago
      |   view attached
    After updating GP from 18.3.1200 to 18.3.1290, I'm getting an error message that states the following: Procedure trigger registration failed on script SOP_DP_Run_Reports once I click ok a second box appears with just the number 2. Click ok and GP loads successfully. Any thoughts on what this is referencing?


    ------------------------------
    Renee Boucher
    Data System Services
    Sterling Heights MI
    ------------------------------
    Academy - Online Interactive Learning from Experts


  • 2.  RE: procedure trigger registration failed on script SOP_DP_Run_Reports

    GPUG ALL STAR
    Posted 9 days ago
    @Renee Boucher

    Looks like the parameter list for the latest build might have changed and so a trigger from one of your third party products is failing to register (as the parameters must match).

    Sadly, unless the ISV includes the product name in the trigger registration failure message (which I do and promote as best practice), the only way to identify the product is to (after making a backup) remove products one by one until the error message stops. No need to actually log in. Then the last product removed is the one with the issue.

    Contact the developer of that product and notify them that they will need an updated dictionary for 18.3.1290.

    Regards

    David

    ------------------------------
    David Musgrave MVP, GPUG All-Star

    Managing Director
    Winthrop Development Consultants

    Perth, Western Australia

    http://www.winthropdc.com
    ------------------------------

    Academy - Online Interactive Learning from Experts


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