We have recently set-up Vault version 4.04, and are having an issue with getting Shadow Folders working.
Our setup is as follows;
- IIS server running the Server
- Database is stored on another server - SQL 2005
- Setup to use Windows Authentication (working for clients)
- Created an AD account for web services to run under
- set the admin password when installing, and have not changed
- Web site installed into different path than c:\inetpub\wwwroot (d:\Web Sites\Vault)
However, when running the web client, going to admin and then Shadow Folders we are getting the following error message;
The Shadow Folder Service was unable to connect to the Vault server. Please enter the login to be used by the Shadow Folder Service
I have attached the installation logs and service logs etc if these are of any help
Regards
Tom
Shadow Folders
Moderator: SourceGear
Shadow Folders
- Attachments
-
- vault_install.log.txt
- Vault Install Log
- (11.63 KiB) Downloaded 418 times
-
- sgvault.log.txt
- Vault Log
- (21.46 KiB) Downloaded 215 times
-
- vaultshadowfolderservice.txt
- Shadow Folder Log
- (33.94 KiB) Downloaded 246 times
Can you browse to d:\Web Sites\ and look for the Vault shadow folder directory under there? Once it's found, look at its properties and see if the AD account Vault is running under has permissions to that directory. If not, add it.
Last edited by Beth on Tue Aug 21, 2007 7:30 am, edited 1 time in total.
OK,
After some further investigation, I found that in the web.config for the ShadowFolders I found that there was a line for <identity impersonate ....>
By temporarily removing this, I was able to eventually get into the Shadow Folders maintenance screen.
Then, once there I was able to add 1 Shadow Folder for '$/Common', however when I try and add '$/Production Source' it does not get added. Also, an ASP.NET error happens that stops the VaultAppPool and I have to restart it.
The following was added to the web.config for the ShadowFolders;
<WorkingFolderAssociations>
<rep repid="2">
<sfa assoc_key="2:$/common-d:\vaultshadow\common" reppath="$/Common" localpath="D:\VaultShadow\Common" readonly="False" repid="2" synchepository="False" filedateoption="2" initialget="True" webpath="D:\Web Sites\Vault\VaultShadowFolder" />
</rep>
</WorkingFolderAssociations>
I did notice the repid="2" in there, and when I am attempting to add another Shadow folder, the add button link indicates it is also using repid="2".
Regards
Tom
After some further investigation, I found that in the web.config for the ShadowFolders I found that there was a line for <identity impersonate ....>
By temporarily removing this, I was able to eventually get into the Shadow Folders maintenance screen.
Then, once there I was able to add 1 Shadow Folder for '$/Common', however when I try and add '$/Production Source' it does not get added. Also, an ASP.NET error happens that stops the VaultAppPool and I have to restart it.
The following was added to the web.config for the ShadowFolders;
<WorkingFolderAssociations>
<rep repid="2">
<sfa assoc_key="2:$/common-d:\vaultshadow\common" reppath="$/Common" localpath="D:\VaultShadow\Common" readonly="False" repid="2" synchepository="False" filedateoption="2" initialget="True" webpath="D:\Web Sites\Vault\VaultShadowFolder" />
</rep>
</WorkingFolderAssociations>
I did notice the repid="2" in there, and when I am attempting to add another Shadow folder, the add button link indicates it is also using repid="2".
Regards
Tom
Could you open up a Vault client, connect to a repository, go to Help - Technical Support and copy the information from there to me? That will provide some useful environment information.
The <identity impersonate> entry is supposed to be the AD account you are running Vault under. Did that not match what you are using? When you removed it, you are making the shadow folders run under an ASPNET account instead of the custom account.
Also, could you check your Shadow Folder log? To find the Shadow Folder's log file, look in the temporary directory of the user the web service runs as. Usually this is the ASPNET user, whose temp folder is something like C:\Documents and Settings\<your machine name>\ASPNET\Local Settings\Temp. If you have configured the Shadow Folder service to run under an impersonated account, check that user's Local Settings\Temp folder.
The <identity impersonate> entry is supposed to be the AD account you are running Vault under. Did that not match what you are using? When you removed it, you are making the shadow folders run under an ASPNET account instead of the custom account.
Also, could you check your Shadow Folder log? To find the Shadow Folder's log file, look in the temporary directory of the user the web service runs as. Usually this is the ASPNET user, whose temp folder is something like C:\Documents and Settings\<your machine name>\ASPNET\Local Settings\Temp. If you have configured the Shadow Folder service to run under an impersonated account, check that user's Local Settings\Temp folder.