When a user opens a DSN file in Orcad 16.6 (with 101 hotfix), a DSNLCK file is created so that anyone else trying to open the same file gets a warning and can only do read-only mode. There is an issue where if a user has a design open for several hours or overnight, the DSNLCK file might as well not exist, because anyone can open and edit the design that they already have open. According to server logs, the additional user's PC deletes the previous DSNLCK file and creates their own.
Has anyone else seen this behavior? Any idea what could be going on or how to fix? I'm at a loss for how to troubleshoot this, as the server logs seem to point to Orcad having a mind of it's own on if it wants to obey DSNLCK files or delete them.