cancel
Showing results for 
Search instead for 
Did you mean: 

Netweaver 2004 MAX DB Installation, Phase 30.

Former Member
0 Kudos

Hello Everyone.

Me and my group at university are working on installing the SAP system, and are in Phase 30. The Installation then stops with the error message

"Instance EC3/DVEBMGS01 [ABAP:

MSNOTRUNNING] did not stop after 5:00 minutes. Giving up."

Peculiar is the warning:

"/usr/sap/EC3/DVEBMGS01/work/kill.sap: kill: Kein derartiger Prozess" (No such procedure).

The signal 2 is sent to a procedure, in the file "kill.sap". The procedure with the named ID does not exist. The ID does not change with the use of "Retry" or with a reboot.

We believe there is a problem with the Message Server, that is supposed to be shut down after it is activated.

The following Warnings appear:

"Could not stop instance 'DVEBMGS01' of SAP system EC3."

"Connect to message server (ecosap3/3901) failed: NIECONN_REFUSED."

My group, and myself, are all currently stumped on this one.

What could we do? Is there a possibilitiy to manually start up this Message Server? And with what parameters if so?

Thank you in advance, for those who read and respond...

Jason

P.S. this is what we have in our log...

---

INFO 2006-12-06 15:34:26

An error occured and the user decided to retry the current step:

"|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Start|ind|ind|ind|ind|0|0|start".

INFO 2006-12-06 15:34:34

Starting instance EC3/DVEBMGS01...

WARNING 2006-12-06 15:34:34

Connect to message server (ecosap3/3901) failed: NIECONN_REFUSED.

Account 101 already exists.

INFO 2006-12-06 15:39:30

Creating file /sapinst/stop_EC3_DVEBMGS01.log.

INFO 2006-12-06 15:39:33

Output of /usr/sap/EC3/DVEBMGS01/work/kill.sap is written to the

logfile stop_EC3_DVEBMGS01.log.

WARNING 2006-12-06 15:39:33

Execution of the command "/usr/sap/EC3/DVEBMGS01/work/kill.sap"

finished with return code 1. Output: /usr/sap/EC3/DVEBMGS01/work/kill.sap:

kill: Kein derartiger Prozess

WARNING 2006-12-06 15:39:33

Could not stop instance 'DVEBMGS01' of SAP system EC3.

WARNING 2006-12-06 15:39:38

Connect to message server (ecosap3/3901) failed: NIECONN_REFUSED.

WARNING 2006-12-06 15:40:02

Connect to message server (ecosap3/3901) failed: NIECONN_REFUSED.

ERROR 2006-12-06 15:40:02

CJS-30087 Instance EC3/DVEBMGS01 [ABAP: MSNOTRUNNING] did not stop

after 5:00 minutes. Giving up.

ERROR 2006-12-06 15:40:02

FCO-00011 The step start with step key

|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Start|ind|ind|ind|ind|0|0|start

was executed with status ERROR .

-


Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Please post in the specific

Regards,

Sandro

Former Member
0 Kudos

Thank you, question posted in specific forum

Regards

Jason

Former Member
0 Kudos

Anyway have you tried to start it with the command

startsap

from the user sap<SID> ?

Sandro

Former Member
0 Kudos

Yes we tried this now, and here are the results:

====================================

RUN SAPSTART AS USER: EC3ADM

====================================

cd /usr/sap/EC3/DVEBMGS01/exe

bash-3.00$ ./sapstart

Could not open the ICU common library.

The following files must be in the path described by

the environment variable "LD_LIBRARY_PATH":

libicuuc.so.30, libicudata.so.30, libicui18n.so.30 [nlsui0.c 1620]

pid = 9824

-


bash-3.00$ echo $LD_LIBRARY_PATH

/usr/sap/EC3/DVEBMGS01/exe/

-


bash-3.00# ls *.30

libicudata.so.30 libicui18n.so.30 libicuuc.so.30

====================================

RUN SAPSTART AS USER: ROOT

====================================

bash-3.00# cd /usr/sap/EC3/DVEBMGS01/exe/

bash-3.00# ./sapstart

./sapstart=>sapparam(1c): No Profile used.

./sapstart=>sapparam: SAPSYSTEMNAME neither in Profile nor in

Commandline

        • unknown SAPSYSTEMNAME.

(9834) Exiting with Return-Code -101. (Unknown Sap-System-Name)

It did not seem to work, because the sapstart did.

We tried using the StartSap, but it mentions something with

"SAPSYSTEMNAME not set"

Former Member
0 Kudos

"It did not seem to work, because the sapstart did'nt seem to start".

We tried using both methods, and nothing happened