1 ACCEPTED ANSWER
Whenever a Unity Scheduler task runs OK when executed manually, but fails when executed at its scheduled time by a Unity Scheduler Service, the first thing I like to examine is the Windows Account that's running the Unity Scheduler Service.
When a task is executed manually, it is run on the Application Server. The IIS Worker process that runs the Application Server usually runs as a Windows Domain Account with network access, including access to all the OnBase Disk Groups etc.
When a task is executed on its schedule by a Unity Scheduler Service instance, the Windows Account that runs the service should also be an account with network access, including access to the OnBase disk Groups. So it should have the same permissions as the account running the Application Server's IIS Worker Process. I.e. it should probably be a Windows Domain Account.
When a Unity Scheduler Service Instance is installed, if you don't specify a Windows Account to run the service instance, it will use the default account, LocalSystem. But LocalSystem does not have network access, and so it generally won't be sufficient to run tasks (unless all the disk groups are on the local machine).
The screenshot below shows two Unity Scheduler Service Instances. The first runs as LocalSystem, the second as a Domain Account
Whenever a Unity Scheduler task runs OK when executed manually, but fails when executed at its scheduled time by a Unity Scheduler Service, the first thing I like to examine is the Windows Account that's running the Unity Scheduler Service.
When a task is executed manually, it is run on the Application Server. The IIS Worker process that runs the Application Server usually runs as a Windows Domain Account with network access, including access to all the OnBase Disk Groups etc.
When a task is executed on its schedule by a Unity Scheduler Service instance, the Windows Account that runs the service should also be an account with network access, including access to the OnBase disk Groups. So it should have the same permissions as the account running the Application Server's IIS Worker Process. I.e. it should probably be a Windows Domain Account.
When a Unity Scheduler Service Instance is installed, if you don't specify a Windows Account to run the service instance, it will use the default account, LocalSystem. But LocalSystem does not have network access, and so it generally won't be sufficient to run tasks (unless all the disk groups are on the local machine).
The screenshot below shows two Unity Scheduler Service Instances. The first runs as LocalSystem, the second as a Domain Account
