We were trying to start the SAP java Instance, but the Java Instance was not coming up even after 2

hour. Its status was starting application in Server0.

We increased the heap menory to 2GB, still the issue persisted.

After some 1 hour we saw that the /sapmnt mount point was 100% full, once we created free space,

the Java came Up in 2 min  

During instance startup, dispatcher and all the server nodes get restarted again and again with the

error message "Configuration Manager Returned False! Kernel Not Loaded. System Halted"

If the above mentioned error message is recorded in std_server0, then look at the respective default

trace file for further hints.  In our case, we could see an error message "Error Occurred: Secure Store

Lib Dir Does Not Exist", since we performed a system copy from one system to the other, we missed

to change the configurations in configuration manager to point the secure store lib directories to the

correct path.

You can make the necessary changes using

Config Tool -> Instance -> Dispatcher/Server Node - >  Manager - > Configuration Manager

Make sure that a valid path is given for secstorefs.keyfile, secstorefs.lib and secstorefs.secfile

parameters, this should resolve the issue.

Please note that you will not be able to make the above change under global dispatcher/server

configuration, hence you need to set it for all the server/dispatcher nodes.

Two places you need to check: EventViewer (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 theability 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 failto start, users cannot log in to the system. The following scenarios will illustrate possible causes of why an SAP instance might notstart and the reason of the message:"DISPATCHER EMERGENCY SHUTDOWN ".Developer Traces:dev_disp Dispatcher developer tracedev_ms Message Server developer tracedev_wp0 Work process 0 developer traceThe "services" file, which contains TCP and UDP services and their respective port numbers. This plain-text configuration file islocated 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.

1. Dispatcher does not start due to a port conflict No work processes (disp+work.exe) exist in Task Manager.Dispatcher shows status "stopped" in the SAP MMC.Errors found in "dev_disp":LOG Q0I=> NiPBind: bind (10048: WSAEADDRINUSE: Address already in use) [ninti.c 1488]*** ERROR => NiIBind: service sapdp00 in use [nixxi.c 3936]*** ERROR => NiIDgBind: NiBind (rc=-4) [nixxi.c 3505]*** ERROR => DpCommInit: NiDgBind [dpxxdisp.c 7326]*** DP_FATAL_ERROR => DpSapEnvInit: DpCommInit*** DISPATCHER EMERGENCY SHUTDOWN ***Problem AnalysisI highlighted the keywords in the error messages above: Address already in use Service sapdp00 in use The TCP port numberassigned in the "services" file is being occupied by another application. Due to the conflict, the dispatcher shuts down.Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.ProfProjects.com | Page 1/4 |This page was exported from - SAP ADMINExport date: Tue Nov 6 7:04:24 2012 / +0000 GMTSolutionIf 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 theappropriate "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 followingOS 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.

2: Dispatcher dies due to a database connection problem No database connections.No work processesSAP MMC -> WP Table shows all processes as "ended".Errors found in "dev_disp":C setuser 'tst' failed -- connect terminatedC failed to establish conn. 0M ***LOG R19=> tskh_init, db_connect (DB-Connect 000256) [thxxhead.c 1102]M in_ThErrHandle: 1M *** ERROR => tskh_init: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 8437]*** ERROR => W0 (pid 2460) died [dpxxdisp.c 11651]

