FAQ: Command Line Client null error on get

A collection of information about Vault, including solutions to common problems.

Moderator: SourceGear


Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
PostPosted: Tue Feb 17, 2004 2:50 pm
When performing a Get or Check Out, you might receive the following error:

Code: Select all
<error >
Value cannot be null.
Parameter name: path
< /error >
< exception >
System.ArgumentNullException: Value cannot be null.
Parameter name: path
at System.IO.Directory.CreateDirectory(String path)
at VaultClientOperationsLib.ClientInstance.CreateDiskFolders(VaultClientFolde
rColl folders)
at VaultClientOperationsLib.ClientInstance.Get(VaultClientFolder folder, Bool
ean recursive, Boolean forceLatest, MakeWritableType makeWritable, SetFileTimeTy
pe setFileTime, MergeType merge)
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand()
at VaultCmdLineClient.VaultCmdLineClient..ctor(String[] cmdlineargs)
< /exception >
< result success="no" />
< /vault>


Receiving this error means a working folder has not yet been set.

To set a working folder, use the following command:

Code: Select all
vault -user me -password secret -host myvaultserver -repository "Default Repository" setworkingfolder $ C:\temp


To unset a working folder, use the command
Code: Select all
vault vault -user me -password secret -host myvaultserver -repository "Default Repository" unsetworkingfolder $


If no working folder is set, a destination path is needed to be specified. This will also override any working folder set if there is one.

Note: If using destpath, files will always be overwritten. Use working folders if you don’t want your files to be overwritten.

Example:
Code: Select all
vault -user me -password secret -host myvaultserver -repository "Default Repository" get $/hello.world/underground -destpath c:/temp

Return to Knowledge Base (Vault)

Who is online

Users browsing this forum: No registered users and 2 guests

cron