Problems creating a folder

Guest · Post by **Guest** » Thu Dec 23, 2004 4:17 pm

Hi I'm new to Vault and I'm having trouble getting going. Whenever I try to create a folder in the Vault database, I get the following error message

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)

Anybody have any idea what this is and how to fix it?

lbauer · Post by **lbauer** » Thu Dec 23, 2004 5:05 pm

What version are you using?

Is this a new problem? Are other users unable to create folders?

Anything helpful in the Vault Server log file? It's the sgvault.log file in the %windir%/temp/sgvault directory.

Guest · Post by **Guest** » Fri Dec 24, 2004 7:08 am

Hi

I'm using Vault 3.0.1. I'm using it in a single user environment currently to evaluate the product. The log file says

# SourceGear Vault Server
----24/12/2004 12:58:58 admin--oemcomputer(127.0.0.1)--SSL Disabled Login
----24/12/2004 12:59:07 admin--oemcomputer(127.0.0.1)--SSL Disabled Failed to load Msxml2.dll.
----24/12/2004 12:59:07 admin--oemcomputer(127.0.0.1)--SSL Disabled Could not create bubble folders: Error in the application.
----24/12/2004 12:59:07 admin--oemcomputer(127.0.0.1)--SSL Disabled VaultLib.VaultResponseAddFolder returned: Success
----24/12/2004 12:59:07 admin--oemcomputer(127.0.0.1)--SSL Disabled EndTxFailDBInsert

I guess the initial problem is failing to load msxml2.dll. And doing a search on my machine shows it isn't there. So I guess that's the problem. I presume installing MSXML 4 will fix it... I'll give it a go

lbauer · Post by **lbauer** » Fri Dec 24, 2004 9:01 am

You might check out this link:

http://support.microsoft.com/default.as ... -us;823490

Guest · Post by **Guest** » Fri Dec 24, 2004 12:54 pm

Thanks for the speedy response (especially on Christmas eve!). That's fixed the problem