Stats

Locked Locked
Replies 1
Subscribers 165
Views 4560
Members are here 0

DSNLck lock files not working after several hours

FormerMember over 7 years ago

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.

Parents

jbethune over 7 years ago

We have had this problem. We were never able to find a suitable resolution. We have used Tortoise SVN as version control, which has a lock feature of its own that is very handy for this sort of thing.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

jbethune over 7 years ago

We have had this problem. We were never able to find a suitable resolution. We have used Tortoise SVN as version control, which has a lock feature of its own that is very handy for this sort of thing.
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data

Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.