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

[Senthil_Kumar]

Apart from IISRESET did you move the .AC$ file mentioned in the solution?

http://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/Can-not...

As mentioned here please install 2015 SP1 and try the check-in again.

Hope this helps.

[Senthil_Kumar]

Apart from IISRESET did you move the .AC$ file mentioned in the solution?

http://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/Can-not...

As mentioned here please install 2015 SP1 and try the check-in again.

Hope this helps.

[Anonymous]

Hi Senthil,

Sure did. Didn't change anything. Also should have mentioned that I've got all current service packs and hot fixes for both products.

[Anonymous]

Hi Senthil,

Sure did. Didn't change anything. Also should have mentioned that I've got all current service packs and hot fixes for both products.

[Senthil_Kumar]

That's strange. Is it only specific DWG file or all the DWG files? You have mentioned that you are in touch with our Product support. Hope they can look into this and resolve. 

[Senthil_Kumar]

That's strange. Is it only specific DWG file or all the DWG files? You have mentioned that you are in touch with our Product support. Hope they can look into this and resolve. 

[Neil_Cross]

Where is your Vault server in relation to your PC... is it on your PC or on a server? If it's on a server, is the server local to you or in another office?

I don't think it's been mentioned here but if you have the rights, temporarily disable any and all anti-virus & firewall programs on your PC and the server for the time period of one check-in to see if that changes anything, obviously re-enable everything ASAP.

Eager to hear the answer to how big the file is too and whether or not this happens on other drawings.

[Neil_Cross]

Where is your Vault server in relation to your PC... is it on your PC or on a server? If it's on a server, is the server local to you or in another office?

I don't think it's been mentioned here but if you have the rights, temporarily disable any and all anti-virus & firewall programs on your PC and the server for the time period of one check-in to see if that changes anything, obviously re-enable everything ASAP.

Eager to hear the answer to how big the file is too and whether or not this happens on other drawings.

[Anonymous]

---

@Anonymous-Autodesk wrote:

That's strange. Is it only specific DWG file or all the DWG files? You have mentioned that you are in touch with our Product support. Hope they can look into this and resolve. 

---

It does not discriminate which files that it times out on.

[Anonymous]

---

@Anonymous-Autodesk wrote:

That's strange. Is it only specific DWG file or all the DWG files? You have mentioned that you are in touch with our Product support. Hope they can look into this and resolve. 

---

It does not discriminate which files that it times out on.

[Anonymous]

---

@Neil_Cross wrote:

Where is your Vault server in relation to your PC... is it on your PC or on a server? If it's on a server, is the server local to you or in another office?

I don't think it's been mentioned here but if you have the rights, temporarily disable any and all anti-virus & firewall programs on your PC and the server for the time period of one check-in to see if that changes anything, obviously re-enable everything ASAP.

Eager to hear the answer to how big the file is too and whether or not this happens on other drawings.

---

Vault and PC are one and the same. I am the only one connected to it, and only user.

The first thing I thought of was anti-virus also due to similar issues in previous installations, but as you questioned, the setup is different so I don't imagine any issues would occur since file transfer is only local, not over the network. Our antivirus is web based and therefore only scans web material.

The same anti-virus has been on my machine for over 6 months. This issue is has not been occuring for that long.

As above, files are not discriminated on, including based on their size.

[Anonymous]

---

@Neil_Cross wrote:

Where is your Vault server in relation to your PC... is it on your PC or on a server? If it's on a server, is the server local to you or in another office?

I don't think it's been mentioned here but if you have the rights, temporarily disable any and all anti-virus & firewall programs on your PC and the server for the time period of one check-in to see if that changes anything, obviously re-enable everything ASAP.

Eager to hear the answer to how big the file is too and whether or not this happens on other drawings.

---

Vault and PC are one and the same. I am the only one connected to it, and only user.

The first thing I thought of was anti-virus also due to similar issues in previous installations, but as you questioned, the setup is different so I don't imagine any issues would occur since file transfer is only local, not over the network. Our antivirus is web based and therefore only scans web material.

The same anti-virus has been on my machine for over 6 months. This issue is has not been occuring for that long.

As above, files are not discriminated on, including based on their size.

[Neil_Cross]

Have you got DWF creation switched on?

I've seen this happen before almost identically, but it was around 4-5 years ago on a much older version of Vault and I can't for the life of me remember what the issue was, it might come back to me.  But DWFs jumped to mind.  If you have them enabled during check-in, switch the creation off and see if that makes a difference?

[Neil_Cross]

Have you got DWF creation switched on?

I've seen this happen before almost identically, but it was around 4-5 years ago on a much older version of Vault and I can't for the life of me remember what the issue was, it might come back to me.  But DWFs jumped to mind.  If you have them enabled during check-in, switch the creation off and see if that makes a difference?

[Mark.Lancaster]

In addition to what Neil said, anything in your Windows Event log?   And when you say your up to date, the Vault Basic server and client have the same build #.

[Mark.Lancaster]

In addition to what Neil said, anything in your Windows Event log?   And when you say your up to date, the Vault Basic server and client have the same build #.

[Anonymous]

---

@Neil_Cross wrote:

Have you got DWF creation switched on?

I've seen this happen before almost identically, but it was around 4-5 years ago on a much older version of Vault and I can't for the life of me remember what the issue was, it might come back to me.  But DWFs jumped to mind.  If you have them enabled during check-in, switch the creation off and see if that makes a difference?

---

Hi Neil,

