Documente Academic
Documente Profesional
Documente Cultură
Below
is the list of some basic startup problems with solution. I am sure you will be find it very
useful.
Two places you need to check: Event Viewer (Application and System logs) and the SAP
Management Console (MMC). Event Viewer can provide useful information and it may help you
pinpoint where the problem resides. The SAP MMC gives you the ability to visually see the
system status (green, yellow or red lights), view the work processes status and view the
developer traces, which are stored in the "work" directory. Example:
/usr/sap/TST/DVEBMGS00/work.
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:
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), Event Viewer
(EVENTVWR.exe).
Dispatcher Monitor (DPMON.exe), which is located under /usr/sap//sys/exe/run. Database
logs.
Problem Analysis
I highlighted the keywords in the error messages above: Address already in use Service sapdp00
in use The TCP port number assigned in the "services" file is being occupied by another
application. Due to the conflict, the dispatcher shuts down.
Solution
If your server has a firewall client, disable it and attempt to start the SAP instance again.
If the instance starts successfully you can enable the client firewall back again.
If there is no firewall client at all, or if disabling it did not resolve the problem, edit the
"services" file and check what port the appropriate "sapdp" is using.
If the instance number is 00, look for sapdp00. If the instance number is 01 look for sapdp01
and so on. You can use the following OS command to help you resolve port conflicts:
netstat -p TCP There are also utilities on the Internet that can help you list all the TCP and UDP
ports a system is using.
Problem Analysis
A connection to the database could not be established because either the SQL login specified
in parameter "dbs/mss/schema" is set incorrectly or the SQL login was deleted from the
database server. This parameter needs to be set in the DEFAULT.pfl system profile (under
/usr/sap//sys/profile). In the messages above, we see that the SQL login 'tst' is expected but it
does not exist at the database level.
Solution
Set the entry to the appropriate database owner. If the system is based on Basis <= 4.6 or if the
system was upgraded from 4.x to 4.7 the database owner should be "dbo". But, if the system
was installed from scratch and it's based on the Web AS 6.x the database owner should match
the SID name in lower case. Example: if the SID is TST then the database owner should be "tst".
If the parameter is set correctly in the DEFAULT.pfl profile check at the database level if the SQL
login exists. If it doesn't, create it and give it database ownership to the .