Assembly Corruption - Internal error in persistence operation

Assembly Corruption - Internal error in persistence operation

chris
Contributor Contributor
1,787 Views
27 Replies
Message 1 of 28

Assembly Corruption - Internal error in persistence operation

chris
Contributor
Contributor

Hello everyone, hoping someone out there has had a similar issue and can offer some solutions. 

 

Back in October our entire department updated to Inventor 2024.1 and Vault Pro 2024.1. the upgrade process with smoothly for everyone but one of our users started to experience the following error on a weekly basis since then. It happens once a week to only 1 user but never at the same time or day consistently, she once had 3 in a single day.

 

1. She would open and work on an assembly like normal.

2. She would save and close the assembly (sometimes checking into the vault, other times not just to switch to another task or go home for the evening).

3. She would go back and open the assembly only to get the following messages:

chris_0-1714487101510.png

(ignore the file path, this is just a Onedrive copy I keep on record to show the error. Doesn't matter if I get it from the vault or copy it from her system, the same error persists.)

4.After hitting Okay she gets:

chris_1-1714487207016.png

" Internal error in persistence operation (Post restore of Object 0000014D9B49D8F8 meta-type UCxUserFolderFixedEntry in segment AmBrowserSegment ends up causing a cycle)"

5. After this occurs the assembly is corrupted but all of the parts are fine, allowing her to rebuild the assembly and not have any issues other than time loss.

 

This problem has happened on assemblies that have been un-vaulted as well as assemblies freshly checked into the vault.

 

Here is a bit of a background on our department set-up:

-10 users All using the same vaulted components, project files, templates, libraries etc.

-Common settings and file paths are used during the upgrade process to have everyone pointing in the right direction.

-Common drawing techniques and processes (most users come into the department with only the bare minimum of Inventor knowledge and get trained the same way).

-We all use Autodesk certified workstations from HP/Dell.

-The only person with access to editing these templates, libraries and other common files is myself. All of these files are kept in a "Released"/Locked state to prevent accidental changes.

-The only Add-ins we use are Woodworking for Inventor and InsertPlus. Again this is department wide

-We use Multi-Solid bodies top down designs

 

Solutions we have tried so far:

-We have replaced her computer Twice! (Both times with brand new computers. Once was the same time as a new hire using the same install process and setups, the new hire has never had issues).

-We have created a new Windows Domain account for her at a computer upgrade

-New vault account created as well

-Verified all network connections, have even moved her across the office to an entirely different set of ports

-We have been in constant contact with our Reseller and have had an Autodesk Tech review the corrupted file and our system setups (only thing found was something reference to Void Tools which one user had on his computer in the entire network. This has since been removed months ago but the problem persists on units he never touched)

-No errors show up in the Windows Error log or on the Vault Server logs.

 

I have searched the forum for the same error but none of those results have helped this situation. Most results recommend replacing the computers in question but we have already done that twice to no success.

 

 

0 Likes
1,788 Views
27 Replies
Replies (27)
Message 21 of 28

chris
Contributor
Contributor

Hi John

Are you referring to windows Admin privilege's or vault admin? Our IT department won't let users have window admin but a vault admin account is simple enough.

 

Hi Fredrick

No we aren't using model states regularly. None of these corrupted files have used them.

 

Hi Jim

That is possible. If I understand correctly you are referring to opening from windows explorer? I believe she opens all the files directly from the inventor application or double clicking to open from the vault if its not currently on her system. I know other people in our department frequently open from windows explorer and don't have any issues. But I'll verify this behaviour with her.

0 Likes
Message 22 of 28

sundars
Autodesk
Autodesk

I think it would help to see what the corruption is. Can you provide a simple dataset which shows the problem? Like @johnsonshiue said earlier, it looks like some browser folder cyclic dependency causing the issue. 

 

Steps to reproduce along with a dataset will go a long way, but I am happy to run through the data internally to see what the corruption is all about.

 

You can reach me at: sundarsATautodeskDOTcom.

 

Thanks

-shiva

 

 

Shiva Sundaram
Inventor Development
0 Likes
Message 23 of 28

chris
Contributor
Contributor

Hi Shiva

I have sent you an email with a bunch of OneDrive links to several assemblies that have been corrupted. 

Currently we have no way to consistently reproduce this error as it appears random other then a weekly-ish basis (but never at a consistent time or day), and only happens mainly to 1 user. ( we have had a 2nd user experience a couple of corrupted files but not with any frequency).

 

Let me know if you would like me to send you anything else.

 

Message 24 of 28

sundars
Autodesk
Autodesk

The root cause of the error is that there appears to be a browser folder with many components. In addition to its child components, the browser folder has a child which refers to itself. In essence we have a parent folder item which has itself as a child. 

Assembly
+ 1_browser folder (parent)

    + 1_browser folder (parent)

 

This leads to the cyclical error we see when opening the assembly. I have inspected our API and tried a sample (as well as @chris dataset but not able to reproduce the error. There must be something at play which we are not seeing immediately.

 

Any steps to reproduce by anyone is greatly appreciated so we can stop this corruption from happening.

 

Thanks

-shiva

 

Shiva Sundaram
Inventor Development
0 Likes
Message 25 of 28

johnsonshiue
Community Manager
Community Manager

Hi Chris,

 

Doe Woodwork for Inventor create browser folders? Or the user creates the browser folders?

Many thanks!



Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer
0 Likes
Message 26 of 28

chris
Contributor
Contributor

Hi John

I have never seen Woodwork create any folders that I am aware of. The folder in question is actually created by an iLogic code we have used for the last 5 years to help clean up our browser. This is in our assembly template file that everyone in our department uses. The code has been reviewed by several people during this investigation and nothing specific has jumped out. I will attach the code in an .txt document for review.

One thing that does make sense is at the beginning we were getting the below pop up during a save, and this was usually a precursor to the assembly being corrupted next time it opened. This pop-up stopped happening after the computer change or is inconsistent at best to show itself.

chris_0-1716985062385.png

 

0 Likes
Message 27 of 28

sundars
Autodesk
Autodesk

Hi @chris 

 

I did suspect that line of code when I looked at it in your "good" dataset, but I discarded the thought because the script is iterating over the occurrences and checking to see if its a library path. I would not expect that to come back with any browser node other that of an occurrence.

 

You could do test each node coming back and throw a message box or error to see if the problem happens.

 

Something like:

   If oNode.Type is kBrowserObjectType

   MessageBox.Show("Error: Unexpected node type found")

 

Btw, I did try running the script several times and it works with the good dataset you sent me. So, still puzzled.

 

Thanks

-shiva

 

 

 

Shiva Sundaram
Inventor Development
0 Likes
Message 28 of 28

sundars
Autodesk
Autodesk

@chris and everyone,

 

I have created a defect on our side to track this issue. Please refer to INVGEN-78220 when talking about this issue.

 

Thanks

-shiva

 

Shiva Sundaram
Inventor Development
0 Likes