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 replies
    3
  • Subscribers subscribers
    3
  • Views views
    163
  • 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

Unable to View or Edit any files in some Version Manager projects

MigrationDeletedUser
We are experiencing an issue in Version Manager where we are unable to open any files (View or Edit) in several of our projects. We have one project that works without any issues. The rest give the following error when we attempt to open any files in the project:

The archive, "T:\PVCS\archives\FilePath\file.name-arc" could not be found at the specified location. Either this archive no longer exists or you cannot currently access this location. Please try the action again. Contact your Serena administrator for further assistance.

The FilePath and file.name are obviously specific to each file. It doesn't matter what file we try to open the error is the same. All of the -arc file are there and all of the rights to these paths and files are the same as they are for the project that is working.
  • 0  
    Hello Kyle,

    Can you indicate what VM release the client is running? Same for server, if there is one. Please indicate the OS versions too.

    Do these errors show up in the desktop client GUI or in the VM I-Net web client? If web client, try a desktop client GUI: same behavior?

    If the GUI is also affected: are you running the VM File Server at all? If yes, or if the behavior is only in the VM I-Net web client, restart the server process/service and retest.

    Running the VM Debug collector from KB doc knowledgebase.serena.com/.../index
  • 0 in reply to   
    Client: 8.1.2 en_US (Build 110)
    Client OS: Windows 10
    Server: 8.1.2.0 Build vm81_20_110
    Server OS: Windows Server 2003 R2

    We only use the desktop client. It happens for all of our projects but one. We have restarted all services and even the entire server and still experience the same issue.
  • 0  
    Kyle,

    We'll need to know if the VM File Server is being used, as it determines whether the client will try to use the actual T: drive or pass the request on to the VM File Server, which changes way the file is read and therefore the troubleshooting process. The Debug log can get us that info. Just launch the GUI using this tool, then reproduce the problem and submit the output.

    Please note that the age gap between VM 8.1.2 and Windows 10 is very large (over 9 years; VM 8.1.2 did not support Windows clients beyond Windows XP), so expect to find problems due to Windows architecture changes (specifically ones related to UAC). Your company should really upgrade to VM 8.5.3 or VM 8.6.

    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.