Vault Server 2014 to 2015 database migration fails

[OutFrontPS]

Doing a "dry run" test (a cloned VM) of migrating our vault to 2015. This is our standard procedure we've been doing for many years with much success.

The 2014 to 2015 upgrade however, is giving us grief. After the install, the first time you open ADMS Console it of course migrates/upgrades the databases. When it attempts to do our database - it fails with the error:

"The Delete Statement Conflicted with a reference constraint"

See full error attached in picture below. I've tried twice now (2 separate clones) and the problem happened both times. Obviously we're going to hold off upgrading the production system until we know how to get by this problem.

Any thoughts/help would be appreciated!

[OutFrontPS]

It seems very similiar to the issue outlined here:

http://knowledge.autodesk.com/sites/default/files/file_downloads/ts1101007_readme.txt

But that's a hotfix for 2009 - even though it fairly accurately describes our problem

[OutFrontPS]

Here's the full error out of the console log.

Connectivity.Application.VaultManager.ServiceException: The DELETE statement conflicted with the REFERENCE constraint "FK_ItemToComp_ComponentIterationID". The conflict occurred in database "ACPS_MANU", table "dbo.ItemToComp", column 'ComponentIterationID'.
Cannot insert duplicate key row in object 'dbo.BOMComponent' with unique index 'IX_BOMComponent_1'. The duplicate key value is (4549, 7F487859-42AF-D311-E358-56BF4DD47FAC).
The statement has been terminated.
The statement has been terminated. ---> System.Data.SqlClient.SqlException: The DELETE statement conflicted with the REFERENCE constraint "FK_ItemToComp_ComponentIterationID". The conflict occurred in database "ACPS_MANU", table "dbo.ItemToComp", column 'ComponentIterationID'.
Cannot insert duplicate key row in object 'dbo.BOMComponent' with unique index 'IX_BOMComponent_1'. The duplicate key value is (4549, 7F487859-42AF-D311-E358-56BF4DD47FAC).
The statement has been terminated.
The statement has been terminated.
   at Connectivity.Core.Database.TransactionContext.OnSqlException(SqlException e)
   at Connectivity.Core.Database.SqlAccess.ExecuteNonQueryInternal(SqlCommand cmd)
   at Connectivity.Core.Database.SqlAccess.ExecuteNonQuery(CommandType commandType, String[] commandText, Int32 commandTimeout, SqlParameter[] commandParameters)
   at Connectivity.Core.Database.SQLScript.ProcessBatches(LocalWorkgroupContext context, String[] batches, Int32 commandTimeout, SqlParameter[] parameters)
   at Connectivity.Core.Database.SQLScript.ExecuteScriptString(String script, Int32 commandTimeout, SqlParameter[] parameters)
   at Connectivity.Core.Operations.Migrate.ExecuteTransactedMigration(Migration currentmigration)
   at Connectivity.Core.Operations.Migrate.Execute()
   at Connectivity.Core.Services.KnowledgeVaultService.MigrateKnowledgeVault(String vaultName, OnProgressDelegate onProgress)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)
   --- End of inner exception stack trace ---
   at Connectivity.Application.VaultManager.ProgressCommand.Execute()
   at Connectivity.Application.VaultManager.MigrateAllCommand.MigrateVaults(LoginInfo dbLogin)
26/05/2014 6:00:24 PM Migration of 'ACPS_MANU' failed: The DELETE statement conflicted with the REFERENCE constraint "FK_ItemToComp_ComponentIterationID". The conflict occurred in database "ACPS_MANU", table "dbo.ItemToComp", column 'ComponentIterationID'.
Cannot insert duplicate key row in object 'dbo.BOMComponent' with unique index 'IX_BOMComponent_1'. The duplicate key value is (4549, 7F487859-42AF-D311-E358-56BF4DD47FAC).
The statement has been terminated.

[johannes.bauer · Accepted solution]

Hello Riese,

thanks for engaging with Autodesk in the forums.

For this kind of issue it is the best to open a support case in subscription center for product support to help you.

Thanks!

[kolesaa]

Hi rise.

I have the same problem, create a case (09700321 Link), but Autodesk is silent. How did you solve the problem?

Thank.

[david_j2_myers]

Similar error here as well.  Case submitted  on 7/7/2014 (09770639).  Escalated to development for resolution. No resolution as of 7/18.

[michael.strange]

Same issue here. Any fix yet?

[michael.strange]

Case # 09910479.  Is there a fix for this??!!??

[OutFrontPS]

Hi,
Autodesk looked at our data set after we opened a support ticket and wrote a script to fix it.
After that the migration went OK.

Best Regards,

Riese Heemskerk
Out Front Portable Solutions
905-563-9790 ext:234
1-800-282-1239
riese@outfrontps.com



--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

[Maxim-CADman77]

In our case after two months of (not sure what we were waiting) Autodesk
suggested remote session.

AFAIK they found some cyclic dependency in one of SQL tables.

After removing some raw the migration was successful.

[per_jonsson]

Hi

Migration from 2014 to 2015 ended with the same issue. Where can we find the database script mentioned in this thread?

/Regards Per Jonsson

[per_jonsson]

Hi

I found the solution. Download DM1904923 from Autodesk and do an upgrade.

/Regards, Per Jonsson