Trouble Starting ADMS

[karthur1]

I am still having trouble with this.  Here is a link to my original post.  It is marked "Solved" but it actually is not.  Nothing I have tried works.  My backup is supposed to run on Saturday.  When I checked my backup this morning, it did not backup over the weekend. The event viewer shows the same thing as my original post

When I went the server this morning and tried to start the ADMS, I get the " " message the first time I try to start it. When I try to start it again... it works.

As as workaround, I have to just start the ADMS, then close it.  If I do this each friday afternoon before I leave, the backup will complete.

Any suggestions on how to get this to work consistently?

Kirk A.

Windows 7 x64 -12 GB Ram
Intel i7-930 @ 3.60ghz
nVidia GTS 250 -1GB (Driver 301.42)
INV Pro R2013, SP1.1 (update1)
Vault Basic 2013, SP1

[marina.collet]

Did you try changing the Internet Security options as explained here (latest update): http://crackingthevault.typepad.com/crackingthevault/2011/07/error-1920-error-during-vault-server-in...

[karthur1]

Yes, I tried that in Dec-2012.  Didn't resolve the issue.

[r.smith1]

Hi Kirk,

Please try this link and let us know the results. 

http://wikihelp.autodesk.com/Vault/enu/Community/Troubleshooting/Increasing_OS_Service_Timeouts

and

http://wikihelp.autodesk.com/Vault/enu/Community/Tips_and_Tricks

[karthur1]

Ron,

On the first link.. I don't have a "ServicesPipeTimeout" variable.

[r.smith1 · Accepted solution]

      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

[karthur1]

Ron,

Missed that in the Wiki.  Got it added now.  Will see if it runs over the weekend.

Thanks

[karthur1]

The backup ran on saturday... YEAAAAA!!!

I really think this fixed it, but before I mark this as solved, I will wait another week and see if it runs this coming weekend.

Thanks

[karthur1]

Backup ran this week also.  This seems to be fixed now.

Thanks Ron!