on 12-21-2012 2:11 PM
Hello SAPGurus,
I am not able to start the J2EE engine of the SAP because the processes dispatcher,SDM are totally stopped and server0 is in "Starting Framework" status. I tried to post two discussions before but was not helpfull, the issue is pending since long time. I tried to change some parameters of the instance.properties like Xms value,XX:NewSize,XX:MaxNewSize also changed MaxHeap Size to 128 from 3000 for the node instance_id->server_ID in cluster data. I did this with refernce to Note 736557 - Changes made with the Config Tool. The values were changed as per the values mentioned in the configtool. It is to note that the Locking Manager is not working. I raised a message to SAP they said to restart the cluster as the LockingManager is getting hanged I tried that also but still no change in status.Please let me know what should I check in the UME LDAP data in config tool.Please help me to solve it as this one is taking a toll. Pasting the following logs for reference.
SDM Developer Trace
Unrecognized option: null
[Thr 4144] *** ERROR => JHVM_LoadJavaVM: Cannot create Java VM (rc=-1) [jhvmxx.c 553]
[Thr 4144] *** ERROR => Cannot load Java VM (server) (rc=-1) [jlnchxxi.c 752]
[Thr 4144] **********************************************************************
*** ERROR => Java VM initialization failed.
*** Please see SAP Note 943602 , section 'Java VM initialization issues'
*** for additional information and trouble shooting.
**********************************************************************
DISPATCHER Developer Trace
Unrecognized option: null
[Thr 4144] *** ERROR => JHVM_LoadJavaVM: Cannot create Java VM (rc=-1) [jhvmxx.c 553]
[Thr 4144] *** ERROR => Cannot load Java VM (server) (rc=-1) [jlnchxxi.c 752]
[Thr 4144] **********************************************************************
*** ERROR => Java VM initialization failed.
*** Please see SAP Note 943602 , section 'Java VM initialization issues'
*** for additional information and trouble shooting.
**********************************************************************
DEV_JCONTROL
[Thr 5780] Fri Dec 21 14:07:12 2012
[Thr 5780] ***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
[Thr 5780] *** ERROR => NiIRead: SiRecv failed for hdl 3 / sock 452
(SI_ECONN_BROKEN/10054; I4; ST; 192.168.1.194:1711) [nixxi.cpp 4424]
STD_SERVER0.OUT
Loading: LockingManager ...
Thanks & Regards,
Abhishek Paritosh
Hi Abhishek,
Run the below command and then try to start the cluster once again.
Procedure to Reset in Unix Environment:
1. We have to stop the SDM first, to do that
/usr/sap/<systemid>/<system instance>/SDM/program/sh StopServer.sh # to stop SDM
2. /usr/sap/<systemid>/<system instance>/SDM/program/sdm.sh jstartup mode=standalone
3. /usr/sap/<systemid>/<system instance>/SDM/program/sdm.sh changepassword sdmhome=/usr/sap/<systemid>/<system instance>/SDM/program newpassword=<new password>
4. /usr/sap/<systemid>/<system instance>/SDM/program/sdm.sh jstartup mode=integrated
5. Now start the SDM, to do that
/usr/sap/<systemid>/<system instance>/SDM/program/sh StartServer.sh # to start SDM
Procedure to Reset in Windows Environment:
It almost the same procedure what we have followed to reset the password in UNIX for SDM
1. Go to the drive we have installed Portal ( C:\ or D:\ ), from the command prompt.
2. let us suppose the portal is installed in C:\ drive
3. From the command prompt. go to SDM directory as
C:\usr\sap\J2E\JC00\SDM\program
4. Execute the following (just copy-paste)
sdm jstartup "sdmhome=C:\usr\sap\J2E\JC00\SDM\program" "mode=standalone"
5. Execute following line (replacing Password1 with your new password for SDM)
sdm changepassword "sdmhome=C:\usr\sap/J2E/JC00/SDM/program" "newpassword=Password1"
6. Also revert SDM back to integrated mode
sdm jstartup "sdmhome=C:\usr\sap\J2E\JC00\SDM\program" "mode=integrated"
7. Start SDM
StartServer.bat
Finally opened the config tool and also set the same password for the user secure storage area.
Kindly update on this.
With Regards
Ashutosh Chaturvedi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi abhishek,
I mentioned the points above .
Please follow the below link as per your os.
http://wiki.sdn.sap.com/wiki/display/EP/Reset+SDM+Password+in+Unix+and+Windows+Environment
Even in config tool you need to do the activity.It is also mentioned out there.
With Regards
Ashutosh Chaturvedi
Hi Abhishek,
Just goto the below directory.
/usr/sap/<SID>/<INSTANCE_NAME>/SDM/program/log directory.
Paste all the logs out here.
Will start from beginning.
Please follow the below link :
http://help.sap.com/saphelp_nw04/helpdata/en/76/fb72ec091f4bf8a2d8ba321bb7e8d9/content.htm
With Regards
Ashutosh
Hello Ashutosh,
Finally I was able to start the J2EE engine of the SOLMAN SAP system. The problem was in sdm_jstartup.properties file located in the directory structure E:\usr\sap\SDX\DVEBMGS00\SDM\program\config. Earlier following were the wrong paramters mentioned in the file
sdm_jstartup.properties
sdm.ClassPath=G:\usr\sap\QCM\DVEBMGS00\SDM\program\bin\SDM.jar
sdm.JavaParameters=null
Above two parameters were changed to and SDM worked.
sdm.ClassPath=G:\usr\sap\QCM\DVEBMGS00\SDM\program/bin/SDM.jar
sdm.JavaParameters=
Note:- Check out the difference in the slashes and value for paramter sdm.JavaParameters
Thanks everyone for the participationa and the help provided.
Regards,
Abhishek Paritosh
Hi Abhishek,
Try to start the server with safe mode.
In insatnce.properties file you need to change the value of a parameter.
instance.runMode=safe
Then try to start the java instance and paste the content of default trace and server0.out file
You can do it from config tool as well.
open the config tool and Select the file tab.
On selecting file tab , you will get dropdown where you will find safe mode.
With Regards
Ashutosh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello
There is no need to reset the password of SDM.
Also I dont understand why there is a need to restart the server node in safe mode when the dispatcher and server0 processes are running.
The steps to restart in safe mode and reset of SDM are irrelevant for your issue.
I request you to check the logs I have pointed out to you in the previous reply.
Also make sure to cross check the configuration files of the SDM in the SDM\program\config directory.
Cheers
RB
Hello Reagan,
It is to inform you that while trying to change the password it throwed the following
Jan 7, 2013 11:23:42 AM Info: = Starting to execute command 'jstartup' =
Jan 7, 2013 11:23:42 AM Info: ==============================================
Jan 7, 2013 11:23:42 AM Info: Starting SDM - Software Deployment Manager...
Jan 7, 2013 11:23:42 AM Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0014.20071029094708.0000
Jan 7, 2013 11:23:43 AM Info: SDM operation mode successfully set to: Standalone
Jan 7, 2013 11:23:43 AM Info: Initializing Network Manager (50017)
Jan 7, 2013 11:23:43 AM Info: Checking if another SDM is running on port 50018
Jan 7, 2013 11:23:43 AM Info:
Jan 7, 2013 11:23:43 AM Info: SDM operation mode successfully set to: Integrated
Jan 7, 2013 11:23:44 AM Info: Operationmode for JStartupFramework set to "integrated".
Jan 7, 2013 11:23:44 AM Info: Successfully executed. Return code: 0
I dint found this port by using command netstat -a but I found the same on the server where the SDM is working, could this be a port issue. Please suggest.
Regards,
Abhishek Paritosh
Hello Abhishek
Can you launch SAP MMC Console and check the status of SDM from there please ?
If it is down there please try a restart from the SAP MMC Console.
I know it sounds weird but there is no indication of a restart that way in the entire post.
If that fails please check the latest SDM trace files.
You can find the SDM under the J2EE Process Table
Thanks to confirm.
Cheers
RB
Hello Reagan,
I checked files sdm_jstartup.properties and sdm_jstartup.properties.vmprop and matched the same with the other server. There were some differences like the backslash and forwardslash. And tried to restart the server. But still the SDM is not working. Please suggest.
Regards,
Abhishek Paritosh
Hello
The SDM issue can be resolved by a quick restart of the server.
Cheers
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello RB,
Thanks for your participation. It's strange that even though there are two files sdm_gui.out and sdm_gui.err present in the directory structure but those are of 0kb means there is nothing present in the files. I am attaching file sdmlog20130107.log.txt for the same thing.Please suggest.
Regards,
Abhishek Paritosh
Hello Abhishek,
As suggested set environment variable JAVA_HOME and update the jvm path in Configtool and take a restart.
Also check the listener, possibly check the default_trace of dispatcher if anything is reported there, although it is running.
Please paste default trace of the server node if dispatcher is not throwing any error.
Regards,
Amit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Amit,
Thanks for the participation. I have added the JAVA_HOME parameter and the jvm path in Configtool for dispatcher_ID and server_ID is C:/j2sdk1.4.2_17-x64 which is the same mentioned in the instance profile. Please suggest where can I check the listener.
Regards,
Abhishek Paritosh
Hello Abhishek,
Can you also attach the default trace of Dispatcher and Server node.
As you have mentioned that your ABAP Stack is working, then listener is not having any issue.
You can restart Listener and then restart the Java again and send us the above mentioned default trace of Dispatcher and server node.
It the system Dual Stack or MCOD?
Regards,
Amit
is there any directory structure which I need to use wherein I can use this command, because the command is not working generally.
C:\Documents and Settings\sdxadm>lsnrctl stop
'lsnrctl' is not recognized as an internal or external command,
operable program or batch file.
Regards,
Abhishek Paritosh
Hello,
Please check below discussions for listener issue.
http://scn.sap.com/thread/1731095
https://scn.sap.com/message/9314455
http://scn.sap.com/thread/3200660
Although as I mentioned LIstener will not be the issue in this case, as ABAP is working fine.
Kindly provide default trace of SDM and DIspatcher?
Regards,
AMit
Hello Amit,
Good news is that now I am able to start the server0 process too it shows in green and I am able to launch the portal of the solman system which was not possible before. But the bad news is that the SDM is still stopped. When I try to start the SDM from the directory path G:\usr\sap\QCM\DVEBMGS00\SDM\program\startSDM.BAT then it opens the gui with the following on the prompt. But the sap mmc shows the SDM in grey status only. Please advice.
CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiVie
PrintNode
CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder e
code
CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjec
s
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/Ins
anceBuilder readElement
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/Ins
anceBuilder readSequence
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/Typ
MappingImpl initializeRelations
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/Gen
ratedComplexType _loadInto
Starting SDM - Software Deployment Manager...
tc/SL/SDM/SDM/sap.com/SAP AG/7.0014.20071029094708.0000
Initializing Network Manager (50017)
Checking if another SDM is running on port 50018
<<< frog.jar: version 5.4.6 02/01/06 sap.theme: null >>>
SDM started successfully.
Redirecting output to the two files "G:\usr\sap\QCM\DVEBMGS00\SDM\program\log\s
m_gui.out" and "G:\usr\sap\QCM\DVEBMGS00\SDM\program\log\sdm_gui.err" respectiv
ly.
Regards,
Abhishek Paritosh
Hello Abhishek,
Good to hear this.
But there are lots of error which needs to be removed.
1. In the default trace of server node:
"Plain###Error while sending HTTP data. Status: 401. Message: Unauthorized. Please check if the target SLD system is available and the SLD bridge is started there.#"
Resolve above error and make sure it gets removed there after.
2. In default trace of dispatcher:
"Plain###Error occurred while reading message from R/3 dispatcher. The J2EE engine will be shut down. Please check if the R/3 dispatcher is running and then restart the J2EE engine.#"
Resolve this error too.
3. SDM:
Kindly reset the password of your SDM and then try again. Lots of blogs can be found on how to reset SDM password.
Regards,
Amit
Hello Amit,
There is no RFC SAPSLDAPI in the SOLMAN system. May be this is the reason because when I try tcode SLDCHECK it throws the following error
the RFC RFC destination SAPSLDAPI does not exist
=> Create the RFC destination by using transaction SM59!
Please advice whether the RFC should be maintained in SOLMAN or other ECC system.
Regards,
Abhishek Paritosh
Hello Amit,
1.As suggested by you I changed the password of the SDM and restarted the system but still SDM is not working. Also I checked if SDM is using port 50018 by the help of command netstat -a I couldn't see the port 50018 anywhere in the screen. Please suggest if there is any command which could free the port 50018 if used in any sense.
2. Please suggest how changing the password of SDM helps in starting it. Is it used anywhere in the process of starting the SDM.
Regards,
Abhishek Paritosh
Hi Abhihsek
Could you check the JAVA_HOME in the environment variable in the system properties?
system variables JAVA_HOME=C:\j2sdk1.4.2_13-x64?
Regards
Sriram
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Abhishek,
You need not required to set the JAVA_HOME ENV . Reason is already the instance profile contains jstartup profile. this will take more priority than the ENV's.
I just want you to give a try by creating an entry in services file for exampe (services file under /etc/services in case of unix , windows ->system32->drivers->etc->services in case of windows).
Please give a try and check whether it helps. If not, please attach the dev_server0 logs from work directory as well as default trace from cluster/log directory.
As well as please confirm whether before change of ports,was your system up and running?
Thanks and Regards,
VImal
Hello Joseph,
Thanks for the participation. First of all there are two services file one is services and services.1, how should I know which is the service file which the system is using. Next I have added the following at the last
Global dispatcher configuration 3011
in both the services file.Please tell me if this is correct. The java stack I guess was never up because before people over here tried to do EHP5 on there system and ABAP stack worked with it but they faced an error with the Java stack as Java enginee was not working. Also I tried to add JAVA_HOME but still server0 and SDM is not working. Please help me out as I have to solve this issue asap.
Regards,
Abhishek Paritosh
Hi,
It seems you have problem with JDK installed, JDK is not compatiable,cwhats your JDK version?
follow the note 943498.
also check note 940893.
with regards,
samarth jh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Samarth,
Changed the value of port to 3011 from 8101 in global dispatcher config->services->p4->3011 and now the dispatcher service is working. Thank GOD. But still the server0 and SDM is not wokring. I am working on Windows Server 2003 and MS SQL2005 and SOLMAN is 7.0 SPS15 and java version is "1.4.2_17". How should I know which JDK is compatible to the system.
Regards,
Abhishek Paritosh
Hi Samarth,
Following are the parameters set for
instance_ID15597->server_ID1559750
Java Parameters:-
-Djco.jarm=1
-XX:MaxPermSize=256M
-XX:PermSize=256M
-Xms1024M
-XX:NewSize=171M
-XX:MaxNewSize=171M
-XX:+DisableExplicitGC
-verbose:gc
-XX:+PrintGCDetails
-XX:+PrintGCTimeStamps
-Djava.awt.headless=true
-Dsun.io.useCanonCaches=false
-XX:SoftRefLRUPolicyMSPerMB=1
-XX:SurvivorRatio=2
-XX:TargetSurvivorRatio=90
-Djava.security.policy=./java.policy
-Djava.security.egd=file:/dev/urandom
-Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
dispatcher_ID1559750
Java Parameters:-
-XX:NewSize=57M
-XX:MaxNewSize=57M
-Xms170M
-XX:+DisableExplicitGC
-verbose:gc
-Djava.security.policy=.java.policy
-Djava.security.egd=file:/dev/urandom
-Djco.jarm=1
instance_ID15597
Java Parameters:-
-Djco.jarm=1
Please suggest if anything is missing.
Regards,
Abhishek Paritosh
Hi Abhishek,
what changes you have made to the fine running system? tell me your environment.
Thanks:
Kishore Cherkumalla.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kishore,
Changed the value of port to 3011 from 8101 in global dispatcher config->services->p4->3011 and now the dispatcher service is working. Thank GOD. But still the server0 and SDM is not wokring. I am working on Windows Server 2003 and MS SQL2005 and SOLMAN is 7.0 SPS15 and java version "1.4.2_17"
Regards,
Abhishek Paritos
Hi Kishore,
Do you find anything different in the following marked in bold from dev_server0 pls tell me if Xss should be Xms.
-> arg[ 26]: -Dmemory.manager=1024M
-> arg[ 27]: -Xmx1024M
-> arg[ 28]: -Xms1024M
-> arg[ 29]: -DLoadBalanceRestricted=no
-> arg[ 30]: -Djstartup.mode=JCONTROL
-> arg[ 31]: -Djstartup.ownProcessId=4232
-> arg[ 32]: -Djstartup.ownHardwareId=N1614910102
-> arg[ 33]: -Djstartup.whoami=server
-> arg[ 34]: -Djstartup.debuggable=no
-> arg[ 35]: -Xss2m
-> arg[ 36]: -DSAPINFO=QCM_00_server
-> arg[ 37]: -DSAPSTART=1
-> arg[ 38]: -DCONNECT_PORT=3929
-> arg[ 39]: -DSAPSYSTEM=00
-> arg[ 40]: -DSAPSYSTEMNAME=QCM
-> arg[ 41]: -DSAPMYNAME=qerossm_QCM_00
-> arg[ 42]: -DSAPPROFILE=G:\usr\sap\QCM\SYS\profile\QCM_DVEBMGS00_qerossm
-> arg[ 43]: -DFRFC_FALLBACK=ON
-> arg[ 44]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 45]: -DSAPSTARTUP=1
-> arg[ 46]: -DSAPSYSTEM=00
-> arg[ 47]: -DSAPSYSTEMNAME=QCM
-> arg[ 48]: -DSAPMYNAME=qerossm_QCM_00
-> arg[ 49]: -DSAPDBHOST=QEROSSM
-> arg[ 50]: -Dj2ee.dbhost=QEROSSM
Regards,
Abhishek Paritosh
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.