Product: Dynamics GP (Enterprise) & Automation

Article Link: http://help.truecommerce.com/en/articles/6543216-dynamics-gp-enterprise-troubleshooting-automation

If you've found that Automation has stopped running - more often than not one of the dependencies that Automation relies on has ran into some issues and may need to be corrected in order for it to kick off an event again.

Here are some things you'll want to check and make sure are operational to ensure proper operations.

You'll want to ensure the Task is actually enabled within Automation.

Select: (Task) → Edit

Enable: Enabled (task will execute on schedule)

Launch: Windows Services

Find: GPAX Integration Service

If the service is stopped, be sure to Start it - if it's already running it can be helpful to Restart the service to clear it of any jams that may of occurred from large transactions or system errors.

You'll want to make sure that the Scheduler Taskbar Process is properly running - it's a small application that lives within your Taskbar and usually hidden in the Tray Icons section - if it's missing, you'll want to start the process again and ensure the icon appears.

Starting the Service

Navigate: Open Windows Menu → Type "Scheduler Taskbar Process"

Launch: Scheduler Taskbar Process

Note: If you've restarted the GPAX Integration Service in the above step - you'll need to start the Scheduler Taskbar Process again as it'll automatically close anytime the GPAX Integration Service is stopped or restarted.

Not Launching

If you're having issues launching the Taskbar Process or not seeing it populate the System Tray section this usually implies permissions issues - you'll want to log in as a local admin and see if the issue persists.

Automation Events will only fire off if you're logged in as the same User for Windows as is marked in your Automation Task.

If you are not the same user - the task will not run

Checking User

You can launch Command Prompt (cmd.exe) and run the task whoami to check your windows user - if the EventOwner within Automation is not the same as the logged in user, the task will not run

You'll need to make sure Dynamics GP is already running in the background, if Dynamics GP is not running - please start it before attempting to run any Automation Tasks to ensure it's able to access the program properly.

In addition to that - you must have Dynamics GP logged in as the user setup as the GPUserName for the task, otherwise you will not have permissions to run (as Automation simply calls the current opened instance of Dynamics GP

rev 9/8/22