bacpac Import failed from LCS into local Dev Box

(5) Share

Report

Posted on by D356FO_Dev

144

Hi,

We have made multiple attempts to import a new .bacpac file from LCS into our local development environment; however, each attempt has failed with consistent results. The import process fails due to corruption in the .bacpac file.
Although, as mentioned above we created each time new export in LCS.

Additionally, we attempted to perform the import using PowerShell, but that approach was unsuccessful as well.

Note: Both the source and target environments are on the same Platform Update (PU).

We would appreciate any guidance or a recommended solution to resolve this issue.

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (7)

Answers (1)

Martin Dráb 239,022 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Do you have the latests versions of SSMS and SqlPackage?

Can you please elaborate your statement "that approach was unsuccessful as well"? Did you get the same error or was it unsuccessful for another reason?

Was this reply helpful? Yes No
D356FO_Dev 144 on at

Like (1)

Report
Copy link

Link copied!

Hi Martin,

Thanks for responding quickly.
Yes SSMS and sql package are upto date.

This is the error with powershell approach:
[Invoke-Process] Error output was: \r\n *** Error importing database:Could not import package.
Error SQL72014: Core Microsoft SqlClient Data Provider: Msg 4630, Level 16, State 1, Line 1 The permission 'KILL DATABASE CONNECTION' is not supported in this version of SQL Server. Alternatively, use the server level 'ALTER ANY CONNECTION' permission.
Error SQL72045: Script execution error. The executed script:
GRANT KILL DATABASE CONNECTION TO [ms_uno_dev_writer];

Was this reply helpful? Yes No
Suggested answer

Martin Dráb 239,022 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

The problem with 'KILL DATABASE CONNECTION' is well-known. You can use Repair-D365BacpacModelFile from d365.tools, for instance, to fix the file.

Was this reply helpful? Yes No
D356FO_Dev 144 on at

Like (1)

Report
Copy link

Link copied!

I use the following commands
C:\> Repair-D365BacpacModelFile -Path C:\Temp\repair\testbackup\model.xml -KeepFiles -Force
Removed the original model.xml and renamed model-edited.xml back to model.xml.

After that, I compressed the folder contents into a ZIP archive and changed the file extension back to .bacpac.

However, during the import process, I encountered the following error:

origin.xml not found

I’ve verified that the origin.xml file is indeed present in the root of the folder before compression. It appears the import process is still failing to detect it.

Looking forward..

@Martin Dráb

Was this reply helpful? Yes No
Verified answer

Martin Dráb 239,022 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

I haven't dealt with this problem by myself, but there are resources to consult. Fix "The permission 'KILL DATABASE CONNECTION' is not supported in this version of SQL Server" while importing a D365FO .bacpac mentions that a new checksum would have to be calculated and that it can be address by using /mfp parameter, rather then trying to update the package manually. Give it a try.

Was this reply helpful? Yes No
DN-27070130-0 61 on at

Like (1)

Report
Copy link

Link copied!

Hi,

Anyone have success for restore .bacpac file to Local Dev?
I already try using /mfp to using custom model.xml but the error still same, like the sqlpackage still using model.xml from .bacpac

How to make a new calculated checksum after I modified model.xml??

Was this reply helpful? Yes No
Martin Dráb 239,022 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

You seem to suggest that the .bacpac doesn't contain the modified file, which means that you skipped the step "Then copy and replace the modified model.xml into the zipped package and change the package file extension from .zip to .bacpac".

Was this reply helpful? Yes No