Starting SDM Server in integrated mode

Hi,
I am trying to start the SDM Server after upgrading to SP17 but the server doesnot start in the 'integrated' mode. The reply I get is the following "SDM server not up after 55 seconds. Waiting for another 5 seconds". It is starting in the 'standalone' mode and I am able to connect through the remotegui. The server is running on AIX. The log doesnot have any information regarding what is happening. Please help.
Regards,
Sanjib

Hi Pascal,
Sorry for the delay in replying. I am starting the GUI by executing the script RemoteGui.bat and I am able to connect to SDM of other servers. There is one particular server whose SDM server doesnot start in integrated mode.
Passing the command ./sdm.sh jstartup mode=integrated ends with return code = 0. And after that I pass the command ./StartServer.sh. These commands are as per SAP Note 860939. I have waited for 600 seconds as you have suggested and the following is the snapshot from the sdmlog20060929.log file:
Sep 29, 2006 7:48:58 AM Info: Starting SDM - Software Deployment Manager...
Sep 29, 2006 7:48:59 AM Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.4017.00.0000.20060420082457.0000
Sep 29, 2006 7:49:01 AM Info: SDM operation mode successfully set to: Integrated
Sep 29, 2006 7:49:01 AM Info: JStartupFramework is active
Sep 29, 2006 7:49:01 AM Info: Operation mode of SDM in JStartupFramework is "Integrated".
Sep 29, 2006 7:49:01 AM Info: Check if Server is running already.
Sep 29, 2006 7:49:01 AM Info: OK server is not running. Enable SDM Process in JStartupFramework.
Sep 29, 2006 7:49:02 AM Info: enabling SDM Process with JStartupFramework
Sep 29, 2006 7:49:02 AM Info: enabled SDM Process with JStartupFramework
Sep 29, 2006 7:49:02 AM Info: Successfully enabled SDM Process in JStartupFramework.
Sep 29, 2006 7:59:07 AM Error: SDM server startup not finished after 600 seconds. Giving up.
Sep 29, 2006 7:59:07 AM Error: Could not start SDM. Processing error. Return code: 4
Thanks and regards,
Sanjib Kumar Brahma

Similar Messages

Could not start SDM Server - another Server may be running already

Hi
I have some problems with SDM after upgrade to SP16.
Right now i can't neither start it, nor change password..
it has an error but i don't understand it, because i have only one instance and the server is stopped.
I'm enclosing the error, please, if you have some ideas let me know.
Thank you.
Oct 10, 2006 12:34:29... Error: ERROR: Could not start SDM Server - another Server may be running already.
Oct 10, 2006 12:34:29... Error: Another SDM is running already for this SDM_HOME directory. Exiting. Throwable: com.sap.sdm.client_server.launch.SDMRunningException Throwable message: Another SDM instance is running on this host
Oct 10, 2006 12:34:29... Error: Could not start SDM. Processing error. Return code: 4

A lot of thanks of your answer (both of you)..
None of the prerequisits of the note exists on my system.
"1)There is a started SDM server on the system. All SDM commands have to be executed when there is no started SDM server. Or SDM port is busy by another application."
Server is on red color. I had reseted all tha instance, nobody use it, any applications.
"2)2. The executed command can be run only if SDM is in standalone mode."
Yes, i ran before the next command: Execute :
sdm jstartup "mode=standalone" "sdmhome=C:/usr/sap/<SID>/<Instance>/SDM/program"
"3. SDM port is busy by another application."
the port is only used for sdm wich is off...
Anyway, in order to get the solution, i started with the steps described on the note, but i had a problem with the StopServer.bat
3.Run
StopServer.bat (for Windows)
When i run it, i got another message (i though a similar one):
"Sending shutdown on port 50018
Shutdown failed: SDM currently runs in monolithic mode. Logons cannot be accepted.
Could not shutdown server.
Details: Shutdown failed: SDM currently runs in monolithic mode. Logons cannot be accepted.
Processing error. Return code:4"
Any ideas?
Thank you.

Starting the server in Japanese mode after deployment in english mode.

