Bug fix for Job Processor (2023)

Before troubleshooting, read theJob Processor overview:

Job Processor Components

Job Processor consists of three main components.

jobs: Tasks sent to the job queue and completed by the job processor; These are typically repetitive tasks such as property updates or DWF creation.
job queue: The server-side utility that accepts jobs from Vault clients and records job execution details.
processor: The client-side component that polls the job queue for tasks and executes them with the appropriate components.

Job Processor Process

Once started, the job processor will check the job queue every 10 minutes (this is configurable).
When an item is in the queue, the next jobs in the queue are reserved based on priority.
Downloads the files to the local computer.
Opens the files, typically in a "headless" (no UI) version of the associated product.
Updates the file properties if necessary and saves the file as a new version.
When a DWF update is required, the Job Processor creates the DWF file and uploads it to Vault, appending the DWF file to the source file. this will not create a new version.
Go to the next job.

Frequently asked questions about the processor

Does Job Processor need to be installed on a server?

no Job Processor is a client application. Ideally, it should be installed on a workstation with similar specs to a CAD workstation.

What are the system requirements for Job Processor?

See the system requirements for Vault Client in the Autodesk Knowledge Base:https://knowledge.autodesk.com/support/vault-products/troubleshooting/caas/sfdcarticles/sfdcarticles/System-requirements-for-Autodesk-Vault-products.html.

Also review the requirements for each application required to run jobs on the processor.

Inventor:https://knowledge.autodesk.com/support/inventor-products/troubleshooting/caas/sfdcarticles/sfdcarticles/System-requirements-for-Autodesk-Inventor-Products.html
Revit:https://knowledge.autodesk.com/support/revit-products/troubleshooting/caas/sfdcarticles/sfdcarticles/System-requirements-for-Autodesk-Revit-products.html

Can I install Job Processor on an end user computer?

Yes, but Autodesk does not recommend this. Job Processor is a Vault Client installation option and can be installed and run on any computer. But while the Job Processor is running, it opens applications and uses system resources. In the case of Inventor, temporary project files are created and used. For this reason, Autodesk recommends installing Job Processor on a dedicated computer.

Does the job processor use a license?

No, Job Processor does not require an Inventor license.

For example, when the job processor runs Inventor DWF Publishing (InventorDwfPublishCount), it starts Inventor and runs that job type a specified number of times before closing and restarting Inventor. That way Inventor doesn't start and stop every time it runs one of these jobs.

See:Configure job processor usage limits for CAD services.

How often does a processor look for jobs?

This is configurable, but by default the Job Processor searches for jobs every ten minutes.

What kind of jobs does the job processor run?

By default, Job Processor is configured to create visualization files (DWF) and synchronize properties. It can be configured to update revision tables and sync files to a supported Autodesk cloud drive using Project Sync. It can also be expanded to run any number of custom tasks.

What kind of monitoring is recommended?

The job processor should run unnoticed in the background. Under normal conditions, administrators should check the queue daily to look for specific failed tasks that need to be resent or underperforming processors.

Seehttp://underthehood-autodesk.typepad.com/blog/2015/09/monitor-your-job-processor.html.

(Video) Troubleshooting Job Processor with Process Monitor

What software does Job Processor use?

Inventor Server: For DWF creation of Inventor formats
TrueView: For AutoCAD DWF creation
Revit: For DWF creation of Revit files
MS Office 2013: For older Office file formats

Custom jobs may require additional applications. See the online help for complete job type requirements.

How do I rerun a failed job?

Failed jobs can be resubmitted via the job queue.

How do I automate the Job Processor?

Job Processor can be set to start automatically as soon as your computer starts. This is done in the Job Processor Settings dialog box. Some administrators set up Job Processor to run off-peak jobs when additional licenses are available. This is typically done using scheduled tasks and batch files.

Who should be enrolled in Job Processor?

The Windows user who has the credentials to run CAD applications on the computer.

If possible, a separate vault user should be created to run jobs with elevated file privileges, as the job processor user may need to edit shared or locked files to update properties.

Whose name appears on a new file version?

When Job Processor creates a new file version, the Vault user logged into Job Processor at that time is added as the creator.

Revision tables allow you to choose to show file details of the first released version instead of the latest.

How long does the software take to process orders?

This can vary widely, but individual jobs typically complete in under a minute, depending on computer resources, file size, and job type; The total time depends on the number of jobs.

