Hmm... I was playing around with the new 5.0 release and it looks like there's something weird about the repository deletion function (through webadmin > "Source Control Repositories").
If I click the red "X" an informational/warning message is displayed about permanent deletion. But the "OK" button does not work. It executes asynchronously and receives an incorrect or malformed response. This happens on the server side, it does not matter if I do the same in Firefox, IE or Safari.
This was with a completely clean 5.0.0.18071 installation on Win 2003 Enterprise, SQL Server 2008 SP1.
Vault 5.0, repository deletions
Moderator: SourceGear
Re: Vault 5.0, repository deletions
I was able to reproduce this. I've logged bug 14689 and we'll address this in a maintenance release.
Thanks for the report.
Note: I removed the SQL commands you posted because trying to modify database directly, rather than using the Vault clients, can cause unexpected results and could destroy important data.
Thanks for the report.
Note: I removed the SQL commands you posted because trying to modify database directly, rather than using the Vault clients, can cause unexpected results and could destroy important data.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Re: Vault 5.0, repository deletions
I can explain the details of this failure a little bit more.
First, the repository deletion does work. The "Please wait while the server deletes the repository..." does not pop up, but if left alone after clicking OK, the confirmation dialog will go away when the deletion finishes.
Secondly, this behavior does not happen when deleting the first repository in the list.
Thanks for the report, We'll make sure that we get this fixed in 5.0.1.
First, the repository deletion does work. The "Please wait while the server deletes the repository..." does not pop up, but if left alone after clicking OK, the confirmation dialog will go away when the deletion finishes.
Secondly, this behavior does not happen when deleting the first repository in the list.
Thanks for the report, We'll make sure that we get this fixed in 5.0.1.
Subscribe to the Fortress/Vault blog