Shadow folders don't want to update

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
TobiasR
Posts: 3
Joined: Tue Nov 14, 2006 1:50 pm

Shadow folders don't want to update

Post by TobiasR » Tue Nov 14, 2006 2:03 pm

Hi! I've been trying to get the shadow folders to work correctly from Vault. I've been trying to follow the different suggestions made in earlier threads on this forum but I've had no luck sofar.

When I choose the shadow folder I want for my repository folder in the admin interface everything copies (if the folder is empty, if there's old files nothing is overwritten). After I've assigned the shadow folder I get the following error in vaultshadowfolderservice.txt:

2006-11-14 20:48:56 <generic>: [<No Name>:1412] Vault's Shadow Folders encountered an exception attempting to apply the delta to [ReposName]. The Shadow Folders for the repository may not be syncrhonized with the Vault Server. Access to path Vault_WF_2102542268 denied.

I'm attaching my vaultshadowfolderservice.txt if someone wants to have a look. I'm letting both the VaultService and the VaultShadowService impersonate a user on the server and I've used the changeidentity-program to set both services up with this user. The services are running on an Windows 2003 Server with IIS6.0 and SQL Express 2005.

I would be really grateful if someone could help me!

//Tobias Rundbom
Attachments
vaultshadowfolderservice.txt
(1.79 KiB) Downloaded 355 times

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Tue Nov 14, 2006 2:42 pm

The shadow folder must be empty when set up, so in that regard what you saw was correct.

What you are seeing can indicate a problem with permissions. Do you know what account Vault is running under? If not, can you send me the vault_install.log file located in the windows temp directory (%temp%)? You can either send it using the private function here, or send it to support at sourcegear.com and reference this post with ATTN: Beth.

Is the server the shadow folder on in the same network? On the same server?

If you are using a Windows 2003 server you may need additional configuration: http://support.sourcegear.com/viewtopic.php?t=536

Are either servers domain controllers?

TobiasR
Posts: 3
Joined: Tue Nov 14, 2006 1:50 pm

Post by TobiasR » Wed Nov 15, 2006 12:08 am

Ok! So I had to do some large changes to how the server was set up anyway so I reinstalled Vault. Under the default installation with Vault running under Network Service and a ShadowFolder set up on the local file system on the same server as both the Shadow Service and the Vault Service are on I don't get the error stated above anymore. However, when I checkin files they don't get shadowed in to the specified folder.

I can't find the "vault_install.log" but I've sent you the "sgvault.log" file. In that file there's only information about one start of the vault service on the server and a checkout-checkin of a file that I changed. That file wasn't shadowed. I also sent you the current "vaultshadowfolderservice.txt".

//Tobias

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Wed Nov 15, 2006 11:37 am

Was the file already checked out when you performed the reinstall? The shadow folders usually only shadow when there is a version change, so there is a chance it was confused if it was already checked out. Any major changes to that file??

On your SQL server piece, are you using Windows authenticatin or SQL authentication? Is the SQL server on the same server as Vault? What version of SQL server are you using.

I think you may need to check the permissions on the Shadow Folders themselves. Are that machine's users allowed to write to that folder?
Is the shadow folder on a mapped drive??

TobiasR
Posts: 3
Joined: Tue Nov 14, 2006 1:50 pm

Post by TobiasR » Wed Nov 15, 2006 12:29 pm

No, the file was not checked out when I made the reinstall. I've actually been watching so that the checkin would increase the version counter on the file when testing, and it did in the case I sent you.

I'm using windows authentication on the SQL Server and the SQL Server is on the same machine as Vault. The Sql Server is an Sql Server Express 2005 (9.0.2047)

I don't get any shadowed files even if I set the "Everyone" permission of the Shadow Folder to "Full permissions"... To me it looks like the ShadowFolderService doesn't recognize that there's a new version of the file, but I might be wrong... The shadow folder is located on the servers C:\.

Any ideas?

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Wed Nov 15, 2006 3:36 pm

Send me an email to support at sourcegear dot com referencing this post and attn Beth. I think we may need to take this a step further in order to find out what's going on.

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Mon Dec 04, 2006 8:42 am

A follow up on this issue.

In this person's server log were calls to the shadow folder service, but it was using https.

Code: Select all

https://<vault server name>/VaultShadowFolder/VaultShadowFolderService.asmx 
The shadow folder web.config file was configured to use http, which is as it should be.

The Shadow Folder function registers the plugin from Vault to Shadow Folder plugin by way of Admin Tool login. When you log into the Admin Tool using SSL, Vault will call the Shadow Folder plugin using SSL. If you log into the Admin Tool without SSL, Vault will call the Shadow Folder plugin through a normal socket.

The user then logged into the Admin tool without SSL, removed the prior shadow folders and the set-up of the shadow folders, and reset up shadow folders from the beginning.

Post Reply