We have a new server Windows 64 bit 2008 R2 Standard
The server has the same name and IP or hte original.
I installed the vault server successfully and can connect via the admin Website:
http://gvppweb003/VaultService/VaultWeb ... Login.aspx
I tried to connect through the client or visual studio.
I get the following error.
Unable to connect to http://gvppweb003/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: The request failed with the error message:
--
<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="/VaultService/VaultWeb/Login.aspx?ReturnUrl=%2fVaultService%2fVaultService.asmx">here</a>.</h2>
</body></html>
Any help?
New Server - Cannot connect with client
Re: New Server - Cannot connect with client
Was the original server taken out of the network?
Can you reach the web URL from a client? http://your Vault server/vaultservice/vaultweb
If you can't, could you post the exact error?
Can you ping the new server from a client?
Make sure that anonymous access is enabled on the website in your IIS Manager. Is that set?
Can you reach the web URL from a client? http://your Vault server/vaultservice/vaultweb
If you can't, could you post the exact error?
Can you ping the new server from a client?
Make sure that anonymous access is enabled on the website in your IIS Manager. Is that set?
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: New Server - Cannot connect with client
Beth,
Thanks for your reply.
Yes, the original server was taken off the Network.
The Webpage can be reached via a client machine http://gvppweb003/VaultService/VaultWeb/Default.aspx
We enabled anonymous from IIS and we get another error:
"Could not get public key from server"
I also queried the tblPlugins table, and does the multiple entries here cause any problems?
Thanks for your reply.
Yes, the original server was taken off the Network.
The Webpage can be reached via a client machine http://gvppweb003/VaultService/VaultWeb/Default.aspx
We enabled anonymous from IIS and we get another error:
"Could not get public key from server"
I also queried the tblPlugins table, and does the multiple entries here cause any problems?
You do not have the required permissions to view the files attached to this post.
Re: New Server - Cannot connect with client
The solution to that error is to check the permissions on the RSA/Machine Keys folder. Instructions can be found in this forum thread: http://support.sourcegear.com/viewtopic ... 44&t=12245&.Could not get public key from server
In the plugins, what matters is which ones are active. The easiest place to manage those URLs is in the Vault admin web page under the Vault Professional Plugins link. You don't need to keep any that aren't active, but you will need
for Source Control
- -- 1 http://your Vault server/VaultIndexService/VaultIndexService.asmx
-- 1 http://your Vault server/VaultNotifyService/VaultNotifyService.asmx
-- 1 http://your Vault server/VaultShadowFolder/VaultShadowFolderService.asmx
- -- 1 http://your Vault server/VaultNotifyService/VaultNotifyService.asmx
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: New Server - Cannot connect with client
Beth,
Thanks again.
But, your link above only gives:
'You are not authorised to read this forum.'
In an addendum.
The VaultAppPool ran under ApplicationPoolIdentity, and I changed it to LocalSystem, but still am getting the key error. I had this setup up on the same type of server (Windows 2008 Server R2) temporarily to test this first, and did not get these errors. Actually it may have been the same server. Out server support setup a server with the name (name)-new, and I loaded the Vault Server on it. Last week we were suppose to flip from our current production server (name) to the new one. This original server never had the Vault Server, and all that was do be done was turn off the old server, and then give the new server the old server (name) and IP, and reconnect the new server to the domain.
I don't know if this has any bering on our problem, but mention it here. Primarly because I am no sure what got botched in the 'flip'. I think that since partial files and partial install of the Vault Server was still on this server, that they created a bran new virtual server instance and did a partial move to this one from a our testing 'new' server. God, I know that this is confusing. After the flip, I had to run the Vault Server UN-Install, so I could re-install. I was hoping to get a clean install.
Why would the original install on Server 2008 R2 not have this problem, and this one does?
Thanks again.
But, your link above only gives:
'You are not authorised to read this forum.'
In an addendum.
The VaultAppPool ran under ApplicationPoolIdentity, and I changed it to LocalSystem, but still am getting the key error. I had this setup up on the same type of server (Windows 2008 Server R2) temporarily to test this first, and did not get these errors. Actually it may have been the same server. Out server support setup a server with the name (name)-new, and I loaded the Vault Server on it. Last week we were suppose to flip from our current production server (name) to the new one. This original server never had the Vault Server, and all that was do be done was turn off the old server, and then give the new server the old server (name) and IP, and reconnect the new server to the domain.
I don't know if this has any bering on our problem, but mention it here. Primarly because I am no sure what got botched in the 'flip'. I think that since partial files and partial install of the Vault Server was still on this server, that they created a bran new virtual server instance and did a partial move to this one from a our testing 'new' server. God, I know that this is confusing. After the flip, I had to run the Vault Server UN-Install, so I could re-install. I was hoping to get a clean install.
Why would the original install on Server 2008 R2 not have this problem, and this one does?
Re: New Server - Cannot connect with client
Here's what you need to know from that link.
This error is caused when the ASP.Net process account that the Vault web service is running does not have the correct security rights on the %ALLUSERSPROFILE%\Application Data\Microsoft\Crypto\RSA\MachineKeys folder. To correct this, go through the following steps:
1. Determine which account is being used by the Vault Service. The system started message in the Vault server log file will contain a line stating "Identity = USER", where user is ASPNET, SYSTEM, NETWORK SERVICE, or the user that is being impersonated.
2. Make sure that the user specified above has read / write / modify permissions to the %ALLUSERSPROFILE%\Application Data\Microsoft\Crypto\RSA\MachineKeys
3. If the problem persists after adding these permissions, stop IIS, and find a file that starts with "edb3...." in the directory mentioned earlier. Delete it, and then restart IIS. Then try to log into Vault.
This error is caused when the ASP.Net process account that the Vault web service is running does not have the correct security rights on the %ALLUSERSPROFILE%\Application Data\Microsoft\Crypto\RSA\MachineKeys folder. To correct this, go through the following steps:
1. Determine which account is being used by the Vault Service. The system started message in the Vault server log file will contain a line stating "Identity = USER", where user is ASPNET, SYSTEM, NETWORK SERVICE, or the user that is being impersonated.
2. Make sure that the user specified above has read / write / modify permissions to the %ALLUSERSPROFILE%\Application Data\Microsoft\Crypto\RSA\MachineKeys
3. If the problem persists after adding these permissions, stop IIS, and find a file that starts with "edb3...." in the directory mentioned earlier. Delete it, and then restart IIS. Then try to log into Vault.
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: New Server - Cannot connect with client
This did the trick.
Thank you.
However, instead of deleting the machine key file, edb3..., when the second step didn't work, I added the USER (VaultAppPool) permissions to the edb3... file directly. I did not want to stop IIS; as I am not the only application owner on the server.
Providing the folder and the file the USER permissions will work without restarting IIS.
Thank you.
However, instead of deleting the machine key file, edb3..., when the second step didn't work, I added the USER (VaultAppPool) permissions to the edb3... file directly. I did not want to stop IIS; as I am not the only application owner on the server.
Providing the folder and the file the USER permissions will work without restarting IIS.
Re: New Server - Cannot connect with client
Thanks for the update. I'm happy to hear you are working again.
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support