Undeletable Tmp files in Vault

[Zenda]

We are using VS2005 with Vault 3.1.6. We found that some temporary files got created (by VS2005?) and checked in to our project folder in Vault. They all have names like ~sak47cdd02401c62846.tmp and they have the same comment "Temporary file created by Microsoft Visual Studio to detect SourceGear Vault Client capabilities". The main problem is those files can't be deleted even by the Admin! The following error were reported when we tried to delete them:

2/6/2006 1:25:06 PM] An error occurred while trying to end a transaction.
[2/6/2006 1:25:06 PM] An exception was encountered during the transaction. Exception: Exception of type System.Exception was thrown. at VaultClientOperationsLib.ClientInstance.Commit(ChangeSetItemColl givenItems, Boolean keepCheckedOut, Boolean removeLocalCopy, Boolean bIsImport, DateTime dateImport, Int32 nUserIDImport, Int64& nRevID)
[2/6/2006 1:25:06 PM] Transaction failed
[2/6/2006 1:25:06 PM] Item $/Sandbox/Users/~sak47cdd02401c62846.tmp caused the transaction to fail: Deletion Failed.
[2/6/2006 1:25:06 PM] Transaction failed

The questions are:
1. Is there any way to delete those tmp files?
2. How do we stop them from being created? I know they might be created by VS2005 but any help from SourceGear will be greatly appreciated.

[dan]

Yes, Visual Studio does create and automatically delete these files in Vault, and there isn't much you can do about it.

However, they should just be regular files, and normally these don't show up in the tree at all, because VS automatically deletes them.

Can you check the server log at c:\windows\temp\sgvault\sgvault.log and see if there is more information on the error?

[Zenda]

We ran the Query and it works!

EXEC sp_dboption @dbname = 'sgvault', @optname = 'arithabort', @optvalue = 'on'

The wrong option might be set incorrectly when we moved our Vault DB to another volume. Thank you for your prompt response!

[dan]

If anyone else runs into this, it was traced to DB parameters not being set correctly. We added a KB article at http://support.sourcegear.com/viewtopic.php?t=5527 that describes the DB options that must be set.