My 3.1.9 installation uses a DB on a separate machine and the Domain\MachineName$ model. During the upgrade, I specify the 'sa' login during database creation. All proceeds normally until somewhere in mid process the installation stops and complains that the data base is in single user mode. I have re-attempted numerous times. I restore the old database each time and delete the installer's handiwork (new and converted DB's). I've stopped and started SQL Server. I've attempted to remove the Single User setting on the DB.
Any suggestions?
Update 3.1.9 to 4.1.1 fails with Single User Mode issue
Moderator: SourceGear
-
RickDaniel
- Posts: 6
- Joined: Sun Apr 20, 2008 10:33 pm
-
RickDaniel
- Posts: 6
- Joined: Sun Apr 20, 2008 10:33 pm
Log file sent
Thanks, I forwarded the log file by email.
I tried one other thing. I restored the original DB and attempted to upgrade to v3.5.0 and v3.5.3 instead of v4.1 and got the same result at the same spot (upgrading stored procedures) in both cases. I also attempted the v4.1.1 installation LOCALLY on the SQL Server (running Server 2008) without success.
I tried one other thing. I restored the original DB and attempted to upgrade to v3.5.0 and v3.5.3 instead of v4.1 and got the same result at the same spot (upgrading stored procedures) in both cases. I also attempted the v4.1.1 installation LOCALLY on the SQL Server (running Server 2008) without success.
Last edited by RickDaniel on Thu Apr 24, 2008 7:03 pm, edited 1 time in total.
-
RickDaniel
- Posts: 6
- Joined: Sun Apr 20, 2008 10:33 pm
Progress
Well, I am making progress.
I moved the database to my notebook (Vista). The notebook never had Vault on it. I installed Vault on the notebook and pointed it at the local sgvault v3.1.9 database. The upgrade and install went without error.
I moved the newly upgraded v4.1.1 databases back to the SQL Server (running Win Server 2008) and tried to run the Vault install on the previous Vault Server (running Win Server 2003). The install failed again with the single user mode issue in the same place, even though the database was already at v4.1.1.
So this is progress. I am beginning to suspect something with Win Server 2008 security issues on the SQL Server.
I moved the database to my notebook (Vista). The notebook never had Vault on it. I installed Vault on the notebook and pointed it at the local sgvault v3.1.9 database. The upgrade and install went without error.
I moved the newly upgraded v4.1.1 databases back to the SQL Server (running Win Server 2008) and tried to run the Vault install on the previous Vault Server (running Win Server 2003). The install failed again with the single user mode issue in the same place, even though the database was already at v4.1.1.
So this is progress. I am beginning to suspect something with Win Server 2008 security issues on the SQL Server.
-
RickDaniel
- Posts: 6
- Joined: Sun Apr 20, 2008 10:33 pm
More Progress
More progress, but not quite there. On SQL Server deleted the Vault databases. On Web server uninstalled Vault. Did a fresh default install on the web server, pointing the database to the SQL Server without incident. Now have a blank database on the SQL Server and a new v4.1.1 on the web server and am able to connect from Admin and put in the key.
As mentioned in the previous post, I also have a converted v4.1.1 set of data on my notebook computer.
Backed up the Vault databases (sgmaster and sgvault) and copied the dump files to the SQL server and restored them. Visually checked all the users (sgvaultuser). All seemed fine, but webserver\vaultservice is accessible but can not connect to the newly restored DB. Admin client says: "Login Failed: The Vault Server could not establish a connection to the database. Please check the server's log for detailed information. (FailDBConn)"
I've browsed the forum, is there something special I need to do when restoring the DB on a new SQL Server to get the installation to work?
It seems like I am almost there.
As mentioned in the previous post, I also have a converted v4.1.1 set of data on my notebook computer.
Backed up the Vault databases (sgmaster and sgvault) and copied the dump files to the SQL server and restored them. Visually checked all the users (sgvaultuser). All seemed fine, but webserver\vaultservice is accessible but can not connect to the newly restored DB. Admin client says: "Login Failed: The Vault Server could not establish a connection to the database. Please check the server's log for detailed information. (FailDBConn)"
I've browsed the forum, is there something special I need to do when restoring the DB on a new SQL Server to get the installation to work?
It seems like I am almost there.
I would suggest uninstalling Vault, leaving the databases on SQL Server, then reinstalling Vault.
The log file suggests a problem with sgvaultuser at not being able to log into SQL Server. Although this account name is the same in the database, SQL Server treats treats these as different accounts.
When you install Vault, the installer takes care of creating the proper accounts and giving them the proper permissions.
Details here:
http://support.sourcegear.com/viewtopic.php?t=924
The log file suggests a problem with sgvaultuser at not being able to log into SQL Server. Although this account name is the same in the database, SQL Server treats treats these as different accounts.
When you install Vault, the installer takes care of creating the proper accounts and giving them the proper permissions.
Details here:
http://support.sourcegear.com/viewtopic.php?t=924
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Another option would be to delete and recreate the database user:
1 - Remove the sgvaultuser's access to both the sgvault and sgmaster databases.
2 - Delete the sgvaultuser from the SQL Server
3 - Recreate the sgvaultuser.
4 - Give the sgvaultuser permissions to both the sgvault and sgmaster databases.
5 - Make sgvaultuser a db_owner of both the sgvault and sgmaster databases.
1 - Remove the sgvaultuser's access to both the sgvault and sgmaster databases.
2 - Delete the sgvaultuser from the SQL Server
3 - Recreate the sgvaultuser.
4 - Give the sgvaultuser permissions to both the sgvault and sgmaster databases.
5 - Make sgvaultuser a db_owner of both the sgvault and sgmaster databases.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
-
RickDaniel
- Posts: 6
- Joined: Sun Apr 20, 2008 10:33 pm
The solution was a very careful application of your advice above.
I was never successful at a reinstall over the old database using a remote SQL Server. I did a clean install (new database) to prove everything worked, then restored an upgraded version of the old database.
There was an intermediate step though. Since I could never get a good upgrade of my 3.x database in the target config (remote SQL DB), I installed in a local configuration on another machine (SQL same machine as Vault) where I could get a successful 3.x to 4.x DB upgrade. I then restored that DB back to my target configuration with remote SQL.
I used SQL Authentication (not windows auth) and it was absolutely necessary to drop all the sgvault users in both the databases and the server logins. Then the script you referenced above got me up and running. The script is simple. The key was 1) finding another machine that could succesfully upgrade the DB, then 2) getting all the vault users out and re-created manually.
I was never successful at a reinstall over the old database using a remote SQL Server. I did a clean install (new database) to prove everything worked, then restored an upgraded version of the old database.
There was an intermediate step though. Since I could never get a good upgrade of my 3.x database in the target config (remote SQL DB), I installed in a local configuration on another machine (SQL same machine as Vault) where I could get a successful 3.x to 4.x DB upgrade. I then restored that DB back to my target configuration with remote SQL.
I used SQL Authentication (not windows auth) and it was absolutely necessary to drop all the sgvault users in both the databases and the server logins. Then the script you referenced above got me up and running. The script is simple. The key was 1) finding another machine that could succesfully upgrade the DB, then 2) getting all the vault users out and re-created manually.
-
RickDaniel
- Posts: 6
- Joined: Sun Apr 20, 2008 10:33 pm
Re: Update 3.1.9 to 4.1.1 fails with Single User Mode issue
Update.
When upgrading to 4.1.3 I had the same issue of the DB hanging up in single user mode during install. I tried several times. I was about to try the above referenced technique again.
This time, I went to the DB server and installed vault directly on it using all the default settings except using "sa" as the SQL login and the database upgrade completed. I then went back to the intended server and updated and it also went fine.I am back to normal again but for some reason continue to be unable to update from the server if not on the same machine as the SQL Server. My vault server is a generic W2K Server machine and the DB is on a different machine running W2k8 Server x64.
This approach was a little easier.
When upgrading to 4.1.3 I had the same issue of the DB hanging up in single user mode during install. I tried several times. I was about to try the above referenced technique again.
This time, I went to the DB server and installed vault directly on it using all the default settings except using "sa" as the SQL login and the database upgrade completed. I then went back to the intended server and updated and it also went fine.I am back to normal again but for some reason continue to be unable to update from the server if not on the same machine as the SQL Server. My vault server is a generic W2K Server machine and the DB is on a different machine running W2k8 Server x64.
This approach was a little easier.