I just upgraded Vault from v3.5.3 to v4.1.6. After upgrading, I have two critical problems: 1) the client cannot connect to the server, and 2) the admin tool will not let me configure shadow folders.
I've followed the debugging steps at http://support.sourcegear.com/viewtopic.php?p=2450, but they haven't helped me solve the problem. I'm going to report my observations below in the hope that someone can help me.
1. When I use the Vault client to connect to the server from the client, I get the message "Unable to connect to http://matsonconsulting.com/VaultService. No server was found at the specified URL. Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client. Web Exception: Client found response content type of 'text/html', but expected 'text/xml'."
2. When I use the Vault client to connect to the server from the server, everything seems to work fine.
3. When I browse to http://MatsonConsulting.com/VaultService from the client, I get the message "You are not authorized to view this page".
4. When I browse to http://localhost/VaultService from the server, I get the message "You are not authorized to view this page".
5. When I browse to http://MatsonConsulting.com/VaultServic ... rvice.asmx from the client, I get the message "Server Application Unavailable".
6. When I brose to http://localhost/VaultService/VaultService.asmx from the server, I get the expected page.
7. When I browse to http://MatsonConsulting.com/VaultVervice/admin on the client, I get the message "Server Application Unavailable".
8. When I browse to http://localhost/VaultService/admin on the server, I can login to the admin tool as expected.
9. When I use the admin tool and click on "Shadow Folders" for any repository, I get the error "Client found response content type of 'text/html', but expected 'text/xml'. The request failed with the error message: -- Server Application Unavailable"
I've been using Vault since v3.1.6, and I've spent many hours troubleshooting problems every time I upgrade. Along the way, I've kept notes on what fixed the problem each time. Based on those notes, I've taken the following additional steps.
10. I gave the Internet Guest Account broad permissions on the folders "VaultService" and "VaultShadowFolder" and all their subfolders.
11. In IIS, the virtual directories for VaultService and VaultShadowFolders did not have application names assigned to them. I assigned "VaultService" and "VaultShadowFolders" respectively.
12. I went into VaultShadowFolder\Web.config and I replaced all instances of the formal server name with "localhost".
Note that v3.5.3 was working properly before the upgrade. The upgrade procedure gave me no errors.
Can anyone offer advice?
-TC
Upgrade to v4.1.6 Failed -- Please Help
Moderator: SourceGear
I've continued working on this problem for the past few hours, and I've made good progress. I discovered that, during installation, I had mistakenly installed the virtual folders under the default website, instead of the intended website (which is not the default). When I fixed that, most of the problems were resolved.
Unfortunately, shadow folders still don't work. During the upgrade, I lost all my shadow folders. When I restore them, I don't get any errors. Nevertheless, they just don't work. If I add a file to a folder, it doesn't get added to the shadow folder. If I edit a file, it doesn't get edited in the shadow folder.
Can anyone provide me with troubleshooting tips for shadow folders?
-TC
Unfortunately, shadow folders still don't work. During the upgrade, I lost all my shadow folders. When I restore them, I don't get any errors. Nevertheless, they just don't work. If I add a file to a folder, it doesn't get added to the shadow folder. If I edit a file, it doesn't get edited in the shadow folder.
Can anyone provide me with troubleshooting tips for shadow folders?
-TC
I'm still working on this problem. I've discovered that if I delete the shadow folder configuration, then restore it, Vault will synchronize the shadow folder once, but only once. After that, all changes are ignored.
Please help. I'm desperate to get Vault working. Knowing that upgrades never go smoothly, I allocated 8 hours to perform the upgrade over the weekend. I'm already beyond that, and I still have no clue how to fix the shadow folders.
-TC
Please help. I'm desperate to get Vault working. Knowing that upgrades never go smoothly, I allocated 8 hours to perform the upgrade over the weekend. I'm already beyond that, and I still have no clue how to fix the shadow folders.
-TC
Terrence,
Your questions have brought me to a resolution. I changed the shadow folder settings from "Optimized for Speed" to "Synchronized with Repository", and now everything works. As far as I know, "Optimized for Speed" should work for me, so there is still a bug somewhere. However, I'm not going to worry about that -- "Synchronized with Repository" is doing the job just fine.
I must say, I get frustrated whenever I reconfigure Vault, but you guys are quick with support, and I always find a solution eventually. That makes you much better than most software vendors. Thank you.
Given the number of things that can go wrong with shadow folders, I would like to make a suggestion: If you put a simple shadow folder troubleshooting checklist in the knowledge base, you could probably help a lot of people and avoid support requests like mine. (e.g: 1. Try changing from "Optimized for Speed" to "Synchronized with Repository"; 2. Change Web.config to use "localhost" and not the server name in URLs; 3. If you are requiring SSL connections, change URLs in Web.config to use "https"; 4. Open C:\WINDOWS\Temp\SGShadowFolder\vaultshadowfolderservice.txt and look for ... etc. etc.)
-TC
Your questions have brought me to a resolution. I changed the shadow folder settings from "Optimized for Speed" to "Synchronized with Repository", and now everything works. As far as I know, "Optimized for Speed" should work for me, so there is still a bug somewhere. However, I'm not going to worry about that -- "Synchronized with Repository" is doing the job just fine.
I must say, I get frustrated whenever I reconfigure Vault, but you guys are quick with support, and I always find a solution eventually. That makes you much better than most software vendors. Thank you.
Given the number of things that can go wrong with shadow folders, I would like to make a suggestion: If you put a simple shadow folder troubleshooting checklist in the knowledge base, you could probably help a lot of people and avoid support requests like mine. (e.g: 1. Try changing from "Optimized for Speed" to "Synchronized with Repository"; 2. Change Web.config to use "localhost" and not the server name in URLs; 3. If you are requiring SSL connections, change URLs in Web.config to use "https"; 4. Open C:\WINDOWS\Temp\SGShadowFolder\vaultshadowfolderservice.txt and look for ... etc. etc.)
-TC