Inventor 2025 BUG on check-in files to Vault (iLogic checks)

[jonathan.victor]

I'm having trouble to check-in files to Vault, some files when we click on check-in trows the error message below, and makes it impossible to check-in, even on files that dows not have rules or event triggers setted, the error happens, not a single one action that I've tried worked. How can I fix it? The image below show an exemple that happens on a iAssemblie file and each one of the members. This error showed after migrating from V2022 to V2025. I've seem this error to show in drawings and assemblies, at the first moment.

Another post on API forum for the same issue, when I thougt it was an iLogic issue

( https://forums.autodesk.com/t5/inventor-programming-ilogic/inventor-2025-vault-ilogic-checks-issue/m... )

@johnsonshiue 

@WCrihfield 

[WCrihfield]

Hi @jonathan.victor.  I have not used Vault yet myself, even though our company has been talking about implementing it for years, and have plans to in the near future.  And, I am still using Inventor Pro 2024.2.1, so not using 2025 yet.  So, I am not able to test or recreate your situation, and may not be the best candidate to figure it out for you right now.  However, I have been working extensively with iLogic rules for many years now, and have utilized both the 'Event Triggers' dialog's settings, and custom event handlers within rules for years not too, so I might be able to at least ask a few questions, or comments that may help in that area.

When you go to the Manage tab, iLogic panel, and click on the Event Triggers dialog.  You will notice that there are 5 tabs along the top of that dialog (in 2024).  The tab on the far right named "This Document" is for stuff that will only effect this one Document.  However, if rules contained within this tab do tasks that reach into Documents that are referenced within this Document, then these settings can potentially effect many different documents.  Now, look into each of the other tabs, to see if there are any settings in those.  It can be difficult to understand at times, but if you put a rule under an event on the All Documents tab, then you may see that same rule, under the same event, (but greyed out) in at least one of the other 'document type specific' tabs (matching the type of the current document), and may also see that same rule, under the same event, on the 'This Document' tab (also still greyed out).  Similarly, if you put a rule under an event in the Drawings tab, and the current document is a drawing, you will see that same rule, under the same event, in the This Document tab also.

Rules placed under the Before Save event can be tricky to design properly at times.  For instance, you do not want to use any code within that rule that will 'save' the current document, because that can cause an endless loop, since this rule is triggered to run by saving.  This document will already continue to be saved after your rule finishes running...at least that is what should happen.  Also, if a rule is designed to run in the middle of 'catching an event', then there are certain things that likely should not be included in those types of rules.  Things like MsgBox or MessageBox calls, because those will 'pause' the rule from continuing until you click the OK button on those dialogs, then the code will continue to run the rest of the code after that line of code.  Those types of interruptions are not good to use within code that is running in the middle of an event.  There are other types of dialogs that can sometimes be shown while code is running also, and those should usually also be avoided by codes running in the middle of events.

Just some food for thought.

[jonathan.victor]

Thanks for your fast replying, we are familiar with all those event triggers and it's bahaviors on the different modes for drawings, documents, etc. I have checked every tab and existing codes, since Iwas the resposible for creting them, and yet, no one is set to run on on thse files or file types for default on the files that I've tested, I still don't know what is causing this behavior on Vault, on my company I'm checking my colleagues Inventor files looking for some pattern that we could identify the cause. Thanks ever sinc, and I'm surprised for you not using Vault tbh.

[johnsonshiue]

Hi Jonathan,

I am sorry I am not a Vault expert. I can only speculate it. This sounds that on check-in, Vault has an option to check if there is an iLogic rule. What if the check is disabled? Or what if iLogic Add-In is unloaded?

Many thanks!

[MjDeck]

Hi @jonathan.victor , are you saying that the workaround of temporarily disabling Event Triggers ( as described in Message 15 of your other thread ) no longer works?

Another thing to try would be creating an environment variable named iLogicCheckInOpenAll and set it to False. Unlike the other workaround, this one you would only have to do once. Exit Inventor, set the variable, and restart Inventor. To set the variable, follow the procedure listed under "Set environment variables in the System Control Panel" on this page.

[jonathan.victor]

Hi @MjDeck , yes, it works as a temporary workaround, since it turns possible to check-in to Vault, but it also makes us to, on majority of cases, click on close document to pop-up the check-in dialog if I just click on check-in button, Inventor saves the document and dependent documents, but throws an "Some documents had save unsuccessful" error message. This thread I opened since I noticed it's wasn't an ilogic specific issue, but an Inventor one.

I'm not able to test your Local Variable method right now, but I'll talk to the my IT team to test this. Thanks ever since.

[MjDeck]

Hi Jonathan - the "Some documents have save unsuccessful" error sounds like a separate problem. If you want us to look at that, please post sample files.