Hi,
I have a problem
We are developing some system for Japanese clients.
Now problem is that we need to deploy all on their server which shows every hting
in Japanese. Its going to be really very difficult for us.
Is there any key or property in weblogic server by changing that we can change
the language (english-->japanese)
Actually what I wanted was first to run the server in English mode. deploy each
and every thing sucessfuly.
Then stop the server.
Change that flag or whatever to use japanese character set.
Start the server again so that it run in japanese language and having every thing
already deployed.
Is it possible approach?
Any other suggestions are also most welcome.
Thanks and Regards
Pavitra

Hi,
You would have to use the below command to give the root directory to start the server in MSI mode
-Dweblogic.RootDirectory=path
Example:
java -Dweblogic.RootDirectory=c:\MyServerRootDirectory weblogic.ServerTo get more information on this you can check the below link
Topic: Starting a Managed Server in MSI Mode
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/server_start/failures.html#wp1058998
Regards,
Ravish Mody

Starting Weblogic Server in Development Mode

Hello,
How can I start a managed server in development mode? I set STARTMODE=false in
the StartManagedServer.cmd. However, this did not work. Any ideas? Thanks in
advance.

收到，谢谢！
内容不错

Start weblogic server in debug mode through command prompt

Hi,
Please help me in starting the weblogic server in debug mode through command prompt.I am using weblogic 10.3.6 app server.
Thanks

Hi,
To debug weblogic startup issues you can pass the below jvm arguments:
-Dweblogic.slc=true
-Dweblogic.debug.DebugServerLifeCycle=true
Debug options are available in weblogic based on the subsystem, such as security, jms, jdbc, deployment..etc
You can refer to :
https://blogs.oracle.com/vijaya/entry/weblogic_web_service_debug_flags
Thanks,
Sharmela

Error starting J2EE server in debug mode

I am trying to start the Sun 1.4 application server in a debug mode. I get an error
err:FATAL ERROR in native method: No transports initialized
: No such file or directory
Error [2] in bind() call!
Socket transport failed to init.
Transport dt_socket failed to initialize, rc = -1.
The setting in config.xml file is:-
debug-enabled="true" debug-options="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=1044
Any help will be appreciated.
Thanks,
Milind

I changed the port number and it worked. Not sure why port 1044 as specified in the Sun documentation doesnot work.
Milind

Starting managed server in MSI mode

Is it possible to access an application deployed on a managed server which is started in MSI mode(Admin server is stopped)??

Hi,
MSI mode just says that the Managed Server Can be started without the AdminServer Running. But the Application Serving functionality wise there is no difference. So even if your Managed Server is running on MSI mode ..it will serve the Application as it could server with Non-MSI mode.
So Yes, The Application can be accessed from the ManagedServer which is running in a MSI mode.
Thanks
Jay SenSharma
http://weblogic-wonders.com/weblogic (WebLogic Wonders Are Here)

Starting BIP Server in background mode on Windows

Hi,
When we start the standalone BIP Server inside an OC4J container on Windows, a command prompt remains open. If you close the command prompt the BIP Server process dies.
Is there a way to start the BIP Server in a background mode ?
Please advise.
Thanks,
Chetan

Thanks all for your reply.
I used the javaservice to create a windows service.
javaservice -install "OC4J" "C:\Program Files\Java\jdk1.5.0_07\jre\bin\client\jvm.dll" -XX:MaxPermSize=128m -Xmx512m "-Djava.class.path=C:\oracle\OracleBIPublisher\oc4j_bi\j2ee\home\oc4j.jar" -start oracle.oc4j.loader.boot.BootStrap -description "Oracle BI Publisher OC4J Service"

Starting J2EE server in console mode

