none
After 2013 to 2016 migration reporting Database rebuild gives error SqlError: 'The INSERT statement conflicted with the FOREIGN KEY constraint "FK_MSP_LOOKUP_TABLE_STRUCTURES_2_MSP_LOOKUP_TABLES". RRS feed

  • Question

  • Restoring custom fields after a migration of Project server 2013 to 2016 gives the following error on the first step "restore custom fields". 

    SqlError: 'The INSERT statement conflicted with the FOREIGN KEY constraint "FK_MSP_LOOKUP_TABLE_STRUCTURES_2_MSP_LOOKUP_TABLES". The conflict occurred in database "WSS_Content", table "pjpub.MSP_LOOKUP_TABLES".' Source: '.Net SqlClient Data Provider' Number: 547 State: 0 Class: 16 Procedure: 'pjpub.MSP_RESTORE_LOOKUP_TABLE_STRUCTURES' LineNumber: 9

    Run using sharepoint administrator

    Lookup tables were all opened and saved correctly before the rebuild. no errors shown at that stage. 

    If anyone could assist we'd really appreciate it. I can't find anything similar on technet for custom lookups.

    Friday, July 27, 2018 12:34 AM

All replies

  • If i read your problem statement correctly, it reads as though you restored the custom fields.

    Restore the project database from a previous backup.


    Michael Wharton, Project MVP, MBA, PMP and a Great Guy <br/> Website http://www.WhartonComputer.com <br/> Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Saturday, July 28, 2018 2:19 AM
    Moderator
  • Hi Michael

    Yes we restored the custom fields deliberately to trigger a rebuild of the reporting Database. However that rebuild job triggered by the restore of custom fields has failed at the first step of restoring the custom field data. Restoring the original database and retrying the job has just resulted in the same error. We need to determine the cause of the error so we can correct it in this environment. We routinely rebuild the reporting DB in our 2013 Database to correct data for downstream feeds to our data Warehouse. Not being able to do this in the migrated 2016 environment will cause us to have data integrity issues, so is a show stopper for migrating to the new environment. 

    Any guidance on the error source would be very appreciated. 

    thanks & regards

    Paul. 

    Wednesday, August 1, 2018 6:18 AM
  • I would open a support ticket with Microsoft Support and see if they can resolve the inferential integrity issue.

    Michael Wharton, Project MVP, MBA, PMP and a Great Guy <br/> Website http://www.WhartonComputer.com <br/> Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Tuesday, August 14, 2018 1:43 AM
    Moderator