This document describes how to troubleshoot the Error in creating I/O Handles for Job xxx error, when a job runs on a Windows agent.
There are no specific requirements for this document.
The information in this document is based on the Tidal Enterprise Scheduler.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Refer to Cisco Technical Tips Conventions for more information on document conventions.
Verify that the account that runs the Tidal Agent service has these Local Security Policy permissions:
Act as part of the operating system
Adjust memory quotas for a process
Bypass traverse checking
Logon as a batch
Logon as a service
Replace a process level token
If any changes are made to the Local Security Policy of the user, stop and restart the Tidal Agent Service and test the job run again. If you use a runtime user for the job that is different than the Tidal Agent service account, make sure that the runtime user has Logon as a batch Local Security Policy permissions.