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 :
Finance | Project Operations, Human Resources, ...
Suggested Answer

Integration Manager - Could not run file trigger script

(0) ShareShare
ReportReport
Posted on by

Hi,

   I created a new integration to update the userdef2 field in Customer master, but IM is getting this error:

Could not run file trigger script

The Integration has selected the Destinarion Edit Mode like Update Only.

My source files only has CurtomerID and Userdef2.

Regards

Julia Gallegos

Categories:
I have the same question (0)
  • Suggested answer
    Derek Albaugh Profile Picture
    Microsoft Employee on at

    We more frequently see this type of error outside of Integration Manager and more so with third party products.

    If your integration is using Standard adapter, not eConnect, try running the integration against a Dynamics GP instance with no third party products or customizations installed.

    You can use these steps to get a 'clean' GP directory to run against:

    1. Have all users log out of Dynamics GP on the machine you're running IM on, then rename the GP directory from something like C:\Program Files (x86)\Microsoft Dynamics\GP\ to C:\Program Files (x86)\Microsoft Dynamics\GP_OLD\.

    2. From there, in Control Panel > Programs and Features, right-click on Dynamics GP, choose 'Change' and then select the 'Repair' option when prompted with the options window. Verify the Repair process runs successfully. Its run successfully

      Repair will re-create the entire GP directory under the original name, minus modified forms/reports dictionary files, third party products, customizations, etc.

    3. In this 'new' Dynamics GP directory, setup a dexsql.log to run via the Dex.ini file and save changes.

    4. Login to Dynamics GP through this 'new' GP directory as 'sa' preferably then run the integration re-creating this error message.

    Another option if using a standard adapter integration is to turn on the settings in the Microsoft.Dynamics.GP.IntegrationManager.ini file that will "show dynamics" while it's integrating...

            ShowDynamics=TRUE

            DoUIRedraw=TRUE

    This will show you the GP windows as the integration is going through, which can help if there's a modified or third-party version of the window, along with the dexsql.log.

    We see this also if the window or transaction prompts the user with any type of dialog box where they have to click OK to continue the processing. By default, Integration Manager nor eConnect know how to handle the dialog boxes, thus will cause error messages such as this.

    I'd start with the above and see what that shows if anything.

    Thanks

  • Julia_Gallegos Profile Picture
    on at

    Thanks Derek.

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!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 660

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 655 Super User 2026 Season 1

#3
CP04-islander Profile Picture

CP04-islander 557

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans