The credentials supplied to the package were not recognized – D365FO on-premises
Applying deployable package on a D365 Finance and Operations environment would not always be a straight journey to light. We are born to overcome errors.
The application of package on Local Business Data a.ka LBD is done in two folds:
- Download of package
- Applying of package
What to do in a case of failure?
In both step. It would be smart to always check the SF explorer and identity the primary orchestrator. That is were you get enough logs about the cause of the failure.
The credentials supplied to the package were not recognized
Here, I did check the primary orchestrator and go the error ”
| Unable to connect to service fabric. Exception : System.Fabric.FabricException: An error occurred during this operation. Please check the trace logs for more details. —> System.Runtime.InteropServices.COMException: The credentials supplied to the package were not recognized (Exception from HRESULT: 0x8009030D) at System.Fabric.Interop.NativeClient.IFabricClientSettings2.SetSecurityCredentials(IntPtr credentials) at System.Fabric.FabricClient.SetSecurityCredentialsInternal(SecurityCredentials credentials) at System.Fabric.Interop.Utility.<>c__DisplayClass28_0.<WrapNativeSyncInvoke>b__0() at System.Fabric.Interop.Utility.WrapNativeSyncInvoke[TResult](Func`1 func, String functionTag, String functionArgs) — End of inner exception stack trace — at System.Fabric.Interop.Utility.WrapNativeSyncInvoke[TResult](Func`1 func, String functionTag, String functionArgs) at System.Fabric.Interop.Utility.RunInMTA(Action action) at System.Fabric.FabricClient.InitializeFabricClient(SecurityCredentials credentialArg, |
“
What to do?
I did ran .\Test-D365FOConfiguration.ps1 on the orch and voila, the VM is in a broken state.
To resolve the error, run the .\Set-CertificateAcls.ps1 script to reset the ACLs.
Re-run .\Test-D365FOConfiguration.ps1 to be sure the error is gone and retry the deployment from LCS.
