SourceGear Support

This appears to be a server install issue, and not a vault install issue.
Sorry for the false alarm.
You can close this thread.

Other websites had issues too, and we're getting a fresh web server.

These features/roled we already enabled.

• Web Server (IIS) \ Web Server \ Common HTTP Features \ Static Content ( checked) Web Server (IIS)
  Web Server \ Application Development \ ASP.NET 4.6 (checked or whatever version you have installed)

We lost a webserver, and no backup. I ran the install for 10.2.0 Vault Pro Server, and got the following error when the install finished and launched the web browser. HTTP Error 500.19 - Internal Server Error The requested page cannot be accessed because the related configuration data for the page i...

I've done most of the things you suggested - recylce pool, IIS reset, etc. So, the plain text PW I've received from the SQL team... does it need to be encrypted? This is a point I have been wondering about? If I was given a PW, 123abc@!, then does it need to be encrytped to ...? I've replaced the se...

1) How were the new passwords changed? I can't be sure, but I would think SSMS (SQL Server Management Studio) by the SQL sa. 2) When you state that nothing works, nobody can log into Vault? Can you please elaborate on the issue? If you receive any errors, please let me know. No one can login into v...

Thanks again. I asked our SQL team to update the PW for 'sgvaultuser', unfortunately they updated the PW for both 'sqvaultuser' and 'vaultAdmin'. I updated both the web configs with the new PW for 'sgvaultuser' in VaultPro and VaultService. Nothing works now. I did validate that the new PW for 'sgva...

Thank you.
So, in the web interface is the 'Admin' user the one connected to the SQL 'vaultAdmin' Login?
See attached.

We have had an install of Vault Professional for a decade over many versions. I have questions about the following statement: "The Vault Server installer will also create a SQL login named 'sgvaultuser', and grant it access to the new databases. The SA account is used only during the installati...

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 folde...

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 Serv...

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 querie...

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?ReturnUrl=%2fVaultService%2fVaultWeb%2fLogin.aspx I tried to c...

Alright, We've moved to our Production Web server. I get Service Unavailable. HTTP 503. I have not decommissioned our former Vault Service web site on the standard desktop. Is there a conflict with this? I didn't want to stop the old vault website until I got this new (permanent one) setup. Please s...

This is resolved: I knew after working on this for awhile that I soon as I posted, I would resolve this. Short answer: Vault 7 doesn't require a Impersonation in the web.config (s) There are more web.config (s) than the 2 I mentioned I put the Identity on the WebApp Pools for Vault as the Upgrade to...

After Upgrading from 6 to 7, we get an error when opening the vault client. This also throws an error in the event log on the web server. We tried to set the web.config to show detail errors, but this didn't work. However, as I mentioned above the machine event log did. I compared the old web.config...