Problem re-establishing shadow folders

[jmlange]

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 using Windows 2003 Server on the front end with IIS 6. The back end is SQL Server 2005. Our Vault version is 4.1.4.
I’ve read and followed the steps in your knowledgebase articles about setting up shadow folders.
Now I’m at the point where I go to the admin site’s “Shadow Folders” menu for the default repository. When I do I get the msg:
“The Vault server could not reach the Shadow Folder Service.”
I turned on debug logging and this is what the log reports as a result of that shadow folder attempt:
----5/7/2009 7:25:42 AM admin--10.0.20.216(10.0.20.216)--SSL Disabled WEB: Started Loading ShadowFolders
----5/7/2009 7:25:43 AM admin--10.0.20.216(10.0.20.216)--SSL Disabled System.Net.WebException: The request failed with HTTP status 401: Unauthorized.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at VaultWebLib.VaultShadowFolderService.TestServerConnection()
at VaultService.Admin.ShadowFolders.TestShadowFolderServiceConnection(String shadowFolderServiceUrl) at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at VaultWebLib.VaultShadowFolderService.TestServerConnection()
at VaultService.Admin.ShadowFolders.TestShadowFolderServiceConnection(String shadowFolderServiceUrl)
----5/7/2009 7:25:43 AM admin--10.0.20.216(10.0.20.216)--SSL Disabled System.Net.WebException: The request failed with HTTP status 400: Bad Request.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at VaultWebLib.VaultShadowFolderService.TestServerConnection()
at VaultService.Admin.ShadowFolders.TestShadowFolderServiceConnection(String shadowFolderServiceUrl) at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at VaultWebLib.VaultShadowFolderService.TestServerConnection()
at VaultService.Admin.ShadowFolders.TestShadowFolderServiceConnection(String shadowFolderServiceUrl)
----5/7/2009 7:25:43 AM admin--10.0.20.216(10.0.20.216)--SSL Disabled WEB: Finshed loading ShadowFolders

[lbauer]

Check the troubleshooting steps here;

http://support.sourcegear.com/viewtopic ... 13&t=11576

Let me know if this does not resolve the problem.

[jmlange]

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.

[lbauer]

Did you try to create a folder for the cache in that location, plus give the account used by the Shadow Folder Service full control of that folder?

[jmlange]

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

[lbauer]

Check Directory Security in the properties of the Vault Shadow Folder virtual directory in IIS. Verify that anonymous access is enabled.

[jmlange]

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:13 10.0.30.252 POST /VaultShadowFolder/VaultShadowFolderService.asmx - 80 - 10.0.30.252 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.42) 401 5 0

2009-05-08 20:59:13 10.0.30.252 POST /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

[lbauer]

On the server machine, can you connect to http://localhost/vaultshadowfolder/vaul ... rvice.asmx?

[jmlange]

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 for the information you want.

More information

This error (HTTP 400 Bad Request) means that Internet Explorer was able to connect to the web server, but the webpage could not be found because of a problem with the address.

For more information about HTTP errors, see Help.

--------------------------------------------

If I do the same thing but substitute our server name for the "localhost" part of the URL it produces:
Server Error in '/vaultshadowfolder' Application.
--------------------------------------------------------------------------------

Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Unrecognized configuration section 'xhtmlConformance'

Source Error:


Line 90: -->
Line 91: <!-- identity impersonate="true" userName="DOMAINorMACHINE\WINDOWSACCT" password="plaintext_pwd"/>-->
Line 92: <xhtmlConformance mode="Legacy" />
Line 93: </system.web>
Line 94: <appSettings>


Source File: C:\Inetpub\wwwroot\VaultService\VaultShadowFolder\web.config Line: 92


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300

[lbauer]

Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300

Based on the information in the error message, the Shadow Folder virtual web service is using the 1.1 .NET Framework.

In IIS, check the Properties of the VaultShadowFolder virtual directory and change the ASP.NET setting to the 2.0 Framework. Vault 4.x requires the 2.0 Framework.

[jmlange]

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 the Vault Server at VaultShadowFolder.VaultShadowFolderService.TestServerConnection() --- End of inner exception stack trace ---

[lbauer]

Could you send me a copy of the web.config file from the VaultShadowFolder directory? Send it to support at sourcegear.com, Attn: Linda. Please include a link to this forum post.

[jmlange]

I just sent that file via email.

[lbauer]

The ShadowFolder web.config file is missing some entries. It's possible the file didn't get written to properly during the upgrade. I was able to reproduce your error when I deleted the highlighted values from my own web.config file.

<!-- <add key="shadowfolder_cachepath" value="c:\Program Files\Sourcegear\Vault Shadow Folder Cache" /> -->
<add key="shadowfolder_login" value="admin" />
<add key="shadowfolder_password" value="K+UtO6rTzxQ=" />
<add key="shadowfolder_vaultserver" value="http://<yourservername>/VaultService" /> </appSettings>
<WorkingFolderAssociations>
</WorkingFolderAssociations>
</configuration>

I don't think there's a way to manually add this because you couldn't recreate the encrypted password. The encrypted admin password in the database doesn't match. Uninstalling (leaving the database when prompted), making sure that web.config file is deleted, then reinstalling to recreate the web.config file would recreate the proper content.

Another option -- send me your admin password, I'll install Vault using that, and then I'll send you the resulting web.config file with the encrypted password.