SourceGear Support

What path are you using for your shadow folder cache path? c:\Program Files\Sourcegear\VaultShadowFolderCache What user account does Vault run under? I'm not sure I understand the question. Vault itself is probably running under the admin account. Did the shadow folders become populated with either...

After following the steps listed in this KB article, I finally got shadowing working on our site. http://support.sourcegear.com/viewtopic.php?t=188 We are running Vault 4.1.4. The server is running Windows 2003 with IIS 6.0. I added one shadow folder association (a folder that contains 9 files) and ...

I just sent that file via email.

I changed that and got a different error message: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: The authentication credentials or Vault server parameters were not found in the Web.Config file. Vault Shadow Folder Service failed to login to ...

No, that doesn't work. Attempting that from the browser gives: The webpage cannot be found HTTP 400 Most likely causes: There might be a typing error in the address. If you clicked on a link, it may be out of date. What you can try: Retype the address. Go back to the previous page. Go to and look f...

Anonymous access is enabled. The errors straight out of the server's IIS logfile are: 2009-05-08 20:58:56 10.0.30.252 GET /VaultService/Admin/ShadowFolders.aspx repid=1 80 - 10.0.30.252 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 200 0 0 2009-05-08 20:59...

That folder already exists and the shadowing account has full access to it.

I did uncomment that line in the web.config but it didn't change the behavior.

I don't think it is even getting that far.

In the IIS log files I am seeing a 401.5 error when that connection attempt is made.

First, some background: We used to use shadowing back 3 years ago (approximately). That was, obviously, many Vault versions ago. We have also moved both the Vault front end and the database to different servers than they were on back 3 years ago. Now we want to get shadowing going again. We are usin...

We had this same problem back in the November/December timeframe. The fix was to change a registry value that allowed longer than 10 minutes for an upload.

Hope this helps.

Thank you! Installing version 4.1.4 of the client and changing that registry setting did the trick.

I am making plans to have all of our users upgrade their Vault clients to 4.1.4 and I'll upgrade the server at that same time.

Can I upgrade *my* client to 4.1.4 without anyone else here in the company upgrading? I want to try this out before I have our users do the same.

I'm a bit concerned about asking our users to regedit to make this change.

I changed that setting and tried the file upload again. While it definitely ran differently it still failed. It got to 92% and then hit the apparent 10-minute time limit on the client and it failed.

Is that 10-minute limit something that can be changed at the client?

After turning on debug logging at the server and trying that file upload again (again with failure), here are the records in the server log: ----12/15/2008 4:09:57 PM jmlange--adsl-70-230-171-48.dsl.stlsmo.sbcglobal.net(70.230.171.48)--SSL Disabled Beginning SQL transaction 37831248 ----12/15/2008 4...

The only thing in that server log for that same date/time are login/logout records. Can I turn on additional logging in that server log file? Would there be benefit to me sending you that file?