1)What are the things to keep in mind when you SAP startup problems in Windows?
Developer Traces:
-- dev_disp Dispatcher developer trace
-- dev_ms Message Server developer trace
-- dev_wp0 Work process 0 developer trace
The "services" file, which contains TCP and UDP services and their respective port numbers. This plain-text configuration file is located under %winnt%/system32/drivers/etc.
Windows Task Manager (TASKMGR.exe).
Dispatcher Monitor (DPMON.exe), which is located under /usr/sap//sys/exe/run.
Database logs.
EventViewer (EVENTVWR.exe).
For a central SAP instance to start successfully, both the message server and the dispatcher need to start. If one of them or both fail to start, users cannot log in to the system. The following scenarios will illustrate possible causes of why an SAP instance might not start and the reason of the message:
"*** DISPATCHER EMERGENCY SHUTDOWN ***".
2)What would you do when the dispatcher would not start due to port conflict? What are the symptoms for the same?
The symptoms in a windows environment might be
No work processes (disp+work.exe) exist in Task Manager.
Dispatcher shows status "stopped" in the SAP MMC.
Errors found in "dev_disp":
Developer Traces:
-- dev_disp Dispatcher developer trace
-- dev_ms Message Server developer trace
-- dev_wp0 Work process 0 developer trace
The "services" file, which contains TCP and UDP services and their respective port numbers. This plain-text configuration file is located under %winnt%/system32/drivers/etc.
Windows Task Manager (TASKMGR.exe).
Dispatcher Monitor (DPMON.exe), which is located under /usr/sap/
Database logs.
EventViewer (EVENTVWR.exe).
For a central SAP instance to start successfully, both the message server and the dispatcher need to start. If one of them or both fail to start, users cannot log in to the system. The following scenarios will illustrate possible causes of why an SAP instance might not start and the reason of the message:
"*** DISPATCHER EMERGENCY SHUTDOWN ***".
2)What would you do when the dispatcher would not start due to port conflict? What are the symptoms for the same?
The symptoms in a windows environment might be
No work processes (disp+work.exe) exist in Task Manager.
Dispatcher shows status "stopped" in the SAP MMC.
Errors found in "dev_disp":
Confused? Feel free to ask
Your feedback is always appreciated.I will try to reply Ur queries as soon as time allows.
Regards,
SAPhelpdesk
0 comments:
Post a Comment