SourceGear Support

This appears to be resolved. I did delete all the files in the shadow folder (actually I renamed the shadow folder and created a new, empty folder using the shadow folder name) then re-created the shadow folder associations in Vault. The files started to propagate to the new, empty shadow folder but...

Vault Server 3.5.1 on Windows Server 2000/.NET 2.0/IIS 5.0 Vault Client 3.5.1 on Windows XP Pro/.NET 2.0 All operations (i.e. check in, check out, add, etc.) work fine except Shadow Folders and the ability to Get Latest Version to the shadow folder. Both Vault web services are using a domain account...

Starting with version 3.5, setting multiple folders to the same working folder is no longer a feature. In the past there were issues that cropped up from that being allowed. One thing you can do is set the working folder of $ and check Force all subfolders to use inheirited working folders. I do ha...

We moved Vault Server to a different machine and upgraded to 3.1.9. Now I am seeing Shadow Folder is using the folder, C:\WINDOWS\TEMP\, as a TEMP directory. when I expect to see Shadow Folder is using the folder, C:\Documents and Settings\<valid username here>\Local Settings\Temp\, as a TEMP direct...

Resolved. The <valid username here> user was specified in the 'processModel' tag in the Machine.config file. I commented out the 'processModel' tag and re-created the Shadow Folders in the admin tool and the Shadow Folder log indicated that Shadow Folders is now using the ASPNET temp directory.

Vault 3.1.8 on Server 2003 Standard (db on SQL Server 2005) In the Shadow Folder log I see the following line: Shadow Folder is using the folder, C:\Documents and Settings\<valid username here>\Local Settings\Temp\, as a TEMP directory. Of course, '<valid username here>' contains a valid domain user...

I think I may have solved this.

The max memory usage on the SQL Server instance was set to 60% of max allowed. I bumped it back up to max allowed and the propagation time for the Shadow Folder went back to normal.

Vault 3.1.8 on Server 2003 Standard and clients on XP Pro SQL Server 2005 on Server 2003 Standard Vault DB and web services on same machine (I know) with Shadow Folder on different machine (Server 2003 Standard) We've been experiencing Shadow Folder latency of 5-10 minutes. Any idea why this might b...

We are using the [3.1.8] Vault Command Line Client for most source control operations. We also have a shadow folder setup for the repository. I had a thought that I could 'speed up' the shadow folder update time by doing a 'Get Latest Version' operation to the shadow folder immediately after a file ...

..latency of a minute or two is not unusual. Are you experiencing something longer?

No, just wondering if there's a way to speed it up.

Thanks!

Jon

I've noticed some (albeit minor) latency with shadow folder propagation.

I was wondering if there are any statistics available and/or if there is any way to optimize the propagation of changes to the shadow folder?

TIA,

Jon

Umm... I changed the IIS properties on the VaultService and VaultShadowFolder web services to use ASP.NET 1.1 instead of 2.0 and it started working.

It's amazing how the weekend can clear one's head!


Jon

Vault 3.1.8 - Server installed on Windows Server 2003 Standard. When I try to create a shadow folder on a local drive I get System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.NullReferenceException: Object reference not set to an instance of an object. at ...

RESOLVED!!! It was a .NET Framework 1.1 issue. I resolved it by manually repairing the .NET Framework 1.1 as described here: http://support.microsoft.com/kb/830646 NOTE: After repairing the 1.1 Framework, Vault worked fine but it seemed to cause some problems with the 2.0 Framework. I did another re...

RESOLVED!!! It was a .NET Framework 1.1 issue. I resolved it by manually repairing the .NET Framework 1.1 as described here: http://support.microsoft.com/kb/830646 NOTE: After repairing the 1.1 Framework, Vault worked fine but it seemed to cause some problems with the 2.0 Framework. I did another re...