iLogic Event-Driven Rule: Cannot find a rule with the name"" (in the document <open document)

[TYoung_Combi]

EDITED TO ADD: It looks as if the rules lost their names during transition from 2020 software to 2023 software, causing this issue.

Since upgrading to Autodesk 2023 software last week, many of my users are getting the following error when closing an assembly:

"More Info" text:

System.ArgumentException: RunRule: Cannot find a rule with the name: "" (in the document TBSR0400002.01.iam).

   at Autodesk.iLogic.Core.RuleProcessing.RuleRunManager.RunRule(String ruleName, NameValueMap ruleArguments)

   at iLogic.EventsRuleRunner.RunListOfRules(Document doc, iLogicCentral central, InventorEventCode eventCodeA, IList`1 ruleNames)

As stated, this was not happening prior to the upgrade. What do I need to look for to stop this error from occurring?

[JMGunnar]

Any Event trigger ? 

Best Regards Johan

[TYoung_Combi]

@JMGunnar 

There were two event triggers showing rules with no names. I removed those nameless rules, and that took care of the problem.

I am very curious as to why they popped up after the software upgrade...

[JMGunnar]

Where did you remove the rule in "This Document" or All Documents ?

Johan 

[TYoung_Combi]

@JMGunnar I removed from 'This Document'.  The next time this happens, I will remove from 'All Documents'. Still curious as to why it happened after the software update.

[WCrihfield]

Do you recall if the rule(s) it was supposed to run were internal/local rules or external rules?  Have you imported your iLogic Configuration settings from before the upgrade?  (Tools tab > Options panel (may have to expand it down) > iLogic Configuration)  In that 'Advanced iLogic Configuration' dialog, you can use the buttons at the bottom to [Export...] your settings from your previous version of Inventor, then use the [Import...] button to import those settings into your new version of Inventor.  Within those settings, it tells Inventor where to look for your external iLogic rules, and what file extension you are using for your external iLogic rule files (among other things).  It may not be finding your external rules right now.  Just a thought.

[WCrihfield]

Also, just so you know, those Event Triggers settings are stored in two different places, depending on their scope.  The settings that are to effect 'All Documents, 'All Parts', 'All Assemblies', or 'All Drawings' are stored in an external XML file.  And the settings that are to effect just 'This Document' are stored in a hidden iProperty set, within the document itself.  We have been able to access that hidden property set since back around 2012-13, by discovery, not by design, but users accessing it and using it by code, instead of through the user interface dialog, is not recommended by Autodesk.  If you can't get this fixed through normal means, or by simple settings changes, and it is a widespread problem, we may be able to create a batch type iLogic solution for helping to clean some of that up.

[JMGunnar]

@TYoung_Combi 

If only this file the error occurs

I have no direct answer.  / 

more then soultion i have too remove rule from This Document event.

/ as @WCrihfield  writes .

"all documents"  controll external rules. 

and have nothing with This document event.

if error occurs on many files  in  again, you update this post.

Best Regards Johan G

[TYoung_Combi]

Our documents have one particular rule that is fired with a "New Document", "Before Save Document", and "Close Document". Somehow, two of the three occurrences had their rules' names disappear and they appear as a blank rule under the Event Triggers and interestingly enough, it didn't happen with ALL our files; it only sporadically affected files.

I appreciate everyone's feedback on this issue.

[JMGunnar]

problems that occur sporadically

are usually the most difficult to put your finger on

1.do the files consist of ipart / iassembly 

2.does it occur in copy design vault ?

3.what do the rules do ? 

4.in which version was the file created that causes problems or does it happen in new files as well

@TYoung_Combi 

[maxim.teleguz]

ill just leave this here, it is a FIPS error. Policy change that the workplace did. 

This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms when...

[Sumit_ChauhanNZXE4]

how to remove

[JMGunnar]

Best JM Gunnar @Sumit_ChauhanNZXE4