How to add your knowledge

Configure Autodesk Vault Job Dispatch service for automatic restart

    Table of contents
    1. 1. Background
      1. 1.1. Tip Intro
    2. 2. Related Wiki Topics
    3. 3.  

    Background

    In a replicated environment, the "Autodesk Vault Job Dispatch" service is responsible for launching scheduled filestore replication sync jobs on each ADMS server.  If this service is stopped, scheduled filestore replication tasks will not occur at that server.  

    Rebooting the file server would restart the service, but file servers often go for weeks or months without being rebooted in production environments.  If the service fails for some reason, it is likely that the service will remain stopped unless the failure is noticed by a system administrator.

    By setting the "Autodesk Vault Job Dispatch" service to automatically restart after a delay in the event of a failure, we can improve the fault tolerance of the filestore replication tasks.

    NOTES

    1) This tip applies to both filestore replication-only and Connected Workgroup (full replication) replicated environments.  

    2) The "Autodesk Vault Job Dispatch" service launches the filestore replication tasks, along with other scheduled ADMS server tasks.  This service does NOT control the SQL database replication used with Connected Workgroups.  Configure SQL replication monitoring (see links below) to ensure that the database replication is occurring successfully in conjunction with the filestore replication tasks.  Both aspects of replication (filestore and database) need to be monitored.

     

    Tip Intro

    1. On the ADMS server, launch the Services console from Control Panel->Administrative Tools->Services, or by typing SERVICES.MSC at a command prompt.
    2. Locate the "Autodesk Vault Job Dispatch" service in the list of services.  Right-click it and select "Properties"
    3. Select the "Recovery" tab.
    4. Change "First failure" from "Take No Action" to "Restart the Service"
    5. Change "Second failure" from "Take No Action" to "Restart the Service"
    6. Change "Subsequent failures" from "Take No Action" to "Restart the Service"
    7. Change "Restart Service After" to 5 minutes to allow time for server error conditions to potentially be resolved .
    8. REPEAT on every ADMS server in the replicated environment.

    Related Wiki Topics