SAP Production Incident – Troubleshooting SAP Router, APP Dispatcher, and HANA Dependency Failure

Introduction

Recently I handled an SAP Production incident where users were suddenly unable to access critical SAP production services including SAP GUI

At first glance the issue looked like a network or firewall problem because users received a connection refused error when trying to connect to the SAP environment.

However, after tracing the entire SAP landscape step-by-step, the actual issue turned out to be a startup dependency problem involving:

• SAP Router
• SAP Application Dispatcher
• SAP HANA Database
• Web Dispatcher backend connectivity

This article shares the troubleshooting process from infrastructure level until application recovery.

Note: Hostnames, IP addresses, SID names, and environment details have been anonymized for confidentiality.

Environment Overview

The SAP production landscape consisted of several separate virtual machines:

Architecture flow:

Initial Symptoms

Users reported:

SAP GUI error:

At this stage there were several possible causes:

• Firewall issue
• NAT issue
• SAP Router down
• Dispatcher down
• Database issue
• SAP service startup failure

Step 1 – Validate Network Connectivity

Initial external validation was performed using:

Result:

Interesting finding:

This usually means:

Step 2 – SAP Router Investigation

SAP Router port:

was confirmed not listening.

Further inspection on the SAP Router VM revealed that SAP Router was started manually using:

It was not configured as a proper persistent service.

Additional discovery:

The startup script previously used an incorrect parameter:

instead of:

After correcting and starting the service manually:

Result:

SAP Router connectivity was restored successfully.

Step 3 – SAP APP Instance Investigation

Next, SAP instance status was checked:

Initial status:

Instance 31

Instance 30

Port validation:

This explained the SAP GUI connection refusal.

Step 4 – Recover SAP Central Services

Instance 31 was started first:

Result:

However, instance 30 still failed to become healthy.

Step 5 – Dispatcher Failure Analysis

Dispatcher logs were analyzed:

Important logs:

Critical error found:

Multiple work processes terminated unexpectedly.

At this point the investigation shifted toward database dependency.

Step 6 – HANA Database Investigation

HANA status check:

Result:

Important HANA services such as:

• nameserver
• indexserver
• xsengine

were unavailable.

This explained why:

The SAP dispatcher depended on HANA connectivity.

Step 7 – Start HANA Database

Database services were started manually:

After startup:

Ports became available again.

Step 8 – Recover SAP APP Instance

After HANA became healthy:

Result:

Port validation:

SAP GUI connectivity was restored.

Step 9 – Verify Web Dispatcher

Web Dispatcher status:

Initially:

Later:

Backend connectivity recovered automatically after APP and HANA services became available.

Web application login page became accessible again.

Root Cause Analysis

The incident was ultimately caused by:

Affected components:

• SAP Router service
• SAP HANA Database services
• SAP APP dispatcher dependency chain

Impact chain:

Key Lessons Learned

1. Open SAPControl Port Does Not Mean SAP Is Healthy

Ports like:

may still be reachable even when SAP applications are completely down.

Because:

2. SAP Startup Dependency Order Matters

Correct startup sequence:

If APP starts before HANA:

3. SAP Router Should Use Proper Service Management

Running SAP Router manually from shell sessions is risky.

Better approach:

• systemd service
• persistent startup
• automatic recovery

4. Dispatcher Logs Are Extremely Important

The key clue came from:

which clearly showed:

without that log analysis, troubleshooting could easily remain focused on networking instead of backend dependencies.

Final Status

All SAP services recovered successfully:

Conclusion

This incident demonstrated how SAP outages can initially look like simple network issues while the real root cause actually exists deep in service dependency chains.

The troubleshooting flow that worked best was:

In complex SAP environments, understanding the startup relationship between routing services, application dispatcher services, web dispatcher services, and backend databases is critical for fast recovery and accurate root cause analysis.