Value cannot be null. Parameter name: path1

Value cannot be null. Parameter name: path1

alex_hiis6PJP6
Contributor Contributor
3,595 Views
11 Replies
Message 1 of 12

Value cannot be null. Parameter name: path1

alex_hiis6PJP6
Contributor
Contributor

Hi

 

Migrated to Inventor 2025 and have been getting this message when opening Inventor files from Vault.

Tried this solution but it didn't work: 
https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Error-Value-cannot...

Accepted solutions (2)
3,596 Views
11 Replies
Replies (11)
Message 2 of 12

CGBenner
Community Manager
Community Manager

@alex_hiis6PJP6 

Hello and welcome.  Can you tell us more about what Vault you are working on?  Is it also 2025, and is it Basic or Professional?

Did you find a post helpful? Then feel free to give likes to these posts!
Did your question get successfully answered? Then just click on the 'Accept solution' button.  Thanks and Enjoy!


Chris Benner
Community Manager

0 Likes
Message 3 of 12

alex_hiis6PJP6
Contributor
Contributor

Hi @CGBenner. We are using Vault Professional 2025.

 

 

0 Likes
Message 4 of 12

CGBenner
Community Manager
Community Manager

@gandhey Do you have any thoughts on this topic?

Did you find a post helpful? Then feel free to give likes to these posts!
Did your question get successfully answered? Then just click on the 'Accept solution' button.  Thanks and Enjoy!


Chris Benner
Community Manager

0 Likes
Message 5 of 12

alvin
Participant
Participant

I have also just started getting this error after applying the 2025.1 update, both server and client.

Message 6 of 12

alvin
Participant
Participant
Accepted solution

@alex_hiis6PJP6 

Alex, I have just had our support guy connect to my machine to look at this error and he has managed to sort it my changing the Opening behaviour within Vault, from Last State to Default.

I have attached a screen shot of where he made the change within the client.

Not sure if this will address your issue but it is at least worth a try.

 

Message 7 of 12

CGBenner
Community Manager
Community Manager

@alex_hiis6PJP6 Did the information provided answer your question? If so, please use Accept Solution so that others may find this in the future. Thank you very much!

Did you find a post helpful? Then feel free to give likes to these posts!
Did your question get successfully answered? Then just click on the 'Accept solution' button.  Thanks and Enjoy!


Chris Benner
Community Manager

0 Likes
Message 8 of 12

alex_hiis6PJP6
Contributor
Contributor

Thank you @alvin. That option did stop the error from popping up.

0 Likes
Message 9 of 12

mats.jakobssonMKR5Q
Explorer
Explorer
Accepted solution

Have the same problem after uppdates. Run Inventor as "administrator". Then shut down Inventor and then start Inventor as normal.

 

Most problem fixes when you run Inventor once as "administrator" its acces problem to write in to the windows registry....

Message 10 of 12

kevin_tucker7F44U
Explorer
Explorer

Nice one! That definitely worked without having to change any settings or rename the folders in AppData\Roaming as per Autodesk's suggestion. 

0 Likes
Message 11 of 12

Marco_cuterL89WC
Observer
Observer

Thanks alot for your help. It seems incredible but it was the one.

0 Likes
Message 12 of 12

Ryan_Monahan-Sundberg
Observer
Observer

Chiming in on Vault 2026, this fix is still important. Thumbs up. While users CAN get around it by opening from Inventor "through" the Vault, this fix is required to resolve the null pointer error when opening from Vault client directly.  Tools / Options ->  Open File Behavior Settings - click the Settings button next to it. Set ALL to default.