topic Inventor 2016 & Configurator 360 Unspecified Error Messages in Inventor Forum

Inventor 2016 & Configurator 360 Unspecified Error Messages

D0UGLAS — Wed, 13 Dec 2017 17:55:17 GMT

Is it just me or are there others, who spend most of their time trying to fix bugs, trawling through discussion pages trying to find a solution to faults within models, ilogic, missing geometry etc rather than actually producing any drawings?

These are the latest:

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

Autodesk.ETOBase.UserReportException: Exception in function iv_updateAssemblyParameters [Root.theKid]|||| Exception in function Update failure: ||||Inventor errors:|||| Placed member file is missing and can not be found|||| GA01.iam: Errors occurred during update|||| Placed member file is missing and can not be found

Oh and let's not forget LOD representations and BOM's what a nightmare.

kelly.young has edited your subject line for clarity: BUGS N FIXES

Re: Inventor 2016 & Configurator 360 Unspecified Error Messages

Mark.Lancaster — Wed, 13 Dec 2017 17:55:34 GMT

@D0UGLAS

It helps if you specify Inventor version and what updates you have applied to your version of Inventor.

I assuming this error is from an iLogic program or something else. Give us exact details so we can help pinpoint the problem or offer up solutions.

Re: Inventor 2016 & Configurator 360 Unspecified Error Messages

D0UGLAS — Wed, 13 Dec 2017 17:55:52 GMT

Hi Mark,

I use inventor 2016 R3 and Configurator 360. (Active licenses: Autodesk Product Design Suite Premium 2016)

My models work in Inventor but when I have a drawing and an assembly open occasionally report the Unspecified error (Exception from HRESULT: 0x80004005 (E_FAIL))

I am having difficulties with the Configurator 360 which reports the same message in the following context

Autodesk.ETOBase.UserReportException: Exception in function iv_updateAssemblyParameters [Root.theKid]|||| Unspecified error (Exception from HRESULT: 0x80004005 (E_FAIL))||||Inventor errors:|||| Attempting to end an invalid transaction. Id: -1006814016

The error

Specifically occurs within the configurator.

I have written to the configurator team for assistance on both errors.

But any help will be much appreciated.

Kind regards

Douglas.

Re: Inventor 2016 & Configurator 360 Unspecified Error Messages

johnsonshiue — Wed, 13 Dec 2017 17:56:17 GMT

Hi Douglas,

Based on the error message, it sounds like the issue is about iAssembly missing iPart/iAssembly member files. Are the iPart/iAssembly member files located in the folder expected by Inventor?

Many thanks!

Re: Inventor 2016 & Configurator 360 Unspecified Error Messages

D0UGLAS — Wed, 13 Dec 2017 17:56:35 GMT

Thanks Johnson.Shuie

Thanks for the pointer I was heading in that direction.

The message

does not occur with my models in inventor, but in Configurator 360 when I try to load an ikms file.

I had just compared several models that do not work as an ikms with one that does.

One difference is between iparts, which ties up with your observation.

Although the inventor model and configurator can find the parts or can create them, I'd guess the ikms file for the configurator is one step ahead and is looking for parts that don't exist.

With the working ikms the iparts are the default so there is no problem.

Re: Inventor 2016 & Configurator 360 Unspecified Error Messages

Jon.Balgley — Wed, 13 Dec 2017 19:22:01 GMT

I can't reproduce the error message using a simple test case that swaps between pre-existing and non-pre-existing iPart members.

E.g., upload zip of simple IAM model with a single iPart component, where only the current active member is pre-existing in the members folder ("PORTE" in your case), and no other members. On C360, change to different member, it works. Save as RFQ and open from RFQ ... it works.

In contrast, if I attempt to upload this IAM with NONE of the members, i.e., the entire members folder including the current active member is missing, then I get a different error, during the post-upload validation process, and it (correctly) won't let me go further.

I'll email you the model I'm using, which works. Perhaps you can add complexity back to it (relative to your original model) and reach the point where we start to see this error. Or, alternatively, strip complexity out of the original model, until you're not seeing the error. I do understand that it appears to be intermittent, and that makes it harder. But I have found that this "divide and conquer" technique is very effective at identifying the cause of problems.

Re: Inventor 2016 & Configurator 360 Unspecified Error Messages

D0UGLAS — Thu, 14 Dec 2017 08:28:04 GMT

Hi Jon,

From the Configurator 360 I can reproduce the error,

Autodesk.ETOBase.UserReportException: Exception in function iv_updateAssemblyParameters [Root.theKid]|||| Exception in function Update failure: ||||Inventor errors:|||| Placed member file is missing and can not be found|||| filename.iam: Errors occurred during update|||| Placed member file is missing and can not be found

It occurs on opening an ikms file which searches for an ipart when the ipart folder of an upload model is not fully populated. ie "Placed member file is missing and can not be found"

The cause.

Inventor and configurator 360 are able to create new iparts however

1) ikms files require fully populated ipart folders.

Note: Pack and go of the model from inventor does not populate the ipart folder.

Solution 1 upload to configurator 360 from within inventor.

1) Ensure all iparts are present in their subfolder.

2) Upload models to configurator from within inventor ensuring: flag files to include "All files in assy folder and subfolders"

Solution 2 upload to configurator 360 from configurator 360.

1) Before creating the required zip file, ensure all referenced iparts are present in their subfolder.

Many thanks to those who helped.

Re: Inventor 2016 & Configurator 360 Unspecified Error Messages

D0UGLAS — Thu, 14 Dec 2017 09:53:44 GMT

Solution 3 From: Jon Balgley

Testassy.IAM with:

one component, testpart.ipt. (with iparts)
One parameter named “index”, type “ul”, default value “1 ul”. Make it multi-value, with values from 1-9.
One rule containing this line:

iPart.ChangeRow("testpart", index)

One form showing the ‘index’ parameter.

Then zip up the testassy.IAM + testpart.IPT + “testpart" folder with only the default member present (or none).

You can see that it will create the new member files as needed; they don’t need to be pre-created to be used from the iLogic rules. But the member(s) that are in use in the initial state of the IAM (default in this case), must exist in the uploaded package, in order to open the default configuration.