To optimize performance, CAD applications are restarted after a specified number of jobs. This is configurable.

Does Job Processor migrate a file to the latest software version?

Yes, if you create a new version of the file, it will be migrated to the software version running the job.

What if Job Processor doesn't have the right software?

The job type is disabled and will not run on this computer. Jobs can be deactivated manually or configured withJobProcessor.exe.configFile found underC:\Programme\Autodesk\Vault XXXX\Explorer\.

What happens if Job Processor doesn't have the right software version?

The job fails if the file cannot be opened (e.g. an Inventor 2017 file in Inventor 2016).

What should I do if processing is slow?

If you're running a lot of jobs and performance is slow, try the following:

Use more than one job processor.
Set up one computer to handle synchronization properties and another to create DWF files.

Bug fix for Job Processor

Corrupt installation

(Video) Setting up and Configuring Job Processor | Autodesk Virtual Academy

Repair or uninstall the software from the Windows Control Panel and reinstall it.

Make sure the correct licensing is configured

If the processing software requires a license, make sure it can obtain one.

A file type cannot be processed

Make sure you have the appropriate software for the file format you need to work with.

Creo processes PTC files.
Other applications handle their native formats; these include Revit and SOLIDWORKS.
The Vault Enterprise Add-in can be configured to process formats such as CATV5Product, IGES, JT, PDF, STEP, Flat Pattern DXF using publish jobs.

Install the latest service packs

Some bugs can be fixed by installing the latest service packs for both the Processing Software and the Vault Client.

Job Processor not responding

Restart Job Processor. If necessary, end the process in the task manager or restart Windows. If a DWF publication does not work, try opening the same file in Job Processor and manually exporting the DWF file to the local hard drive. If problems persist, reinstall or repair the installation.

Software not registered with Windows

Log in to the Job Processor computer, start the software, and then close it. Look for any error messages you see and fix them by searching the web for more information.

Insufficient user rights

The user account used by Job Processor must have sufficient privileges to perform the required action. For example, if file properties need to be updated when a file is moved from "Work in progress" to "Released", the account must have the necessary permissions to edit file properties. Check the life cycle definitions for this category and the account used by the Job Processor.

Corrupt file errors

There may be a problem with the file itself.
Check if the file can be published manually from the application that originally generated it. The issue could be due to a setting used when publishing.

Order types not processed

Occasionally job type parameters can be deselected in Job Processor; This may have happened when the processing software was unregistered from the operating system. To check this, go to Job Processor > Administration > Job Types and see if the jobs to be processed on this computer are selected.

Remove job types

If you have added or modified custom job types using the Lifecycle Event Editor, you may want to review and remove any broken job handlers or unwanted actions. See this article:https://knowledge.autodesk.com/community/screencast/33b04381-421c-4fa9-a37c-11f05ee2a4fc.

For more details on customizing DWF output, seeDWF Creation - Fine-tuning.

Actions to be taken when jobs are not processed or errors are received

Login to the Vault Client and ensure that Job Processor is enabled for the server you are logged into.
Log in to the Vault Client and make sure you can see queued jobs.
Search the queue for jobs with failed results and identify specific error messages and processor failures.

Job Processor troubleshooting steps

Log in to the Job Processor, stop and restart the processor, and then verify that the jobs continue correctly.
Ensure that licenses for Job Processor are available by manually logging out and back in to the Job Processor utility.
Use Task Manager to manually stop Job Processor processes: JobProcessor.exe and Connectivity.JobProcessor.Delegate.Host.exe. Restart Job Processor.
Use Task Manager to manually stop any CAD applications running unattended on the job processor, and then resubmit the job.
Run all CAD applications on Job Processor to ensure there are no problems with the installations.
Perform DWF file creation tasks manually in Inventor, TrueView, or Revit to ensure they complete correctly.
In the Vault Client on the Job Processor machine, try to refresh the view manually to see if a DWF file can be created. (This process bypasses the job processor.)
Restart Job Processor to resolve update, background process, or crash issues.
Ensure that the operating system and all relevant software on the Job Processor computer are up to date with the latest service packs and fixes.
Empty the temporary folder on the Job Processor (%temp%).
Temporarily disable virus and firewall checks to see if the error persists.
Activate Job Processor on another computer and see if the errors persist.
Log on to the Job Processor computer as a different Windows user to determine if Windows-based permissions or user profile corruption is the problem.
Log in to Job Processor as a different Vault user to see if this relates to Vault user permissions or access.
Perform software repair on components used to run failed jobs (e.g. Inventor, TrueView, Revit, etc.).
Run a software repair on Vault Client.
If you find that Job Processor stops responding when working with large files, try changing the timeout settings in the configuration file.

