We are having problems getting our Shadow Folders to update, so thought we'd delete and re-create. Upon trying to delete, we got the following error:
System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.UnauthorizedAccessException: Access to the path "D:\Inetpub\wwwroot\VaultService\VaultShadowFolder\web.config" is denied.
at System.IO.__Error.WinIOError(Int32 errorCode, String str)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean useAsync, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
at System.Xml.XmlDocument.Save(String filename)
at VaultShadowFolder.VaultShadowFolderService.DeleteWorkingFolderAssociation(String strServerWebPath, Int32 repID, ShadowFolderAssociation sfa)
at VaultShadowFolder.VaultShadowFolderService.RemoveShadowFolderAssociation(Int32 repID, ShadowFolderAssociation association)
--- End of inner exception stack trace ---
The possible "trigger" for this issue is that we enabled SSL yesterday (new server). We have it required for the VaultService, but not the VaultShadowFolder application (didn't know what it would affect). Per one of the other messages, we have checked down in our AllUsers/ApplicationData/Microsoft/RSA/MachineKeys to make sure Everyone has read and execute permission.
I couldn't find any special SSL instructions in the Knowledgebase.
Cannot Delete Shadow Folder
Moderator: SourceGear
Could it be that the shadow folders were in use at the time? Did you try removing those folders while Vault was running and/or users connected?
Your SSL connections are working well otherwise for everyone?
Can you send a the shadow folder log file and a Vault Server Log to me using either the private function here or send it to beth at sourcegear.com and reference this post?
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.
Your SSL connections are working well otherwise for everyone?
Can you send a the shadow folder log file and a Vault Server Log to me using either the private function here or send it to beth at sourcegear.com and reference this post?
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.
One more thing to try. Open up a browser and type in this address:
http://<name of server>/VaultService
That is the path that shadow folders use. If it does not work, then something is in the way of the path.
One thing it could get in the way is if you only have the ssl port enabled and not the regular http port that you were using before. Both ports need to remain open for the shadow folder to continue working here.
You can also check what you have configured in the web.config file for the shadow service which is normally found C:\Inetpub\wwwroot\VaultService\VaultShadowFolder. The path you are looking for will look something like:
<add key="shadowfolder_vaultserver" value="http://<servername>/VaultService" />
Besides the path you will want to see that it has http instead of https.
http://<name of server>/VaultService
That is the path that shadow folders use. If it does not work, then something is in the way of the path.
One thing it could get in the way is if you only have the ssl port enabled and not the regular http port that you were using before. Both ports need to remain open for the shadow folder to continue working here.
You can also check what you have configured in the web.config file for the shadow service which is normally found C:\Inetpub\wwwroot\VaultService\VaultShadowFolder. The path you are looking for will look something like:
<add key="shadowfolder_vaultserver" value="http://<servername>/VaultService" />
Besides the path you will want to see that it has http instead of https.
-
- Posts: 6
- Joined: Fri Sep 22, 2006 3:37 pm
It is true that I configured https to be required. Can I not not require users to connect through https?Beth wrote:One more thing to try. Open up a browser and type in this address:
http://<name of server>/VaultService
That is the path that shadow folders use. If it does not work, then something is in the way of the path.
One thing it could get in the way is if you only have the ssl port enabled and not the regular http port that you were using before. Both ports need to remain open for the shadow folder to continue working here.
So can I go in manually and set the value attribute of this connection string to "https"?Beth wrote: You can also check what you have configured in the web.config file for the shadow service which is normally found C:\Inetpub\wwwroot\VaultService\VaultShadowFolder. The path you are looking for will look something like:
<add key="shadowfolder_vaultserver" value="http://<servername>/VaultService" />
Besides the path you will want to see that it has http instead of https.