When I double-click to start ADMS I get this message, "Error starting service 'Autodesk Data Management Job Dispatch'....."
I can close the error message and try it again and it starts the second time. When I check the event viewer, here is what I see. It says that "A timeout was reached (30000 milliseconds) while waiting..."
In the ADMS, under Tools>Administration, Advanced Settings, Settings, I have set the connection timeout set to 5000 seconds, but still get this error, so this must be something different.
The problem is that when I try to run my Vault backup over the weekend (unattended), it fails because the ADMS doesnt start.
I started seeing this lately myself but thought it was because I was reverting my VMware images for testing. Is there anything in the Event Viewer on why the "Job Dispatch" stopped? I would also double check that the service itself is set to be started automatically. I find once I start the service (again unsure why it stops) the ADMS Console works properly.
There are only three events in the event viewer for that day.
1. the time out error
2. the autodesk data management job dispatch service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
3. Application:Connectivity.ADMSConsole.exe, Description:The process was terminated due to a n unhandled exception.
I checked the Services and the autodesk data management job dispatch is set to start automatically.
Can I get you to quickly check this blog post before we dig deeper:
I did the suggestion at th bottom of the blog " The quickest method would be to unplug the network cable, start the service and plug it back after the Service is running".
The ADMJD was already started, so I stopped it, unplugged the server network cable, started the service, then plugged the cable back in.
We will see how it goes over the weekend when the backup task runs. The next time I see this error, I will see if the service is started or not.
With the "3. Application:Connectivity.ADMSConsole.exe, Description:The process was terminated due to an unhandled exception.", is it possible to get more information around the issue? The information in the "General tab" might be able to help us out. Hopefully what you did will get you through the weekend backup.
Checked the backup this morning. Noticed that the backup did not run over the weekend. I checked the event viewer and found the same three errors listed for Saturday (thats when the backup runs).
I tried to start the ADMS Console and got this message.
Clicked OK and tried again and it started the second time. Same thing as before, so doing the "unplug the cable" trick didnt do it.... Must be something a little more deeper than that.
I followed the link to the blog mentioned above and ended up here. In the user comments, Hans Veer suggests to to this.
So I tried that and we will see how it goes.
I am still having issues in getting the ADMS backup to run consistently when it is started from a scheduled task. Still getting the same error in the Event Viewer.
Start with some of our most frequented solutions to get help installing your software.
Upgrading to a 2015 product? Make sure to check these out 1st!