Multiple Shadow Folders problem

[plexus]

We are using Shadow Folders with a share on a server other than the Vault server. So far it has worked fine. We have two repositories that each have a shadow folder pointing to the same share on the same server, but different subfolders of that share like this:

Repository1
$/path1 shadows to \\server\Inetpub\Directory1

Repository2
$/path2 shadows to \\server\Inetpub\Directory2

So far this has worked with no problems. However, now we want to add another shadow folder in Repository2 like this:
$/path3 shadows to \\server\Inetpub\Directory3

When we do this, the admin site shows the shadow folder as added, but the files do not show up in the destination folder, and we get the following in the vaultshadowfolderservice.txt log:

10/28/2008 12:23:39 PM <generic>: [<No Name>:5788] GetEntryAssembly() returned null; not logging assembly name
10/28/2008 12:23:39 PM <generic>: [<No Name>:5788] Starting Shadow Folder Thread for repository 7.
10/28/2008 12:23:39 PM <generic>: [<No Name>:5788] Shadow Folder Thread for repository 7 started.
10/28/2008 12:23:39 PM <generic>: [<No Name>:1596] Shadow Folder is using the folder, C:\WINDOWS\TEMP\, as a TEMP directory.
10/28/2008 12:23:39 PM <generic>: [<No Name>:5564] SimpleLogger finalized
10/28/2008 12:23:40 PM <generic>: [<No Name>:1596] Vault Shadow Folder encountered a problem: Object reference not set to an instance of an object.

DO you have any ideas on what the problem could be? Like I said, Shadow Folders are working for the original 2 entries added.

[jclausius]

What version of Vault are you using for Shadow Folders?

[plexus]

Sorry, I shoudl have known to include that. It is version 4.0.5.15922.

[jclausius]

If you look within the Vault Server's directory structure, you will find a web.config for the Shadow Folder service. If you inspect that file, there will be entries for Shadow Folder repository / destination associations.

Do the listings in that file look correct?

[plexus]

Everything looks the same as the others except for "initialget="True"" All of the others that are working have initialget set to false.

[jclausius]

Can you check the "case" of this third path?

If I remember correctly there may have been a bug in 4.0.x, in which the case of the paths was important. Can you see if their is any capitalization along those paths are present, and if so, make the web.config entry an exact match. This bug was fixed in Vault 4.1.

[plexus]

Yeah, I looked for the case of the paths, and was careful to make sure the case matched. We have run into that bug before and it causes the CPU to go to %100 when we don't get it right. What I do is browse to the destination in WIndows Explorer and copy the path from the address bar, so I don't think that is the problem.

[jclausius]

What about the repository path? Any case sensitive issues there?

[plexus]

No. The repository path is all lowercase, and so it the entry for it in the web.config.

[jclausius]

Can you send the vaultshadowfolderservice.txt, shadow folder's web.config, and the Vault Server's log file to support AT sourcegear DOT com via e-mail. (Reference this thread in the email HS:214045). I want to take a look at all elements to see if I can spot anything which may be causing this.

[plexus]

Email sent.

[jclausius]

Thanks.

In the meantime, take a look at deleting and re-adding the Shadow Folder association through the Admin Client, making sure the case is correct for both local and repository paths. I had originally thought you could make changes to web.config itself, but there are other values that may computed so entries to this file should be initiated by the admin client.