idw's refuse to check in

idw's refuse to check in

benjaminlCXXVQ
Contributor Contributor
1,724 Views
8 Replies
Message 1 of 9

idw's refuse to check in

benjaminlCXXVQ
Contributor
Contributor

Ok, I've got 2 idw's that refuse to check in. Both drawings are different iAssembly configurations of the same assembly, there is only 1 part difference between the two. The drawings are basically identical besides that 1 part difference. I have been having trouble lately to get them to check-in to vault.

 

The most recent thing I did to the drawings was update the revision history table and add tags. The update was the addition to a couple label tags. 

 

The previous time I had them checked out, I struggled to get them checked in too, but I finally did manage it. This time I've done all the tricks I can think of: restarting both Inventor and Vault, rebooting the computer, opening and closing the idw's, updating the properties in the vault tab and running updates. Vault and Inventor are both up to date, all parts and subassemblies are checked in. The only thing that is not checked in, and has the green bubble under the vault browser tree is the top level idw that I am trying to get checked in.

 

When I hit check-in, I get the window popup that says " 'filename.idw' must be saved before it can be checked in. Do you want to save and continue?"
I've done this I don't know how many times. Sometimes if I freshly just reopened the file, it will look like it did something as it will cycle from sheet 1 to sheet 2 and back, but it will never bring up the window to check it in. Even just closing the file only asks if you want to save it, it never says anything about wanting to check it in. Even the idea of "maybe it will just work tomorrow" isn't working, as I have been trying to check these in since last Thursday and it is now Monday.

 

I've exhausted all the tricks I can think of, and I haven't seen quite this problem proposed in the forums. The one that sounded the closest said it just happened to work when he tried it the next day and did not offer a workable solution.

 

Any help would be appreciated!

0 Likes
Accepted solutions (1)
1,725 Views
8 Replies
Replies (8)
Message 2 of 9

johnsonshiue
Community Manager
Community Manager

Hi Benjamin,

 

I suspect you may need to check out the iAssembly factory file, the iAssembly member file and other reference files also.

Many thanks!

 



Johnson Shiue ([email protected])
Software Test Engineer
0 Likes
Message 3 of 9

benjaminlCXXVQ
Contributor
Contributor

I had previously tried that, and it hadn't worked. 
I did figure, what the heck, let's try it again.

I checked out the factory assembly, when that didn't work, I even checked out the iAssembly that was in a particular drawing. 

benjaminlCXXVQ_0-1727178879904.png

That way, both items on the vault browser tree for the .idw were considered checked out. It produced the same results.

benjaminlCXXVQ_1-1727178922002.png

 

It is only saying that the idw needs to be saved before checking in. When you hit yes, it thinks for a few moments (supposedly saving) and then does nothing. If you hit check-in again, it just does the same thing.

 

I can however just select the 2 assemblies and check just those in, even from the idw, vs going straight to the assembly file. If the idw is selected though, I only get this message saying it needs saved.

0 Likes
Message 4 of 9

johnsonshiue
Community Manager
Community Manager

Hi! I believe this may be related to the Save options. Please take a snapshot of Tools -> App Options -> Save and share it here. I suggest you make all conditions prompt to save (except Migration). And default to No to Save.

In this way, you will see which file needs to be saved and why.

Many thanks!



Johnson Shiue ([email protected])
Software Test Engineer
0 Likes
Message 5 of 9

benjaminlCXXVQ
Contributor
Contributor

Ok, so here's what I had:

benjaminlCXXVQ_0-1727264567911.png

 

And you're saying I should change it to this?

benjaminlCXXVQ_1-1727264614508.png

 

So, when I save, it is still telling me the top level idw needs to save, which is what it's been doing:

benjaminlCXXVQ_2-1727265037085.png

 

Then when I go to check-in, it still brings up the window saying it needs to be saved to check-in:

benjaminlCXXVQ_3-1727265736333.png

And it proceeds to do nothing noticeable when you hit yes.

Closing the file just asks you if you'd like to save before closing.

 

So, if it's actually a saving issue, how do I fix it and get it to "actually" save? 

 

 

 

0 Likes
Message 6 of 9

johnsonshiue
Community Manager
Community Manager

Hi Benjamin,

 

I think I need to see the files to understand the behavior better. If possible, please pack&go the Inventor files and share it on a cloud drive of your choice. Grant the download privilege to me ([email protected]).

Many thanks!



Johnson Shiue ([email protected])
Software Test Engineer
0 Likes
Message 7 of 9

benjaminlCXXVQ
Contributor
Contributor

I've sent it.

*Private information removed

0 Likes
Message 8 of 9

johnsonshiue
Community Manager
Community Manager

Hi Benjamin,

 

I have not receive the file. Please resend it.

Please do not share your email address here, since it is your personal information.

Many thanks!



Johnson Shiue ([email protected])
Software Test Engineer
0 Likes
Message 9 of 9

benjaminlCXXVQ
Contributor
Contributor
Accepted solution

Update:

 

@johnsonshiue took a look at my files and could not replicate the issue at hand. He had suggested for me to do these things:

  • Please make sure all critical Windows updates are installed and the graphics driver is updated. Close all apps and clean up %temp%.
  • Install the latest Inventor 2025 and Vault 2025 updates.
  • Go to Inventor -> Tools -> App Options -> Save -> set all “Prompts to Save” to Yes and set “Default Condition” to “Don’t Save.” This will give you clear ideas why the given file is listed in the Save dialog.
  • Disable the iLogic rules and try saving the idw file. After that, are you able to check in? If yes, it means something in the rules is hindering the check-in process.

The save options were already there, except for the migration was "no" on prompt to save, as he had previously stated above. I changed that to yes as well.

 

It seems that buried deep in some sub assembly were a couple nuts and bolts that needed migrated. We upgraded from Inventor/Vault 2022 to 2025 a couple months ago. We had migrated the entire library, so even I didn't think that would be the issue.

 

It took a couple saves, updating properties, and such to get it to sort it all out, but it DID finally check in this time!