error creating lock file. error code 87

[Anonymous]

My wonderful and illustrious IT department installed the 4 millionth update this weekend and of course something always has to break as a result of making our devices more "effective". Upon reopening all of my programs to begin working on my previous programs I received a stream of "error creating lock file" messages. Error code 87. The last forum post I read about this issue the solution was not helpful and was speaking to error code 31. The assembly is the only file that won't effectively resolve after the typical "cycling of the switches". The individual parts all are fine. What's going on here?

[Mark.Lancaster]

@Anonymous 

Welcome to the Autodesk User's Community..

Can you confirm there's enough free disk space on the "E" drive...   Is the "E" drive local or network shared location?

[johnsonshiue]

Hi! The issue seems to be discussed recently. Please take a look at the following articles and see if they apply to you.

https://knowledge.autodesk.com/support/inventor/troubleshooting/caas/sfdcarticles/sfdcarticles/Inven...

https://forums.autodesk.com/t5/inventor-forum/error-creating-the-lock-file/td-p/7524053

Many thanks!

[Anonymous]

The problem was with the RSA key client that was installed by the IT department for the network drive. It was apparently not using the same protocols and was not allowing inventor to write to the drive.

[Anonymous]

That was a separate issue they had and I tried their suggested fix. It didn't work. Also the error codes are different. The issue was the incompatibility of security protocol with the newly installed client not allowing inventor access to certain write functions. The client was rolled back and the issue was mostly fixed. However, in the process we had used the pack n go function to port the files to the local hard drive but it kept some remnant associations that should've been deleted with the assembly update (almost like it had pulled the old versions into the cache of assembly files), they didn't show up in the BOM as they were modified or deleted but the pack n go ported them to the new location. This also happened in reverse when the network drive was restored. Now I can't open an assembly from the group of files I was working on without it forcing me into the file search window for associated assembly files that don't exist anymore or aren't supposed to exist in association. Moral of the story: don't install security clients until you know it's compatible with your most used software suites. Gotta love corporate mandates to local IT.