Replies: 1 comment
-
Thanks for reporting, I created issue #708 to discuss this further. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I"m using latest d365fo.tools (as of Jan 9, 2023) and latest SQLpackage.exe version 16.1.6374.0.
I've done over 50 of these imports over past 3 years, so am familiar with procedure and always have success.
I"ve used different databases going back 3 months.
D365FO version is 10.0.30.. I've even built 10.0.26 servers and pulled databases back from 4 months ago that i've imported before and i still get this error.
I've manually decompressed bacpac files with no errors.
_Error is: PS C:\windows\system32> Import-D365Bacpac -BacpacFile "J:\bacpac\CG_GOLD2.bacpac" -ImportModeTier1 -NewDatabaseName GOLD
[02:07:15][Invoke-Process] Exit code from SqlPackage.exe indicated an error happened. Will output both standard stream and error stream.
[02:07:15][Invoke-Process] Standard output was: \r\n Importing to database 'GOLD' on server 'xxxxxxxxxxxxxx'.
Time elapsed 0:01:05.56
[02:07:15][Invoke-Process] Error output was: \r\n *** Error importing database:Could not load package from 'J:\bacpac\CG_GOLD2.bacpac'.
File contains corrupted data.
WARNING: [02:07:15][Invoke-Process] Stopping because of Exit Code. | Stopping because an Exit Code from SqlPackage.exe wasn't 0 (zero)
like expected.
[02:07:15][Invoke-SqlPackage] The SqlPackage.exe exited with an error.
WARNING: [02:07:15][Invoke-SqlPackage] Stopping because of errors._
Beta Was this translation helpful? Give feedback.
All reactions