Object reference not set to an instance of an object

[JMGunnar]

Any more tips too this error 

Object reference not set to an instance of an object

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

1.try too start workgroup 2020 after we change license 

2.reinstall vault client 

Best Reagards Johan

[JMGunnar · Accepted solution]

Here my solutions after many hours

reinstallation of Vault client

I rename ADPSDK mapp 

%APPDATA%\Autodesk\ADPSDK 

please update this info in 

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

[tomkennedySKK7K]

Thank you very much for posting this, saved me a lot of time.

Though I do wish I'd checked the forum before trying all steps on the Autodesk steps (including deleting the users profile!) 🙂

[Edoardo.Baima]

thank you so much @JMGunnar .

Tagging @CGBenner to have the article updated since right now it isn't helpful without Gunnar tip. Thank you

[steveh3]

THANKS!!!! @JMGunnar 

Anybody know what is causing this?

We are on ADMS 2023.2 server and were still using 2021 Thick Client. Last night we had 12 of our 48 of our users where we had to rename this folder. Some were Windows 10 others were Windows 11 machines.

Something happened and we had to rename the %APPDATA%\Autodesk\ADPSDK  folder?

Seems kind of ironic that others had same issue last night and this discussion was at top of list.

Autodesk any thoughts?

Best,

steveh

[ArkanceBeluxSupport]

Multiple customers in Belgium are facing same issue since this afternoon!

Renaming %APPDATA%\Autodesk\ADPSDK  folder solved issue.

[steveh3]

We are up to about 24 out of 48 users. Some users were even logged in and were knocked off and can't get back in until we renamed the folder.

Best,

Steve H.

[sellis]

Thanks! Nice quick fix. 🙂

We just had two users run into this issue today. Both had inventor crash when interacting with vault. 

[mslosar]

At this point I can tell you we're up to like 6-7 people reporting this here this morning as well. Something clearly changed and for this many people, has to be the autodesk end of the spectrum.

[ihayesjr]

All,

The files in the folder you are renaming is used by an Autodesk component called ADP.

A recent update to the component installed a version of the file that broke Vault 2021.

We are working on getting the component re-released with a fix. 

I hope we can get this re-released ASAP.

[steveh3]

THANKS for the update Irvin!!!

At least we know how to fix it and what caused it.

Appreciate it!

Best,

Steve H.

[karthur1]

I just had a user on 2020 have this same issue.  I followed the KB article but problem still persisted, then I found this post.  Renaming the ADPSDK folder did the trick.  Note: It would be nice if they would update the KB webpage.

Thanks

[ihayesjr · Accepted solution]

The article has been updated. You may have to clear your browser cache to see the update.

[elin.bosma]

Renaming the folder works. But with me, it only works for an hour or so darafter I have to repeat the process.

[Richard.Rankin · Accepted solution]

Hi All,

Autodesk has released an update to address this issue.

It will automatically self-update all machines connected to the internet within the next 24 hours including the impacted users and the workaround will no longer be required.

[steveh3]

Thanks Richard and your team for the update.

FYI...We already had a couple of machines this morning, where we had to use the work around a second time. If it still persists on Friday....I'm sure somebody will let you know :-).

Best,

Steve H.

[L00K]

Hi Richard,

question: how or where can we access mentioned update?
We are behind the firewall so non of the updates will show up automatically in out systems,
Does this updated apply to client or server?

Best Regards
Lukas

[Richard.Rankin]

Hi Lukas,

Are any of your users impacted??

[L00K]

yes, 5 so far.

[lscadden]

Has anyone that solved this by following the process listed and wound up with a different complication opening files from Vault?  The work around did work however, now I am getting this message opening from Vault:

Even after deleting my working folder copy of the project file and performing a "get" from Vault to replace it I am still dealing with this issue ...   I am just curious as to if this is a related issue most of us are seeing or if coincidentally this is an unrelated issue that happened to do this after the workaround.  I even tried a reinstall Vault to fix this one.

It did not work!

Luke Scadden

Nuaire Inc.

WIN 10

Inventor/Vault 2020