Just wondering if anyone else has been seeing this issue and how you all addressed it or maybe help you address it.
We've been having Vault Workgroups 2012 come to a stand still a few times, most recently this week.
On top of us finding numerous issues with our older AutoCAD files interacting with Vault (see my other thread here), we have verified that if our w3wp process gets to +1.7gig or more, Vault comes to a crawl or crashes.
What we've been able to verfiy also is that when a user activates a Inventor file out of Vault, this process increases in memory usage and then drops back down to normal once the process is done. But when an AutoCAD file is checked out or into Vault, the memory jumps up as expected, but then it only resets about 1/2. In other words if the Acad file bumps the process memory up by 500mb, when it's done, it only releases 250mb, whereas Inventor releases all 500mb. So what happens is with numerous users all activating Acad files, the memory amount keeps mounting (5 steps forward, 3 steps back) until it eventually reaches the 1.7g range and Vault starts to drag.
The IT department here will now be running or invoking a IIS reset over night each night to clear the w3wp process memory in hopes we don't see this again.
Just wondering how anyone else who might be experiencing this is handling it?
Solved! Go to Solution.
Definitely sounds like a memory leak. Are you running SP1 and post SP1 hotfix?
We're on SP1, but haven't installed the post SP1 hotfix as of yet.
I am not sure that I can offer any help, just a confirmation that we have this issue as well!
We see this happen quite often. Our Vault never seems to slow, but frequently locks up. The strange thing is that it will occur every day for a week (sometimes two or three times a day) and then it will not happen again for 2 weeks, 3 weeks, etc..
We store AutoCAD .DWG files as well as .PDFs, .DOCs, etc... in out Vault (basic), but no inventor files. Unlike yours, ours will usually get to ~3GB before it locks up. The ADMS console runs on a dedicated server, so when this occurs, we do a reset of IIS and everything goes back to normal within a few seconds.
We have another server in a remote office that runs Vault Server as well. I set it up about 6 months ago and have never had to restart IIS. Granted it is not used nearly as much as the Vault server at this location, but still strange. The local ADMS console is using SQL Express while the remote ADMS console uses the full version of SQL (not sure if that would really make a difference).
I have not install SP1 as of yet.
Hope it helps!
I'd suggest doing as our IT guy here did and write up a script to do a daily restart/reset of the IIS process, thus clearing the memory. It's been working fine for us since...knock on wood.
Start with some of our most frequented solutions or visit the Installation and Licensing Forum to get help installing your software.