Troubleshooting the package installation to a Tier-1 environment by using LCS

Introduction

When you install the package in a Tier-1 environment by using the LCS portal the process should be completed without any issue in 99%. Unfortunately,  there is still 1% when you may experience various issues.

Issue types

Disc space

Before you install the binary package in a Tier-1 environment via LCS portal (Maintain – Apply updates), please make sure that there is enough space on the disk where the folder *\AosService\PackageLocalDirectory is hosted. Usually, it is the "K" drive.

Otherwise, the preparation process can fail and the LCS environment will be in the "Preparation failed" state. If you download the log, it will be empty and the reason for the failure can be unclear.

Visual Studio

If the process fails at the Preparation stage or later and when you download the log it contains the data about preparation steps only, and the file "PreServicing-xxxxxxxxxxxxxxxxxxxx.error" contains only one line:

The specified module 'C:\Program Files\Microsoft Security Client\MpProvider' was not loaded because no valid module file was found in any module directory.

It may mean that a Visual studio instance was open in the environment when you started the process. In this case, you need to log in to the environment via an RDP connection. Then you should close the Visual Studio instance in all user sessions, close your RDP connection, and resume the process.

If you see no open Visual Studio instances in the environment you need to open Visual Studio in your session. Most probably it will install some updates or components behind. You need to keep it open for 5-10 minutes. Then you should close the Visual Studio instance, close your RDP connection, and resume the process.

Maintenance mode

Occasionally, the environment can be in the maintenance mode. In this case, you can face an issue on the step "GlobalUpdate script for service model: AOSService on machine: Machine Name" and the environment will be in the "Failed" state.

In this case, you need to log in to the environment via an RDP connection and check the Services (Control Panel\System and Security\Administrative Tools\Services). If you see that the "Microsoft Dynamics 365 Unified Operations: Batch Management Service" is stopped and it cannot be started it is the root cause of the issue. You need to be able to start this service otherwise you can’t resume the installation process.

In order to find a reason, you need to take a look at the Windows event logs.

If you see there 3 errors in a row it may mean that the environment is in the maintenance mode.

•  The description for Event ID 110 from source Microsoft Dynamics 365 for Finance and 

    Operations cannot be found. Either the component that raises this event is not installed on 

    your local computer or the installation is corrupted. 

    You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the 

    event. The following information was included in the event:

    AX is shutting down due to an error.

    Microsoft.Dynamics.AX.Batch.BatchService+MaintenanceModeBatchStartupException: 

    Exception of type

    'Microsoft.Dynamics.AX.Batch.BatchService+MaintenanceModeBatchStartupException' 

    was thrown.

    at Microsoft.Dynamics.AX.Batch.BatchService.OnStart(String[] args)

    Exception details:

    Microsoft.Dynamics.AX.Batch.BatchService+MaintenanceModeBatchStartupException: 

    Exception of type

    'Microsoft.Dynamics.AX.Batch.BatchService+MaintenanceModeBatchStartupException' 

    was thrown.

    at Microsoft.Dynamics.AX.Batch.BatchService.OnStart(String[] args)

•  Faulting application name: Batch.exe, version: 7.0.7198.49, time stamp: 0xb4453638
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

    Exception code: 0x80131623

    Fault offset: 0x00007ffb9cb54093

    Faulting process id: 0x1508

    Faulting application start time: 0x01da8cdf84d8bc61

    Faulting application path: K:\AosService\WebRoot\bin\Batch.exe

    Faulting module path: unknown

    Report Id: 6054eadb-7058-44e4-966c-fcd600a10af7

    Faulting package full name: 

    Faulting package-relative application ID:

• Application: Batch.exe

   Framework Version: v4.0.30319

   Description: The application requested process termination through       System.Environment.FailFast(string message).

   Message: Tearing the process down due to an unhandled exception.

   Stack:

   at System.Environment.FailFast(System.String, System.Exception)

   at <Module>.FailFast(UInt32, System.String, System.Exception)

   at <Module>.OnAppDomainUnhandledException(System.Object,

   System.UnhandledExceptionEventArgs)

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at System.ServiceProcess.ServiceBase.Run(System.ServiceProcess.ServiceBase[])

   at Microsoft.Dynamics.AX.Batch.Entrypoint.Main(System.String[])

To be on the safe side you can use the standard documentation. You can query data from the "SQLSYSTEMVARIABLES" object and if you see that 'CONFIGURATIONMODE' is 1, the system is in the Maintenance mode.

If it is true you need to revert the environment to the normal state. Then you need to start the "Microsoft Dynamics 365 Unified Operations: Batch Management Service" manually. If it  starts - you fixed the issue. After that, you can close your RDP connection, and resume the process.