Vault Basic 2015 check in error - time out

[Anonymous]

Hi All,

Have been using Vault Basic 2015 for the calendar year so far, previous use is Vault Pro 2011-14 and Vault basic 2009-11

When checking in dwg files via AutoCAD or the client the progress bar gets as far as below then freezes:

Post this, around 5-10mins later I get the following dialogue box

I did a bit of searching on the forum and found this issue which, when looking at the resolution (cmd iisreset) fixes the issue temporarily

http://forums.autodesk.com/t5/vault-general-discussion/drawings-will-not-check-in-please-help/m-p/43...

I've had some assistance from my reseller who changed the iis timeout setting from 120 to 900. He also had a look through my logs, but there wasn't any standout. In fact during the timeout periods there is no log items.

This has since caused the more frequent occurances of my issue of not being able to check in. iisrest fixes it still but it is now at a stage where it is required almost after every check in.

It's been sent to a Autodesk support person, but was hoping I might get to resolve it via this forum.

Thanks

[Anonymous]

Hi All,

Have been using Vault Basic 2015 for the calendar year so far, previous use is Vault Pro 2011-14 and Vault basic 2009-11

When checking in dwg files via AutoCAD or the client the progress bar gets as far as below then freezes:

Post this, around 5-10mins later I get the following dialogue box

I did a bit of searching on the forum and found this issue which, when looking at the resolution (cmd iisreset) fixes the issue temporarily

http://forums.autodesk.com/t5/vault-general-discussion/drawings-will-not-check-in-please-help/m-p/43...

I've had some assistance from my reseller who changed the iis timeout setting from 120 to 900. He also had a look through my logs, but there wasn't any standout. In fact during the timeout periods there is no log items.

This has since caused the more frequent occurances of my issue of not being able to check in. iisrest fixes it still but it is now at a stage where it is required almost after every check in.

It's been sent to a Autodesk support person, but was hoping I might get to resolve it via this forum.

Thanks

[Anonymous]

---

@Neil_Cross wrote:

Thanks man 

I fear it's a band-aid fix though at best.  I don't know if you're working in an office or at home, but if you can get the Vault put onto a proper server that would be best.  But if you're just a one man band doing some work or a student, I appreciate that isn't really a realistic option.  

---

Band-aid indeed. It's back!! No changes, still no dwf on check-in.

Working in an office but we don't have "server". I work locally and publish PDFs for otherws to view.

[Anonymous]

---

@Neil_Cross wrote:

Thanks man 

I fear it's a band-aid fix though at best.  I don't know if you're working in an office or at home, but if you can get the Vault put onto a proper server that would be best.  But if you're just a one man band doing some work or a student, I appreciate that isn't really a realistic option.  

---

Band-aid indeed. It's back!! No changes, still no dwf on check-in.

Working in an office but we don't have "server". I work locally and publish PDFs for otherws to view.

[Anonymous]

Autodesk via Reseller suggests a dot net reinstall.

Will provide an update of results after it has been completed.

[Anonymous]

Autodesk via Reseller suggests a dot net reinstall.

Will provide an update of results after it has been completed.

[Anonymous]

So below was the prescribed fix.

- Uninstalling .NET via Windows Programs & Features - Running the Microsoft .NET clean uninstall & repair utility (link below to the utility) https://www.microsoft.com/en-us/download/details.aspx?id=30135

- Re-installing .NET (link below to 4.5.2) http://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/How-to-...

- Repairing Vault via Windows Programs & Features

Seems to have worked...only time will tell.

[Anonymous]

So below was the prescribed fix.

- Uninstalling .NET via Windows Programs & Features - Running the Microsoft .NET clean uninstall & repair utility (link below to the utility) https://www.microsoft.com/en-us/download/details.aspx?id=30135

- Re-installing .NET (link below to 4.5.2) http://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/How-to-...

- Repairing Vault via Windows Programs & Features

Seems to have worked...only time will tell.

[Anonymous · Accepted solution]

Issue came back a week anad a half later.

Reseller got Autodesk involved and I had a screen share session with them. This was after it was suggested by the reseller I move to an expensive alternative of a virtual server to reduce the risk of weird occurances like this.

Autodesk rep spent around an hour trying all sorts of weird and wonderful things, then it came down to deleting files from the following locations:

C:\Users\<username>\AppData\Local\Temp

C:\Windows\Temp

Apparently some install files from previous versions of the software could have caused it and is a common occurance when migrating from older versions.

Funny thing is that I've only ever had 2015 version on here.

Anyway, it's been working for some time now and if there are any changes I will update the thread.

[Anonymous · Accepted solution]

Issue came back a week anad a half later.

Reseller got Autodesk involved and I had a screen share session with them. This was after it was suggested by the reseller I move to an expensive alternative of a virtual server to reduce the risk of weird occurances like this.

Autodesk rep spent around an hour trying all sorts of weird and wonderful things, then it came down to deleting files from the following locations:

C:\Users\<username>\AppData\Local\Temp

C:\Windows\Temp

Apparently some install files from previous versions of the software could have caused it and is a common occurance when migrating from older versions.

Funny thing is that I've only ever had 2015 version on here.

Anyway, it's been working for some time now and if there are any changes I will update the thread.

[Neil_Cross]

I'd be very very surprised if this doesn't come back again... I'm open to being told I'm wrong here but I'm 99% convinced that those 2 folders have little to no involvement in the checkin/transactions between client and server.

But maybe the support guy did a few other things which did make the difference in the end, hopefully it's sorted 

[Neil_Cross]

I'd be very very surprised if this doesn't come back again... I'm open to being told I'm wrong here but I'm 99% convinced that those 2 folders have little to no involvement in the checkin/transactions between client and server.

But maybe the support guy did a few other things which did make the difference in the end, hopefully it's sorted 

[Anonymous]

I am skeptical also. Only time will tell.

I've cleared the C:\Temp regularly before to remove errors but never the other two.

Everything he did other than deleting files from those folders he restored to their original state prior to logging off.

He suggested the typical trouble shooting of disabling the anti virus as the http protocol is used to transfer from the client to the server, though I wasn't convinced since it's all local and nothing is going through the network. But once he saw the files in those temp folders he likened the issue to the migration one I outlined above. So once he deleted the files he was convinced that it was a one off issue that shouldn't repeat itself, and that the anti virus software should be having no intereference as I suggested.

[Anonymous]

I am skeptical also. Only time will tell.

I've cleared the C:\Temp regularly before to remove errors but never the other two.

Everything he did other than deleting files from those folders he restored to their original state prior to logging off.

He suggested the typical trouble shooting of disabling the anti virus as the http protocol is used to transfer from the client to the server, though I wasn't convinced since it's all local and nothing is going through the network. But once he saw the files in those temp folders he likened the issue to the migration one I outlined above. So once he deleted the files he was convinced that it was a one off issue that shouldn't repeat itself, and that the anti virus software should be having no intereference as I suggested.

[Anonymous]

Here I am 1.5yrs later upgrading to 2017 vault basic and had the same issue.

Just installed the hot fix and then did the above fix. So far so good.

[Anonymous]

Here I am 1.5yrs later upgrading to 2017 vault basic and had the same issue.

Just installed the hot fix and then did the above fix. So far so good.