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
    7
  • Subscribers subscribers
    7
  • Views views
    1047
  • 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

StarTeam 14.0 checked out file - Office Error 'File in use'

Brady Barker

Hello,

Our environment uses StarTeam Cross Platform Client version 14.0.4-136 with StarTeam Server 2009R2. Our StarTeam configuration hasn't changed in years. When using StarTeam with the Office suite, users have been experiencing the following Word error (after checking out a file in StarTeam, and double clicking it to open in Word/Excel): 

Although the error indicates that the file is 'locked for editing', the file is not locked in StarTeam. In other cases, the user who has the file locked in StarTeam, has also seen this error. Since this error is populated from the Office suite, I've followed Microsoft guides to fixing this error, to no resolve. After doing some testing, I've found that this error is only populated by opening the file from the StarTeam UI. If I check out the file, and open it from File Explorer, it opens in read-write mode... whereas opening it from the StarTeam UI can only open it in Read-Only Mode. After opening it once in StarTeam, the file is only able to open in Read-Only Mode from File Explorer. A reboot temporarily fixes this issue.

Has anyone experienced similar issues, or would be able to provide support for this? Thank you!

  • 0

    do you have this option set on your project "Mark unlocked working files read-only" ?

    wiht this option on, unlocked files are set to read-only ( not the locked ones) . Setting is per project

  • 0 in reply to 

    Hello. Thanks for the response. I've verified that the Project Option "Mark unlocked working files read-only" is unchecked. Even if it were checked, users that have certain documents locked, is also reporting that he receives the "filename.docx is locked for editing by another user" and is only able to open in read-only. 

    If you have any other suggestions, please let me know. Thanks for the support! 

  • 0 in reply to 

    try this also: in CPC, Tools/Personal Options/Workspace, make sure to uncheck "Enable File System Watching". 

    Obviously CPC 14.0 is quite old.

  • 0 in reply to 

    I tried unchecking the Workspace Option "Enable File System Watching" yesterday, which didn't resolve the issue. 

    CPC 14.0 is indeed old. Our StarTeam server is even older- 2009 R2. What are the odds that we are just seeing some deprecation issues? I find it odd that this issue is intermittent- it works temporarily after a reboot. Could this be some sort of caching issue?  

  • 0 in reply to 

    CPC 14 was issued in 2015, was not tested against newer patched OS  - lots of issues can pop up. Actually StarTeam Server and CPC are working very well given you are running such old versions. 

  • 0 in reply to 

    Well, not much has changed with our StarTeam environment. We haven't made any configuration changes in a long time, so it's odd that these issues are cropping up out of nowhere. I've tried rolling back Office and Windows versions, and the issue is still persistent. 

  • 0   in reply to 

    You could use a tool like SysInternal's (Now Microsoft) Process Explorer or Process Monitor to watch the IO. Process Explorer has an option to see open file handles and which process has them open. Perhaps you have a antivirus tool that is involved and hopefully this would help reveal the issue. We can also help you upgrade to a later version if you are interested.

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.