Harvest Workarea Disconnected

Products

• CA Harvest Software Change Manager - OpenMake Meister

Issue/Introduction

My Workbench WorkArea has become disconnected. That is to say, it is no longer referenced in Harvest as under source control.  How can I restore the connection between my Workbench WorkArea and the SCM Repository?

Environment

CA Harvest SCM Workbench Client 12.x and above

Resolution

For any of a variety of reasons, you may encounter a situation with your SCM Workbench WorkArea where the files are no longer “bound” to their corresponding items in the SCM Repository.  It is as if you right clicked on the top level folder in your WorkArea and selected “SCM WorkArea” and “Unshare WorkArea”.  All the binding information is gone, leaving just the files.

Here’s how to restore the binding information:

1. For safety, first open Windows Explorer, navigate to the WorkArea on your computer’s local file system and make a backup of the WorkArea folder:

<Please see attached file for image>

<Please see attached file for image>

2. Next, in SCM Workbench, delete the WorkArea:

<Please see attached file for image>

Make sure to leave the “Delete project contents” checkbox unchecked:

 

<Please see attached file for image>

3. Identify the correct Client Path folder for your WorkArea.  When re-establishing your WorkArea you will need to specify the folder on your local computer’s file system in which it should be placed.  The name of the folder you select should be one level above the top level folder in your WorkArea.  In the example created for this article, the top level folder in my WorkArea is named “SampleRepository”.  On my local computer’s file system, this folder “SampleRepository” is found in the “E:\Temp” folder.  So, in Step 4, when selecting the Client Path, I will choose the “E:\Temp” folder.  It is very important that you choose the correct folder when selecting your Client Path folder.  Otherwise, when Harvest compares the folder structure and files in the SCM Repository with the corresponding folder structure and files on your local computer’s file system, they will not match and Harvest will assume all of the files on your local file system are new files to be checked in.

<Please see attached file for image>

4. Re-add the WorkArea:             

<Please see attached file for image>

Make sure to enter the correct Client Path folder as you found it in Step 3, then click “Next” 

<Please see attached file for image>

 

Make sure to uncheck the Populate WorkArea from Repository checkbox and click “Finish” 

<Please see attached file for image>

Click OK

<Please see attached file for image>

 

The Output Log will make it look like it’s checking out all the files again.  No worries – it’s just comparing all the existing files with the repository and checking out any new ones. 

<Please see attached file for image>

5. The last step is to do a synchronize so that any differences between the repository and the local WorkArea folder can be resolved

<Please see attached file for image>

 

In my example case I had made an offline change to README.TXT.  Synchronize was able to find the change and I had the chance to merge it in: 

<Please see attached file for image>

After this, the bindings between your Workbench WorkArea and the SCM Repository should be restored.