DB Upgrade of Vault 3.1 to 4.1.2 failed.

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
mschoenholzer
Posts: 6
Joined: Wed Sep 10, 2008 3:49 am

DB Upgrade of Vault 3.1 to 4.1.2 failed.

Post by mschoenholzer » Tue Sep 16, 2008 9:35 am

Dear Vault Team.
Unfortunateley the Installer was unable to migrate the Vault Database.
Plz see the Log attached.
Any hints how to fix it?

Thanks. Regards Martin

Log:
--------------------------------------------------
Looking for IIS Version
Configuring your new Vault Installation
Requesting the IIS Process User...Requesting Vault Admin user password...OK
Connecting to the SQL Server...OK
Verifying the SQL Server requirements...OK
Checking for an existing databases...Found.
Asking for database's fate...Keep existing.
Upgrading the existing source control database...
This may take a long time. Do NOT stop this process!
Checking the installed database version...OK
Ensuring that sgvaultuser has access to the database... Grant database access to sgvaultuser...OK
Upgrading SourceGear master database schema...OK
Upgrading SourceGear source control database schema...Verletzung der PRIMARY KEY-Einschränkung 'pk_serialnumbers'. Ein doppelter Schlüssel kann in das 'dbo.serialnumbers'-Objekt nicht eingefügt werden.
Verletzung der PRIMARY KEY-Einschränkung 'pk_groups'. Ein doppelter Schlüssel kann in das 'dbo.groups'-Objekt nicht eingefügt werden.
Verletzung der PRIMARY KEY-Einschränkung 'pk_users'. Ein doppelter Schlüssel kann in das 'dbo.users'-Objekt nicht eingefügt werden.
Verletzung der PRIMARY KEY-Einschränkung 'pk_groupmembers'. Ein doppelter Schlüssel kann in das 'dbo.groupmembers'-Objekt nicht eingefügt werden.
Dropping extended properties
Dropping foreign keys from [dbo].[tblgroupmembers]
Dropping foreign keys from [dbo].[tblcheckoutlistitems]
Dropping foreign keys from [dbo].[tblfsobjectlabelchanges]
Dropping foreign keys from [dbo].[tbldelayusersecuritychanges]
Dropping foreign keys from [dbo].[tblusersecuritychanges]
Dropping foreign keys from [dbo].[tblsessions]
Dropping foreign keys from [dbo].[tblsessionlabelqueries]
Dropping foreign keys from [dbo].[tblsessionbranchsandbox]
Dropping foreign keys from [dbo].[tblclientoptions]
Dropping foreign keys from [dbo].[tbluserrepositories]
Dropping foreign keys from [dbo].[tblloginattempts]
Dropping foreign keys from [dbo].[tblfsobjectlabels]
Dropping foreign keys from [dbo].[tbltransactions]
Dropping foreign keys from [dbo].[tblhistoryfavorites]
Dropping foreign keys from [dbo].[tblsessionrecursivelabelqueries]
Dropping foreign keys from [dbo].[tblsessionfolderexports]
Dropping foreign keys from [dbo].[tblcloaks]
Dropping foreign keys from [dbo].[tblwatchers]
Dropping constraints from [dbo].[tblusers]
Dropping constraints from [dbo].[tblusers]
Dropping constraints from [dbo].[tblusers]
Dropping constraints from [dbo].[tblusers]
Dropping constraints from [dbo].[tblusers]
Dropping constraints from [dbo].[tblusers]
Dropping constraints from [dbo].[tblgroupmembers]
Dropping constraints from [dbo].[tblgroups]
Dropping constraints from [dbo].[tblgroups]
Dropping constraints from [dbo].[tblloginattempts]
Dropping constraints from [dbo].[tblsessions]
Dropping index [idxuserlogins] from [dbo].[tblusers]
Dropping index [idxsessionsuserid] from [dbo].[tblsessions]
Dropping [dbo].[spcleansessions]
Dropping [dbo].[spdeletesession]
Dropping [dbo].[spaddsession]
Dropping [dbo].[splogin]
Dropping [dbo].[spgetlogininfo]
Dropping [dbo].[spdeletelicensekey]
Dropping [dbo].[spdeleteserialnum]
Dropping [dbo].[spaddserialnum]
Dropping [dbo].[spgetserialnums]
Dropping [dbo].[spcleanloginattempts]
Dropping [dbo].[spchangepassword]
Dropping [dbo].[spgetgroupmembers]
Dropping [dbo].[spgetgroups]
Dropping [dbo].[spdeletegroupmembers]
Dropping [dbo].[spaddgroupmember]
Dropping [dbo].[speditgroup]
Dropping [dbo].[spaddgroup]
Dropping [dbo].[tbllicensekeys]
Die Anweisung wurde beendet.
Dropping [dbo].[tblloginattempts]
Dropping [dbo].[tblsessions]
Dropping [dbo].[tblgroups]
Die Anweisung wurde beendet.
Dropping [dbo].[tblgroupmembers]
Die Anweisung wurde beendet.
Die Anweisung wurde beendet.
Rebuilding [dbo].[tblusers]
Vorsicht: Wenn Sie Teile eines Objektnamens ändern, werden Skripts und gespeicherte Prozeduren möglicherweise funktionsunfähig.
Creating primary key [pk_tblusers] on [dbo].[tblusers]
Adding constraints to [dbo].[tblusers]
Adding foreign keys to [dbo].[tbluserrepositories]
Adding foreign keys to [dbo].[tblusersecuritychanges]
Adding foreign keys to [dbo].[tblfsobjectlabels]
Adding foreign keys to [dbo].[tblclientoptions]
Adding foreign keys to [dbo].[tblhistoryfavorites]
Adding foreign keys to [dbo].[tblwatchers]
Adding foreign keys to [dbo].[tblcloaks]
Adding foreign keys to [dbo].[tbldelayusersecuritychanges]
Adding foreign keys to [dbo].[tblfsobjectlabelchanges]
Adding foreign keys to [dbo].[tbltransactions]
Adding foreign keys to [dbo].[tblcheckoutlistitems]
The database update failed
Error during Vault upgrade script.
Vault Setup is exiting due to a failure or cancellation. Error Code = -1280

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: DB Upgrade of Vault 3.1 to 4.1.2 failed.

