Unspecified error (0x80004005 (E_FAIL)) on 'Place iLogic Component' with form and 'Show on Place Component' enabled

Unspecified error (0x80004005 (E_FAIL)) on 'Place iLogic Component' with form and 'Show on Place Component' enabled

Maxim-CADman77
Advisor Advisor
370 Views
3 Replies
Message 1 of 4

Unspecified error (0x80004005 (E_FAIL)) on 'Place iLogic Component' with form and 'Show on Place Component' enabled

Maxim-CADman77
Advisor
Advisor

When I use 'Place iLogic Component'* that contains the iLogic-form and 'Show on Place Component' enabled I get "Unspecified error (0x80004005 (E_FAIL))":

MaximCADman77_0-1734346022320.png

More info:
System.Runtime.InteropServices.COMException (0x80004005): Unspecified error (0x80004005 (E_FAIL))
at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
at System.RuntimeType.ForwardCallToInvokeMember(String memberName, BindingFlags flags, Object target, Object[] aArgs, Boolean[] aArgsIsByRef, Int32[] aArgsWrapperTypes, Type[] aArgsTypes, Type retType)
at Inventor.ModelState.Activate()
at ThisRule.Main() in rule: Rule0, in document TutorialFile-(Inv22-ShowFormOnPlace-1)-02.ipt:line 4
at Autodesk.iLogic.Exec.AppDomExec.ExecRuleInAssembly(Assembly assem)
at Autodesk.iLogic.Exec.AppDomExec.ExecCodeHere()
at Autodesk.iLogic.Exec.AppDomExec.ExecCodeInOtherDomain(AppDomain otherDomain, String assemName)
at iLogic.RuleEvalContainer.ExecRuleEval(String execRule)

 

When I use same workflow with copy of .ipt with the only difference - form property 'Show on Place Component' disabled (see both IPTs attached) - I get standard table-like form with key parameters and place process works as expected (Model State - switches to the one chosen by user).

 

What I'm missing?

 

*
Not sure if it is important but iLogic-component is located in folder set be library in active project.

 

PS:

This issue is reproducible in Inventor 2022.6 and 2025.2.1 (believe also in between releases).

 

PPS:
Dear @MjDeck could you, please, look at this?

Please vote for Inventor-Idea Text Search within Option Names

0 Likes
371 Views
3 Replies
Replies (3)
Message 2 of 4

MjDeck
Autodesk
Autodesk

Hi Maxim - thanks for reporting this. I created internal issue INVGEN-82583 for this problem.


We can probably fix it in a future release of Inventor. But note that even if we can avoid the error message and activate the model state in the part, there is still a problem.

You can see this by using the form or editing the parameter value directly in the part itself, before placing it in an assembly. The ModStateNum parameter is itself captured in the model state table. When you change it:

  • The value changes in the current model state. Now the current model state is out of sync with the required value.
  • The rule activates the correct model state for that value.

Now you have two model states that have the same value of ModStateNum.


This would work much better if there was a way to keep the ModStateNum parameter out of the model state table. You can do that in the part itself by setting the Edit Factory Scope mode (under Manage > Author). But that doesn't help with Place iLogic Component.

If you only want to activate a different model state, there is no need to use Place iLogic Component and create separate copies of the part. It would be better to create a parameter and rule in the assembly itself to activate different model states in each component occurrence. Then you only need one copy of the part.


Mike Deck
Software Developer
Autodesk, Inc.

Message 3 of 4

CGBenner
Community Manager
Community Manager

@Maxim-CADman77 Did the information provided answer your question? If so, please use Accept Solution so that others may find this in the future. Thank you very much!

Did you find a post helpful? Then feel free to give likes to these posts!
Did your question get successfully answered? Then just click on the 'Accept solution' button.  Thanks and Enjoy!


Chris Benner
Community Manager

0 Likes
Message 4 of 4

C_Haines_ENG
Collaborator
Collaborator

Could you upload the code you use as a text file?

0 Likes