How to solve a very slow Start up of ADMS Console on the Vault Server

Recently a Vault Professional 2013 customer was experiencing an unusually long delay when the ADMS Console was opened on the Vault Server. On this machine, the host was Windows Server 2008 R2 running in a Virtual Machine.

After clicking on the shortcut icon for the Autodesk Data Management Server Console 2013, then logging in, there was a 3-5 minute delay before the Console information came up. When you clicked on anything, it would go to "Not Responding" for another 3-5 minutes.

The Windows Event Viewer showed an error 1503 on the Autodesk Vault Job Dispatch Service.

The solution was to add an entry in the Windows registry for ServicesPipeTimeout like this:

 

1. Click the Start button, then click Run, type regedit, and click OK.

2. In the Registry Editor, click the registry subkey

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

 

3. In the details pane, locate the ServicesPipeTimeout entry, right-click that entry and then select Modify.

Note: If the ServicesPipeTimeout entry does not exist, you must create it by selecting New on the Edit menu, followed by the DWORD Value (32 Bit), then typing ServicesPipeTimeout, and clicking Enter.

(Click to enlarge)

 

4. Click Decimal, enter the new timeout value in milliseconds 120000, and then click OK.

5. Open Services.msc and locate the Autodesk Data Management Job Dispatch service.

6. Under the services Properties change the startup type to Automatic (Delayed Start), and then click OK.

(Click to enlarge)

7. Restart the computer. 

 

For more information on this solution see the Autodesk WikiHelp topic Increasing OS Service Timeouts and also Microsoft's TechNet article Event ID 7009 — Basic Service Operations

 

 

Warning! Problems caused by improperly editing the Windows registry could render your computer operating system unusable. Microsoft provides a wealth of critical information that you need to know about the registry in the Microsoft Knowledge Base at http://support.microsoft.com/support. Use the Microsoft® Registry Editor only at your own risk and only after backing up the registry as well as the system.dat and user.dat files as outlined for your operating system in the Microsoft Knowledge Base and in the related solution, TS66513. Additional information about the registry is also contained in the Help topics in the Microsoft Registry Editor.

 

Comments

[Chris]

The Autodesk Data Management Job Dispatch service can also cause no networking on a Vault server for a long time on boot in a virtual environment.

My server is also Windows Server 2008 R2 running as a virtual machine (Xenserver 6). Whenever the server booted there would be no networking for 5 minutes, which is the default ServicesPipeTimeout value of 300000ms.

Reducing the value would reduce time that networking was down on boot and setting the Autodesk Data Management Job Dispatch service to delayed start fixed the problem entirely.

I'm guessing this is because the failure to start of the Autodesk Data Management Job Dispatch service was delaying Xenserver tools drivers from starting.

Thanks for the tip it would have taken me much longer to find the solution without your blog post.

[Bob]

Thank you, for the tip, Chris.

[Bob Felton]

Thanks for the note. I would hope you found the details for this solution from your search engine that has located these key words:

Vault, Server, ADMS Console, Slow, error 1503, Event Viewer, Registry, ServicesPipeTimeout

Thanks again for the appreciation.

[net.au]

It's difficult to find well-informed people for this topic, but you sound like you know what you're talking about! Thanks