Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Not Answered
  • Replies reply
    1
  • Subscribers subscribers
    3
  • Views views
    694
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

PVCS 8.4.3.0: Semaphores Issue: Could not access file because it is in use by another user. Close archive.

MigrationDeletedUser
When I attempt to lock or add a version label to any of the files in my project I get the same "Could not access file because it is in use by another user" error. The project is configured to save the semaphores in a particular folder and no semaphores exist in that folder. I also checked the archive location and did not see any semaphores. Is there somewhere else the semaphores might be saved? Has anyone had a similar issue before?

I am running PVCS Serena Version: 8.4.3.0 on Windows


Any help would be greatly appreciated.

Thanks,

Edison
  • 0  
    Hello Edison,

    Are you using the VM File Server to access the repository? If yes, make sure the dedicated semaphore directory matches the Client name of one of the Path Map entries on the same File Server.

    If VM File Server is not used, make sure you as the end-user have the permissions to create the semaphore files in the specified directory. Not being able to create the file has the same effect as there being one already.

    With kind regards,

    - Richard.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.