View job processor logs

If the errors persist despite troubleshooting, read this information about error logging and possible fixes.

Access to error details

AVFS Logs: The file server logs all failed tasks here.
Job Queue: From any Vault Client connected to AVFS, select Tools > Job Queue to view job details.
Event Viewer: Job Processor logs all jobs in the Event Viewer application log on the computer. This can be useful when troubleshooting failed or incomplete jobs.
Process logs:C:\%appdata%\Autodesk\Autodesk Vault Job Processor\JobProcessor.log.

Enable verbose logging

(Video) We FIXED a DEAD CPU!!

Find themJobProcessor.exe.configFile. For example, for Vault Professional 20xx this is in by defaultC:\Programme\Autodesk\Vault Professional 20xx\Explorer. This location is different if you are using Vault Workgroup or another version of the Vault Client.

Copy JobProcessor.exe.config before editing it.
Open JobProcessor.exe.config in Notepad.
Locate the following section and the text <add key="LogLevel" value="0" />.
Change the log level from 0 to 1.

<!-- 0 This is generally something that might matter to a user if they see it in the log file. It can help user to know the status of all jobs. 1 This is generally something that a developer might care about if they see it in the log file. It can help the developer to diagnose the detailed problems. The default value is 0 --> <add key="LogLevel" value="0" /> <!--The value of InventorUpdateRevBlockReleasePeriodInMinutes must be at least 5 minutes--> <add key="InventorUpdateRevBlockReleasePeriodInMinutes" value="10" / > < !--The minimum value for InventorDwfPublishReleasePeriodInMinutes is 5 minutes--> <add key="InventorDwfPublishReleasePeriodInMinutes" value="10" /> <!--The minimum value for TrueViewDwfPublishReleasePeriodInMinutes is 5 minutes--> <add key="TrueViewDwfPublishReleasePeriodInMinutes" value="10" /> <add key="DataManagement.Common.Logging.ApplicationName" value="JobProcessor" /> <add key="DataManagement.Common.Logging.Enabled" value="True" /> <add key ="DataManagement.Common.Logging.ServiceMachine" value="." /> <add key="DataManagement.Common.Logging.LogFile" value="" /> <add key="DataManagement.Common.Logging.SerializeProperties" value="False" /> <add key="DataManagement.Common. Logging.Viewer.Path" value="H:\Common\Logging\LoggingBin\MessageViewer\DataManagement.Common.Messaging.Viewer.exe" /> <add key="DataManagement.Common.Logging.Viewer.AcceptLocalMessageOnly" value=" True" /> <add key="DataManagement.Common.Logging.Viewer.Port" value="8080" /> <add key="DataManagement.Common.Logging.Viewer.AutoLaunch" value="False" />

After changing the value to 1, save the JobProcessor.exe.config file and then restart Job Processor.

When Job Processor processes a new job, information is added to the JobProcessor.log file.

Also, more detailed information is published in JobProcessorJobActivity.log.

Check the new information in both new files.

error reference

"Unknown error publishing"

This can have several causes. If this occurs with specific files, manually open the affected file and try saving it to a new file and re-creating the failed task (e.g. create DWF).

Possible causes:

Missing references
model corruption
Data not migrated
Missing links or applications in the Job Processor

"Cannot get file version for ID xxxxxxx" or "An error occurred while attempting to get a file."

This happens when a job is created for a specific file, but the file is removed (e.g. deleted) from Vault before the job could run.

"Index (zero-based) must be greater than or equal to zero and less than the size of the argument list."

This may be due to the DWF file attached to the file being updated being locked (e.g. checked out or in use). Try the following to resolve the issue:

Contact the user and tell them to check the file back in and resubmit the job.
Log in as an administrator, remove the reservation on the file, and resubmit the job.
Delete the DWF file from the vault and resubmit the job (this will lose the version history).

"The new Job Processor service is not responding."

This error occurs whenJobProcessor.exeorConnectivity.JobProcessor.Delegate.Host.exedo not react anymore. You must log in to the computer and do one of the following:

Exit and restart Job Processor; or,
End both processes in the task manager and restart the job processor.

"This file is only available on the following websites, which are currently inaccessible:"

