Vault 2026.2 update error 303 critical issue

[JanInventor]

We did migrate our multi-site Vault Professional 2023 to 2026.2. After migration most users could not change state of any file anymore. Only users 2 not effected access groups could change state. Even adding administration role to the access groups did not work. Same 303 error on the test server that upgrade from the tested 2026.1 to 2026.2.

On a support page Autodesk did stated a workaround by resetting the transition security what did solve the problem. But after that all State-based security files were set to Object-based security. This way users can check out Released files.

I am now doing a Quick Change + Roll Back on all Released files to get State-base security back. I guess this will take 90 hours. Does anyone know a way to set files to State-based security without a Quick Change + Roll Back?

I will advise to NOT upgrade to 2026.2 and wait till 2026.3.

https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Error-303-You-do-n...

[gandhey · Accepted solution]

Hello @JanInventor ,

Please note we are working on this on issue on priority.

regards,

Yogeshwar

(Vault team)

[mark.burgessUNP2D]

Any progress on this issue?  My company unfortunately didn't find out about this until after the upgrade was completed and are experiencing the same issue. 

[gandhey]

Hello  ,

The work for this fix and the next 2026 update is underway. Please expect to see this fix available very soon.

Regards,

Yogeshwar

(Vault team)

[gandhey]

Vault 2026.2.1 update released - which has the fix for this issue.

Regards,

Yogeshwar

(Vault team)

[JanInventor]

The fix is not noted in the release notes.

[johannes.bauer]

Resolved an issue where non-Admin users encountered Error 303 when changing item status on a specific lifecycle. PDM-49897

https://help.autodesk.com/view/VAULT/2026/ENU/?guid=Vault_ReleaseNotes_CLC_updates_fixed_defects_202...

@JanInventor 

[JanInventor]

Ok.
We do not use Vault Items, The issue was that we could not change status of files.

[johannes.bauer]

@JanInventor I do agree, it is missing files, but also applies to files.

[loic_voisin]

Very good news !!

[mark.burgessUNP2D]

My company has installed the patch on our Vault server and Clients but I am still unable to change files from State Based Security to Object Based Security.  

Which means that the 9000 files that randomly changed Security methods recently are still invisible to the bulk of our users. 
Please advise how I am meant to make these files visible to our users if I can't fix the security method?  Not to mention how I do it efficiently when the 9000 effected files are scattered randomly through the overall catalogue?  

[loic_voisin]

I completely agree;

I have two clients who are experiencing this major issue.

It’s random—it doesn’t affect all lifecycle stages.

Security settings have changed, and the way files behave is completely different from before.

For example, if I set a file to “To Be Reviewed” and I had configured Vault so that the administrator group could edit that file, I get a padlock icon on the file.

However, according to the actual security settings, the administrator is supposed to be able to edit that file. It’s incomprehensible!!

The only solution I’ve found is to copy the lifecycle and set it as the default for the category.

This will resolve the issue for new files, but then I’ll have to process all the existing files… That’s another story…