Windows Task Scheduler does not run tasks for Sage 100
Description
Sage 100 Task Scheduler job doesn’t run tasks at the time configured, or doesn’t run at all. In Windows Task Scheduler the following error:
- Scheduled Task Failing (0x80070569: Logon failure: the user hasn’t been granted the requested logon type at this computer.
- A related symptom is when running on Workstation, the following error displays: “Exception thrown” (Windows error) but when running directly on the Sage 100 server get User Name/Password error.
Cause
- Windows logon/login is missing “Log on as a batch job” privileges.
- Issue with specific Windows administrator user specified – corrupted user account.
- Printing problems using the task scheduler – See Related Solutions
Resolution
The logon used will need to have the associated privilege added to the account:
- Open Start
- In the search field type gpedit.msc and, click enter.
- This brings up the Local Group Policy Editor
- Expand Computer Configuration, Windows Settings, Security Settings, Local Policies, User Rights Assignment.
- Locate the policy Log-on as a batch job.
- Right click Logon as a batch job policy and go to properties.
- Click Add User or Group and add the appropriate accounts.
- Click Apply and OK to save.
Configure the required security privileges:
- Set up the Sage 100 shortcut to “Run as Administrator”, if UAC is turned of on the workstation
- Launch Sage 100 and access the Task Scheduler to set the job.
Sage 100 Advanced or Premium running as a Service:
- Go to Control Panel, Administrative Tools, Services.
- Look for Sage 100 (Premium or Advanced) (####) where #### represents the active Port number.
- Right click and select Properties.
- Click the Logon tab and “This Account”.
- Enter the credentials of the actual Administrator or Domain Administrator account and Apply.
- Change after everyone exits Sage 100.
- Log on to Windows with the account defined for the Sage 100 service.
- Set up default printer for that user account. The Task Scheduler uses the account defined in Windows Services to run the jobs. It isn’t using the Windows account defined in Sage Task Scheduler, when the account is specified directly on the service.
Create a new domain user in Windows when the issue relates to a specific Windows user account.
The Task Scheduler task is stuck when selecting “Run Now”
In this case, the “Executing$” field in the SY_TaskSchedulerHeader file displays with a value of “Y”. Use Data File Display and Maintenance (DFDM) to access this file record and adjust ‘N’