Hello Everyone,
I have just installed WAS 640 SP3 J2EE only on AIX5.2 unix server. J2ee server starts and stops without any problem. I can even see the J2EE engine through the web.
Administrator user is locked because of the wrong password entries. I am trying to follow OSS note : 669848, it explains how to unlock Administrator user for SP3 systems which requires to stop the Java instance and start it console mode by jlaunch. when I run the following command after setting the LIBPATH to /usr/sap/NWS/JC00/j2ee/os_libs, but it never put me the console mode.
"jlaunch -file=/usr/sap/NWS/JC00/j2ee/cluster/instance.properties -nodeName=ID1693850 pf=/usr/sap/NWS/SYS/profile/NWS_JC00_cgunx130 -traceFile=tracefile3.log -startMode=console".
tracefile3.log shows the following error message at the end.
Fri Dec 17 17:44:25 2004
ERROR => DlLoadLib: dlopen()= No such file or directory -> DLENOACCESS (2,No
such file or directory) [dlux_mt.c 310]
ERROR => Can't load VM shared library (libjvm.a) (rc=-2) [jhvmxx_mt.c 1380]
ERROR => Cannot load DLL for Java VM [jlnchxxi_mt. 527]
I use java 1.4.1
cgunx130:nwsadm 22> java -version
java version "1.4.1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1)
Classic VM (build 1.4.1, J2RE 1.4.1 IBM AIX 5L for PowerPC (64 bit JVM) build caix641411-20040301 (JIT enabled: jitc))
Could you please help me to UNLOCK the Administrator user.
Thanks,
Tuncay

Please, can u put how do you resolve the problem, i've the same situation.
eulerss

SDM Server in Monolithic mode

Hi All,
While updating the java SP-stacks, I am not able to login into JSPM and when checked at SDM Tool server, server is in monolithic mode.
Please provide me your inputs how to change monolithic mode to standlone mode.
SAP PI 7.0 -- On Suse Linux 10
Thanks in Advance.
Regards
Shiva

wrong forum !

How to start the server in debug mode

HI
Im working on weblogic server 8.1 sp. My requirement is to run the application in hosted on weblogic server with out restaring the server i.e dynamiically turn to debug mode with out stopping. IM using Log4j method for logging. please let me know how to do it... if any one have sample java code
Thanks & regards
shiva

I am not sure, how can you do it on the fly, but if you want to restart the server here are the parameters you need to add to the java arguments
-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=$Port
(where Port will be any port you want to connect to).
Thanks
Togotutor
<a class="jive-link-external" href="http://www.togotutor.com">http://www.togotutor.com</a> (Learn Programming and Administration for Free)
Edited by: togotutor on Aug 12, 2010 3:44 PM

SDM server does not start (J2EE)

Hi,
currently i'm trying the Calculator example, But when it comes to deployment, NetWeaver couldn't connect to the SDM Server.
It seems that this server wasn't startet. The problem is, i'm not able to start this server and i don't know why.
In the Management Console i see the following nodes (my pc is named STGN0017):
+ STGN0017
+ STGN0017 1 (green)
 - Process List (green)
 msg_server.exe (Running)
 enserver.exe (Running)
 - Syslog
+ STGN0017 0 (yellow)
 - Process List (yellow)
 jcontrol.exe (some process running)(yellow)
 igswd.exe (Running) (green)
 - Process Table
 dispatcher (Running)
 server0 (Stopped; Exitcode:-2; Restart:No)
 SDM (Stopped; Exitcode:0; Restart:No)
When i open the J2EE View (Window > ShowView > J2EE Engine) i see the following:
Remote engine
+ localhost:3601
+ J2E instance 00 on stgn0017 (yellow)
 - dispatcher (green)
 - SDM (red)
 - server0 (red)
