Inventor Check In Trouble with Vault Basic 2016

[jnewton534097]

This has happened on two computers I have. I though I was have problems with one computer and setup a second computer but the same has happened. Initially after setting up the vault client to connect to my vault server via LAN, everything works fine check out check in no problem. After about 2 weeks of vault usage things start happening. I pretty much have to coax it to check parts out and eventually you can't check in any parts. It just hangs and the computer dings at me. This is a big problem for me since we just hired a second cad guy. Additional note: I don't have any problem checking parts with Inventor on localhost. Current on all service packs for Inventor, Vault Client, & Vault Server.

Is there some type of IIs Server user quota limit? I can't seem to find anything about this problem. Any ideas?

Thanks in advance.
John Newton

[mflayler]

There could be numerous reasons why this is happening but there is not enough information in your post to really dig into it. So lets start off with the easy stuff...

Do you have NOD32 Antivirus running anywhere? This has been identified as an antivirus program that actually stops Vault functionality in a recent update.
What are your server specs, version of Vault, etc
Can you attach your Vault Logs; ADMS, Server, etc
What version of SQL are you running with this Vault, be specific for SQL version

You might also find more help on the Autodesk Vault forums as more people check there than the AUGI forums. Either way this information should be supplied.

[jnewton534097]

Thanks mflayler for you response. Specs as follows:

Autodesk Vault Basic 2016 client Build 21.1.4.0 Update 1
Vault Basic Server Build 21.1.4.0 Update 1
Internet Information Services (Version 7.5.7600.16385)
SQL Server 2008 Express Edition Version 10.3.5500.0

Server/Workstation:
Dell Precision T3610
Intel Xeon CPU E5-1620 v2 @ 3.70GHz
16GB RAM
Windows 7 Pro 64Bit Service Pack 1

FYI: While I was getting all the above information I noticed that I had 2 SQL servers running, (AUTODESKVAULT) & (SQLEXPRESS). SQLEXPRESS must have been setup by default at install. I knew I wasn't using it and it was using resources so I disabled it and the SQL Server Browser. Long story short, now able to check in and out remotely. Only time will tell if this will fix problem for good.

Thanks,
John