Yes I do, but it gets past that process in the progress bar and gets to the last part which is vault check in - as shown on progress bar above.

I will try this though.

[Anonymous]

---

@Neil_Cross wrote:

Have you got DWF creation switched on?

I've seen this happen before almost identically, but it was around 4-5 years ago on a much older version of Vault and I can't for the life of me remember what the issue was, it might come back to me.  But DWFs jumped to mind.  If you have them enabled during check-in, switch the creation off and see if that makes a difference?

---

Hi Neil,

Yes I do, but it gets past that process in the progress bar and gets to the last part which is vault check in - as shown on progress bar above.

I will try this though.

[Anonymous]

---

@Mark.Lancaster wrote:

In addition to what Neil said, anything in your Windows Event log?   And when you say your up to date, the Vault Basic server and client have the same build #.

---

Windows Event Log? please explain?

Yes to build being the same

[Anonymous]

---

@Mark.Lancaster wrote:

In addition to what Neil said, anything in your Windows Event log?   And when you say your up to date, the Vault Basic server and client have the same build #.

---

Windows Event Log? please explain?

Yes to build being the same

[Neil_Cross]

If that doesn't work, based on your Vault ADMS being local, log out of Vault in AutoCAD then log back in but use the server name:

localhost

Try a check-in, if that makes no difference, try:

127.0.0.1

If there's still no difference, could you open ADMS and go to the logs in the left hand side bit, export both the console and server log for today and attach it to this thread? And jot down at what time you experienced a failed check-in so that it's easy to find that entry in the log.

[Neil_Cross]

If that doesn't work, based on your Vault ADMS being local, log out of Vault in AutoCAD then log back in but use the server name:

localhost

Try a check-in, if that makes no difference, try:

127.0.0.1

If there's still no difference, could you open ADMS and go to the logs in the left hand side bit, export both the console and server log for today and attach it to this thread? And jot down at what time you experienced a failed check-in so that it's easy to find that entry in the log.

[Anonymous]

Will try both of these and get back to you.

Thanks for your help, as always your time is invaluable.

[Anonymous]

Will try both of these and get back to you.

Thanks for your help, as always your time is invaluable.

[Anonymous]

I turned off the dwf creation and it seemed to have worked all day, but now as I get ready to leave for the day it's frozen up again. I will endeavour to get back to you about the other changes you suggested early next week.

freeze is happening as we speak so I will keep the time logged and copy the logs as well

[Anonymous]

I turned off the dwf creation and it seemed to have worked all day, but now as I get ready to leave for the day it's frozen up again. I will endeavour to get back to you about the other changes you suggested early next week.

freeze is happening as we speak so I will keep the time logged and copy the logs as well

[Anonymous]

Logs from friday attached.

freeze occured around 4pm

[Anonymous]

Logs from friday attached.

freeze occured around 4pm

[Anonymous]

---

@Neil_Cross wrote:

If that doesn't work, based on your Vault ADMS being local, log out of Vault in AutoCAD then log back in but use the server name:

localhost

Try a check-in, if that makes no difference, try:

127.0.0.1

If there's still no difference, could you open ADMS and go to the logs in the left hand side bit, export both the console and server log for today and attach it to this thread? And jot down at what time you experienced a failed check-in so that it's easy to find that entry in the log.

---

Just did a iisreset, logged out, changed server name to localhost, logged in and upon check in it's frozen again. Will try 127.0.0.1 next.

[Anonymous]

---

@Neil_Cross wrote:

If that doesn't work, based on your Vault ADMS being local, log out of Vault in AutoCAD then log back in but use the server name:

localhost

Try a check-in, if that makes no difference, try:

127.0.0.1

If there's still no difference, could you open ADMS and go to the logs in the left hand side bit, export both the console and server log for today and attach it to this thread? And jot down at what time you experienced a failed check-in so that it's easy to find that entry in the log.

---

Just did a iisreset, logged out, changed server name to localhost, logged in and upon check in it's frozen again. Will try 127.0.0.1 next.

[Anonymous]

fail on the 127.0.0.1 as well

[Anonymous]

fail on the 127.0.0.1 as well

[Anonymous]

Hasn't frozen all day with the only change from yesterday being that the computer has restarted.

I am using the PC name as the local host as it was originally and DWF creation is still off.

[Anonymous]

Hasn't frozen all day with the only change from yesterday being that the computer has restarted.

I am using the PC name as the local host as it was originally and DWF creation is still off.

[Anonymous]

---

@Neil_Cross wrote:

Have you got DWF creation switched on?

I've seen this happen before almost identically, but it was around 4-5 years ago on a much older version of Vault and I can't for the life of me remember what the issue was, it might come back to me.  But DWFs jumped to mind.  If you have them enabled during check-in, switch the creation off and see if that makes a difference?

---

I've accepted this as a solution, as it's the only thing I've changed and haven't had issues since.

Thanks again Neil.

as always, your help in this forum is invaluable.

[Anonymous]

---

@Neil_Cross wrote:

Have you got DWF creation switched on?

I've seen this happen before almost identically, but it was around 4-5 years ago on a much older version of Vault and I can't for the life of me remember what the issue was, it might come back to me.  But DWFs jumped to mind.  If you have them enabled during check-in, switch the creation off and see if that makes a difference?

---

I've accepted this as a solution, as it's the only thing I've changed and haven't had issues since.

Thanks again Neil.

as always, your help in this forum is invaluable.

[Neil_Cross]

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.  

[Neil_Cross]

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.