This blog describes how you can start/stop clustered SAP instances in a Windows Failover cluster environment. It also describes how the SAP HA interface behaves from an end user / administrator perspective. Clustered SAP instances can contain: an ASCS instance (message server, enqueue server, optional: gateway and/or Web Dispatcher) for an ABAP system or a....
This blog shows how to find TCP ports used or reserved by applications on Windows. It is not related to specific SAP applications. Problem: An application cannot start, because the port it wants to use, is in use by another application (or components of the operating system). How can we found out which application uses....
This blogs explains the communication between Dispatcher of an ABAP application server instance to the Message server of the central ASCS instance. Many customers want to use additional hostnames on Windows to separate SAP TCP/IP communication from other traffic. This blog shows how to configure this. The following picture shows the communication of an ABAP....
The SAPonWin Check Tool (SCT) collects configuration and logging data from a Windows Server host. Based on the collected information, the SAPonWin Check Tool validates your configuration and checks for common misconfigurations, for example: Operating System: Operating System Version, Windows Service Start-up types, Permissions for file System objects and network shares, etc. Network configuration: Forward/Backward Name Resolution of....
This blog discusses the new features of SAP’s cluster resource DLL for the Windows Failover cluster. Version 4.0.0.18 has been released in July 2022. For more information where to download this DLL and how to update it, please see SAP note 1596496. You find saprc.dll in c:windowssystem32 folder: New feature central operations log You find....
This blog describes the steps how to move a clustered SAP (A)SCS instance from one Windows domain (= Active Directory) to another. The procedure to recreate the Failover cluster and the SAP related resources, can be also used in disaster/emergency situations, for example, if both cluster nodes are lost. In such situations create a new....
Over the time, the Windows Failover Cluster logs grow and grow and consume up to several GBytes on the system disk (C: by default) of the cluster nodes. In general, it is a good idea to create a backup of the cluster logs and clear the cluster logs on all cluster nodes afterwards, for example,....
This blog explains how to move an existing SAPMNT share from one location to another. It can be used in Failover cluster configurations, distributed environments or even on standard installations, if you want to change the hostname used for “SAPGLOBALHOST”. Example: Your SAP system uses a SAPMNT share on host “old”. The profile parameter SAPGLOBALHOST....
During support situations for SAP NetWeaver or S/4 HANA based systems, you might often be asked to upgrade the executables of your system (often called “SAP kernel”) to a current release. But which version is running in your system? Here are several methods to determine the version of an SAP executable: 1. Using SAPMMC 2.....
This blog discusses the installation and configuration of SAP NetWeaver or S/4 HANA in a Windows Failover cluster, which cluster nodes are located in different subnets. The configuration of the cluster, the configuration of network related things like dynamic DNS synchronisation, DNS server synchronisation, Windows OS configuration, etc. are mandatory for operations of SAP NetWeaver....