16 May 2018

D365 F&O - Debugging in on-premises environments

If you are facing errors in your Dynamics 365 for finance and operations on-prem environment there is currently no real debugging story available. But there is a new article from Tariq Bell on how to debug using WinDbg:

https://blogs.msdn.microsoft.com/axsa/2018/05/16/debug-a-dynamics-365-for-finance-and-operations-on-premises-instance-without-visual-studio/

At least a starting point and a really nice GUI ;)

09 May 2018

D365 F&O Deployment to on-prem failed during download

If the deployment of Dynamics 365 for finance and operations fails after preparing phase when the asset is downloading you should check the logs. If there is a message like the one below just verify that the orchestrator nodes are online and click retry.

MachineName SRV-XYZ
Message Unable to download asset xyzxyzxyzxyzxyzxyz

Detail at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo) at System.Environment.get_StackTrace() at Microsoft.Dynamics.Operations.Local.LocalAgentEvents.LocalAgentEventHelpers.ErrorPrettify(LocalAgentEventSource source, Exception ex, Int32 errorCode, String format, Object[] values) at OrchestrationService.LcsArtifactsProvider.d__10.MoveNext() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Runtime.CompilerServices.AsyncMethodBuilderCore.MoveNextRunner.Run() at System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(Action action, Boolean allowInlining, Task& currentTask) at System.Threading.Tasks.Task.FinishContinuations() at System.Threading.Tasks.Task`1.TrySetResult(TResult result) ...

27 April 2018

D365 F&O financial reporting deployment error - event logs

AX LocalAgent:

Error 1 

Message
Module financialreporting failed
Detail
System.InvalidOperationException: An error was encountered. Details may be found in the deployment logs at 'C:\ProgramData\Microsoft Dynamics ERP\Management Reporter\Logs' System.AggregateException: One or more errors occurred. ---> System.TimeoutException: Operation timed out. ---> System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x80071BFF at System.Fabric.Interop.NativeClient.IFabricApplicationManagementClient10.EndProvisionApplicationType3(IFabricAsyncOperationContext context) at System.Fabric.Interop.Utility.<>c__DisplayClass22_0.b__0(IFabricAsyncOperationContext context) at System.Fabric.Interop.AsyncCallOutAdapter2`1.Finish(IFabricAsyncOperationContext context, Boolean expectedCompletedSynchronously) --- End of inner exception stack trace --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at SetupInfrastructure.ServiceFabricApplicationSetupManager`1.d__24.MoveNext() --- End of inner exception stack trace --- at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification) at Microsoft.Dynamics.Performance.Deployment.FinancialReportingDeployer.Program.DeployApplication(AXConfigurationSettings settings, String packagePath, ApplicationPrincipalUserSettings principalUserSettings) at Microsoft.Dynamics.Performance.Deployment.FinancialReportingDeployer.Program.Setup(ParameterHandler parameterHandler) at Microsoft.Dynamics.Performance.Deployment.FinancialReportingDeployer.Program.Main(String[] args) ---> (Inner Exception #0) System.TimeoutException: Operation timed out. ---> System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x80071BFF at System.Fabric.Interop.NativeClient.IFabricApplicationManagementClient10.EndProvisionApplicationType3(IFabricAsyncOperationContext context) at System.Fabric.Interop.Utility.<>c__DisplayClass22_0.b__0(IFabricAsyncOperationContext context) at System.Fabric.Interop.AsyncCallOutAdapter2`1.Finish(IFabricAsyncOperationContext context, Boolean expectedCompletedSynchronously) --- End of inner exception stack trace --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at SetupInfrastructure.ServiceFabricApplicationSetupManager`1.d__24.MoveNext()<--- args="" assembly="" assemblyfile="" at="" currentfolder="" microsoft.dynamics.performance.deployment.financialreportingdeployer.program.main="" moduleargs="" setupcore.setupmanager.="" setupcore.setupmanager.launchprocessinappdomain="" startupexe="" string="" system.appdomain._nexecuteassembly="" system.appdomain.executeassembly="" tring="" untimeassembly="" workingdir="">c__DisplayClass12_1.b__6()

Error 2

Message
Task OrchestrationService.DeployModulesRunnerTask,OrchestrationService failed for command id 3f3c0269-1c9d-448f-8e89-4e9a019cb8f4
Detail
System.InvalidOperationException: Unable to deploy modules at OrchestrationService.DeployModulesRunnerTask.Run(OrchestratorRunbookResource runbookResource, String commandId, String jobId, String runbookTaskId) at OrchestrationService.OrchestrationJobManager.<>c__DisplayClass14_0.b__4()



26 April 2018

D365 F&O on-premises | deployment failed for application financial reporting alias management reporter

During our installations and code deployments into Dynamics 365 for Finance and Operations on-premises we struggled a lot with one of the last steps of the installation: The financial reporting application. We have seen different issues till now. And there are several things to check when this step fails.

  • Check EventLog of primary orchestrator node for error messages in the local-agent folder.
  • Install ETW-Manisfest on the orchestrator node if not already there to check the MR logs:
    https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/deployment/troubleshoot-on-prem#mr
  • Check the userinfo table of AX DB. There must be a user called FRServiceUser 
  • Check if there are reports still checked out:

    select * from reporting.ControlReport where CheckedOutTo is not null

  •  If yes just update the following tables (on your own risk):
    update Reporting.ControlReport
    set CheckedOutTo = null


    update Reporting.ControlRowMaster
    set CheckedOutTo = null


    update Reporting.ControlColumnMaster
    set CheckedOutTo = null


    update Reporting.ControlTreeMaster
    set CheckedOutTo = null

If all the above is not solving the issue you could also try to replace the financialReporting DB with an empty financialReporting database.

D365 F&O | Workflow editor - Your security settings do not allow this application to be run on your computer

When opening the workflow editor from Dynamics 365 for Finance and Operations you may see an error message saying: "Your security settings do not allow this application to be run on your computer."



This is a security configuration from Windows. Check the registry settings regarding the prompting level for trusted sites and local intranet (Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\Security\TrustManager\PromptingLevel). They should be enabled. If not just change them.


Than you just need to add the D365 F&O url as a trusted site in internet explorer setting. Try again and it should look like this:







15 November 2017

Dynamics 365 Unified Operations Platform Update 11 - failed in step 11

Dynamics 365 Unified Operations Platform Update 11 - failed on a sandbox environment in step 14 with the following error:

Start-Process C:\DynamicsTools\7za.exe -ArgumentList "x J:\DeployablePackages\432bcfed-4a5e-4b32-8e50-4aff2033e323\AOSService\Packages\files\dynamicsax-systemhealth-develop.7.0.4679.35176.zip -oJ:\AosService\PackagesLocalDirectory\SystemHealth -y -mmt" -RedirectStandardOutput C:\DynamicsAX\RunbookExecution-ExecuteParallelRunbook-432bcfed-4a5e-4b32-8e50-4aff2033e323_I0_R0\output\install-AXpackages_11152017093919-dynamicsax-systemhealth-develop.7.0.4679.35176-output.log -RedirectStandardError C:\DynamicsAX\RunbookExecution-ExecuteParallelRunbook-432bcfed-4a5e-4b32-8e50-4aff2033e323_I0_R0\output\install-AXpackages_11152017093919-dynamicsax-systemhealth-develop.7.0.4679.35176-error.log -Wait -WindowStyle Hidden -PassThru
7Zip failed to extract package Bin. At J:\AosService\PackagesLocalDirectory\InstallationRecords\dynamicsax-framework-bin.7.0.4679.35176\tools\installpackage.ps1:38 char:5
+     throw "$($_.Exception.Message)"
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
7Zip failed to extract package Bin. At J:\AosService\PackagesLocalDirectory\InstallationRecords\dynamicsax-framework-bin.7.0.4679.35176\tools\dynamicspackagemanagement.psm1:104 char:9
+         throw "7Zip failed to extract package $packageName."
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



To solve this issue I navigated to
J:\DeployablePackages\432bcfed-4a5e-4b32-8e50-4aff2033e323\AOSService\Packages\files\ and
J:\AosService\PackagesLocalDirectory\SystemHealth and changed properties of these folders. Removed the read only flag and clicked on apply. It will ask for admin rights and if you check again the read only flag is still partely there. A resume of the package deployment worked well.