# 2941 - Error migrating database after upgrade
**URL:** https://www.finalbuilder.com/forums/t/2941-error-migrating-database-after-upgrade/5892
**Category:** Bugs
**Created:** [February 17, 2014, 1:43am UTC](https://www.finalbuilder.com/forums/t/2941-error-migrating-database-after-upgrade/5892 "2014-02-17T01:43:55Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@skermajo](https://www.finalbuilder.com/forums/u/skermajo)
#### Post date: [February 17, 2014, 1:43am UTC](https://www.finalbuilder.com/forums/t/2941-error-migrating-database-after-upgrade/5892/1 "2014-02-17T01:43:55Z")
Hi
Error below after upgrading to 1.0.0.2941. Obviously, this is preventing us from building at the moment (haven’t tried to downgrade - seemed dangerous to me). We’re running on Postgres as installed by the Continua installer.
Cheers
Joel
Log Name: Application
Source: Continua
Date: 17/02/2014 9:43:15 AM
Event ID: 0
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: BUILD-MASTER.AGData.local
Description:
Could not initialise database:
System.Exception: An error occurred executing the following sql:
ALTER TABLE core\_securityentitygroup ADD CONSTRAINT PK\_core\_securityentitygroup\_securityentityid\_groupid PRIMARY KEY (securityentityid, groupid)
The error was ERROR: 42P16: multiple primary keys for table “core\_securityentitygroup” are not allowed
—\> Npgsql.NpgsqlException: ERROR: 42P16: multiple primary keys for table “core\_securityentitygroup” are not allowed
at Npgsql.NpgsqlState.\d\_\_a.MoveNext()
at Npgsql.ForwardsOnlyDataReader.GetNextResponseObject()
at Npgsql.ForwardsOnlyDataReader.GetNextRowDescription()
at Npgsql.ForwardsOnlyDataReader.NextResult()
at Npgsql.ForwardsOnlyDataReader…ctor(IEnumerable`1 dataEnumeration, CommandBehavior behavior, NpgsqlCommand command, NotificationThreadBlock threadBlock, Boolean synchOnReadError)
at Npgsql.NpgsqlCommand.GetReader(CommandBehavior cb)
at Npgsql.NpgsqlCommand.ExecuteNonQuery()
at FluentMigrator.Runner.Processors.Postgres.PostgresProcessor.Process(String sql)
--- End of inner exception stack trace ---
at FluentMigrator.Runner.Processors.Postgres.PostgresProcessor.Process(String sql)
at FluentMigrator.Runner.MigrationRunner.AnnounceTime(String message, Action action)
at FluentMigrator.Runner.MigrationRunner.ExecuteExpressions(ICollection`1 expressions)
at FluentMigrator.Runner.MigrationRunner.Up(IMigration migration)
at FluentMigrator.Runner.MigrationRunner.ApplyMigrationUp(Int64 version)
at FluentMigrator.Runner.MigrationRunner.MigrateUp(Boolean useAutomaticTransactionManagement)
at FluentMigrator.Runner.Initialization.TaskExecutor.Execute()
at Continua.Migrations.Runner.Execute(String database, String connectionString, String fileName)
at Continua.Server.Service.Migrator.Begin()
Exiting…
Event Xml:
0
2
0
0x80000000000000
4158405
Application
BUILD-MASTER.AGData.local
Could not initialise database:
System.Exception: An error occurred executing the following sql:
ALTER TABLE core\_securityentitygroup ADD CONSTRAINT PK\_core\_securityentitygroup\_securityentityid\_groupid PRIMARY KEY (securityentityid, groupid)
The error was ERROR: 42P16: multiple primary keys for table “core\_securityentitygroup” are not allowed
—> Npgsql.NpgsqlException: ERROR: 42P16: multiple primary keys for table “core\_securityentitygroup” are not allowed
at Npgsql.NpgsqlState.<ProcessBackendResponses\_Ver\_3>d\_\_a.MoveNext()
at Npgsql.ForwardsOnlyDataReader.GetNextResponseObject()
at Npgsql.ForwardsOnlyDataReader.GetNextRowDescription()
at Npgsql.ForwardsOnlyDataReader.NextResult()
at Npgsql.ForwardsOnlyDataReader…ctor(IEnumerable`1 dataEnumeration, CommandBehavior behavior, NpgsqlCommand command, NotificationThreadBlock threadBlock, Boolean synchOnReadError)
at Npgsql.NpgsqlCommand.GetReader(CommandBehavior cb)
at Npgsql.NpgsqlCommand.ExecuteNonQuery()
at FluentMigrator.Runner.Processors.Postgres.PostgresProcessor.Process(String sql)
--- End of inner exception stack trace ---
at FluentMigrator.Runner.Processors.Postgres.PostgresProcessor.Process(String sql)
at FluentMigrator.Runner.MigrationRunner.AnnounceTime(String message, Action action)
at FluentMigrator.Runner.MigrationRunner.ExecuteExpressions(ICollection`1 expressions)
at FluentMigrator.Runner.MigrationRunner.Up(IMigration migration)
at FluentMigrator.Runner.MigrationRunner.ApplyMigrationUp(Int64 version)
at FluentMigrator.Runner.MigrationRunner.MigrateUp(Boolean useAutomaticTransactionManagement)
at FluentMigrator.Runner.Initialization.TaskExecutor.Execute()
at Continua.Migrations.Runner.Execute(String database, String connectionString, String fileName)
at Continua.Server.Service.Migrator.Begin()
Exiting…
\
---
### Author:  [@Sparky](https://www.finalbuilder.com/forums/u/Sparky)
#### Post date: [February 17, 2014, 2:39am UTC](https://www.finalbuilder.com/forums/t/2941-error-migrating-database-after-upgrade/5892/2 "2014-02-17T02:39:15Z")
Hi Joel,
Can you shutdown the continua server service, run the following SQL commands on your postgres database, then restart the server service?
`ALTER` `TABLE` `core_securityentitygroup ``DROP` `CONSTRAINT` `pk_core_securityentitygroup_securityentityid_groupid;`
`ALTER` `TABLE` `core_accesscontrollistentryrole ``DROP` `CONSTRAINT` `pk_core_accesscontrollistentryrole_accesscontrollistentryid_rol;`
The latest build adds primary keys which were missing in previous builds. I’m not sure why you already had them - I’ll investigate
---
### Author:  [@skermajo](https://www.finalbuilder.com/forums/u/skermajo)
#### Post date: [February 17, 2014, 3:11am UTC](https://www.finalbuilder.com/forums/t/2941-error-migrating-database-after-upgrade/5892/3 "2014-02-17T03:11:55Z")
Thanks Dave.
In addition to those two I also had to drop pk\_versioninfo\_version from versioninfo. After doing that everything starts up as expected (and the keys reappeared). Thanks for helping sort it so quickly!
Joel
---
### Author:  [@Sparky](https://www.finalbuilder.com/forums/u/Sparky)
#### Post date: [February 17, 2014, 3:20am UTC](https://www.finalbuilder.com/forums/t/2941-error-migrating-database-after-upgrade/5892/4 "2014-02-17T03:20:50Z")
Hi Joel,
Good to know that its now working. I think your Continua server must have started as an early beta version? The primary keys existed in a beta version 16 months ago but were incorrectly commented out from the migration. We will now update the migration code to check if they exist before creating them.
---
### Author:  [@skermajo](https://www.finalbuilder.com/forums/u/skermajo)
#### Post date: [February 17, 2014, 3:26am UTC](https://www.finalbuilder.com/forums/t/2941-error-migrating-database-after-upgrade/5892/5 "2014-02-17T03:26:40Z")
Thanks Dave. Yes, this server has been around since early betas.