Vault Basic 2013 over VPN crashes

[andrewspence]

I am running Inventor Pro 2013 with Vault Basic 2013.  When connected at my office, Vault Explorer opens and works fine.  As soon as I am remote, and establish a VPN connection to my office, Vault Explorer will try and open (logs in) and then crashes.  I have applied all the service packs and hotfixes.  Also, there was another post about a very similar problem that was solved by changing IP addresses - this did not work for me.

It is important to note, that I am connected to Vault - I can check files in and out through Inventor.  However I simply cannot open Vault explorer.  It's not quite a normal crash.  The program initially opens with the login screen (vault-during-open.jpg), but as soon as the login is complete, I get the Autodesk error report dialog (vault-during-crash.jpg).  However, after I submit the error report, Vault stays open, and shows a connection in the lower right corner, but is not functional (vault-after-crash.jpg).

Any help?

[r.smith1]

Hi Andrew,
When you submit the CER, do you supply an email address, or do you have the CER number perhaps so it can be reviewed?

[andrewspence]

Yes I do submit an email address - everytime.

I should note that this happens occasionally when not over VPN. It happened this morning CER_98653988.

[r.smith1]

Andrew,
Does this error happen to everyone or just you? Can you reproduce the problem if someone else logs into your computer, or you login to someone else's computer?

[andrewspence]

Ron - 

It's just me - just my workstation.  I've had other people log in with their profile on my machine and cannot duplicate.  I have logged in on other's machines with my profile and cannot duplicate.  I had IT create a new profile for me, when I tried that it crashed the first time.  I did a clean uninstall/reinstall of Vault Basic and the problem persists.

Like the beginning post stated, it started out only when over a VPN connection.  Then it started happening when at the office as well.  Hywell was working on it for a while, and narrowed it down to the xml exchange between my laptop and the server - specifically the return of xml to my laptop, but nothing was ever solved.