This can be caused by a break in network connectivity between the ADMS and AVFS servers.

This can also occur if the AVFS computer has restarted or had a power failure.

Resending the job once communication between ADMS and AVFS is restored should resolve the issue.

"File locked;"

This Job Processor error can occur when a user tries to perform a task on a file such as: B. Sync property but the file is locked for the Job Processor user account.

"Sync properties are not allowed on non-tipping versions"

This error indicates that a new version of this file was created before the job could complete. This can happen when a user changes the status of a file, e.g. B. from "in progress" to "in review". Administrators can ignore, delete, or filter out this error type.

lack of adequate permissions

(Video) EEVblog #1288 - Synology NAS Dumpster Find! (REPAIR)

There are a number of permission issues that can prevent access to edit a file (object and state-based security). Recheck user access to specific CAD or visualization files, or log in to Job Processor as an elevated user. Note that the job processor cannot update locked visualization files.

Non-unique visualization files

If you have "Enforce unique filenames" enabled and duplicate visualization files exist in Vault, the job processor is not allowed to check in updated visualization files.

This can happen when the Job Processor cannot access a Vault license (all licenses may be in use). In this case, users must ensure that licenses are available and manually log in again through the Job Processor client.

"User does not have the correct authentication type"

The job processor does not have the correct permissions to run a specific job.

"Cannot generate a visualization file for a non-CAD file"

This can happen when a virus scanner is running on the Job Processor computer. Test with virus scanner disabled and add Autodesk products to exception list.

"Retrieving the COM class factory for the component with CLSID {C343ED84-A129-11D3-B799-0060B0F159EF} failed due to the following error: 8007045a A dynamic link library (DLL) initialization routine failed. (Exception from HRESULT: 0x8007045A)."

This can occur when checking in an IPT file linked to a DWG. It occurs when the processConnectivity.WindowsService.JobDispath.exeis started before the processConnectivity.JobProcessor.Delegate.Host.exe.

To fix this, start Vault Client as the first process, refresh the file view with Job Processor and add one or more jobs to the job queue. Start Job Processor.

Appendix

Batch file to start Job Processor from command line:

See:Job Processor Command Line

REM start Job Processorstart JobProcessor.exeREM prevents the Job Processor from processing any more jobs in its queue after the current jobJobProcessor.exe has ended. /pauseREM allows the Job Processor to resume processing jobs in its queue from a paused state after the current jobJobProcessor.exe /stop has ended

You can also use command line arguments in combination with a scheduled task and Powershell to restart JobProcessor.exe on the VM every few hours.

# === powershell.ps1-Skript ===& "C:\Programme\Autodesk\Vault Professional 2021\Explorer\JobProcessor.exe" /stopWait-Process JobProcessor& "C:\Programme\Autodesk\Vault Professional 2021\Explorer \JobProcessor.exe"# === powershell.ps1-Skript ===

That/PauseThe command ends the current job and then exits the Job Processor (which frees Inventor's resources).

This article shows you how to do this with Vault 2013 Professional:http://justonesandzeros.typepad.com/blog/2012/10/job-processor-command-line-tricks.html.

Job processor configuration file timeout settings

C:\Programme\autodesk\autodesk vault xxxx\explorer\JobProcessor.exe.config

<add key="PeriodInMinutes" value="10" /> <!-- WebService-Timeout (in Millisekunden)--> <add key="WebServiceTimeout" value="1000000" /> <!-- 1000 Sek. = 1000000 Milli --> <!-- RequestSendTimeout (in Minuten)--> <add key="RequestSendTimeout" value="90" /> <!-- RequestReceiveTimeout (in Minuten)--> <add key="RequestReceiveTimeout" value= "90" /> <!-- HostServiceSendTimeout (in Minuten)--> <add key="HostServiceSendTimeout" value="10" /> <!-- HostServiceReceiveTimeout Timeout (in Minuten)--> <add key="HostServiceReceiveTimeout " value="90" /> <!-- PingTimeout-Timeout (in Sekunden)--> <add key="PingTimeout" value="30" />

Application cycles for the configuration of the job processor

<add key="UpdateRevBlockMigrateLatestINV" value="0" /> <add key="InventorUpdateRevBlockCount" value="100" /> <add key="InventorDwfPublishCount" value="100" /> <add key="TrueViewDwfPublishCount" value ="500" />

(Video) Identify performance issues with queue processor and job scheduler activities in Pega