Value cannot be null. Parameter name: String

Don Thimsen · Post by **Don Thimsen** » Sat Feb 02, 2008 8:51 am

We have an automation tool that use the HTTP interface in Vault to extract files from vault. I just found out that our automation is no longer working. I also found that the HTTP is no longer working in Vault 4.0.6 either (note: we just upgraded from 3.5.2). To demonstrate the problem:

http://vault_server_name/VaultService/VaultWeb/

login

Select the default repository

Drill down to any file and get to the History Menu

Click on the lastest version and you'll receive:

"Value cannot be null. Parameter name: String"

I assume this is a bug. Do you know what string that the GetFile.aspx is looking for?

Thanks,
Don

Beth · Post by **Beth** » Sat Feb 02, 2008 9:02 pm

Check out this thread here: http://support.sourcegear.com/viewtopic.php?p=37366&. Any chance that the path has a special character in it like that user's path did?

Don Thimsen · Post by **Don Thimsen** » Sat Feb 02, 2008 9:10 pm

Thanks Beth,

It's the same problem. Every member that we use with our automation tool starts with the hash (#). Looks like I'll be waiting for a patch as well. Any ideas about when you think this might be fixed?

Don

Don Thimsen · Post by **Don Thimsen** » Mon Feb 04, 2008 12:12 am

Beth,

No hurry on the patch... I modified our automation tool to translate the hash (#) in the file name to a %23. It worked.

Thanks,
Don

Beth · Post by **Beth** » Mon Feb 04, 2008 2:32 pm

I don't have a date on the fix. It's listed and the developers are aware of it.

Post by **jeremy_sg** » Fri May 30, 2008 3:41 pm

Vault 4.1.2 contains a fix for this bug.