RoboHelp 2020 - can lock and unlock a file, but can't save changes

Thank you for coming back with this information as it will help others who hit this issue.

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

Hi all. Eventually got RH2020 working with AzureDevOps Server...

In the end, the local TFS guru and I started from scratch, and tried to upload my local project to an empty folder on the AzureDevOps Server.

It was a little tricky specifying the server folder (the "Project" folder in the Connection Settings) just right, as I wanted RH2020 to create it in an existing directory structure on the server where I already have other RH2015 projects, but here’s what my problems boiled down to:

- Even though the specific local folder I had my RH2020 project in wasn’t already mapped to any workspaces, the workspace name I specified in the Connection settings was already in use for other local folders on my PC, and it didn’t like that.

Even when I tried using a local folder that was in a structure completely outside of any existing structure (not overlapping the existing local workspace at all), using a workspace name that already existed on my PC was a no-go.
(This was unexpected, as with RH2015, I had multiple RH2015 projects integrated with TFS in local folders that all use the same workspace name.)

- Although I specified a new (empty) server directory ("Project" folder ) for RH to create, the parent directory I wanted it created under was already mapped to a local folder that existed in a different local workspace. So that failed.

When I unmapped all of the folders "upstream" from where I wanted to create my "Project" folder, RH2020 created the folder I specified in the “Project” field ok, and then uploaded the files ok.

Doing this meant I had to rearrange my pre-existing workspace after unmapping the upstream folders, by re-mapping the existing child folders directly to my other workspace (as I could no longer just do a "get latest" on their parent folders.)

If that all sounds horribly complicated, it was, and I would probably not have figured it out on my own as I'm not hugely experienced with workspaces. Much thanks to my local TFS guru whose experience pinned down the problems.

Sorry I can't help on this one. I studiously always avoided source control for precisely this sort of reason. 🙂

Being serious, I do see its use in some scenarios.

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

First thought is your user doesn't have write access to the local folder location.

Next thought is, given you said you uploaded the project manually, perhaps you've checked in something that shouldn't be source controlled, which is thus not writable (because it's not being checked out by RH). To confirm this, manually check out the entire project using TFS, make a change and save. If it works, then I think something needs to be removed from source control. I'm not familiar enough with New UI to suggest what those files or folders might be. Hopefully Peter comes along with an answer, otherwise try contacting support using the email address here: https://helpx.adobe.com/contact/enterprise-support.other.html#robohelp