SourceGear Support

That pretty much clears it up.

I am just doing a SQL Server in place upgrade on the same machine. Will I need to do anything special when I do the Visual Studio upgrade, which I plan to do after the SQL Server and Vault 10 upgrades?

Thanks for the information which I'll review.

All upgrades are in place upgrades of an existing server. I guess since the SQL Server will be a new instance the Vault database backup / restore is still recommended rather than hoping the SQL upgrade will deal with it properly?

I am planning to do the following upgrades:
SQL Server 2014 to 2017
Visual Studio 2015 to 2017
Vault Professional 9.1 to 10.0

What would be the recommended sequence for these upgrades?

I believe I have solved it as follows: I uninstalled Vault Administrator and then restored the 4 vault databases (sgmaster, sgnotify, sgvault, and sgfaultindex) from the Vault 7.x backup I did before I started all of this process. Two of the databases (sgmaster and sgvault) were showing in single us...

Making some progress. I couldn't even get into Sgmaster's properties because of the single-user mode. But I set it via an SQL command run against Master. I still can't get it to accept my login even after I did another reinstall. Perhaps I'll do an uninstall, restore the database from a backup I mad...

I did a reinstall, was very careful about the password, and still get the error when it goes to the web page to do the initial login necessary to enter license keys. This is probably significant but I'm not sure what to do about it: I went into SSMS and the only sgmaster database showing is "sg...

I uninstalled, saving the database, and then installed 9.1. I feel something else is going on with the user name / password validation other than my supposed inability to type a password correctly 3 times in a row, but I'll do another install and even use a simple different password.

Yes I did.

I upgraded to Vault Professional 9.1.0.30584 from Vault Standard 7.2.1.265. When I try to login to the administrative website after login, I get "Login Failed: The username or password supplied is invalid". I reinstalled but got the same message. I saved the database from 7.2.1.265, and th...

I resolved the problem.

I went back and reviewed the SQL services and saw that they had not started. I changed the login accounts, got them to start and Vault is now operational.

Thanks for your help and sorry for the confusion. The Windows error message threw me.

If you open a browser on the Vault server and go to http://localhost/vaultservice/index.html, does it come up? If no page comes up, then open your IIS Manager. Is the website or application pools stopped? Can you perform an IIS reset by going to Start - Run and typing iisrest? When I try to access ...

Slowly but surely I'm getting the upgrade to both the Windows server and Vault implemented but have run into another problem. Server is Windows Server 2012 R2 running SQL Server 2014. Vault is version 7.2.1. Yesterday I made the changes suggested to the ApplicationPoolIdentity and made sure the pool...

I recently installed 7.1.2 on a Windows Server 2012 R2 running SQL Server 2014. I was able to access the database through the Vault 7.1.2 client without any problem. This is a new server and as I continued to add various roles and features to it, Vault stopped working, giving a "503: Service Un...

Following your steps worked perfectly. Only problem I had was when I opened a solution in Visual Studio 2010 it went to the old server and gave a "protocol not supported" error. Workaround was easy. I went offline on the solution, unbound everything, and then bound them to the new server a...

I am currently using Vault Standard version 5.1.2 on a Windows 2003 Server with SQL Server 2008 R2. I have installed a new Windows 2012 R2 server with SQL server 2014 and have purchased the Vault 7.2.1 upgrade and need some advice on the proper way to migrate to the new server and new version of Vau...