Closed git-no closed 2 hours ago
We've found some similar issues:
If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.
Note: You can give me feedback by 👍 or 👎 this comment.
As a test, could you try to set:
$bcContainerHelperConfig.usePwshForBc24 = $false
and then run the command (you can always set it back to true afterwards)
@freddydk Thank you Freddy for the quick response.
After setting $bcContainerHelperConfig.usePwshForBc24 = $false
and creating a new container the command within the container console
Invoke-NAVApplicationDatabaseConversion -DatabaseServer EXTERNAL -Database b -Credential c
breaks with a new error
Access is denied.
+ CategoryInfo : NotSpecified: (:) [Invoke-NAVApplicationDatabaseConversion], CryptographicException
+ FullyQualifiedErrorId : System.Security.Cryptography.CryptographicException,Microsoft.Dynamics.Nav.Management.InvokeNAVApplicationDatabaseConversion
Maybe in BC 24 the connection handling to external database server has changed and a regular PS credential ist not enough anymore.
I checked also the PS version within the container. It is now 5.1.20348.2760.
@freddydk Dear Freddy, I close this ticket. The reason of the issue is not the container helper. Thank you.
Szenario
Convert an external database to the BC version from within the BC container. The BC container console is default Powershell 7.
Issue
Runing the BC command
within the container (BC 24.6 also tested with 24.4) terminal (PS7) breaks with error
Is there an issue with PS7 and Microsoft.Extensions.Logging.ILoggingBuilder version 5.0.0.0?
The database conversion did work till BC 23 / PS5.
Expectation
Microsoft Business Central command
Invoke-NAVApplicationDatabaseConversion
should work within the BC 24.x container.Container Log
Docker version 4.34.2
WinRM config is