Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML How To Troubleshoot "in use by another user" errors in Version Manager (file in use by another user, project in use by another user)
pvcs .exception.FsLockedByOtherUserException: File "Path
MS-WORD The Comprehensive Guide to Troubleshooting “in use” Errors
To resolve “in use” errors caused by a stale semaphore, that file must be removed. For project databases accessed through the PVCS VM File Server, go to the Version Manager File Server Admin web page at http://localhost:8080/serenafs/Admin and remove the semaphore from the Status tab:
PDF The Comprehensive Guide to Troubleshooting “in use” Errors
1. To resolve “in use” errors caused by a stale semaphore, that file must be removed. For project databases accessed through the PVCS VM File Server, go to the Version Manager File Server Admin web page at http://localhost:8080/serenafs/Admin and remove the semaphore from the Status tab:
CMS-XML TRK: Error: PVCS Notify is in use by another process.
TRK: Error: PVCS Notify is in use by another process.
CMS-XML VM: Diagnosing a 'File in Use' error in Version Manager
Steps to follow to diagnose a 'File in Use' error in Version Manager File in Use Error Diagnosis:
HTML Merant PVCS Version Manager Release Notes
Project Meta-data Directory (P*.prj) Not Always Moved When the Project is Moved [1038161] Version Manager on Windows platforms could fail a project move operation because the directory being moved was " in use ", resulting in error messages such as: "Could not rename "\\server\share\...\old_dir\P2tkjy.prj" to "\\server\share\...\new_dir\P2tkjy.prj". This has been fixed.
CMS-XML File checked in using VMI-Net loses associated SBM issue done via SourceBridge
PVCS Version Manager 8.3
CMS-XML About: PVCS Version Manager builds the Initialization on UNIX (.islvrc) with the wrong priv area.
One of the primary places that users run into problems on UNIX is in use problems on the private area. Each user should have their own private area. The following document explains why is is not uncommon to inadvertently set up a shared PVCS area and how to resolve this for current and for future users.
CMS-XML TRK: Error: Cannot Copy trkadmn: There has been a sharing violation. The source or destination file may be in use.
This error will be caused by other Tracker applications running on Windows whilst you are attempting to apply a service pack to PVCS Tracker.
CMS-XML KM-Dim9:12005-ART_VOLID_IN_USE Volume_id already in use
Please gather any applicable information from the list below and contact Dimensions Support for help with this error message. What you need to troubleshoot :
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs