In our daily routine as basis consultant we are getting many queries and issues with respect to SAP GUI logon like slowness, hanging and connection errors.
The reported error by SAP GUI are too generic in nature and in parallel there can be various reason for the error.
Example 1 : Connection error.
Example 2 : GUI hang.
Hence, In this blog I have tried to provide some initial troubleshooting steps to handle this type of issues.
<NR> = Instance number
Firstly Check SAP GUI logon is Possible?
Option 1 : If answer is No and load balancing is not used then proceed with approach A.
Option 2 : If answer is No and load balancing used then proceed with approach B.
Option 3 : If answer is Yes with approach C.
Approach A :
Check 1: login to OS and check whether dispatcher and work process are running.
Process Name: dw.sap<SID>_DVEBMGS00
Command “ps -eaf | grep dw.sap”
*Use Task Manager on windows.
Check 2: Use sapcontrol to check instance status and should be in green status
Command : “sapcontrol –nr <NR> -functionGetProcessList
Check 3: Dispatcher TCP port is open or not.
Default TCP port 32<NR>
OS level: “netstat -an | grep <port>” on UNIX and “netstat | findstr <port>” on Windows
Check 4: Dispatcher status
OS level “dpmon pf=<instance_profile>” Or “sapcontrol -nr 0 -function ABAPGetWPTable”
Application server is operational if above checks are successful, but the front end can’t connect to the application server. In that case you need check connectivity with application from your local system.
“telnet <APPS hostname> sapdp<NR>”
“niping –c –H <APPS hostname> -S sapdp<NR>”
Approach B :-
Check 1 : Check message server process running or not.
Process name : “ms.sap<SID>_<instance>”
Command : “ps –eaf | grep ms.sap” for UNIX or Task Manager on Windows.
Check 2 : Ports are open or not.
Default : 39<NR>, 81<NR>, 36<NR>
Command : “netstat –an | grep <port>” UNIX or “netstat | findstr <port>” for windows
Check 3 : Check if you are able to remotely connect to the TCP port from your local system to application server
Command : “telnet <MShostname><port>” or “nipping –c –H <MShostname> –S <post>”
Check 4 : Use lgtst to test the output of the service
Command : “lgtst –H <MS hostname> -S sapms<SID>”
Approach C :- In this case we need to check request dispatched and processed by dispatcher or not.
Check 1 : The system may behave as if requests are in hang status. Common cause may be that the dispatcher is not dispatching request to work process.
“dpmon pf=<instance_profile>” OR “sapcontrol –nr <NR> -function GetQueueStatistic”
Check 2 : Transaction: SM51 > Goto > Server Name > Information > Queue Information
There are many possibility if dispatcher is not dispatching request to work process i.e High workload or WP is not free, which we will troubleshoot in my next blog.
Thanks & Regards,