Error in SMD Agent
Hello All,
In order to install Wily Introscope Agent, initially I have installed
a SMD Agent on managed system host.
After the installtion of SMD Agent , while starting the SMD agent I am getting below error .
Starting SMDAgent ...
Establishing connection to server '[host is empty]' on port [port is
empty]
Smd connector is disabled because no SLD association and no credentials
found.
Smd connector is disabled because no SLD association and no credentials
found.
Waiting for connection ...
Checking server availability...
Warning :
Connecting to SMD server null failed - error counter: 0 -
com.sap.engine.services.jndi.persistent.exceptions.NamingException: No
InitialContext can be created because the java.naming.provider.url
property is no specified in the jndi environment.
Next try to push instance data in SLD is Tue May 19 14:36:31 CDT 2009
I have given user SLDAPIUSER in SLDAPICUST transaction. This user
which is not locked and I have also reconfirmed the password of this
user.
Kindly request your suggestion!!!!
Regards,
Suhas
Santosh Asuthkar
I am receiving the same error in my SMD agent log:
Starting SMDAgent ...
Dec 8, 2009 1:43:48 PM [Thread[main,5,main]] Info Establishing connection to server '[host is empty]' on port [port is empty]
Dec 8, 2009 1:43:51 PM [Thread[SMDAgent connection thread,5,main]] Info Smd connector is disabled because no SLD association and no cred
entials found.
Dec 8, 2009 1:43:51 PM [Thread[SMDAgent connection thread,5,main]] Info Smd connector is disabled because no SLD association and no cred
entials found.
Dec 8, 2009 1:43:51 PM [Thread[SMDAgent connection thread,5,main]] Info [null] Waiting for connection ...
Dec 8, 2009 1:43:52 PM [Thread[SMDAgent connection thread,5,main]] Info [null] Checking server availability...
Dec 8, 2009 1:43:53 PM [Thread[SMDAgent connection thread,5,main]] Warning Connecting to SMD server null failed - error counter: 0 - com.sa
p.engine.services.jndi.persistent.exceptions.NamingException: No InitialContext can be created because the java.naming.provider.url property i
s no specified in the jndi environment.
Dec 8, 2009 1:43:54 PM [Thread[SLD-Registration,1,main]] Info [SLDReg] Next try to push instance data in SLD is Wed Dec 09 01:43:54 EST
2009
Dec 8, 2009 1:46:52 PM [Thread[SLD-AssocWatcher,1,main]] Info [SLDManagingConnectionMonitor] Next time to check Managing System Associat
ion is Tue Dec 08 14:01:52 EST 2009
Can you please provide details if you found a solution?
Thanks!!!!!
Jeff
Similar Messages
-
Hi friends,
Getting the below error in step 10 (configuration check) in managed system configuration.
The SMD Agent is not able to connect the Satellite System (J2EE stack).
Please check the JAVA Connect Parameters provided in the Managed System Setup Wizard for this
System.
java.rmi.RemoteException.P4 Connection failed -
P4AuthorizationException -
com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException:
Access is denied to SAP System sid [XYZ/null]: check the connection
credentials.More details about the error in agent 'xyz' log file
(SMDAgentApplication.X.log).; nested exception is:
com.sap.engine.services.security.exceptions.BaseLoginException: Cannot
authenticate the user.
The SMD log file referred to in the log above gives the same information and not anything much useful.
Any idea what could be the reason for the above error?
Thanks,
ArindamHi All,
Thaks for your suggestions. I chcked the note 182020, but the issue described in the note is for error byte code adapter installation whcih is not my case. The byte cde adapter intallation has been successful in our solman system All the steps from 1 to 9 are green. Only in step 10, check cniguration I am getting the above error.
The logon test wth the user id in step 3 "Enter system parameters" is successful. The message server port is also correct.
Hi Khaja,
I went to the links as suggestedby you but there its about a ifferent error message "Invalid Response Code: (401) Unauthorized.". I am not getting any such kind of error.
All I am getting is this -
The SMD Agent is not able to connect the Satellite System (J2EE stack).
Please check the JAVA Connect Parameters provided in the Managed System Setup Wizard for this System.
java.rmi.RemoteException.P4 Connection failed -
P4AuthorizationException -
com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException:
Access is denied to SAP System sid [XYZ/null]: check the connection
credentials.More details about the error in agent 'xyz' log file
(SMDAgentApplication.X.log).; nested exception is:
com.sap.engine.services.security.exceptions.BaseLoginException: Cannot
authenticate the user.
Thanks,
Arindam -
The SMD Agent 'HOSTNAME hasn't been found!
Dear,
I have already upgrade the Solution Manager 7.0 EHP1 . I have a problem with my SMD error The SMD Agent 'BASAPI02' hasn't been found!
I want to setup E2E Root Cause Analysis for ERP 6.0 Stack Java system.
So I configured SMSY, I've already installed SMD Agent in managed system successfully also.
When I run the Diagnostics Setup -> Managed System -> Setup WIzard,
in the Setup Parameter Step , it said that " No SMD Agent is currently available (ie not assigned). Please install an agent for BASAPI02 or unassign an existing agent in Agent Administration Why is that so ?
In the Agent Administration ( DIagnostics Administration -> Managed SYstem -> Agent Administration) found that the agent is online.
does anyone know why this happens and how to resolve
Thanks in advance,
AntonioHello Antonio
The agent name registration or agent registration on it's own depends on the version of your diagnostics agent.
From diagnostics agent 7.20 and higher if you have installed it using default connection setting in sapinst then you don't need to seperately register the diagnostics agent in the agent candidate management.
Once the agent is known you should see it in the agent administration list. If you don't see the agent in the agent administration list it would mean it is not yet known and you have to go through the agent candidate management first.
The server name assignment is normally done through the managed system setup. After selecting your SAP system to be configured and pushing the setup button you get a screen in which you have to fill in the hostname, user+pass and so on at the left side bar. On the right side you should see one or more lines that represent your SAP system.
You have to expand that line and then select the appropriate agent from the list. After selecting the correct agent from the list your diagnostics agent will get the hostname assignment and you will be prompted to wait and refresh because the agent is then automatically restarted.
Kind regards
Tom -
Error while installing SMD agent
Hi ,
1) Can any one please justify/brief the need of installing SMD agent on ABAP stack?
2) When I tried to install the SMD 711 agent on ABAP stack I could see the below error when i click sapinst.exe.
" Running msiexec failed with return code 1063: undefined
command line was :
msiexec.exe /norestart /L vcredist_x64.log /i vcredist_x64.msi /qn "
I tried with Changing the environment variable of Temp and tmp to C:\usr\sap\<sid>\tmp and also tried with directory c:\temp but in vain .
enivronment:- Windows 64-bit.
Note:- SMD agent was successfully installed on Development systemn
Please suggest.
Thank you
JayanthHi ,
Log from vcredist_x64.log. Please have a look
" Product: Microsoft redistributable runtime DLLs VS2005 SP1(x86_x64) -- Error 1719. The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.
Error 1719. The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.
Action ended 2:47:00: SxsInstallCA. Return value 3.
Action ended 2:47:00: INSTALL. Return value 3.
MSI (s) (FC:38) [02:47:00:489]: Windows Installer installed the product. Product Name: Microsoft redistributable runtime DLLs VS2005 SP1(x86_x64). Product Version: 8.0.50727.762. Product Language: 1033. Installation success or error status: 1603.
Does this mean that , I should download new sapinst file for service market place and try again ??
Thank you
Jayanth -
SMD agent starts, but stderr0 has errors
Hallo Gurus,
we had installed the new Diagnostic Agents 7.11 for our EP.
Now the Agent runs after installation, but in the stderr0 we have the following errors.
(13107436) New Child Process created.
(13107436) Starting local Command:
Command: jc.sapDAA_SMDA97
pf=/usr/sap/DAA/SYS/profile/DAA_SMDA97_sapipp
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/HTTP/file_access_0 (ref.by icm/HTTP/file_access_0) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_0 (ref.by icm/server_port_0) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_1 (ref.by icm/server_port_1) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_2 (ref.by icm/server_port_2) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_3 (ref.by icm/server_port_3) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_4 (ref.by icm/server_port_4) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_5 (ref.by icm/server_port_5) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_6 (ref.by icm/server_port_6) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_7 (ref.by icm/server_port_7) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_8 (ref.by icm/server_port_8) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_9 (ref.by icm/server_port_9) missing.
jc.sapDAA_SMDA97=>sapparam(14): ssl/pse_provider[SMDA] (ref.by ssl/pse_provider) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/HTTP/file_access_0 (ref.by icm/HTTP/file_access_0) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_0 (ref.by icm/server_port_0) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_1 (ref.by icm/server_port_1) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_2 (ref.by icm/server_port_2) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_3 (ref.by icm/server_port_3) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_4 (ref.by icm/server_port_4) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_5 (ref.by icm/server_port_5) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_6 (ref.by icm/server_port_6) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_7 (ref.by icm/server_port_7) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_8 (ref.by icm/server_port_8) missing.
jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_9 (ref.by icm/server_port_9) missing.
jc.sapDAA_SMDA97=>sapparam(14): ssl/pse_provider[SMDA] (ref.by ssl/pse_provider) missing.
In the sdn are no answer for this issue.
Some suggestion???
regards
ChrisWe get data from the agent, but i think that is not all data that we can get...
SAPSYSTEMNAME = DAA
SAPSYSTEM = 97
INSTANCE_NAME = SMDA97
DIR_CT_RUN = $(DIR_EXE_ROOT)/$(OS_UNICODE)/rs6000_64
DIR_EXECUTABLE = $(DIR_INSTANCE)/exe
SAPLOCALHOST = sapepp
DIR_PROFILE = $(DIR_INSTALL)/profile
_PF = $(DIR_PROFILE)/DAA_SMDA97_sapepp
SETENV_00 = DIR_LIBRARY=$(DIR_LIBRARY)
SETENV_01 = LD_LIBRARY_PATH=$(DIR_LIBRARY):%(LD_LIBRARY_PATH)
SETENV_02 = SHLIB_PATH=$(DIR_LIBRARY):%(SHLIB_PATH)
SETENV_03 = LIBPATH=$(DIR_LIBRARY):%(LIBPATH)
SETENV_04 = PATH=$(DIR_EXECUTABLE):%(PATH)
# Copy SAP Executables
_CPARG0 = list:$(DIR_CT_RUN)/j2eeinst.lst
Execute_00 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG0)
_CPARG1 = list:$(DIR_CT_SAPJVM)/sapjvm_5.lst
_CPARG2 = source:$(DIR_CT_SAPJVM)
Execute_01 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG1) $(_CPARG2)
# JStart configuration
SAPJVM_VERSION = 5.1.038
jstartup/vm/home = $(DIR_SAPJVM)
jstartup/bootstrap = no
# Start SMD Agent
_JC = jc.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME)
Execute_02 = local rm -f $(_JC)
Execute_03 = local ln -s -f $(DIR_EXECUTABLE)/jstart$(FT_EXE) $(_JC)
Start_Program_00 = local $(_JC) pf=$(_PF)
# File generated automatically by the diagnostics agent sapinst.
# Created 2010.09.23 at 12:23:10 GMT
# sapinst classes version: 7.01.2.6.20090526074537
# Title: DAA_SMDA97_sapepp
# Description: File which specify the start parameters used by Jstartup framework for Diagnostics Agent process.
# Don't modifiy manually this script.
smd/agent/type=710
jstartup/instance_properties=$(DIR_INSTANCE)/SMDAgent/smdagent.properties -
Urgent!! Setup of SMD Agent failed due to Remote Error....
I am getting the following error when i tried to Setup the Smd agent using setup wizard:
<b>The assignment of server frces4153 to SMD Agent failed
Remote error occurs during the connection to the smd agent for agent frces4153</b>
Can you please give me the solution for this...
<b>Reward points of all the replies....</b>
Ajay KandeThnx for ur suggestions, Now i colud see the following error "[Setup]Failed to assign SMD Agent to frces4146/EP7 (frces4146)
[EXCEPTION]
Time out occurred when calling method 'getService' on object [com.sap.smd.api.IAgentContext_Stub@7fc07fc] after 10000 ms.... [siehe Details]
from the logs....
Ajay Kande -
Hi,
I get following error msg when I try to assign agent during RCA setup
The assignment of server sapsrmqas201 to SMD Agent failed
Unexpected error during the server name assignation (sapsrmqas201) for agent sapsrmqas201.xxx.xxx.com
In setup wizard, I choose agent installed on that server and when I click on set button I get this msg.
Any idea on solution for this.
Regards,
ShyamHi
Do you able to see the SMD agent as green under agent admin in solman workcernter?
if so try to restart the agent and try to start the setup wizard again,
Might be the issue with smd connection with Solman? have you registered the SMD to central SLD?
Please refer to the Diagnostics Setup Guide 7.11.pdf in [http://service.sap.com/diagnostics |http://service.sap.com/diagnostics ]-> media library
there you find more information on how to set up the connection parameters that are used by the SMD Agent to connect to Solution Manager.
Thanks,
Jansi -
SMD agent not starting correctly FAIL: NIECONN_REFUSED (Connection refused)
I am getting the following message when I start the agent. I don't see any errors except for this, and when I try to connect it in agent_adminstration, it never connects. Just eventually times out after 30 mins.
FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen()
cat jvm_SMDAgent.out
LoadBalanceRestricted=no
P4ClassLoad=P4Connection
SAPDBHOST=
SAPINFO=SMD_98_server
SAPMYNAME=ssmsap_SMD_98
SAPSTARTUP=1
SAPSYSTEM=98
SAPSYSTEMNAME=SMD
application.home=/usr/sap/SMD/exe
com.ibm.cpu.endian=little
com.ibm.oti.configuration=scar
com.ibm.oti.jcl.build=20080922_1143
com.ibm.oti.vm.bootstrap.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
com.ibm.oti.vm.library.version=23
com.ibm.util.extralibs.properties=
com.ibm.vm.bitmode=64
file.encoding=UTF-8
file.separator=/
ibm.signalhandling.rs=false
ibm.signalhandling.sigchain=true
ibm.signalhandling.sigint=true
ibm.system.encoding=UTF-8
j2ee.dbhost=
java.assistive=ON
java.awt.fonts=
java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
java.awt.printerjob=sun.print.PSPrinterJob
java.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
java.class.version=48.0
java.compiler=j9jit23
java.ext.dirs=/opt/IBMJava2-amd64-142/jre/lib/ext
java.fullversion=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
J9VM - 20080922_23329_LHdSMr
JIT - 20080815_1845_r8
GC - 200809_04
java.home=/opt/IBMJava2-amd64-142/jre
java.io.tmpdir=/tmp
java.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
java.runtime.version=2.3
java.specification.name=Java Platform API Specification
java.specification.vendor=Sun Microsystems Inc.
java.specification.version=1.4
java.util.prefs.PreferencesFactory=java.util.prefs.FileSystemPreferencesFactory
java.vendor=IBM Corporation
java.vendor.url=http://www.ibm.com/
java.version=1.4.2
java.vm.info=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
J9VM - 20080922_23329_LHdSMr
JIT - 20080815_1845_r8
GC - 200809_04
java.vm.name=IBM J9 VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Sun Microsystems Inc.
java.vm.specification.version=1.0
java.vm.vendor=IBM Corporation
java.vm.version=2.3
jstartup.debuggable=yes
jstartup.mode=JCONTROL
jstartup.ownHardwareId=F2143454721
jstartup.ownProcessId=17393
jstartup.whoami=server
jxe.current.romimage.version=9
jxe.lowest.romimage.version=9
line.separator=
memory.manager=256M
os.arch=amd64
os.name=Linux
os.version=2.6.9-89.ELsmp
path.separator=:
sun.boot.class.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm/jclSC14/classes.zip:/opt/IBMJava2-amd64-142/jre/lib/core.jar:/opt/IBMJava2-amd64-142/jre/lib/charsets.jar:/opt/IBMJava2-amd64-142/jre/lib/graphics.jar:/opt/IBMJava2-amd64-142/jre/lib/security.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmpkcs.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorb.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorbapi.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjcefw.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjssefips.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjgssprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjsseprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjaaslm.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmcertpathprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/server.jar:/opt/IBMJava2-amd64-142/jre/lib/xml.jar
sun.boot.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
sun.io.unicode.encoding=UnicodeLittle
sun.java2d.fontpath=
sys.global.dir=/usr/sap/SMD/SYS/global
user.country=US
user.dir=/usr/sap/SMD/J98/SMDAgent
user.home=/home/smdadm
user.language=en
user.name=smdadm
user.timezone=
user.variant=
Running SMD Agent ...
[p4://ssmsap:50004] Agent ready.
Initialization done.
cat jvm_SMDAgent.out
LoadBalanceRestricted=no
P4ClassLoad=P4Connection
SAPDBHOST=
SAPINFO=SMD_98_server
SAPMYNAME=ssmsap_SMD_98
SAPSTARTUP=1
SAPSYSTEM=98
SAPSYSTEMNAME=SMD
application.home=/usr/sap/SMD/exe
com.ibm.cpu.endian=little
com.ibm.oti.configuration=scar
com.ibm.oti.jcl.build=20080922_1143
com.ibm.oti.vm.bootstrap.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
com.ibm.oti.vm.library.version=23
com.ibm.util.extralibs.properties=
com.ibm.vm.bitmode=64
file.encoding=UTF-8
file.separator=/
ibm.signalhandling.rs=false
ibm.signalhandling.sigchain=true
ibm.signalhandling.sigint=true
ibm.system.encoding=UTF-8
j2ee.dbhost=
java.assistive=ON
java.awt.fonts=
java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
java.awt.printerjob=sun.print.PSPrinterJob
java.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
java.class.version=48.0
java.compiler=j9jit23
java.ext.dirs=/opt/IBMJava2-amd64-142/jre/lib/ext
java.fullversion=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
J9VM - 20080922_23329_LHdSMr
JIT - 20080815_1845_r8
GC - 200809_04
java.home=/opt/IBMJava2-amd64-142/jre
java.io.tmpdir=/tmp
java.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
java.runtime.version=2.3
java.specification.name=Java Platform API Specification
java.specification.vendor=Sun Microsystems Inc.
java.specification.version=1.4
java.util.prefs.PreferencesFactory=java.util.prefs.FileSystemPreferencesFactory
java.vendor=IBM Corporation
java.vendor.url=http://www.ibm.com/
java.version=1.4.2
java.vm.info=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
J9VM - 20080922_23329_LHdSMr
JIT - 20080815_1845_r8
GC - 200809_04
java.vm.name=IBM J9 VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Sun Microsystems Inc.
java.vm.specification.version=1.0
java.vm.vendor=IBM Corporation
java.vm.version=2.3
jstartup.debuggable=yes
jstartup.mode=JCONTROL
jstartup.ownHardwareId=F2143454721
jstartup.ownProcessId=17393
jstartup.whoami=server
jxe.current.romimage.version=9
jxe.lowest.romimage.version=9
line.separator=
memory.manager=256M
os.arch=amd64
os.name=Linux
os.version=2.6.9-89.ELsmp
path.separator=:
sun.boot.class.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm/jclSC14/classes.zip:/opt/IBMJava2-amd64-142/jre/lib/core.jar:/opt/IBMJava2-amd64-142/jre/lib/charsets.jar:/opt/IBMJava2-amd64-142/jre/lib/graphics.jar:/opt/IBMJava2-amd64-142/jre/lib/security.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmpkcs.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorb.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorbapi.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjcefw.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjssefips.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjgssprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjsseprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjaaslm.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmcertpathprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/server.jar:/opt/IBMJava2-amd64-142/jre/lib/xml.jar
sun.boot.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
sun.io.unicode.encoding=UnicodeLittle
sun.java2d.fontpath=
sys.global.dir=/usr/sap/SMD/SYS/global
user.country=US
user.dir=/usr/sap/SMD/J98/SMDAgent
user.home=/home/smdadm
user.language=en
user.name=smdadm
user.timezone=
user.variant=
Running SMD Agent ...
[p4://ssmsap:50004] Agent ready.
Initialization done.cat dev_SMDAgent
trc file: "/usr/sap/SMD/J98/work/dev_SMDAgent", trc level: 1, release: "701"
node name : smdagent
pid : 17393
system name : SMD
system nr. : 98
started at : Wed Oct 7 08:56:32 2009
arguments :
arg[00] : /usr/sap/SMD/J98/../exe/jlaunch
arg[01] : pf=/usr/sap/SMD/J98/../SYS/profile/SMD_J98_ssmsap
arg[02] : -DSAPINFO=SMD_98_server
arg[03] : pf=/usr/sap/SMD/J98/../SYS/profile/SMD_J98_ssmsap
JStartupReadInstanceProperties: read instance properties [/usr/sap/SMD/J98/profile/smd.properties]
-> ms host :
-> ms port : 36
-> OS libs : /usr/sap/SMD/exe
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Used property files
-> files [00] : /usr/sap/SMD/J98/profile/smd.properties
Instance properties
-> ms host :
-> ms port : 36
-> os libs : /usr/sap/SMD/exe
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Bootstrap nodes
Worker nodes
-> [00] smdagent : /usr/sap/SMD/J98/profile/smd.properties
[Thr 182894174624] Wed Oct 7 08:56:32 2009
[Thr 182894174624] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 182894174624] JLaunchRequestQueueInit: create pipe listener thread
[Thr 1074792800] JLaunchRequestFunc: Thread 1074792800 started as listener thread for np messages.
[Thr 1085282656] WaitSyncSemThread: Thread 1085282656 started as semaphore monitor thread.
[Thr 182894174624] SigISetDefaultAction : default handling for signal 17
[Thr 182894174624] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 182894174624] CPIC (version=701.2009.01.26)
[Thr 182894174624] [Node: SMDAgent] java home is set by profile parameter
Java Home: /opt/IBMJava2-amd64-142
[Thr 182894174624] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/SMD/J98/../exe/jvmx.jar
JStartupIReadSection: read node properties [smdagent]
-> node name : SMDAgent
-> node type : server
-> node id : 1
-> node execute : yes
-> java path : /opt/IBMJava2-amd64-142
-> java parameters : -DP4ClassLoad=P4Connection -Xj9 -Xmn50m -Xgcpolicy:gencon
-> java vm version : J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
-> java vm vendor : IBM J9 VM (IBM Corporation)
-> java vm type : server
-> java vm cpu : amd64
-> heap size : 256M
-> init heap size : 256M
-> root path : ../SMDAgent
-> class path : ../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
-> OS libs path : /usr/sap/SMD/exe
-> main class : com.sap.smd.agent.launcher.SMDAgentLauncher
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : /usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar
-> parameters : run jcontrol
-> debuggable : yes
-> debug mode : no
-> debug port : 58981
-> shutdown timeout : 20000
[Thr 182894174624] JLaunchISetDebugMode: set debug mode [no]
[Thr 1086335328] JLaunchIStartFunc: Thread 1086335328 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [SMDAgent]
-> stack : 1048576 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -DP4ClassLoad=P4Connection
-> arg[ 4]: -Xj9
-> arg[ 5]: -Xmn50m
-> arg[ 6]: -Xgcpolicy:gencon
-> arg[ 7]: -Dsys.global.dir=/usr/sap/SMD/SYS/global
-> arg[ 8]: -Dapplication.home=/usr/sap/SMD/exe
-> arg[ 9]: -Djava.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
-> arg[ 10]: -Djava.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
-> arg[ 11]: -Dmemory.manager=256M
-> arg[ 12]: -Xmx256M
-> arg[ 13]: -Xms256M
-> arg[ 14]: -DLoadBalanceRestricted=no
-> arg[ 15]: -Djstartup.mode=JCONTROL
-> arg[ 16]: -Djstartup.ownProcessId=17393
-> arg[ 17]: -Djstartup.ownHardwareId=F2143454721
-> arg[ 18]: -Djstartup.whoami=server
-> arg[ 19]: -Djstartup.debuggable=yes
-> arg[ 20]: -DSAPINFO=SMD_98_server
-> arg[ 21]: -DSAPSTARTUP=1
-> arg[ 22]: -DSAPSYSTEM=98
-> arg[ 23]: -DSAPSYSTEMNAME=SMD
-> arg[ 24]: -DSAPMYNAME=ssmsap_SMD_98
-> arg[ 25]: -DSAPDBHOST=
-> arg[ 26]: -Dj2ee.dbhost=
[Thr 1086335328] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [SMDAgent]
-> arg[ 0]: run
-> arg[ 1]: jcontrol
[Thr 1086335328] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 1086335328] Wed Oct 7 08:56:35 2009
[Thr 1086335328] JLaunchISetState: change state from [Initial (0)] to [Initial (0)]
[Thr 1086335328] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 1086335328] Wed Oct 7 08:56:38 2009
[Thr 1086335328] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 1086335328] JLaunchISetState: change state from [Starting (2)] to [Running (3)]
[Thr 1101334880] Wed Oct 7 08:56:43 2009
[Thr 1101334880] JLaunchISetState: change state from [Running (3)] to [Starting applications (10)]
[Thr 1101334880] Wed Oct 7 08:56:48 2009
[Thr 1101334880] JLaunchISetState: change state from [Starting applications (10)] to [Running (3)] -
Start of SMD agent fails!
Hi!
After the installation of SMD AGENT 7.00 SP09 we've got some problems starting the agent.
The errorlog says: (/usr/sap/SMD/J98/SMDAgent/log/SMDSystem.0.log)
Oct 11, 2006 2:11:26 PM [Thread[SMDAgent connection thread,5,main]] Error Exception ID: 1160572286256
Registering agent on server myhost.de:50004failed:
com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException
However, the manual setup of the agent succeeds:
./smdsetup.sh /usr/java14_64 myhost.de 50004 j2ee_admin PASSWORD
SAP Solution Manager Diagnostic - SMD Agent Setup - Copyright (c) 2005 SAP AG
SMD Agent Setup is in process ...
- STEP 1: checking JDK location
JDK location is consistent: /usr/java14_64/bin
- STEP 2: checking JDK Version
JDK Version is correct: 1.4.2
- STEP 3: checking Connection to SMD Server
SMD Server check completed successfully
- STEP 4: generating Runtime Properties
runtime.properties has been created.
- STEP 5: generating Launcher
smdagent.bat has been created.
smdagent.sh has been created.
- STEP 6: generating SecStore
secstore.properties: has been created.
secstore.properties: user has been set.
secstore.properties generation completed successfully.
- STEP 7: checking P4 Connection and SMD Agent Registration
SMD Agent Registration succeeded
SMD Agent Setup completed successfully
During the start process of the agent, the agent appears in the agent administration tab in SMD/admin, but it disappears after the erroneous shutdown.
What can we do?
Thanks for all hints solving our problem!
Greetz,
André RichterHi Rahul,
please try SMD Agent 7.00 SP10! We had no problems with this version!
Also make sure that the OSUser has enough privileges. We use the "sidadm" to start the agent.
Regards
André -
Install SMD agent on EP6 fails
Hi,
I get an error when installing SDM agent on EP6 (HP-UX):
STEP 7: checking P4 Connection and SMD Agent Registration
External Command Executed:
/opt/java1.4/bin/java -DP4ClassLoad=P4Connection -Dsap.p4.remote_classloading=false -cp ":/usr/sap/SMD/J97/SMDAgent/lib/sapxmltoolkit.jar:/usr/sap/SMD/J97/SMDAgent/lib/smdagent.jar:/usr/sap/SMD/J97/SMDAgent/lib/tc_sec_secstorefs.jar:/usr/sap/SMD/J97/SMDAgent/lib/iaik_jce_export.jar:/usr/sap/SMD/J97/SMDAgent/lib/launcher/logging.jar:/usr/sap/SMD/J97/SMDAgent/lib/smdserver.jar:/usr/sap/SMD/J97/SMDAgent/lib/exception.jar:/usr/sap/SMD/J97/SMDAgent/lib/sapj2eeclient.jar:/usr/sap/SMD/J97/SMDAgent/lib/launcher/smdagentlauncher.jar:" com.sap.smd.setup.Setup /p4connection
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
P4 Connection succeeded but SMD Agent Registration failed
Root exception is: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of smdserver.
I couldn't find anything on SAP Market Place but a similar thread here advised to check if SDM servers is not in maintenance mode.
Well, it's not.
Can someone please help?
Thx
BertHi,
Did you connect to smd server http://host:port/smd and desactivate maintenance mode in Agent Administration page?
This should solve your issue.
Regards,
Frederic -
Hello,
I have been trying to install SMD Agent in my BI system but Solution Manager can't check it, this is the message in Solman_setup
Wilyhost Agent configuration finished without errors, but on Enterprise Manager (sapl917.intra.banesco.com:6001) no Wilyhost Agent was detected from host svs978. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
Step Wilyhost Agent Details
Created destination QBB|svs978_QBB_01
Created action QBB - QBB AbapSystem
Created action QBB|svs978_QBB_01 - QBB|svs978_QBB_01 AbapInstance
Created 2 action(s).
0 Wilyhost Agent(s) from host svs978 are connected to the EM.
Wilyhost Agent configuration finished without errors, but on Enterprise Manager (sapl917.intra.banesco.com:6001) no Wilyhost Agent was detected from host svs978. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
do you know something??? i restarted the agent but nothing happens
Thanks!!!!Hello...
For JAVA
Software Components
Vendor Name Version Provider Location Applied
sap.com ADSSAP 7.01 SP4 (1000.7.01.4.0.20090417021200) SAP AG SAP AG 20091103161136
sap.com BASETABLES 7.01 SP4 (1000.7.01.4.0.20090417015900) SAP AG SAP AG 20091103153957
sap.com BI_MMR 7.01 SP4 (1000.7.01.4.0.20090417021807) SAP AG SAP AG 20091103161215
sap.com BI_UDI 7.01 SP4 (1000.7.01.4.0.20090416221700) SAP AG SAP AG 20091103162333
sap.com CAF 7.01 SP4 (1000.7.01.4.0.20090417194106) SAP AG MAIN_NW701P04_C 20091103163937
sap.com CAF-UM 7.01 SP4 (1000.7.01.4.0.20090417194111) SAP AG MAIN_NW701P04_C 20091103161325
sap.com CORE-TOOLS 7.01 SP4 (1000.7.01.4.0.20090417021948) SAP AG SAP AG 20091103154019
sap.com ISAGENT 8.1 SP0 (8.1.0.0.20090605095817) SAP AG SAP AG 20091210142716
sap.com JLOGVIEW 7.01 SP4 (1000.7.01.4.0.20090417020000) SAP AG SAP AG 20091103154104
sap.com JSPM 7.01 SP4 (1000.7.01.4.2.20090918151100) SAP AG SAP AG 20091201201543
sap.com KM-KW_JIKS 7.01 SP4 (1000.7.01.4.0.20090514115300) SAP AG SAP AG 20091103161349
sap.com LM-SERVICE 7.01 SP5 (1000.7.01.5.2.20091211060559) SAP AG SAP AG 20091224192630
sap.com LM-TOOLS 7.01 SP5 (1000.7.01.5.3.20091208123420) SAP AG MAIN_NW701P05_C 20091228135344
sap.com SAP-JEE 7.01 SP4 (1000.7.01.4.1.20090612152648) SAP AG SAP AG 20091103154150
sap.com SAP-JEECOR 7.01 SP4 (1000.7.01.4.0.20090417015900) SAP AG SAP AG 20091103154414
sap.com SAP_JTECHF 7.01 SP4 (1000.7.01.4.2.20090612144700) SAP AG SAP AG 20091103154520
sap.com SAP_JTECHS 7.01 SP4 (1000.7.01.4.2.20090612152905) SAP AG SAP AG 20091103162132
sap.com SWLIFECYCL 7.01 SP4 (1000.7.01.4.0.20090511115334) SAP AG MAIN_NW701P04_C 20091103151458
sap.com UMEADMIN 7.01 SP4 (1000.7.01.4.0.20090417195012) SAP AG MAIN_NW701P04_C 20091103165828
For ABAP
SAP_BASIS 701 0004 SAPKB70104
SAP_ABA 701 0004 SAPKA70104
ST-PI 2008_1_700 0001 SAPKITLRD1
PI_BASIS 701 0004 SAPK-70104INPIBASIS
CRMUIF 500 0003 SAPK-50003INCRMUIF
SAP_BW 701 0004 SAPKW70104
SAP_AP 700 0016 SAPKNA7016
BBPCRM 500 0015 SAPKU50015
CPRXRPM 400 0015 SAPK-40015INCPRXRPM
ST 400 0021 SAPKITL431
BI_CONT 704 0004 SAPK-70404INBICONT
ST-A/PI 01L_CRM570 0000 -
ST-ICO 150_700 0022 SAPK-1507MINSTPL
ST-SER 701_2008_2 0005 SAPKITLOQ5
LM Components were updated for EHP1 SPS21, I installed SMD Agents in DEV and some QA servers and they work, but this one specially works as a fail over for a PRD cluster enviroment, and for that reason I'm using logical name, in SMSY it is configure with the same name, do you have any ideas?
Thanks!!! -
RCA - SMD agent is not getting started
Hello Gurus ,
We have installed SMD agent 7.11 on managed system. It installed smoothly but at the time of starting the agent , it is giving error as follows.
jcmon=>sapparam(14): icm[SMDA]/HTTP/file_access_0 (ref.by icm/HTTP/file_access_0) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_0 (ref.by icm/server_port_0) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_1 (ref.by icm/server_port_1) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_2 (ref.by icm/server_port_2) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_3 (ref.by icm/server_port_3) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_4 (ref.by icm/server_port_4) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_5 (ref.by icm/server_port_5) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_6 (ref.by icm/server_port_6) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_7 (ref.by icm/server_port_7) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_8 (ref.by icm/server_port_8) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_9 (ref.by icm/server_port_9) missing.
jcmon=>sapparam(14): ssl/pse_provider[SMDA] (ref.by ssl/pse_provider) missing.
jcmon=>sapparam(14): icm[SMDA]/HTTP/file_access_0 (ref.by icm/HTTP/file_access_0) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_0 (ref.by icm/server_port_0) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_1 (ref.by icm/server_port_1) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_2 (ref.by icm/server_port_2) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_3 (ref.by icm/server_port_3) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_4 (ref.by icm/server_port_4) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_5 (ref.by icm/server_port_5) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_6 (ref.by icm/server_port_6) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_7 (ref.by icm/server_port_7) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_8 (ref.by icm/server_port_8) missing.
jcmon=>sapparam(14): icm[SMDA]/server_port_9 (ref.by icm/server_port_9) missing.
jcmon=>sapparam(14): ssl/pse_provider[SMDA] (ref.by ssl/pse_provider) missing.
I am seeing following errors in logs.
[Thr 01] Tue Apr 6 10:43:05 2010
[Thr 01] *** ERROR => Can't attach to administration shared memory (rc = 3) [jcmonxx_mt.c 228]
[Thr 01] Tue Apr 6 10:43:08 2010
[Thr 01] *** ERROR => Can't attach to administration shared memory (rc = 3) [jcmonxx_mt.c 228]
[Thr 01] Tue Apr 6 10:43:11 2010
[Thr 01] ***LOG Q0I=> NiPGetHostByName: '' not found: getaddrinfo [niuxi.c 1599]
[Thr 01] *** ERROR => MsIAttachEx: NiBufConnect to /36 failed (rc=NIEHOST_UNKNOWN) [msxxi_mt.c 707]
[Thr 01] *** ERROR => Can't attach to message server [jcmonms_mt.c 138]
[Thr 01] *** ERROR => Can't connect to message server [jcmonxx_mt.c 185]
[Thr 01] Tue Apr 6 10:43:13 2010
[Thr 01] *** ERROR => JsfOpenShm: ShmCreate(79, 4096, ATTACH) failed (rc = 3 SHM segment doesn't exist) [jsfxxshm_mt. 1683]
Please help.Thanks
It was related to DNS server problem.
It is resolved now.
thanks
Deepak Joshi -
I have encountered this error when we are trying to register the SMD agent (a few tries already)
As we still cannot see the SMD agent running from our SolMan server
I have tried to search in SDN and SAP Note on this error but cannot find any hints.
Anyone have experience in solving this? Thanks.
java.rmi.RemoteException: Agent Registration failed: [SMDManager.registerPendingAgent] Receive registration for an already existing entry. Registration REJECTEDHello,
What is your Solution Manager version? Inform the SP and the LM-SERVICE.
Try the following:
1. go to agent admin and enable Maintenance Mode
2. go to tab advanced settings
3. increase the value as follows
Smd.asio.remote.time.out.long.ms = 1800000
smd.asio.remote.time.out.ms = 60000
4. go to NWA page and restart the service
tcsmdserver~service
5. go to agent admin and disable Maintenance Mode
6. restart smd agent and see the result.
Best regards
Guilherme -
Hi,
I am trying to install SMD agents(711) on EP 7.0 system ,Got below error when trying to lauch the intsaller (sapinst)
guiengine: No GUI server connected; waiting for a connection on host xxxxxx, port 21200 to continue with the installation
Jan 11, 2011 5:18:58 PM [Info]: *************************
Jan 11, 2011 5:18:58 PM [Info]: Starting Server
Jan 11, 2011 5:18:58 PM [Info]: Reading server configuration.
Jan 11, 2011 5:18:58 PM [Info]: Reading service configuration SAPinstService.
Jan 11, 2011 5:18:58 PM [Info]: Configuring LogManager ...
Jan 11, 2011 5:18:58 PM [Info]: *************************************************
Jan 11, 2011 5:18:58 PM [Info]: Starting SL Controller ...
Jan 11, 2011 5:18:58 PM [Info]: StorageService switched off.
Jan 11, 2011 5:18:58 PM [Info]: Initializing SecurityManager ...
Jan 11, 2011 5:18:58 PM [Info]: Key Store management switched off.
Jan 11, 2011 5:18:58 PM [Info]: Configuring HTTPManager ...
Jan 11, 2011 5:18:58 PM [Info]: WebstartService switched off.
Jan 11, 2011 5:18:58 PM [Info]: RoleService switched off.
Jan 11, 2011 5:18:58 PM [Info]: AlertService switched off.
Jan 11, 2011 5:18:58 PM [Info]: Starting NotesService ...
Jan 11, 2011 5:18:58 PM [Info]: ProcessService switched off.
Jan 11, 2011 5:18:58 PM [Info]: Starting MIDService ...
Jan 11, 2011 5:18:58 PM [Info]: Starting FileService ...
Jan 11, 2011 5:18:58 PM [Info]: LogService switched off.
Jan 11, 2011 5:18:58 PM [Info]: MailService switched off.
Jan 11, 2011 5:18:58 PM [Info]: Starting services ...
Jan 11, 2011 5:18:58 PM [Info]: Starting service "SAPinstService" ...
Jan 11, 2011 5:18:59 PM [Info]: Service "SAPinstService" started
Jan 11, 2011 5:18:59 PM [Info]: Services started.
Jan 11, 2011 5:18:59 PM [Info]: Starting HTTP server listening on port 4239 ...
Jan 11, 2011 5:18:59 PM [Info]: HTTP server started.
Jan 11, 2011 5:18:59 PM [Info]: SL Controller started.
Jan 11, 2011 5:18:59 PM [Info]: Starting GUI ...
Jan 11, 2011 5:18:59 PM [Error]: java.lang.reflect.InvocationTargetException: null
Jan 11, 2011 5:18:59 PM [Error]: java.lang.reflect.InvocationTargetException: null
Jan 11, 2011 5:18:59 PM [Error]: GUI start failed.
Please help me to solve the issue.
Thanks,
Srini KHi,
I have to cope with the same issue on exactly one of our 60 systems. I have no difficulties to start the SAPInst on any of the other systems, but I can't find any differences in their configurations.
I already tried to apply a newer version of SAPInst (as suggested), but this did not help either (package SAPINST7102_2-20003627.SAR, Rel. 7.10 PL 80 for SunOS).
Do you have any other suggestions how to get the SAPInst up and running on this final system?
Thanks in advance for your help!
Ulf -
Hi
Our Solution Manager is on SP14 and Managed System is on SP15. I want to install the SMD Agent. As per the note 1126895 it is possible and suported. LMSERVICE is SP14.
I used note 1170855 to install it and it was successfull but the status is "in Progress" in http:////<hostname>:<port>/smd page. It says "DEPLOYING APPLICATION". It never finishes.
I checked the log file jvm_SMDAgent.out and it says that
Starting SMDAgent ...
Running SMD Agent ...
Establishing connection to server 'ms://<hostname>:8177/P4
[ms://<hostname>:8177/P4] Waiting for connection ...
[ms://<hostname>:8177/P4] Checking server availability...
[ms://<hostname>:8177/P4] Authentication in progress ...
[ms://<hostname>:8177/P4] Connection established .
[ms://<hostname>:8177/P4] Registering agent on server ...
Exception occured. Please check log files.[Exception ID:1219178405804 ]
[ms://<hostname>:8177/P4] Waiting for connection ...
[ms://<hostname>:8177/P4] Checking server availability...
[ms://<hostname>:8177/P4] Authentication in progress ...
[ms://<hostname>:8177/P4] Connection established .
[ms://<hostname>:8177/P4] Registering agent on server ...
It never finishes.
It is failing at deployment application.
The log file SMDSystem.0.log states following -
Aug 19, 2008 4:30:04 PM [Thread[Thread-2,5,main]] Info
[AgentContext.offlineDeployApplication] ENTERING - deploying file
com.sap.smd.agent.application.runtime_7.0014.20080429115048.0000.war
Aug 19, 2008 4:40:05 PM [Thread[SMDAgent connection thread,5,main]]
Error [Exception ID: 1219178405804 ] java.rmi.RemoteException -
error counter: 1
[EXCEPTION]
java.rmi.RemoteException: Agent Registration failed: Time out occurred
when calling method 'offlineDeployApplication' on object
[com.sap.smd.api.IAgentContext_Stub@1de64fc2] after 600000 ms.
possible cause: com.sap.smd.server.util.concurrent.TimeoutException
at com.sap.smd.SMDServerHandle.internalRegisterAgent
Anybody has experienced it.
Please let me know.
Regards.
SSHello,
Would you kindly share the solution?
Think I run into a similar issue.
Many Thanks,
Jan
Maybe you are looking for
-
Hi gang, I'm trying to migrate from an OS 10.4.11 Mac to an OS 10.6.4 MacBook. I was unsuccessful with the Migration Assistant, having tried the tips located here @ http://support.apple.com/kb/TS2664, so I'm now trying the last tip wherein I copy the
-
Anyone got Issue with Time Machine on Mac OS 10.9.5 on External Hard Drive?
Mac Book Air June 2012, Mac OS 10.9.5 (fully updated) external Hard Drive, USB 3 Dear all, Just realized that my regular Time Machine back-ups don't work anymore: despite several back-ups, Time Machine tells me that I did not back-up for 10 days but
-
How can I convert a pdf file to a world file?
I have been trying for the past hour to export a pdf file so that it can be converted to a word file, and no one seems to be of help.
-
Hi there, I am new to PDF form work, and am wondering if someone could help me with a javascript formula. I want to auto-populate the EXPIRYDATE field, as the same date as the entered AUTHORIZATIONDATE field, but 4 years later. So, I want to be able
-
0 to be terminated from Material Number
The 0MATERIAL is diaplyed in most of our Purchase report which displays the material number preceeding with zero's. eg. 0000000026 and 0000001235 etc. Please guide us in eliminating these zeros. It should display like 26 and 1235. This should be done