Autodesk Vault

[#1]

I have some files in our Vault giving me headache..

As far as I can tell they all are all shrinkwrap/shrinkwrap substitute parts.

They have successfully been created and checked in and most of them updated more than once. "Suddenly" we get the following error when trying get/checkout from the Vault.

"Error 0 - Operation failed: System error. Please contact your system administrator."

If we try to open an assy where one of the failing shrinkwraps are used we get a different error:

"Vault - The server returned the following information: Unknown Server Error."

And the failing parts are unresolved in the assy.

I think we have all updates and service packs installed both for Inventor 2012 and Vault 2012 (basic/free/included version)

Any hints or tips?!

Thanks in advance.

Ivar Mo

Fimtech AS

Norway

[#2]

The funny thing is that I can successfully checkout an older version and update that one, but once checked in - same error...

Anyone know if this is part related or Vault related?

[#3]

Hi,

Is there anyway you can share the Dataset with me? You can send them to me at senthilDOTkumarATautodeskDOTcom

Thanks!

[#4]

One of my shrinkwraps are in the mail.... 37MB... Do you accept that big attachments in your mail system?!

This file is made from a STEP or IGES import - probably imported into IV2008.

The file has an insane detail level, but the "Fill all holes" option was not present back then.... :-)

Thanks for looking into this! :-)

[#5]

Did we get this resolved?

[#6 · Accepted solution]

Yes, it was simply a iisrestart issue...

My backupscript did that but not in correct order.

[#7]

Hi,

I have the same issue. Have I understand it right, did backup solve this issue in your case?

[#8 · Accepted solution]

Hi!

Yes and no.. The problem was both caused by the backup script I had at the time, and the issue was solved by changing the script sligthly...

Try running this on a Command Prompt window on your server:

iisreset /stop

iisreset /start

If this works, try to add the same lines at the bottom of your backupscript.

Hope you solve your problem!

/Ivar Mo

Norway

[#9]

Thank you. It has helped, problem is solved now.