Vault basic problems checking in some dwg

[Anonymous]

We just started using Vault Basic 2016 and have been able to check in drawings no problem. These are AutoCAD mechanical dwg files. We can check in drawings that are 4200 kb or smaller. If over 4200 kb we can not check in our PC locks up and all Autodesk software is not responding. After the 15 min time out we get error "The following files could not be checked in due to restrictions." "The underlying connection was closed: A connection that was expected to be kept alive was closed by the server."

[upchurt]

Hello,

Thanks for reaching out via the forums for this issue. Are you seeing this file size type restriction with all files? If the problem is only occuring with DWG files you can try these steps:

1. On the Vault server, using Windows Explorer, go to ‘C:\Windows\Temp’ directory. Locate all the ac$ files

2. At the Windows Command prompt: IISRESET /STOP

3. Move ac$ files out of the ‘C:\Windows\Temp’ directory.

4. At the Windows Command prompt: IISRESET /START

5. In Vault, try checking in the drawing

This generates a new property filter for the AutoCAD drawings and should allow the check in.

If this issue is occurring with any file that is added to the Vault then it may be a problem with request filtering in IIS. If that is the case you can try uninstalling/reinstalling Vault (make sure you have a backup first) to reset IIS to defaults. Otherwise you can try this guide to changing the request filtering settings in IIS:

https://www.iis.net/configreference/system.webserver/security/requestfiltering/requestlimits#004

Please let me know if this helps and if not please attach your Vault logs and we can further troubleshoot this issue. By default the logs are located here on the Vault server:

C:\ProgramData\Autodesk\VaultServer\FileStore

-Trent

[upchurt]

Hello,

I wanted to follow up on this post and see if the steps I posted helped with this issue.

Let me know if there's anything we can help with and if needed we can start a support case to resolve this issue.

-Trent

[Anonymous]

No sorry this did not help.

Jackie

The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited, please contact the sender by reply email, and destroy all copies of the original message. To reply to our email administrator directly, please send an email to postmaster@pecofacet.com.

[Anonymous]

We have ran a repair and reinstall on the server. Still same issue. I am open to any suggestions and starting a support case.

My It seams to think the problem started when they installed the backup agent. So the removed the backup agent but the problem still persisted.

They also said they moved to faster drives at the vmware level and that the OS does not know it was moved. Could this be the issue?

Thank you,

Jackie Blair III

[upchurt]

Hi Jackie,

Thanks for getting back to me. I sent you a PM regarding the support case and will follow up here with what solution we find.

-Trent

[upchurt · Accepted solution]

For anyone else running into this issue. We found that this problem was related to the FortiClient software in use. Once the client was rolled back to the 5.2.3 version checks ins were working OK.

-Trent