DNN Import Process Failed Due to Foreign Key Constraint "FK_PortalLanguages_PortalLanguages"

Overview

DNN is unable to complete the export-import process with the following ERROR in the stack trace.

2019-03-21 13:38:11.578-05:00 [azscweb-test01][D:3][T:13][ERROR] DotNetNuke.Data.PetaPoco.PetaPocoHelper - [4] Error executing SQL: ;Exec dbo.AddPortalLanguage @0, @1, @2, @3
The INSERT statement conflicted with the FOREIGN KEY constraint "FK_PortalLanguages_PortalLanguages". The conflict occurred in database "<DBName>", table "dbo.Languages", column 'LanguageID'.
The statement has been terminated.
2019-03-21 13:38:11.595-05:00 [azscweb-test01][D:3][T:13][ERROR] DotNetNuke.Services.Exceptions.Exceptions - System.Data.SqlClient.SqlException (0x80131904): The INSERT statement conflicted with the FOREIGN KEY constraint "FK_PortalLanguages_PortalLanguages". The conflict occurred in database "<DBName>", table "dbo.Languages", column 'LanguageID'.
The statement has been terminated.

This article gives a resolution for this error.

 

Environment

DNN 9.x

 

Root Cause

The root cause of the issue is because there is missing language in the destination installation that exists in the exported DNN installation.

 

Resolution

In order to resolve this issue, all the languages that were installed in the source DNN need to be installed in the destination DNN before the import process executed.

Comments

0 comments

Article is closed for comments.