You’re offline. This is a read only version of the page.
25
Hi All,
I have followed the standard documentation (https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/database/dbmovement-scenario-exportuat#import-the-database?) to export UAT db to developer's sandbox but I am facing the issue File contains corrupted data while exporting the db backup from UAT to developer sandbox.
Does anyone familiar with this one?
Thanks,
Hi Zuhad,
There was a discussion in Yammer about the same issue. Try this solution.
Customers have been reporting the .bacpac exported from some environments are unable to be imported on developer boxes. They get an error "File contains corrupted data" when running Sqlpackage.exe.
Root cause: We use .Net Core version of Sqlpackage.exe in our Dynamics-hosted export engine, which has a regression against .Net Standard Sqlpackage.exe. We worked with that team to highlight the issue, and they are fixing it in the .Net Standard version. However, since Microsoft doesn't update SSMS/Sqlpackage on your environments this is surfacing as a breaking change on dev boxes.
If this describes your situation, you can visit docs.microsoft.com/.../sqlpackage-download to download .NET CORE version of Sqlpackage.exe. This is a .zip file that can be extracted to C:\Temp\Sqlpackage-dotnetcore.
From there, instead of using the Sqlpackage.exe under C:\Program Files (x86) they can use the Sqlpackage.exe in C:\Temp\Sqlpackage-dotnetcore.
It is able to better understand the .bacpac file format, as it truly is not corrupted.
Share
Report
All responses (
Answers (
