vault.exe returns bad xml

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

Moderator: SourceGear

Post Reply
flyswacker
Posts: 10
Joined: Wed Apr 08, 2009 12:50 pm

vault.exe returns bad xml

Post by flyswacker » Wed Apr 29, 2009 11:06 am

SourceGear Vault Command Line Client 4.1.4.18402

cases (so far) where returned XML is invalid:

1) Error return on UNSETWORKINGFOLDER

C:\icidev\vault>"C:\Program Files\SourceGear\Vault Client\vault.exe" UNSETWORKINGFOLDER -host stunner -username mikemu -repository ICI
<vault>
<error xmlns="The UNSETWORKINGFOLDER command requires 1 argument.">
<result>
<success>False</success>
</result>
</error>

2) Actual error in the node namespace, we want to display it, how can we get to the text?
<error xmlns="The UNSETWORKINGFOLDER command requires 1 argument.">

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

Re: vault.exe returns bad xml

Post by lbauer » Wed Apr 29, 2009 2:44 pm

You need another argument in the command -- the repository folder where you want to unset the workingfolder. Documentation is online here, or type vault.exe helphtml on your client machine from the command line.

http://download.sourcegear.com/misc/vau ... KINGFOLDER

So the command would be: C:\Program Files\SourceGear\Vault Client\vault.exe" UNSETWORKINGFOLDER -host stunner -username mikemu -repository ICI $/<some repository folder>

Sorry the error message isn't clear.

Note: this command only works on explicitly set working folders, not inherited working folders.
Linda Bauer
SourceGear
Technical Support Manager

flyswacker
Posts: 10
Joined: Wed Apr 08, 2009 12:50 pm

Re: vault.exe returns bad xml

Post by flyswacker » Wed Apr 29, 2009 3:08 pm

The problem is this is a wrapper in powershell, and the invalid XML is killing me. The missing parm was deliberate.
I have to be able to rely on the return XML being properly formed.

Is there a more current release?

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Re: vault.exe returns bad xml

Post by jeremy_sg » Thu Apr 30, 2009 9:22 am

If you're writing a powershell extension that talks to Vault, you should probably be using the IntegrationLib, instead of parsing XML, since powershell is very friendly to handling .Net objects.

For examples of doing things, see our API forum http://support.sourcegear.com/viewforum.php?f=31

Another powershell and Vault related topic is at: http://blog.roub.net/2008/05/vault-awar ... rompt.html
Subscribe to the Fortress/Vault blog

flyswacker
Posts: 10
Joined: Wed Apr 08, 2009 12:50 pm

Re: vault.exe returns bad xml

Post by flyswacker » Thu Apr 30, 2009 11:04 am

This is a conversion from VSS, and the examples you list have not fleshed these topics out to a degree that i can use them in a short time frame.

Getting back to my point, what about the invalid XML that vault.exe is returning?

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Re: vault.exe returns bad xml

Post by jeremy_sg » Thu Apr 30, 2009 1:04 pm

I fixed the namespace error printing. If you want a prerelease 4.1.5 with this fix, please email support at sourcegear.com ATTN: jeremy with a link to this thread.
Subscribe to the Fortress/Vault blog

flyswacker
Posts: 10
Joined: Wed Apr 08, 2009 12:50 pm

Re: vault.exe returns bad xml

Post by flyswacker » Thu Apr 30, 2009 2:37 pm

Yes, i'd like the pre-release. When will it be official? What else was fixed/changed?

flyswacker
Posts: 10
Joined: Wed Apr 08, 2009 12:50 pm

Re: vault.exe returns bad xml

Post by flyswacker » Thu Apr 30, 2009 3:03 pm

I had downloaded the client api previously, and the biggest issue was the help file, none of the topics resolve. They all display this message:

This program cannot display the webpage

Most likely causes:
You are not connected to the Internet.
The website is encountering problems.
There might be a typing error in the address.

What you can try:
Check your Internet connection. Try visiting another website to make sure you are connected.

Retype the address.

Go back to the previous page.

More information

This problem can be caused by a variety of issues, including:

Internet connectivity has been lost.
The website is temporarily unavailable.
The Domain Name Server (DNS) is not reachable.
The Domain Name Server (DNS) does not have a listing for the website's domain.

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Re: vault.exe returns bad xml

Post by jeremy_sg » Thu Apr 30, 2009 4:03 pm

This Microsoft posting may help you...

http://social.msdn.microsoft.com/Forums ... 530b8c4530
Subscribe to the Fortress/Vault blog

flyswacker
Posts: 10
Joined: Wed Apr 08, 2009 12:50 pm

Re: vault.exe returns bad xml

Post by flyswacker » Thu Apr 30, 2009 5:09 pm

All my other .CHM files work.

I found a copy in the NAntTasks folder that works
ms-its:C:\icidev\vault\NAntTasks\VaultClientIntegrationLib.chm::/T_VaultClientIntegrationLib_BackupOption.html

This encoding doesn't work
mk:@MSITStore:C:\Install\sourcegear\VaultClientAPI_4_1_2_18185\VaultClientIntegrationLib.chm::/T_VaultClientIntegrationLib_BackupOption.html

Post Reply