topic Re: System.AccessViolationException error in Installation & Licensing Forum

System.AccessViolationException error

bkimball — Thu, 06 Apr 2017 17:52:11 GMT

I have multiple users getting a "System.AccessViolationException: Attempted to read or write protected memory." error when starting Inventor 2017.

The full error is pictured below. They can close the error and work in Inventor without issue but it's extremely annoying.

I have ran Windows memory tests, fully removed (using Autodesk tool and then manually scrubbing any remaining files I could find) and reinstalled and have had no luck in getting this error to go away. One thing I did find interesting, when I fully removed and reinstalled, the error did not appear when opening Inventor before installing all available patches. Once the Inventor suite was fully patched, the message came back.

I've checked the boards and only saw a few things. One was to disable UAC and that didn't help and the other was more technical than I could understand and wasn't even sure if it was relevant (something to do with attribute values?). Any help you could provide would be greatly appreciated! TIA, Brian

Re: System.AccessViolationException error

Mark.Lancaster — Thu, 06 Apr 2017 18:32:04 GMT

@bkimball

This sounds like your infrastructure is blocking the Inventor Connect Design interface. One a machine (and for a test).. Go to Tools/Add-ins and uncheck both load behavior for Connect Design for A360. Close Inventor and launch it again. Does the message appear?

Re: System.AccessViolationException error

natasha.l — Thu, 06 Apr 2017 18:40:47 GMT

Hello @bkimball,

We have received a case where this has happened, I have put together some suggestions.

Make sure you have the latest service packs installed or Hotfixes by visiting the Autodesk website or account
Apply the Latest Windows updates
Clean Temp folder
Reboot the computer

Let us know how it goes.

Please "Accept As Solution" if a reply has helped resolved the issue or answered your question, to help others in the community.

Re: System.AccessViolationException error

bkimball — Fri, 07 Apr 2017 13:41:18 GMT

Tried Mark's suggestion first and that did the trick! Thank you both for your time! Brian