"Unspecified error (Exception from HRESULT: 0x80004005(E_FAIL))"

[Qube-it]

This error occurs when I try to do a copy design or move a folder or Inventor file inside the Vault client. I have rebooted the server that the ADMS sits on and rebooted my machine and one other that has access to it. I'm running Windows 7 and the other machine is running Windows XP pro (SP3). Both have the same problem. We are still able to check stuff in through the Inventor Vault interface, but unable to move or copy Inventor files. Please help.

-Brian Hall-

[donnie.mann]

Another example. Copy Design throwing the exact same error.

Vault Basic 2014 wih SP1 on Win7 x64 clients.  Affects all standard users on all PCs.

I'm not certain when it started, but pretty sure it's since we moved to 2014 3 weeks ago.  Certainly worked OK with Vault 2013 on Win7.

Have tried:

Replacing the IPJ (there's only one, and it's in the root folder).

Migrating files to Inventor 2014 (it happens with brand new files too)

Rebooting Server & Clients.

Installing Inventor SP1 (and rebooting again)

Turning off UAC is not an option for us unfortunately but I did test it logged in as a Domain Administrator and it worked perfectly so it looks like it's a similar issue.  I can see the files being copied down to the C:\TEMP folder, then the error dialog appears.  Clicking OK on the dialog cancels the operation and the files are removed from C:\TEMP.

Will log a call with Autodesk but wanted to post this anyway, just for the record!

#EDIT# By the way, Rename seesm to work fine, it's only Copy Design that's broken.

Donnie.

P.S.  Hi Mr Cross!  How's life in the sun?

[Maxim-CADman77]

One of our clients reported the issue on file renaming (even so she renames IPT the error is about renaming DWF).

I as administrator don't suffer any problems with the same renaming.

Vault Server version: Pro 2014 SP1 update 1 (build 18.1.8.0)

Client

OS: Win7 64bit Russian

Vault Explorer version: Pro 2013 SP1 Russian

Just in case - VE2010 is also installed on the PC

[Maxim-CADman77]

FYI, In our case insatalling Vault Explorer 2014 SP1 update 1 have helped

[donnie.mann]

Hi,

Just following up on this. As part of the support process from Autodesk, we were asked to bring Vault fully up to date, including applying Cumulative Hotfix 2. I didn't see anything in there that related to our problem, however since applying it, Copy Design now seems to be working properly again!

Donnie.

[Genicee]

I had the same problem. I was able to correct the error by making sure Inventor was open and registered before trying to copy design

Vault Pro 2014

Inventor Pro 2014

[kai.mecke]

Hi -

we just encountered this error during a copy design in Vault Professional 2015.

We figured out, that the project file (ipj) contained a library path within the project path itself. Vault did not like this cascading combination.

This combination was not a problem in 2013 (we updated from 2013 to 2015).

Good luck

[Neil_Cross]

Donald! Sorry just came across this, currently waiting on Symetri to give me some stuff so I'm trawling the forums throwing in my two pence!

Life in the sun? Well, I'm in Newcastle so it's ruddy baltic.  You're further away from the equator so one won't complain too much.  But asides from that it's all good!

Is there anything left to contribute to this issue? Don't particularly want to trawl through 5 full pages but the last few posts appear to be folk confirming a fix.

[iancross]

Just encountered same issue on one of my own VM Servers, Vault Professional 2015 SP1, Disabled UAC on Vault server. Problem is still there,

deleted Inventor Project file from Vault, Created new vault project file in inventor, checked it back into vault

All working fine

Thanks

Ian 

Vault Managed Services

[dilara.tapdik]

If you can do migrate inventor file, It will be work corretly.

[JensMoeller · Accepted solution]

This issue keeps popping up… In Inventor 2015 the problem occurred because the Inventor/Vault project file did not have any mapping to the Project Root and Libraries. Mapping the folder fixed the problem in my case.

[Richard.Rankin · Accepted solution]

Hi Everyone,

Although a very old thread, this continues to be one of the most read Vault forum threads ever.

Autodesk Support have handled a number of these issues over the years and have consolidated various solutions into one troubleshooting article.

Troubleshooting "Unspecified error" (Exception from HRESULT: 0x80004005(E_FAIL))

To hopefully help future readers, I will mark this posting as the accepted solution so that you can jump straight to it, without having to read the whole thread.