I just encountered some errors accessing a repository, so I ran
"analyze" on it. It ran for about three minutes, found problems, and
said that I should run it again using the "-F" option to fix things.
So, I did so. It ran for about three minutes, listed a bunch of
errors and what it was doing about each of them, and reached 100%
completion on pass 4 of 4.
I then tried to close the output window. A message box popped up
asking me if I wanted to cancel this analyze/repair.
Well, no, I don't. But it says it's 100% complete on pass 4 of 4.
So, I waited a minute. Nothing changed.
Looked at Task Manager. Analyze was using basically 100% of the CPU.
And it still is, at 13 minutes and counting.
What should I do?
What should I *not* do?
Thanks in advance for any help.
Bob Vesterman.

Signature
This is the coolest of all sig files.
Robert William Vesterman - 31 Aug 2005 19:58 GMT
>What should I do?
>
>What should I *not* do?
Incidentally, this is VSS 6.0, latest service pack. I'm sorry if this
is the incorrect newsgroup - I didn't even know there was a .Net
version.
And I'm kind of hoping that the answers to my two questions are
"nothing" and "something", respectively.
Thanks,
Bob Vesterman.

Signature
This is the coolest of all sig files.
Robert William Vesterman - 31 Aug 2005 20:07 GMT
>I just encountered some errors accessing a repository, so I ran
>"analyze" on it. It ran for about three minutes, found problems, and
[quoted text clipped - 20 lines]
>
>Thanks in advance for any help.
Okay, never mind. It finally stopped, and the errors seem to have
been fixed.
Bob Vesterman.

Signature
This is the coolest of all sig files.