I'm trying to upgrade from 3.0.1 to 3.1.6, and the installer always fails.. This is a home version, but I've starting to have lots of issues with 3.0.1, so Its time to upgrade.
Here is my setup:
Webserv01.fqdn has the webpart ( I'm trying to install from this machine)
Vault Service is installed in G:\VaultPub\WWWroot\VaultService\
DBServer01.fqdn has the Database, and it sits in G:\VaultDB ( I did move it from C:\*pathTODefaultSQLDatabases* since I installed 3.0.1 )
THe database NAME hasn't changed ( sgvault ).
I have a domain user called VaultServerProcess that IIS Runs under ( I think you guys call it impersonation ). On the database, VaultServerProcess logs in as DomainName\VaultServerProcess ( NOT dbo, which i seam to remember one of the older ones that this database was upgraded from did ). This user is a memer of DB_Owner, and Public.
In the install, I set the SERVER path to the above Web location, and I don't change the path of the admin tool ( I left that as default ).
For IIS Process Model, I use "CUstom", and put in the Username and password ( I even reset the password to make sure its right ). I put in the database server name when it asks ( I don't put anything for the db )..
The exact failure comes when it looks for the old database, doesn't find it ( It does infact exist ), and tries to create a new one. It can't create the new one because "Create Database permission denied in Master". I don't have it in there.
So the uninstall rolls back, and everything still works fine. I can even make new Repositories, add / delete folders, etc. All this runs under VaultServerProcess. ( The client still has problems for me, but that is another issue. maybe ).
Another Funny thing to note. After Install Failure, Vault ( Server or Admin tool ) is not listed in the Add / Remove programs. I was going to see if I could start from scratch, but I can't just "Uninstall it". I'll try the manual Uninstall if all else fails.
Upgrade from vault 3.0.1 to 3.1.6
Moderator: SourceGear
First, make sure that the "Server" value in your registry has the correct information for your SQL server location. That value is what the upgrade installer uses to determine where your SQL server and database is. If that value is incorrect it could cause the problems you are seeing. Change that value to point to your current SQL installation then try to upgrade again.
HKEY_LOCAL_MACHINE\SOFTWARE\SourceGear\Vault Server\Server
Are you logged in as the same user that initially installed the Server? If not, the server will not appear in Add/Remove programs. If that is the case (and the above doesn't work), try logging in as that user, then uninstalling (make sure to keep your database) then re-install.
HKEY_LOCAL_MACHINE\SOFTWARE\SourceGear\Vault Server\Server
Are you logged in as the same user that initially installed the Server? If not, the server will not appear in Add/Remove programs. If that is the case (and the above doesn't work), try logging in as that user, then uninstalling (make sure to keep your database) then re-install.
Mary Jo Skrobul
SourceGear
SourceGear
Since this is an upgrade, the installer may still be looking for the database in the old location. I'd suggest you uninstall, then re-install. You should be able to just point Vault to the location of the SQL Server instance, rather than the actual path to the database.
To manually uninstall the Vault server, first backup your database. Then:
1. Delete the IIS virtual directories: VaultService and VaultShadowFolderService
2. Delete the Vaultservice directory
3. Delete C:\Program Files\SourceGear\ (if the folder exists)
4. Open regedit and look for the following key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
Search for entries for SourceGear, Vault, etc.
Remove those entries from the Uninstall registry folder, and then try to install Vault.
To manually uninstall the Vault server, first backup your database. Then:
1. Delete the IIS virtual directories: VaultService and VaultShadowFolderService
2. Delete the Vaultservice directory
3. Delete C:\Program Files\SourceGear\ (if the folder exists)
4. Open regedit and look for the following key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
Search for entries for SourceGear, Vault, etc.
Remove those entries from the Uninstall registry folder, and then try to install Vault.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Still No go
Sorry it took a while. Didn't have time...
The uninstall stuff didnt' come up for any user ( Even the original installing user name ). So I went ahead and did the manual uninstall. The install is still failing, claiming it can't find a previous database.
I have the server typed in correctly, and the database "sgvault" is running. ( That is the correct name, right?? ). Is there anyway I can tell Vault during install a specific database on a specific database server?
Should I try to upgrade so a diff version of Vault?
The uninstall stuff didnt' come up for any user ( Even the original installing user name ). So I went ahead and did the manual uninstall. The install is still failing, claiming it can't find a previous database.
I have the server typed in correctly, and the database "sgvault" is running. ( That is the correct name, right?? ). Is there anyway I can tell Vault during install a specific database on a specific database server?
Should I try to upgrade so a diff version of Vault?
What value are you entering for the SQL server location during install (in the connect to database dialog)?
If you open Query Analyzer and enter the SQL server location value you are using during install and choose the same authentication type (windows or SQL auth) can you connect? Is the sgvault database there?
If you open Query Analyzer and enter the SQL server location value you are using during install and choose the same authentication type (windows or SQL auth) can you connect? Is the sgvault database there?
Mary Jo Skrobul
SourceGear
SourceGear
The database server name is dbserver01, and the FQDN is dbserver01.fireangelcorp.local. My domain name is FIREANGELCORP.
I assume you when you say "Query Analyzer", you are talking about the "connect to database" in VS 2003... If so, I can connect to the computer ( dbserver01.fireangelcorp.local ), and I can type "sgvault" in for the database name, and it will bring up everything inside the database for me. ( this is on a diff machine than I installed Vault server on )..
Should I try ( This is a hack, i know... ):
Put IIS on the database machine, and install server there. I would hope it would find the database, and upgrade it. I would then install SQL Lite ( Can't remember the name, msde maybe? ) on the webserver, and let Vault create a local database. After the install, I can then edit the webconfig file and tell vault to look for the DB on the other machine...
GE
PS> I'm not a DB expert, just playing with it when I have the chance. I wonder if part of the problem is the error "Create Database permission denied in Master". How would I fix that.
I assume you when you say "Query Analyzer", you are talking about the "connect to database" in VS 2003... If so, I can connect to the computer ( dbserver01.fireangelcorp.local ), and I can type "sgvault" in for the database name, and it will bring up everything inside the database for me. ( this is on a diff machine than I installed Vault server on )..
Should I try ( This is a hack, i know... ):
Put IIS on the database machine, and install server there. I would hope it would find the database, and upgrade it. I would then install SQL Lite ( Can't remember the name, msde maybe? ) on the webserver, and let Vault create a local database. After the install, I can then edit the webconfig file and tell vault to look for the DB on the other machine...
GE
PS> I'm not a DB expert, just playing with it when I have the chance. I wonder if part of the problem is the error "Create Database permission denied in Master". How would I fix that.
Are you using SQL server or MSDE (Query analyzer doesn't come with MSDE)?
So, are you entering "dbserver01.fireangelcorp.local" in the connect to database dialog in the server installer?
But, you would fix this error by making sure that the account you are using to connect to SQL with (in the connect to database dialog) has a db_owner permission for the "master" database (if you have SQL server installed this can be done in Enterprise Manager).
So, are you entering "dbserver01.fireangelcorp.local" in the connect to database dialog in the server installer?
Actually, no. Query Analyzer is separate from VS 2003 and comes with SQL server. But if you can connect from the Vault Server machine with VS 2003 using that information for SQL server then I would think the installer *should* be able to connect also. Are you choosing SQL authentication in the Connect To Database dialog in the installer or Windows Authentication? If the database is on a different machine from the Vault Server you need to choose "SQL authentication" in the connect to database dialog.I assume you when you say "Query Analyzer", you are talking about the "connect to database" in VS 2003...
If you have a sgvault database in SQL already the installer shouldn't be trying to create a new database, so I don't know that this would solve your issue or not because it seems like the installer is connecting to the wrong SQL server instance.I'm not a DB expert, just playing with it when I have the chance. I wonder if part of the problem is the error "Create Database permission denied in Master". How would I fix that.
But, you would fix this error by making sure that the account you are using to connect to SQL with (in the connect to database dialog) has a db_owner permission for the "master" database (if you have SQL server installed this can be done in Enterprise Manager).
Mary Jo Skrobul
SourceGear
SourceGear
I'm using SQL Server 2000. Once I'm confortable, I'll use SQL Server 2005.
I am using dbserver01.fireangelcorp.local as the database in the install. I've also tried dbserver01, and the ip address, with the same results.
I am using WIndows Authentication to connect to the database. I also used WIndows Authentication inside VS 2003. The database is on a different machine.
I'll try to use SQL Authentication. Should I use "sa" as the login??, or should I use the domain user I had set up for this?
The installer tried to create a new one after it can't find the old one ( which is there ). Is there more than one SQL Server Instance?? I thought there could be only one on the machine..
I'll try some more fiddling tommorrow afternoon...
Thanks
GE
I am using dbserver01.fireangelcorp.local as the database in the install. I've also tried dbserver01, and the ip address, with the same results.
I am using WIndows Authentication to connect to the database. I also used WIndows Authentication inside VS 2003. The database is on a different machine.
I'll try to use SQL Authentication. Should I use "sa" as the login??, or should I use the domain user I had set up for this?
The installer tried to create a new one after it can't find the old one ( which is there ). Is there more than one SQL Server Instance?? I thought there could be only one on the machine..
I'll try some more fiddling tommorrow afternoon...
Thanks
GE
In most cases you should use SQL authentication if the SQL server is on a different machine. Use the SA login and password in the Connect to Server dialog so the installer will have the correct permissions to update the database.
You can have more than one named instance of SQL server on the same machine. Is your SQL server a named instance (this would have been set up when you installed SQL server)? If so you should use that name in the Connect to Server dialog instead of the server machine name.
You can have more than one named instance of SQL server on the same machine. Is your SQL server a named instance (this would have been set up when you installed SQL server)? If so you should use that name in the Connect to Server dialog instead of the server machine name.
Mary Jo Skrobul
SourceGear
SourceGear
It Worked!!
Using SA for the database worked.
However... I was always under the impression that SA should never be used.. That is why I had the diff user name to begin with..
Anyway. THANK YOU guys / gals very much. Everything is up and running again
GE
However... I was always under the impression that SA should never be used.. That is why I had the diff user name to begin with..
Anyway. THANK YOU guys / gals very much. Everything is up and running again
GE