The Azure Monitoring Extension for SAP on Windows – Possible Error Codes and Their Solutions

The Azure Enhanced Monitoring Extension for SAP provides configuration information and performance data of the underlying Azure infrastructure and makes it available to the SAP application. It contains built-in self-diagnostics which enables identification of the health and completeness of the infrastructure data required by SAP services and support.

For details on the setup and for possible health checks of the Azure Monitoring infrastructure,  see SAP NetWeaver on Azure Virtual Machines – Deployment Guide  and check SAP Note 1999351 for known issues. For a list of metrics provided in SAP transaction ST06, see SAP Note 2178632.

Having set up the Azure Enhanced Monitoring Extension for SAP, the Windows service AzureEnhancedMonitoring is installed inside the VM and collects all Azure-related data. Afterwards, this data is consumed by SAP Host Agent and by saposcol.exe for further use in the SAP system transaction ST06.

Picture: SAP Azure Monitoring Architecture

SAP Host Agent (e.g. saposcol.exe) and the SAP system consume data of the Azure Enhanced Monitoring service. The Azure Enhanced Enhanced Monitoring service is based on the Azure Monitoring Extension for SAP. The Azure Enhanced  Monitoring Extension for SAP collects data from different sources:

• some local Windows performance and configuration data
• configuration data (config.xml file) stored during setup of the VM
• Azure storage analytics data (used if you use standard storage account for your SAP deployment)
• Windows Azure Diagnostics (WAD) data (by accessing the Azure storage account tables)

As both, the Azure Enhanced Monitoring service and the SAP monitoring are based on the underlying Azure Enhanced Monitoring Extension, issues in the setup of the extension directly lead to an unhealthy status of the Azure Monitoring service as well as of the SAP monitoring.

Identify the Health Status of the Azure Enhanced Monitoring

To check the health status of the Azure Enhanced Monitoring service, log on to the VM and proceed as follows:

1. Open the Windows services and select the service ‘AzureEnhancedMonitoring’.

2. Right-click on the service name and choose ‘Properties’. In the upcoming window, check for the field ‘Path to executable’ (this field points to the installation folder of the Azure Monitoring Extension). This path is similar to
   ‘C:\Packages\Plugins\Microsoft.AzureCAT.AzureEnhancedMonitoring.AzureCATExtensionHandler\<version>\drop’ , where version indicates the current version of the extension.

3. Open a command prompt and switch to the installation folder indicated above.
   In this folder, you can find the command line tool azperflib.exe which enables testing of the monitoring information provided by the Azure extension and its health status.

4. Execute ‘azperflib.exe’.Note: Azperflib.exe runs in a loop and updates the collected counters every 60 seconds. In order to finish the loop, you need to close the command window.

5. Pay attention to the summary metrics ‘Health status’ and ‘Diagnostics’, which are shown at the end of each loop of azperflib.exe:Health status: OK
   Diagnostics: OK

   The Health status is either OK or Failed:
   - If the Health status is ‘OK’, there is nothing more to do.
   - If the Health status is ‘Failed’, the field ‘Diagnostics’ contains further details on the root causes of the health issues.

   Note: These root causes might be related to accessibility issues to WAD or to the storage accounts used, to misconfigurations or changes in configuration of the VM after execution of the setup script.

   Use the Error IDs indicated in the ‘Diagnostics’ metric and follow up with their solutions provided in the table below.

6. Repeat steps 4 and 5 until azperflib.exe reports the ‘Health status’ ‘OK’.

7. As the health status of the SAP Monitoring is directly influenced by the health status of the Azure extension, a healthy status of the Azure Enhanced Monitoring is always reflected in a healthy status of the SAP monitoring.

Error Codes of the Azure Extension and Their Interpretation

Detailed Guidelines on Solutions Provided