Unbalanced 'StopWatchingRoot' error

This forum is for all Flare issues related to getting started and installing the application.
Post Reply
RonM63
Propeller Head
Posts: 22
Joined: Fri Oct 12, 2012 1:09 am

Unbalanced 'StopWatchingRoot' error

Post by RonM63 »

Greetings

I am using Flare v8.1. I have a Project consisting of a Parent and several children that are all merged against the Parent TOC. The source files are kept in MS SourceSafe v8.0.

I successfully built a version of HTML5 Help yesterday and passed it into QA. Today I have tried to open the same project and variously either get errors:
"Failed to run command 'Open'. Exception: Unbalanced 'StopWatchingRoot' + url.ToString()"; or another (which I'm not able to replicate because of the 'unbalanced' error) that is to do with read/write permissions on the SourceControl > LocalCache.mcsccachef > LocalCache.sdf file.

I have tried:
# manually unticking the read only tick box in the localcache.sdf properties. this at least allowed me to open each child project;
# For each Child, to unbind from SourceSafe, rename the SourceSafe version, and rebind. Then I 'checked out all' followed by 'check in all' to sync my working copy and the sourcesafe copy;
# made localcache.sdf writable for the parent project. opened, check out all, check in all. When I do this, the parent project checks out ALL of the child projects as well. I find that odd, being as they are only linked via the TOC? when i tried to check in, it fails to check in all projects.
#back to square one.

Another topic here suggested Reseting Window Layout. Which did nothing to resolve the problem.

The structure in sourcesafe matches the output - Parent with a folder 'subsystems' that contains the child projects.

Can anyone please help me figure out what is going wrong?

Brgds
Ron
RonM63
Propeller Head
Posts: 22
Joined: Fri Oct 12, 2012 1:09 am

Re: Unbalanced 'StopWatchingRoot' error

Post by RonM63 »

update:

this has been reported as a bug.
rob hollinger
Propellus Maximus
Posts: 661
Joined: Mon Mar 17, 2008 8:40 am

Re: Unbalanced 'StopWatchingRoot' error

Post by rob hollinger »

Generally Deleting the Source Control folder should fix this error.
When you open the project, you will get prompted to rebuild the Source Control Cache.

Generally this happens when a mix of Source Control operations happen using Flare and other tools to check files in and out.

There are a few folders that should never be checked into Source Control:
- Output folder
- Analyzer folder
- SourceControl folder
- Project\Users folder

If any of these folders are set to ReadOnly - there can be problems using Flare.
Rob Hollinger
MadCap Software
lrosenquist
Jr. Propeller Head
Posts: 3
Joined: Sat Apr 06, 2013 2:50 pm

Re: Unbalanced 'StopWatchingRoot' error

Post by lrosenquist »

I've deleted the source control folder and pulled the entire project down fresh and still nothing works. I can't load or open a thing in Flare 8.1 OR Flare 9, and am pretty much dead in the water. I have a release in 4 days! Help!


Update: I uninstalled and reinstalled Flare 9, with no luck. I'm out of ideas at this point.
lrosenquist
Jr. Propeller Head
Posts: 3
Joined: Sat Apr 06, 2013 2:50 pm

Re: Unbalanced 'StopWatchingRoot' error

Post by lrosenquist »

I had this problem a while back, then it mysteriously fixed itself a month or so later. Now I'm seeing this issue again, and I found something that resolves my problem. I figured I should post my solution in case someone else has this issue.

I checked my project out from source control, opened the project file in notepad, and changed the text SourceControlBound="true" to SourceControlBound="false". This allowed me to open my project at last. I reinstalled my plugin I was using to bind my project to Perforce, then rebound my project. That seemed to do the trick.
jane-tron
Jr. Propeller Head
Posts: 7
Joined: Tue Dec 23, 2014 3:49 pm

Re: Unbalanced 'StopWatchingRoot' error

Post by jane-tron »

We've had this error recently and the solution was to run Flare as an administrator. Since this old thread is the only result I get when I do a search for the error message, I wanted to share our solution for any future victims of the issue.
Image
Post Reply