If i try to investigate the server with a Browser i get the following message (Adress: http://localhost:50000/):
Dispatcher running but no server connected!
Has anyone an idea how to solve this? Restart in the MMC doesn't help.
I have installed SneakPreview15. But before, SneakPreview 14 was installed. Th installation of 14 crashed during database setup and i removed all files i could find and did a system recovery before installing 15.
Best regards
Manuel

Hi,
there are errors:
std_server0.out:
Error occurred during initialization of VM
Could not reserve enough space for object heap
Reserved 1610612736 (0x60000000) bytes before loading DLLs.
no error information in dev_server0
I cant fint the other two files, but in the loggin folder are some logfiles and the last entries are:
Mar 20, 2006 1:07:47 PM Info:
Mar 20, 2006 1:07:47 PM Info: ============================================
Mar 20, 2006 1:07:47 PM Info: = Starting to execute command 'server' =
Mar 20, 2006 1:07:47 PM Info: ============================================
Mar 20, 2006 1:07:47 PM Info: Starting SDM - Software Deployment Manager...
Mar 20, 2006 1:07:47 PM Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.4015.00.0000.20050927182322.0000
Mar 20, 2006 1:07:49 PM Info: SDM operation mode successfully set to: Integrated
Mar 20, 2006 1:07:51 PM Info: JStartupFramework is requesting to start the SDM Server.
Mar 20, 2006 1:07:51 PM Info: Start the SDM Server integrated in the JStartupFramework.
Mar 20, 2006 1:07:51 PM Info: Initializing Network Manager (50017)
Mar 20, 2006 1:07:51 PM Info: Starting SDM Server listening on port 50018
Mar 20, 2006 1:07:51 PM Info: SDM started successfully.
Thats all for a full starting process
regards,
Manuel

How to start server in debug mode by default

Hi,
Whenever the server starts it does not start in debug mode.
One has to manually start the "SDM" and "Server0" in the debug mode.
Is there a way I can make the server start in debug mode for the first time itself.
regards,
Saurabh

Hi Saurabh,
You can start the server in debug mode using config tool. Just open cofig tool (/usr/sap/<SYS ID>/JC<SYS NR>/j2ee/configtool/configtool.bat).
Click on the your instance. Then under the tab Servers Debug check Debuggable and also Enable Debug mode.
Restart the engine now.
However a word of caution: Starting the server in debug mode decreases the system performance. You should only start the dev server in debug mode.
Hope this helps.
Regards
Sidharth

Starting Server in Debug Mode - Need Some Advice Plz.

Hi Guys,
I have an EP SP 12 Server Running and I am trying to Start the Server in Debug mode from the Netweaver Developer Studio but when I right click the Server and try to choose Debug, the option is greyed out and even while viewing the Debug option from the SAPMMC I see that under the column Debug, it say 'Disabled' for the Server and Dispatcher.
Can anyone suggest how this can be done, I would appreciate any help as I have been working on this for some time.
Best Wishes,
John.
Message was edited by: John Bray
Message was edited by: John Bray

Hi John,
If the you cannot start the server in the debugging mode through the NWDS then you can try the other way round.
Through Config Tool:
You can enable the debuggine mode from the Config Tool as well. Just visit the following path :
C:\usr\sap\<SID>\JC<SYS_NO>\j2ee\configtool\configtool.bat
Click on the your instance. Then under the tab VM Environment, Set the DebugMode = true.
Restart the engine now. This will open the J2EE server again in the Debug Mode.
I hope this helps you!!
Regards
Pravesh
PS: Please conside rewarding points if helpful and solved.

Starting WLS 10.3.5 Managed Server in MSI mode

(1) The first time you start the managed server in MSI, should the Admin Server be in Running Mode?
Or
(2) The Managed Server can be started in MSI mode (first time) with out having Admin Server in RUNNING MODE.
Which is true?
I think (1) is correct as the managed server directory wont be available under <DOMAIN_HOME>/Servers directory until you start the Managed Server. So only once you start the Managed Server, then only you can copy the config folder under Managed Server to start it in MSI mode (Having ADMIIN SERVER in SHUTDOWN state).
Is that correct?
So you can never ever start the Managed Server in MSI mode for the first time (with out having Admin Server in RUNNING MODE) after you create the managed server.
Is that correct?
Edited by: user734247 on Apr 18, 2012 2:58 PM

Your understanding is right.
The first time you are trying to start a managed server, you need admin server in RUNNING state.
From the next time onwards you can start managed server in MSI mode.
Although, as a workaround you can probably create certain files and directories to try and start managed server in MSI mode the first time itself:
1. Ensure that the entire domain directory is present in the machine where managed server is started.
2. Create directory <DOMAIN_HOME>/Servers/<ManagedServerName>/security
3. Create boot.properties file in <DOMAIN_HOME>/Servers/<ManagedServerName>/security/boot.properties with username and password
4. Create config-msi.xml copying from the config.xml in config directory
This list is not exclusive, it might need some more additional files.
You will have to create additional files like startServer.properties etc if we use node manager to start a managed server in MSI mode.
ORACLE strongly recommends to start the managed server through admin server the first time.
Arun

Starting SDM Server in integrated mode

Similar Messages

Maybe you are looking for