When trying to perform some commands from a Vault client, such as Copy Design, Pack and Go, Grid Population or Get\Checkout, you can sometimes receive an error like this:-
Exception of type 'System.OutOfMemoryException' was thrown.
This message occurs due to a limitation in the amount of memory that can be addressed by a 32-bit process such as Vault 2012 (or earlier). Autodesk is aware of this memory limitation and is exploring ways to overcome it.
The Server Log will display this message.
Exception(Inner): Exception of type 'System.OutOfMemoryException' was thrown.
The Windows Event Viewer may display errors afterwards depending on the IIS timeout settings, such as:-
Source: ASP.NET x.x.xxxxxx.x
Event ID: 1309
Exception type: HttpException
Exception message: Request timed out.
Some customers may experience this error for the time after upgrading, which may be attributed to various factors such as the introduction of newer and more complex functionality interactions between the Vault client and Vault Server.
If you experience this error, we recommend that you try the following:-
Upgrade to Vault x 2012 Update 1 (where several improvements were made to better manage the 32-bit memory limitations)
Once, after applying Vault 2012 Update1, run "Update File References" and repeat until the process completes, successfully.
Re-organize files/folders into logical projects/products to avoid operations on large numbers of files.
Reduce the number of unnecessary columns displayed, especially Thumbnails (Right click on the column header> "Remove This Column")
Press F5 to refresh immediately prior to executing the command.Start
Start a new Vault Explorer session with no "Preview" or "Open in Window" memory cache history.
On the Vault Server itself,
Ensure that SQL has the latest supported service pack for the version of Vault being used.
Ensure that Vault Server is running the latest Service Packs and Hotfixes
Ensure the latest recommended SQL Maintenance Plan is configured and is scheduled to run regularly.
Analyse and address possible performance bottlenecks, such as Disk I\O, CPU and Memory.
Consider employing different strategies to reduce the impact. Such as limiting the number of connections to the Vault Server via licensing or IIS, Connection Limit Settings. (see this later blog posting "Limiting Users Connecting to A Vault Server" for one idea). Or adding additional Vault Server Sites using remote SQL (Not available in Vault Basic).
Removing any 3rd Party Bulk processing Addins, connecting to the Vault Server
Upgrade the Vault Server and Clients to a newer release. Vault 2013 is the first release to run the Application Pool as a 64 bit process and is large memory aware. It has many performance enhancing features, refer to the readme for more information.
Vault 2013 has further improvements making this less likely to occur.
Vault 2012 Update 2 reduces memory leaks and adds large memory awarenes