"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-

[Qube-it]

Apparantly I can't do anything with Vault except check-in and check-out files. Copy Design doesn't work, moving files doesn't work, and renaming files doesn't work.

-Brian Hall-

[Anonymous]

Hello Brian,

What version of Vault are you running? And is it possible to get the
ADMS log files? This might help us resolve your issue.

Thanks,
Jim

"Qube-It" wrote in message news:6302846@discussion.autodesk.com:

> Apparantly I can't do anything with Vault except check-in and check-out files. Copy Design doesn't work, moving files doesn't work, and renaming files doesn't work.
>
> -Brian Hall-

[Qube-it]

I am using ADMS 2010. I will post the log files shortly.
-Brian Hall-

[Qube-it]

Here's the server log for the day I made my second post on this thread.
-Brian-

[Qube-it]

Here's the Console Log for the same day.
-Brian-

[Anonymous]

Hi Brian,

In looking at the issue, we are unsure if it is data specific. Does
this only happen with specific file types? Is it possible to open up an
issue with customer support? This way we might be able to resolve your
issue.

Thanks,
Jim



"Qube-It" wrote in message news:6304363@discussion.autodesk.com:

> Here's the Console Log for the same day.
> -Brian-

[Qube-it]

Good idea. I'll open up a support request. I don't know why I didn't before? I guess I'm just so used to just coming here. 🙂

It's not file specific, because I have tried it on many different files (and folders for that matter). I have a theory, but I don't believe I can discuss that on this forum, so I'll go ahead and open up a support request. Thanks Jim.

-Brian Hall-

[Qube-it]

Tracking number for support request is: 1-7748472981

-Brian Hall-

[jgm]

What was the solution for the for support request is: 1-7748472981?

I have a customer having the same problem descript.


Regards

Jens Moeller - CDLIGHT

[mrm01]

I am having the same issue.  Could you update us on the solution?

Thanks!

[spascual]

I'm having the same problem, but my customer design has a substitute part on a level of detail interface.

I thing this is causing the problem.

Help please it very urgent next 21 we start updating meterials to SAP.

Regards

[spascual]

Hi Sirs,

If I delete the level of detail, "substitute", it runs well

May be your **** have not something "normal" that makes this error.

REgards

[spascual]

When I am applying check.in, the substitute is not active and not try to check-in. I think this is the problem

regards

[patricksalvador]

Has there been any official resolution to this error by Autodesk?  I have encountered it today and the above fixes have not worked.  I am using Collaboration 2010 and Inventor pro 2010.

[yuhui.zhang]

Hi All,

There is a hotfix avaiable from Inventor side on the issue of Copy Design with substitute part. Please try again after apply "Hotfix - The property "ReferencedDocumentDescriptors" of substitute cannot be read" (link: http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=15591207&linkID=9242019)

Note: If you do not have Inventor 2010 Service Pack 3 please download and install prior to installing this Hotfix.

Hope it helps.

[mthomas]

We're now experiencing the same issue but only on select files... has anyone had a resolution?

[mthomas]

nevermind... the suggested hotfix corrected the problem!

[Anonymous]

I am having this problem using Vault 2011 SP2.  I cannot move files from one folder to another with Vault Explorer 2011 SP2.

[Anonymous]

Just to add, I am running Inventor 2010 with Vault 2011.  I have applied the patch above on top of SP3 but the problem persists for most files.