Obliterate not working

blaze6947 · Post by **blaze6947** » Thu Jul 19, 2007 1:33 pm

I have been able to obliterate everything with no problems untill now I have one project that I try to obliterate and it just sits there and sits there and sits there.

Is there a manual way to obliterate a project?

Beth · Post by **Beth** » Thu Jul 19, 2007 5:17 pm

There isn't a good manual way to do that.

How may files are you trying to obliterate at once? Could they have a lot of history?

Can you zip up and post a Vault Server Log or send it to support at sourcegear.com (attn: Beth) with a link to this post? Or, take a look around the time you obliterated and see if there are any errors.

blaze6947 · Post by **blaze6947** » Fri Jul 20, 2007 7:29 am

I don't see any errors in the log file at all, I don't even see an entry for the attempt to obliterate the project, all I see is that I logged in with the admin account. The Project is large that I am trying to obliterate but it shouldn't have a large history.

Beth · Post by **Beth** » Fri Jul 20, 2007 7:48 am

You probably need to place the log into debug mode.

If you are on a version of Vault prior to 4.x, then you will go into the Admin tool - Server Options and there will be a setting for the logging. It's probably set to 'quiet' right now. Switch that to 'debug'.

If you are using Vault 4.x or later, go to the Logging link in the Admin web page to find the setting for the logging level.

Once the change is made you will need to perform an iisreset at a command prompt on the server regardless of the Vault version. Then try the action again so that details are captured in the log.

If your log is very large, you also might find it helpful to rename your current log before making changes to the logging level just to keep your log a little shorter.

blaze6947 · Post by **blaze6947** » Fri Jul 20, 2007 2:07 pm

Messing with the logfile has messed up source control on a project, the project was checkedout at the time I was changing the log back to quite mode. The developer was getting an index out of range error when trying to do a Get Latest, so they checked everything in right around the same time that I was changing the debug back to quite mode on the log.

Beth · Post by **Beth** » Fri Jul 20, 2007 5:21 pm

Were you performing an iisreset at the time maybe? The log file setting itself shouldn't have anything to do with the source control portion. An iisreset will temporarily disconnect people from the server.

Also, I think it would be best to have it set to debug mode until this is fully resolved.

For others, we are working offline right now on this issue.