*** ERROR => W1 (pid 2468) died [dpxxdisp.c 11651]*** ERROR => W2 (pid 2476) died [dpxxdisp.c 11651]. . .*** ERROR => W11 (pid 2552) died [dpxxdisp.c 11651]*** ERROR => W12 (pid 2592) died [dpxxdisp.c 11651]my types changed after wp death/restart 0xbf --> 0x80*** DP_FATAL_ERROR => DpEnvCheck: no more work processes*** DISPATCHER EMERGENCY SHUTDOWN ***DpModState: change server state from STARTING to SHUTDOWNProblem AnalysisA connection to the database could not be established because either the SQL login specified in parameter "dbs/mss/schema" is setincorrectly or the SQL login was deleted from the database server. This parameter needs to be set in the DEFAULT.pfl systemprofile (under /usr/sap//sys/profile). In the messages above, we see that the SQL login 'tst' is expected but it does not exist at thedatabase level.SolutionSet the entry to the appropriate database owner. If the system is based on Basis

3: SAP does not start at all: no message server and no dispatcher The message server and the dispatcher do not start at all in the SAP MMC. The following error when trying to view the developertraces within the SAP MMC: The network path was not found. No new developer traces written to disk (under the "work" directory.)Problem AnalysisThe network shares "saploc" and "sapmnt" do not exist. That explains the "network path not found" message when attempting toview the developer traces within the SAP MMC.Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.ProfProjects.com | Page 2/4 |This page was exported from - SAP ADMINExport date: Tue Nov 6 7:04:24 2012 / +0000 GMTSolutionRe-create the "saploc" and "sapmnt" network shares. Both need to be created on the /usr/sap directory

4: Users get "No logon possible" messagesWork processes start but no logins are possible.Users get the login screen but the system does not log them in. Instead, they get this error: No logon possible (no hw ID received bymssg server).In the SAP MMC, the message server (msg_server.exe) shows status "stopped".The dev_ms file reports these errors:[Thr 2548] *** ERROR => MsCommInit: NiBufListen(sapmsTST) (rc=NIESERV_UNKNOWN) [msxxserv.c 8163][Thr 2548] *** ERROR => MsSInit: MsSCommInit [msxxserv.c 1561]

[Thr 2548] *** ERROR => main: MsSInit [msxxserv.c 5023][Thr 2548] ***LOG Q02=> MsSHalt, MSStop (Msg Server 2900) [msxxserv.c 5078]Problem AnalysisWork processes were able to start but the message server was not. The reason is because the "services" file is missing the SAPSystem Message Port entry. Example: SAPmsTST 3600/tcpSolutionEdit the "services" file and add the entry. Then, re-start the instance. Make sure you specify the appropriate TCP port (e.g. 3600) forthe message server.

5: The message server starts but the dispatcher doesn'tThe dispatcher shows status "stopped" in the SAP MMC.The "dev_disp" file shows these errors:***LOG Q0A=> NiIServToNo, service_unknown (sapdp00) [nixxi.c 2580]*** ERROR => DpCommInit: NiDgBind [dpxxdisp.c 7326]*** DP_FATAL_ERROR => DpSapEnvInit: DpCommInit*** DISPATCHER EMERGENCY SHUTDOWN ***Problem AnalysisThe keyword in the messages above is "service unknown" followed by the entry name "sapdp00". The dispatcher entry "sapdp00" ismissing in the "services" file. Example: sapdp00 3200/tcp

SolutionAdd the necessary entry in the "services" file. Example: sapdp00 3200/tcp Then, re-start the instance.

6: Work processes die soon after they startAll work processes die right after the instance is started.The SAP MMC shows work processes with status "ended".Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.ProfProjects.com | Page 3/4 |This page was exported from - SAP ADMINExport date: Tue Nov 6 7:04:24 2012 / +0000 GMTOnly one work process shows status "wait".An ABAP dump saying "PXA_NO_SHARED_MEMORY" is generated as soon as a user logs in.The SAP MMC Syslog shows the following error multiple times: "SAP-Basis System: Shared Memory for PXA buffer notavailable".

Problem Analysis

The instance profile contains misconfigured memory-related parameters. Most likely the "abap/buffersize" instance profileparameter is set to high. Solution

Edit the instance system profile at the OS level under /usr/sap//sys/profile and lower the value assigned to "abap/buffersize". Then,restart the instance. Also, it's important to find out if any other memory parameter were changed. If not, the system should start oncethe adequate memory allocation has been set to the the "abap/buffersize" parameter.Output