Process Scheduler Integrity Check returns the following error status codes in the windows scheduler.
OZProcessScheduler.exe returns different values on error:
-
0 = no error (schedule run ok)
-
101 (0x65) = cannot open session - check username and password in Options
-
102 (0x66) = schedule does not exist
-
103 (0x67) = cannot open database - check username and password in Companies
Tips to troubleshoot
-
Check that there are LanPaks available
-
Ensure "This workstation uses Integration Access Pack licences for Extender applications" is not selected. This is mainly for older versions of Sage 300.
-
Check the User ID and Password set in PS Options – on the Processing tab
-
Check the User ID and Password set in PS Companies – for the company for which the schedule is being run. If this User ID is the same as the User ID set in PS Options, only one lanpak will be required for both sessions.
-
Does the schedule run successfully from within the Schedule setup? To check this, click “run” on the Schedules option for the required schedules
-
Does the schedule run successfully from within the Windows Task Scheduler? To check this, select the appropriate Windows Task Scheduler task, select “Run”, then Click F5/Refresh, and monitor the task. Refer to error codes above.
-
Confirm that the network user configured in Windows Task Scheduler has access to the Sage 300 Site directory, and can access the drives (UNC Path) used in the Schedules.
-
Ensure the task runs whether the user is logged in or not.
-
In some cases, where the user is not local, you need to select "Do not store password". Refer to https://superuser.com/questions/1334931/task-scheduler-batch-run-whether-user-is-logged-on-or-not-not-working
