Trying to give back to the group for all the help over these past many months, I wanted to share a debug tidbit.
We were fighting a job scheduling problem where the scheduler would fail stating:
"No resources are available to schedule operation 9 of assembly 0"
We combed through operation 9 and could not find anything wrong. Calling Epicor, they informed us of a debug feature for scheduling. If you put an empty text file called debug.txt into the root folder of the Epicor server (i.e. c:\), when the job is scheduled, a text file will be created in that users reports folder which shows all the steps the scheduler took. In our case, the last line of the generated text file was a reference to OP 90. Checking that operation, not the one indicated by the initial error dialog, we found that the resource under the capability had been deactivated. Replacing the resource with an active one fixed the issue.
Tim
We were fighting a job scheduling problem where the scheduler would fail stating:
"No resources are available to schedule operation 9 of assembly 0"
We combed through operation 9 and could not find anything wrong. Calling Epicor, they informed us of a debug feature for scheduling. If you put an empty text file called debug.txt into the root folder of the Epicor server (i.e. c:\), when the job is scheduled, a text file will be created in that users reports folder which shows all the steps the scheduler took. In our case, the last line of the generated text file was a reference to OP 90. Checking that operation, not the one indicated by the initial error dialog, we found that the resource under the capability had been deactivated. Replacing the resource with an active one fixed the issue.
Tim