I'm rebuilding our Vault dbs and attempting to add several files >30MB in size, but Vault is failing when uploading them after a couple attempts. They obviously got in at some point, as they were in the Vault db prior to rebuilding.
I noticed the same issue in the Gold Support forum, but didn't see a resolution. We have the Vault upload size set to the maximum, and chunked encoding is turned off (the default).
We're running on Win2003 Server with IIS 6.0.
Any ideas?
Thanks,
Joel
Error adding files over 30MB in size
Moderator: SourceGear
My recommendations for things to try.
1. Try the upload on the server machine, connecting to localhost. That should bypass the network entirely.
2. Is your SQLServer on a different machine? Sometimes, the network connection between Vault and SQLServer will be reset. Try running them on the same box to see if that fixes the problem. Usually, odd network issues are tracked down to MTU settings, or half/full duplex settings.
What error do you get? Does your Vault server log file give you any useful information?
1. Try the upload on the server machine, connecting to localhost. That should bypass the network entirely.
2. Is your SQLServer on a different machine? Sometimes, the network connection between Vault and SQLServer will be reset. Try running them on the same box to see if that fixes the problem. Usually, odd network issues are tracked down to MTU settings, or half/full duplex settings.
What error do you get? Does your Vault server log file give you any useful information?
It's all running on the same box. Oddly, I tried using the cmd-line client instead, and it doesn't have the problem.
Not really, the Vault server log just says "Upload failed".
Could it be a mismatch between the cmd-line and GUI client settings, or do they use the same config?
Not really, the Vault server log just says "Upload failed".
Could it be a mismatch between the cmd-line and GUI client settings, or do they use the same config?
jeremy_sg wrote:My recommendations for things to try.
1. Try the upload on the server machine, connecting to localhost. That should bypass the network entirely.
2. Is your SQLServer on a different machine? Sometimes, the network connection between Vault and SQLServer will be reset. Try running them on the same box to see if that fixes the problem. Usually, odd network issues are tracked down to MTU settings, or half/full duplex settings.
What error do you get? Does your Vault server log file give you any useful information?