Install OK but Admin can't even create a folder in root $

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
fuzzylintman
Posts: 2
Joined: Thu Mar 23, 2006 12:04 pm

Install OK but Admin can't even create a folder in root $

Post by fuzzylintman » Thu Mar 23, 2006 12:10 pm

I successfully installed the server and tested with the two VaultService URLs and everything seemed fine. Then I went into the client (installed on the server) and logged in as Admin, and connected to the root repository. I then tried to create a directory in the root but receive the following error:

This is version 3.1.8.

[3/23/2006 12:54:27 PM] Transaction failed
[3/23/2006 12:54:28 PM] Transaction failed
[3/23/2006 12:56:34 PM] Preparing data to begin transaction
[3/23/2006 12:56:34 PM] Beginning transaction
[3/23/2006 12:56:34 PM] Create folder $/VDS
[3/23/2006 12:56:34 PM] Ending the transaction
[3/23/2006 12:56:38 PM] An error occurred while trying to end a transaction.
[3/23/2006 12:56:38 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)
[3/23/2006 12:56:38 PM] Transaction failed
[3/23/2006 12:56:38 PM] Transaction failed

-mdb

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Fri Mar 24, 2006 5:25 pm

Are there any corresponding errors in the Vault Server Log?
Linda Bauer
SourceGear
Technical Support Manager

fuzzylintman
Posts: 2
Joined: Thu Mar 23, 2006 12:04 pm

Post by fuzzylintman » Fri Mar 24, 2006 11:30 pm

There are several, but one seems to recur and would seem to be the cause:

System.Data.SqlClient.SqlException: Failed to load Msxmlsql.dll.

A search of other posts seems to indicate that this is not an expected error from Vault because it doesn't use this file. The previous solution, apparently, was to reload SQL and Vault.

Let me give you some details so maybe you can find some similarities... I installed this on a Virtual PC running a copy of Microsoft's CRM demo. Although I still wouldn't expect this error to occur, obviously this is not a production-class environment. However, I do not want to install this on our production SQL servers until I can test it properly, and hardware is short. I will re-attempt installation on a new Virtual PC that doesn't have all the other stuff loaded and see how that goes.

-mdb

Post Reply