We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.
We have a project that keeps getting removed from RSC. I just made a new folder, pulled a clean copy, put a space in a topic to verify it would check out, all ok. Rebooted my computer and attempted to open the same project and it indicates it has been removed from version control.
Make sure you haven't got the cpd, pss, or ldb checked in to source control as they contain pc specific information and have caused problems for me in the past when multiple people have been working on the same project. If you added everything to RSC using Robohelp you should be fine, but it's possible someone could have added the files manually through RSC (I haven't used it myself, but I assume it has similar basic functionality to other source control applications).
If they are, delete manually from source control and commit the deletion. (Check that there are no other files checked out, or in a 'pending' state while you're at it.) Then I would delete the CPD and make a backup zip of the project for each PC (stored in a safe place away from you working folder), just to make sure you have a copy of all files in case they haven't been checked in properly or have been removed from source control. After that, I would delete the project from each PC completely and do a fresh "Get Latest" to make sure everyone has the same project files, and open and close the project on each PC. Do this on one PC at a time and make sure noone is working on the project until you're all synced. Try some of your standard workflow and see if you're still getting the problem.
While you've got the "delete cpd" setting turned on, you could also try manually deleting the cpd before opening the project every time, just to see if that makes a difference. This would just (hopefully) rule out a problem with the automatic setting.
None of these files are in source control.
Rebooting our computers results in having our project thrown out of version control every time. If we don't reboot our computers it works fine. Only a reboot of the computer kicks us out.
We have another project that works just fine regardless of rebooting.
You were sort of correct but it required us to remove from version control, rename, delete all the old named files, put it back and have everyone pull fresh local copies. Details at bottom of this thread in case someone has this problem in the future.
I'm a bit concerned you deleted .hcc, .glo, .brs, .ali, and .hhk. This would mean you have deleted your table of contents, glossary, browse sequences, context sensitive help mappings, and index. You've checked to make sure all that sort of thing is still working correctly?
Everything seems to be working perfectly. We don't use browse sequences, this is a service manual and the TOC is there but our manager hates it.
I just gave it another once over and it looks perfect. Rather than using the TOC, we use a flow diagram of our equipment which shows how each part is connected to the other parts, and by clicking on hot-spots in an image, you get your choice of disassembly, theory, or troubleshooting. Those hot-spot links in a popup are a visual intuitive way to approach a service book. I can't give you all my secrets but that has been awesome for us. Everything is where it should be, breadcrumbs work, we gave it a good test drive and so far, nothing is abnormal. I will give the other guys a heads up to watch the TOC to make sure everything is there even though it is hidden by default on compile.
I will say i hate the ribbon at the top of RH2017, RH10 icons were much easier for me but i have been using RH for 16 years or so and change is always hard. Thanks a lot for watching this thread. I wanted to put in our solution before I change roles in my company. I hope I can find a use for RH in my next role but I have to feel it out before I start innovating new things.
Copy link to clipboard
The solution: Once the person with the latest edits checked in, I did the following: