One or more documents have been modified but Save was unsuccessful. You must save the document prior to check in.

[bradeneuropeArthur]

Hi,

[ERROR] One or more documents have been modified but Save was unsuccessful. You must save the document prior to check in.

Why is Vault-pro or the Vault Add-in not able to tell me what files need to be checked.

This is one of the messages with no sense at all, if we don't know what files are mentioned!

Any help is appreciated very much.

Regards,

[gandhey]

Hello,

Please check if following helps :

https://knowledge.autodesk.com/support/vault-products/troubleshooting/caas/sfdcarticles/sfdcarticles...

Regards,

Yogeshwar

(Vault team)

[bradeneuropeArthur]

Hi @gandhey 

I knew that, but since the tree is about 40.000 items long/big I don't see it or the * is not there!

Furthermore Inventor and Vault know that there is a dirty mark and a save required. Why they are not able to list or give information about what files need to be handles?

Thanks and I appreciate your reply! 

[gandhey]

Hello,

I get your point, please help submit a post to the vault ideastation.

And for now please check if following filters in 'Vault Browser' can help you.

Regards,

Yogeshwar

(Vault team)

[bradeneuropeArthur]

Any other ideas?

[swalton]

I get this "very useful" error every so often.  The usual cause is that the user or Inventor dirtied a file without checking it out from Vault. The error message would be much better if it listed the offending files, but it does not. 

This error message has not been changed in the 12 years I have used Vault.

My workaround:

1. Use the Vault browser filter to show only unsaved edits.  
   1. Sometimes this does not work, so I start, but not complete a manual save of the top-level file in Inventor
   2. This seems to help update the file status between Vault and Inventor
2. Review each file to see if I made an intentional change
   1. If so, then check the file out
   2. If not, remember the file
3. Trigger a manual save with Inventor.
   1. Scroll through the save window and change all the files found in step 2 to Yes.
   2. Allow Inventor to save the files to disk, but don't check them out.
   3. If Inventor still won't save the files, I sometimes use Windows Explorer to change the file permissions from "Read Only".  Once this is done, Inventor will be able to save the files.
4. Check in the remaining files.

[CGBenner]

@bradeneuropeArthur  Has any of this information helped you with this issue?  I know this is one you've struggled with, but is there anything in here we can mark as a solution?

[bradeneuropeArthur]

Hi @CGBenner

The replies were very helpful, thanks for that.

But it will not solve the question.

Maybe the Vault team can confirm that they will take this in consideration with the programmers for the next releas(es)

Thanks for asking.

[francis.korde]

Hello, 

I see this topic now but we have had this error for a long time. 

We had it in 2018 and now in the 2021 version. This is mainly due to the fact that some files are "library files" that cannot be modified by almost anyone. And I know for sure that almost all of these files are up-to-date in the Vault. However, users who use these library items get this message almost every time they check in.
Will you ever work on how to manage file updates between Vault and Inventor?
For example, that a Release file cannot be modified in any way?

[bradeneuropeArthur]

Hi,

Is the application option update mass for parts and assemblies consistent for all machines.

This is one of the things that cause files from update 

[francis.korde]

Hello, 

Thanks for the question. 

I pushed the same configuration to all users so I hope so. 

I choose to update physical properties on parts only : 

This choice has been advised by our reseller. I never took the time to test every possibilities thoroughly  but I've read online and never fully understood how it works. I mean, this option clearly says "on save" but, the things is, I don't want Inventor to do anything with a non-check out assembly or part. 

In any case, most of the time, I have several sub-assembly with the star (which, I think, are triggering the message) but never a part. 

What is your recommendation on this? 

[johan.degreef]

@bradeneuropeArthur 

When I get this messag, I completely check out the main assembly that is open, do a save and check it back in. Does that solve your issue too?

[bradeneuropeArthur]

@johan.degreef 

No it doesn't solve it.

Because inventor does not check if files are released in Vault already. It only checks the readonly flag.

@

[SER4]

(Yes old post, just wanted to share some more knowledge).
I think my problem was that I had some Library assemblies that were originally downloaded from STEP files and saved locally.  Some of the parts from the STP that got saved locally have the same filename as some files already Vaulted.

I was only able to determine which components had this problem after I closed everything and reopened the top-level assembly and tried to check in again.  See: "One or more documents have been modified but Save was unsuccessful..." appears in Inventor when try....

So then I opened that locally saved Library assembly and replaced all from Vault those with the duplicate filenames.
Here is also some good options: "You must save the document prior to check in" appears in Inventor and not able to check in file to ...
[FYI, it looks like some people have had migration issues, but I don't think that was my problem here.  "(1) dependent files must be saved before they can be checked in" when checking in files in Vault (a....]

[kevin_j_morin]

these forums suck. Have yet to get some proper help or at the very least seen patches. I am deeply sad, we paid pretty hefty for broken software that just gets swept under the rug. and i bet that I am about to get censored for calling Autodesk out. Go ahead and continue getting that money as long as its "good enough" to work

[Frederick_Law]

---

@kevin_j_morin wrote:

these forums suck.

---

Problem not getting solved got nothing to do with Forum and it's users.

See this "notice" everyday.

Part of the endless loop of dirty files.

Check in and Release will cause files to get dirty, even files that are read only.

Vault then require a save to those files.  Usually it could save to "Release" files but failed on "Checked In" files.

They're both read only but one can write and one cannot.