Just spent over an hour getting a large project copied using Copy Design. Get everything the way I wanted it. It bombed when I hit the last "OK". The error I got was "Out of Memory Exception thrown.....".
Im running Windows 7x64. system has 12GB of ram installed. Only thing I had running in Vault 2012.
Guess I can try it again, but starting to lose confidence in Vault 2012 pretty quickly.
Here is a screen shot of windows Task Manager right after the crash.
Hard to believe that either of us was running out of memory...lol. Seems like that is just a catch-all message.
They updated it because of the issue of it displaying an additional prompt when you checked out stuff.
http://forums.autodesk.com/t5/Autodesk-Vault/Extra-message-when-I-check-out-file/m-p/3060770#M36693
They have also just released a hotfix for the "Value cannot be null" error. If you are seeing this error during a copy design, then install the patch. It fixed my issue.
http://usa.autodesk.com/adsk/servlet/ps/dl/item?id=17235740&siteID=123112&linkID=9261341
Hopefully they will get all the bugs worked out quickly. Only problem, by the time they get them worked out, Vault 2013 will be released. I've already made the decision NOT to roll out 2012 until it works correctly on my "test" machine.
Vault Explorer is only 32bit - so it is unable to access anymore than 2 Gbs of Ram. I run it out of memory constantly performing various tasks and I have 32Gbs...
Its x32... Thats right... forgot. Hopefully moving to x64 is in the works.
No kidding - its crippled the way it is now...
Don't think it's a 32bit issue since 2010 performed these functions well enough. What we know so far, there's a file limit, get latest copy design move etc., that's built into 2012, we've been told it's in the 14,000 link range. Restarting the web server will clear the errors from smaller actions until the limit is hit again. We routinely play with assemblies in the 15-20,000 part range that we simply can't access anymore because of this. Fortunately we found it in the testing phase, 99% of my users are still on 2010.
Eric
Inventor 2012 Pro 64bit Vault 2012 Pro Admin Windows 7 Pro 64bit Quad Core processor 2.26 Ghz 16 GB DDR3 RAM 1.5 GB Nvidia Quadro FX 4800 2 – 320 GB SATA drives
Has anyone found a fix to this problem yet. We updated to 2012 in December and now a few of our engineers are running in to being out of memory even though they are running Windows 7 x64 with more than enough processor and RAM.
This is becoming a major issue for us because a lot of our machines are very similar and it is very time consuming to save the assembly and then the drawing and then remap the source file of the drawing to the new assembly. The machines do not have many parts 3,000-4,000 max and if we could copy the design it would be much more productive.
Thanks,
Steve
The issue is the added functionality they added for 2012 which consumes whatever freeboard we all had with 2010 under a 32 bit structure.
SP1 helps a great deal.
Run "update file references" on everything.
Turn off as many of the main window metadata columns as you can live without.
These three steps made it workable for us. I spoke with Autodesk several times and the "fix" will be a 64 bit version but they couldn't say when that would be released.
Update file references appears to move file association data to the vault which makes copy design move etc. a lot faster and less memory consuming. It's a pretty big hit but it only has to be done once.
I also found that if you redirect your windows temp file to C:\TEMP it helps a bit as well. Ours was buried down in the users documents somewhere and I don't know if the file length got too long and windows just gave up or what but it somewhat helps.
Thanks,
Steve
where did you change the path for the C:\temp? I looked around under Control panel >System, but didnt see where to change it. Mine is the default location as well.
You are in the right spot, under Control Panel > System, on the left side there is a button for "Advanced system settings". At the bottom of the advanced tab there is a button for "Environment Variables..." Within that window you can edit the TEMP and TMP variables and point them to C:\TEMP.
Thanks,
Steve