Post by Beth » Tue Sep 16, 2008 1:27 pm

Were you upgrading from Vault 3.1.9 or some other 3.1.x version?

Is the information you posted from the first install or have you tried to install multiple times? If you tried to install multiple times, then the previous attempt may have not been cleaned up. You would need to delete the sgmaster database and restore a fresh backup of your old database to run the upgrade again.
Beth Kieler
SourceGear Technical Support

mschoenholzer
Posts: 6
Joined: Wed Sep 10, 2008 3:49 am

Re: DB Upgrade of Vault 3.1 to 4.1.2 failed.

Post by mschoenholzer » Wed Sep 17, 2008 1:56 am

Hi Beth.
I'm Upgrading from 3.1.9.3798.
It's was the first attempt.
I restored sgVault and sgMaster now.
What to do now?

Regards Martin

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: DB Upgrade of Vault 3.1 to 4.1.2 failed.

Post by Beth » Wed Sep 17, 2008 7:47 am

Vault 3.1.9 does not have an sgmaster. You actually don't want that there. If you're concerned, rename it to something else. All you want to restore is the original Vault 3.1.9 database and then install. If that install fails then the first time, then post the errors. The error you have means that it sees an sgmaster.
Beth Kieler
SourceGear Technical Support

mschoenholzer
Posts: 6
Joined: Wed Sep 10, 2008 3:49 am

Re: DB Upgrade of Vault 3.1 to 4.1.2 failed.

Post by mschoenholzer » Wed Sep 17, 2008 9:39 am

Hi Beth.
Thanks for your input.
Ok i restored the original Vault 3.1.9 database, removed sgmaster and it's files on the harddrive.
Now the installer seems to lock itself out.

Before i run the setup the sgvault db is in multiusermode, i checked explicitly.
Then Installer fails and complains that sgvault in singleuser mode and can only have one user.
i checked again and sgvault is in single user...
then i checked sql activity log, the only process connected is the installer itself.

I kicked the connection from sgvault, set back to multiusermode and restored db.
Tried again, same error.
How could i resolve that?

Log:
-----------------------------------------------------------------------------------------------
Looking for IIS Version
Configuring your new Vault Installation
Requesting the IIS Process User...Requesting Vault Admin user password...OK
Connecting to the SQL Server...OK
Verifying the SQL Server requirements...OK
Checking for an existing databases...Found.
Asking for database's fate...Keep existing.
Upgrading the existing source control database...
This may take a long time. Do NOT stop this process!
Checking the installed database version...OK
Creating SourceGear master database schema...OK
Ensuring that sgvaultuser has access to the database... Grant database access to sgvaultuser...OK
Upgrading SourceGear master database schema...OK
Upgrading SourceGear source control database schema...Die 'sgvault'-Datenbank ist bereits geöffnet und kann jeweils nur einen Benutzer haben.
Vault Setup is exiting due to a failure or cancellation. Error Code = -1280

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: DB Upgrade of Vault 3.1 to 4.1.2 failed.

Post by Beth » Wed Sep 17, 2008 1:00 pm

It still looks like something from sgmaster is hanging around. Could you send an email to support at sourcegear.com with a link to this thread?
HS: 213506
Beth Kieler
SourceGear Technical Support

mschoenholzer
Posts: 6
Joined: Wed Sep 10, 2008 3:49 am

Re: DB Upgrade of Vault 3.1 to 4.1.2 failed.

Post by mschoenholzer » Thu Sep 18, 2008 1:19 am

Ok, done that.

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: DB Upgrade of Vault 3.1 to 4.1.2 failed.

Post by Beth » Wed Oct 01, 2008 9:07 am

Received. Discussion in progress offline.

HS: 213506
Beth Kieler
SourceGear Technical Support

Post Reply