Skip to main content
Jonontrack1
Participant
April 30, 2009
Question

.apj file is incorrectly marked as checked out

  • April 30, 2009
  • 8 replies
  • 1860 views

All authors have checked in all of their topics, yet Robosource shows one file (in this case rhcolor.apj) as 'Checked Out'. When the author attemps to Uncheck the file, Robosource returns the error message "rhcolor.apj is not checked out"

Anyone got any ideas?

This topic is closed to new replies. Start a new post to keep the conversation going.

8 replies

Gravenstein
Gravenstein
Inspiring
April 30, 2009

Hi Jonontrack1 -

Welcome! Try this: Log into RoboSource Control Explorer and verify that the file is indeed checked out. If it is, do an uncheckout from there. Depending on how the permissions are set up, you might need RSC admin privileges to do this. (Probably not, though.)

If it's NOT checked out, then the problem is likely local to that author's pc.

G

Jonontrack1Author
Participant
May 4, 2009

Thanks for the response G

Looks like the problem was local to the pc ? - would be very interesting to know what conditions would cause it, as we are setting up best practices to avoid these types of situations viz local copy and Robosource are out of sinc, but get latest doesn't fix it.

In the end, the only way we could rectify the problem was to delete the local copy of the project, and then use 'get latest' from robosource.

Regards

Jonontrack1

Gravenstein
Gravenstein
Inspiring
May 4, 2009

Sounds like you applied the right solution by starting over on that pc.

Now I haven't run into this lately, but I'm guessing it's still true...One condition that has caused odd behavior like this at the pc level is when the author moves or copies the source files on the pc. This can confuse RoboSource Control and make synchronizing files a real problem. For example, say an author checks out a file from Location A. Some time later, the author goes to a different copy of the same project in Location B and opens that project. From that vantage point, the author sees that old file checked out to himself/herself, but RSC won't allow any further action on that file. (I think what *RSC* sees is two different authors, because of the two different locations. Or something like that.) The waters get further muddied if the author has deleted the Location A version of the project, because the trail gets lost.

Whenever possible, I like the writers to place their copies of the RSC project in exactly the same location on their pc. For example, everybody accessing the ABC project has the project located on their pc in C:\MyHelpSource\ABC.

G.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices