Solutions

How To Troubleshoot "in use by another user" errors in Version Manager (file in use by another user, project in use by another user)
Your subscription to document S134615 will expire in 308 days (Renew).  To cancel this subscription, click Cancel Subscription above.



ID:    S134615
Published:   
Updated:    07 September 2021

Operating System(s)

  • All Unix
  • All Windows

Product(s)

  • PVCS Version Manager
 

Description

Users can run into messages stating that a user, a file, a project, a project root or some other entity in a project database is "in use" by another user, or that a semaphore cannot be created for the project.
 
The attached document helps covers the following errors:

 

  • Could not access the file because it is in use by another user.
  • Could not access the file "FileName" because it is in use by another user
  • Could not access the project "ProjectName" because it is in use by another user
  • Could not access project root because it is in use by another user
  • Project root in use by another user; pvcs.suite.pvcsidCreationException
  • Version Manager could not access this workspace "WorkspaceName" because it is in use by another user.
  • pvcs.exception.FsLockedByOtherUserException: File "Path\pvcsproj.lck" is locked by another user.
  • PVCS Version Manager could not access the file FileName because it is in use by another user.
  • PVCS Version Manager could not access "EntityPath" because it is in use by another user. Try to access "EntityPath" at a later time.
  • PVCS Version Manager could not access this ProjectRoot "ProjectDatabaseName" because it is in use by another user. Try to access this ProjectRoot at a later time.
  • PVCS Version Manager could not access this Project "ProjectName" because it is in use by another user. Try to access this Project at a later time.
  • PVCS Version Manager could not access this Folder "FolderName" because it is in use by another user. Try to access this Folder at a later time.
  • PVCS Version Manager could not access this Workspace "WorkspaceName" because it is in use by another user. Try to access this Workspace at a later time.
  • PVCS Version Manager could not access this User "UserName" because it is in use by another user. Try to access this User at a later time.
  • PVCS Version Manager could not access this Group "GroupName" because it is in use by another user. Try to access this Group at a later time.
  • PVCS Version Manager could not access this file "FileName" because it is in use by another user. Try to access this file at a later time.
  • PVCS Version Manager could not access this tool configuration file, Path, because is in use by another user. Try to access this tool configuration file at a later time.
  • PVCS Version Manager could not access this project, ProjectName, because is in use by another user. Try to access this project at a later time.
  • PVCS Version Manager could not create the semaphore "ArchivePath" for this project. The semaphore may already exist or the location may be invalid. Try to access the project again.
  • pvcs.suite.PvcsLockedByOtherUserException: PVCS Version Manager could not access this Project "ProjectName" because it is in use by another user. Try to access this Project at a later time.
  • The workspace database is currently in use by another user. Please try again later.
  • Unable to process pvcsid file.
  • CLI_Command: cannot create semaphore "SemaphorePath".
    (Archive accessed via PVCS VM File Server)
  • CLI_Command: error, archive "ArchivePath" is in use.
    (Archive not accessed via PVCS VM File Server)
 
Objects that can return "in use by another user" errors:
  • allusers.ser files
  • Access Control Database files (.db)
  • Archive files (-arc, .??v*)
  • Configuration files (.cfg)
  • pvcsproj.ser files
  • pvcsroot.ser files
  • pvcsid.ser files ("Unable to process pvcsid file.")
 
The error may also be stated as "file in use by another user".

 

Resolution

The attached file provides guidelines for resolving these errors.

Attachment

File NameFile SizeDownLoad
Troubleshooting In Use errors.doc 224K HTTP
Troubleshooting In Use errors.pdf 568K HTTP

Rate this Solution

Find Answers

Type a question or describe what you are looking for below

My Recent Searches

Welcome kb sso

Additional Assistance

  • Submit a Case Online
  • FAQs