The Job Processor is a separate application, installed on a computer with the Vault client, the processes jobs in the Job Server queue. The jobs that can be processed by the Job Process include DWF creation, property synchronization, and custom jobs. Each processed job gets recorded in the JobProcessor.log file in the <installed dir>Vault Professional 2016Explorer directory. There isn’t an easy way to be notified when jobs fail due to errors or issues.
There are a couple of methods which will allow you to get notified of Job Processor failures. First you have to configure the Job Processor, with Vault 2016, to log all jobs to the Windows Event Viewer. To configure the Job Processor to log to the Event Viewer Application log perform the following steps.
-
Navigate to the <installed dir>Vault Professional 2016Explorer directory.
-
Locate and copy the logging_JobProcessor.config file to have a backup copy.
-
Using Notepad, under the configuration/loggingConfiguration/listeners section you will find server lines that have <add name=”Event Log Listener”> that are commented out (via <!– –>).
Uncomment each of these lines. -
Find the line that has source=”Enterprise Library Logging” and change it to source=”Autodesk Job Processor”.
-
You need to run the Job Processor at least one time using the “Run as Administrator” option and have it execute at least one job. You can then close the Job Processor and restart it in a normal mode for processing jobs.
-
Open the Event Viewer and look into the Application log. You will see log entries created by the Job Processor for each job processed.
Now that you have the jobs being logged in the Event Viewer, the Event Viewer has a couple of methods that can use to alert you on specific types of events. The first method would be to use the Attach Task To This Event option in the Actions panel. The second option would be to create a Subscription to collect events from remote computers and store them in logs on the local computer. Take a look at these two options on Microsoft web pages.
Run a Task in Response to a Given Event
– Irvin Hayes Jr., Product Manager
(0)