Setting up Managed system in SMD
I ran the SAPINST and installed the agent on the other system. WHen I try to connect to it, with the Setup Wizard for SMD I get the message below. I can see the system in the SLD on my solution manager.
The agent is started on the other system, i have checked that.
No Diagnostics Agent available at this time
Please install or start an SMD Agent for avphux51
Hello,
Please make sure you have completed the starting of SMD agent also after the setup, u can find it in the guide.
also check the p4 or Https port number is correctly mentioned.
The user and pass mostly would be that of SMDadmin, created during the setup, or u can use SIDADM which will wrk fine.
sometimes root needs to be used as even sidadm can be restricted in ur envt. ( just in case).
Regards,
Kaustubh.
Similar Messages
-
Error setting up new Managed System in SMD
Hi,
we get the following error after trying to setup a new (Java)-System:
DataCollect Initial Data Collect ERROR for host xyz
Step DataCollect Details
Initial Data Collect ERROR for host xyz
!! Exception : An error occurred while uploading the Configuration Data from host [xyz] !(cause=java.lang.Exception [DataCollectorClientUtil_xyz] Error collecting initial configuration files on host [xyz])
Exceptions
com.sap.sup.admin.scheduler.exception.FatalTaskExecutionException: An error occurred while uploading the Configuration Data from host [xyz] !
at com.sap.sup.admin.scheduler.task.remote.config.InitialConfigGatherTask.process(InitialConfigGatherTask.java:72)
at com.sap.sup.admin.scheduler.config.DataCollect.execute(DataCollect.java:138)
at com.sap.sup.admin.setup.AppCfgTasks.runInitialDataCollect(AppCfgTasks.java:57)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:348)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:304)
at com.sap.sup.admin.setup.SapCluster.setup(SapCluster.java:736)
at com.sap.sup.admin.setup.SapCluster.access$000(SapCluster.java:28)
at com.sap.sup.admin.setup.SapCluster$SetupRunner.run(SapCluster.java:1000)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.Exception: [DataCollectorClientUtil_xyz] Error collecting initial configuration files on host [xyz]
at com.sap.smd.agent.plugins.datacollector.util.DataCollectorClientUtil.collectInitialConfigurationData(DataCollectorClientUtil.java:315)
at com.sap.sup.admin.scheduler.task.remote.config.InitialConfigGatherTask.process(InitialConfigGatherTask.java:67)
... 8 more
Caused by: com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: [DataCollector] Error during collectInitialConfigurationData() on host [xyz]; nested exception is:
com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: Error installing template files in the working directory; nested exception is:
com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: No cca_systemlandscape.xml file found
at com.sap.smd.agent.plugins.datacollector.DataCollectorService.collectInitialConfigurationData(DataCollectorService.java:684)
at com.sap.smd.agent.plugins.datacollector.DataCollectorServicep4_Skel.dispatch(DataCollectorServicep4_Skel.java:290)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:716)
... 1 more
Caused by: com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: Error installing template files in the working directory; nested exception is:
com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: No cca_systemlandscape.xml file found
at com.sap.smd.agent.plugins.datacollector.DataCollectorService.installTemplateFiles(DataCollectorService.java:792)
at com.sap.smd.agent.plugins.datacollector.DataCollectorService.collectInitialConfigurationData(DataCollectorService.java:710)
at com.sap.smd.agent.plugins.datacollector.DataCollectorService.collectInitialConfigurationData(DataCollectorService.java:654)
... 5 more
Caused by: com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: No cca_systemlandscape.xml file found
at com.sap.smd.agent.plugins.datacollector.DataCollectorService.installTemplateFiles(DataCollectorService.java:766)
... 7 more
in file SMDAgentApplication.0.log of the server, that hosts the system and the SMD agent, I get:
Nov 27, 2008 2:22:57 PM [Thread[Thread-25,5,main]] Error DataCollectorService@40c5f303: collectInitialConfigurationData()
[EXCEPTION]
com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: Error installing template files in the working directory; nested exception is:
com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: No cca_systemlandscape.xml file found
at com.sap.smd.agent.plugins.datacollector.DataCollectorService.installTemplateFiles(DataCollectorService.java:792)
at com.sap.smd.agent.plugins.datacollector.DataCollectorService.collectInitialConfigurationData(DataCollectorService.java:710)
at com.sap.smd.agent.plugins.datacollector.DataCollectorService.collectInitialConfigurationData(DataCollectorService.java:654)
at com.sap.smd.agent.plugins.datacollector.DataCollectorServicep4_Skel.dispatch(DataCollectorServicep4_Skel.java:290)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:716)
at java.lang.Thread.run(Thread.java:534)
Caused by: com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: No cca_systemlandscape.xml file found
at com.sap.smd.agent.plugins.datacollector.DataCollectorService.installTemplateFiles(DataCollectorService.java:766)
... 7 more
Nov 27, 2008 2:23:03 PM [Thread[Thread-35,5,main]] Warning com.sap.smd.wily.hostagent.action.SapOsColAction - launchDaemon(): launchDaemon: saposcol exited with -1
the mentioned cca_systemlandscape.xml that should be located in usr\sap\SMD\J98\SMDAgent\applications.config\com.sap.smd.agent.application.datacollector is 0 byte.
where should this file be generated/has its source?
kr, achimHelpfull notes:
987835 - How to define Solutions in SMSY for Diagnostics
986350 - SM Diagnostics: "Monitored setup" fails during data collect -
Database configuring problem in setup of managed systems in SMD
Hello,
i'm doing the setup of a CRM 5.0 in SMD Abap+Java and the setup results returns following:
"Database configuration problem" with the exception:
java.lang.NullPointerException
at com.sap.smd.server.manager.SMDPluginProperties.setProperty(SMDPluginProperties.java:114)
at com.sap.smd.agent.plugins.database.ConfigurationTask.configureCustomProperties(ConfigurationTask.java:242)
at com.sap.smd.agent.plugins.database.ConfigurationTask.configureProperties(ConfigurationTask.java:370)
at com.sap.smd.agent.plugins.database.ConfigurationTask.execute(ConfigurationTask.java:124)
at com.sap.sup.admin.setup.AppCfgTasks.configureDbApp(AppCfgTasks.java:115)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:202)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:217)
at com.sap.sup.admin.setup.SapCluster.setup(SapCluster.java:461)
at com.sap.sup.admin.setup.SapCluster.access$000(SapCluster.java:26)
at com.sap.sup.admin.setup.SapCluster$SetupRunner.run(SapCluster.java:669)
at java.lang.Thread.run(Thread.java:534)
Anybody knows which can be the problem?
Thanks a lot
CarlosHi Shriraj,
ensure that the installation path is correct. I only put /urs/sap/<SID> and you must put /usr/sap/<SID>/DV***/.
In my case with that the setup returns all in green.
I hope it helps you
Regards
Carlos -
Failed to push XML template when setup SMD Managed system
Hi,
when I setup a managed system in SMD, I receive the warning:
XML Templates pushed : 0 successful, 1 failed
Failed to push XML template to sv50761/TP4/10 (sv50761.RUV.DE) : com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad Attribute value(:main:, row:10, col:79)(cause=com.sap.engine.lib.xml.pars
er.ParserException XMLParser: Bad Attribute value (:main:, row:10, col:79))
(Data Collect may fail due to missing templates)
Do you still want to proceed ? (Setup operations may fail due to warnings above)
when I check the xml-templates, at the mentioned row, there's the database-information: it shows "9.00.3068#" (a binary value, instead of #)
when I check the database in SMSY there's "9.00.3068#" in version as well, I can't change it there manually, because datasource is TMS/RFC.
In SLD the Version vor the database is displayed correct: 9.00.3068 (without #).
Where does the # occur & how to delete it? How can we setup managed systems without the warning?
kr, achimJust came across this issue and this snote fixed it.
Note 1156714 - Failure to push XML templates during Diagnostics Setup -
Hi,
Do we need to re run managed system setup wizard, each time system stack or EHP is updated ? or even when solman stack is updated ?
Reason: We recently updated solman to SPS27 after which I dont see any data collection happening specially for User Load for ABAP systems
and none for java
BR,
ShyamHello,
Run transaction solman_setup and check in the OVERVIEW what are the Open Activities listed in Basic and Initial Configuration.
All activities there must be redone, grey, red or green.
In these tasks there will be the Diagnostics Configuration. This step includes setting the Maintenance Mode ON and OFF, which will stop all agents and deploy the new software to them (the so-called agelets that are delivered centrally from Solman LM-SERVICE to the managed system's SMD Agent).
This is all you must execute after a LM-SERVICE upgrade.
Therefore there's no reason to rerun the whole setup wizard, as it may cause issues with wrong parameters in the setup wizard. If the managed system is working perfectly and this is only an upgrade, it is not recommended to do the setup wizard again.
Best regards,
Guilherme
Edited by: Guilherme Balbinot on Jul 15, 2011 8:37 AM
Edited by: Guilherme Balbinot on Jul 15, 2011 8:41 AM -
Can SMD be setup to monitor the Managing System?
Hello, We have been working off and on for the last few months
installing Wily Introscope, which in turn required E2E RCA, which in
turn required SMD to be installed. Since virtually all of our systems
are on a relatively low pl of the kernel, 114, we also installed the
latest SP and kernel to our Solution Manager system. So, the SM system
is at 7.00 pl 146, and SPS 16 (it's a dual-stack UNICODE system).
However, every other of our almost 27 ABAP stacks are at pl 114,
unfortunately.
We had read, via SAPNet note 1126859, that the MANAGED system must be
at least at kernel 7.00 pl 121. As I saidl, only our MANAGING SM
system is at that level. So we thought that we'd try to have SM
monitor itself, in the context of SMD and Wily Introscope.
Unfortunately, we got stuck at setting up the trusted RFCs for the SM
system to monitor itself. SAP AG's instructions for setting up the
trusted RFCs is in the following guide: Root Cause Analysis
Installation and Upgrade Guide (v3.30 - July 2008), section
6.3.2 "Setup RFC Destinations to Managed Systems". Transaction SMT1
doesn't permit 2 RFCs with the same target <sid>.
So, our questions:
1. Can a MANAGING system also be a MANAGED system?
2. If so, would you kindly clarify how to configure the RFCs for that
scenario? Or perhaps we don't use RFCs in this scenario?
For now, we will move on and try to setup Wily/SMD for a Java-stack
system we have available (Portal).Hi Felipe Pitta,
The Managing system can be managed, for that include your Solman in a solution and proceed all the needed activities like Agent installation, Wily agent setup etc as you do for the managed systems.
You need to create RFCs to the BI client of the solman if you are the same BI component which is available in Solman (001 is your BI client) or RFCs should be created for the BI system which you are using.
WEBADMIN RFC will be created automatically during SMD Agent installation.
By this your solman's data will be collected.
For furthur clarifications pls revert back
regards
Naveen kumar -
SMD - Diagnostic Administration -- Managed Systems takes long time
Hi All,
On SMD administration URL , http://system:50000/smd ---> Diagnostics administration ---> Agent Administration --> managed systems takes very long time.
Sometimes it never ends and keep on going...
CPU utilization is also very high...
Have anyone encountered this issue ?
We are using Solman 7.00 on Solaris, DB is oracle.
Thanks!Reply with ur System Technical Note,
find below DOCS for Solman System Technical Config,
https://websmp103.sap-ag.de/~sapdownload/011000358700000255562007E/Sizing_Guide_SM_70_SP15.pdf
https://websmp103.sap-ag.de/~form/sapnet?_FRAME=OBJECT&_HIER_KEY=501100035870000015092&_HIER_KEY=601100035870000179416&_HIER_KEY=601100035870000179443&_HIER_KEY=701100035871000457214&#HOME
Basically SMD is mostly dependant on J2ee Heap and Abap Configuration. Set up the required Heap and T-Code ST02 paramaters properly and call the SMD again.
Regards
Srikanth Mandalapu
Edited by: srikanth mandalapu on Oct 10, 2008 12:11 AM -
Setting up a Document management system in SharePoint 2013
Hello All,
I have come across a scenario where Customer needs a Document management system for their organization.
They want to keep the documents of different departments like sales, HR,Finace in corresponding folders and want to include a workflow for approval of the Documents. Also, Documents related to particular department can be modified or added by users in that
department.
I thought of creating a seperate site collection for this purpose & document libraries of each department, setting up the permission on document library level. Is this a correct approach?
I am new to Enterprise content management system of sharepoint. Can anybody give me a guidance on this how to get started.
Regards
Vishnu
dfdCreating separate site collection for each department will help you scale and grow better and easier to group SharePoint sites together.
Refer to the following articles which will give you an idea about the plan you should do before building a Document management system
http://technet.microsoft.com/en-us/library/cc263267.aspx
http://blogs.msdn.com/b/sgoodyear/archive/2009/07/25/determining-between-sharepoint-site-collections-and-sub-sites.aspx
http://atinkerersnotebook.com/2013/10/02/creating-your-own-document-management-system-with-sharepoint/
http://community.dynamics.com/ax/b/tinkerersnotebook/archive/2013/10/02/creating-your-own-document-management-system-with-sharepoint.aspx
--Cheers -
SMD Error in managed system type PI 7.1 EHP1 Step Logical Ports error
Hi people,
Solution Manager Ehp1 7.0 SPS24
I am currently runnig the wizard setup for managed System, everything is fine but when I run for PI 7.1 I get the following error:
Fri Sep 10 20:29:48 2010 Logical Ports A failure occured while creating the logical port for JAVA XI : PORT_NOT_CREATED
Step Logical Ports Details
A failure occured while creating the logical port for JAVA XI : PORT_NOT_CREATED
!! Exception : PORT_NOT_CREATED
Exceptions
com.sap.mw.jco.JCO$AbapException: (126) PORT_NOT_CREATED: PORT_NOT_CREATED
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1511)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3980)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3514)
at com.sap.sup.admin.setup.SolManRfcAdapter.createXIlogicalPort(SolManRfcAdapter.java:185)
at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:427)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:335)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:549)
at com.sap.sup.admin.setup.SapCluster.setup(SapCluster.java:1695)
at com.sap.sup.admin.setup.SapCluster.access$000(SapCluster.java:35)
at com.sap.sup.admin.setup.SapCluster$SetupRunner.run(SapCluster.java:1965)
at java.lang.Thread.run(Thread.java:534)
Any ideas?
Thanks in advanceHi everyone,
Thanks everyone.
Guilherme, finally I understand what really happens. "Refresh" is not working properly in the Setup Wizard.
First I have done what I can:
System Type Managed Products Product Instances
DPI ABAP SAP Netweaver PI 7.1 Application Server ABAP (I could not select PI at the same time)
DPI JAVA SAP Netweaver PI 7.1 Application Server Java + Process Integration
But, when I refresh the browser Internet Explorer appears the following:
System Type Managed Products Product Instances
DPI ABAP SAP Netweaver PI 7.1 Application Server ABAP + Process Integration
DPI JAVA SAP Netweaver PI 7.1 Application Server Java + Process Integration
And then I do not get the error anymore. (I have to repeat step 2 in the wizard "Check Prerequisites for Diagnostics)
And If I run transaction SMSY, I can see how PI is mantained since the wizard refresh SMSY.
Product Instance Selection tab:
Application Server ABAP (Flag selected: relevant)
Process Integration (Flag selected: Also Installed, Technical System[ DPI, Java])
Application Server Java (Flag selected: relevant, Technical System[ DPI, Java])
So, if I use this configuration in the SMSY, when I run "solman_setup", configuring DPI (My PI7.1), when I run "Configure Diagnostics", the wizard shows ABAP + PI as expected.
Thanks a lot Guilherme!! -
SMD - MANAGED SYSTEM SETUP WIZARD.
Hi,
I'm on Solman SPS 15, trying to setup EWA for portals.
Ran the managed system setup, got the error.
Step DataCollect Details
Initial Data Collect ERROR for host XXXXXXX
!! Exception : Tue Jun 24 11:03:08 EDT 2008 | storeComponentVersion(...):ComponentVersion ComponentVersion [SAP J2EE ENGINE 7.00][01200314690200004229][N/A][N/A]:Cannot insert/update/delete the component '[IComponent: key=1199734241239977, name=SAP J2EE ENGINE 7.00, internalVersion=7.00 PatchLevel 29172.450, ppmsId=01200314690200004229, date=Tue Jun 24 11:03:06 EDT 2008, status=[N], mod=[M], messageServer=XXXXX:3901, masterComponent=true]'! Please see log for next warning(s).
com.sap.sup.admin.scheduler.exception.FatalTaskExecutionException: Tue Jun 24 11:03:08 EDT 2008 | storeComponentVersion(...):ComponentVersion [SAP J2EE ENGINE 7.00][01200314690200004229][N/A][N/A]:Cannot insert/update/delete the component '[IComponent: key=1199734241239977, name=SAP J2EE ENGINE 7.00, internalVersion=7.00 PatchLevel 29172.450, ppmsId=01200314690200004229, date=Tue Jun 24 11:03:06 EDT 2008, status=[N], mod=[M], messageServer=XXXXXX:3901, masterComponent=true]'! Please see log for next warning(s).
at com.sap.sup.admin.scheduler.task.remote.AbstractGatherRemoteTask.checkTaskResult(AbstractGatherRemoteTask.java:42)
at com.sap.sup.admin.scheduler.task.remote.config.InitialConfigGatherTask.parseXml(InitialConfigGatherTask.java:107)
at com.sap.sup.admin.scheduler.task.remote.config.InitialConfigGatherTask.process(InitialConfigGatherTask.java:68)
at com.sap.sup.admin.scheduler.config.DataCollect.execute(DataCollect.java:138)
at com.sap.sup.admin.setup.AppCfgTasks.runInitialDataCollect(AppCfgTasks.java:57)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:305)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:263)
at com.sap.sup.admin.setup.SapCluster.setup(SapCluster.java:655)
at com.sap.sup.admin.setup.SapCluster.access$000(SapCluster.java:28)
at com.sap.sup.admin.setup.SapCluster$SetupRunner.run(SapCluster.java:903)
at java.lang.Thread.run(Thread.java:534).
Plz advise.
Thx in advance.#1.#00144F17012A00C700000018000066BD0004506CFD4B5C16#1214328943107#/Applications/AdminConsole/ConfigurationChangeReportingUpload#sap.com/tcwddispwda#com.sap.sup.admin.upload.configreport.xml.ConfigurationChangeHandler#J2EE_ADMIN#16932##XXXXX_SID_28888050#J2EE_ADMIN#0964c860421111dd94ec00144f17012a#Thread[Thread-83,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/Applications/AdminConsole/ConfigurationChangeReportingUpload#Plain###[7498] storeComponentVersion(...):ComponentVersion [SAP J2EE ENGINE 7.00][01200314690200004229][N/A][N/A]:Cannot insert/update/delete the component '[IComponent: key=1214257551084558, name=SAP J2EE ENGINE 7.00, internalVersion=7.00 PatchLevel 29172.450, ppmsId=01200314690200004229, date=Tue Jun 24 13:35:42 EDT 2008, status=[N], mod=[M], messageServer=XXXXX:3901, masterComponent=true].
I found this in application log
Edited by: Kobby bryant on Jun 24, 2008 7:39 PM -
SMD Installation Error in Managed Systems
We are installing SMD 7.11 in all our managed systems running on Aix 6.1, we are able to install in all the systems except one, which gives the error at the below step.
SAPVM.log
$ cat SAPVM.log
SAPCAR: processing archive /sapinst_sm/smd/SMD711_01_IM_AIX_PPC64/COMMON/INSTALL/SAPVM.SAR (version 2.01)
x sapjvm_5
x sapjvm_5/jre
x sapjvm_5/jre/bin
x sapjvm_5/jre/bin/java
x sapjvm_5/jre/bin/keytool
x sapjvm_5/jre/bin/policytool
x sapjvm_5/jre/bin/kinit
x sapjvm_5/jre/bin/klist
x sapjvm_5/jre/bin/ktab
x sapjvm_5/jre/bin/rmiregistry
x sapjvm_5/jre/bin/rmid
x sapjvm_5/jre/bin/tnameserv
x sapjvm_5/jre/bin/orbd
x sapjvm_5/jre/bin/servertool
x sapjvm_5/jre/bin/unpack200
x sapjvm_5/jre/bin/pack200
x sapjvm_5/jre/lib
x sapjvm_5/jre/lib/applet
x sapjvm_5/jre/lib/ppc64
x sapjvm_5/jre/lib/ppc64/server
x sapjvm_5/jre/lib/ppc64/server/libjvm.so
SAPCAR: checksum error in sapjvm_5/jre/lib/ppc64/server/libjvm.so (error 12). No such file or directory
$
sapinst_dev.log
INFO 2011-11-21 13:46:11.588
CJSlibModule::writeInfo_impl()
Output of /tmp/sapinst_exe.13631492.1321899048/SAPCAR -x -v -i -f /sapinst_sm/smd/SMD711_01_IM_AIX_PPC64/COMMON/INSTALL/SAPVM.SAR, sapjvm_5:
SAPCAR: processing archive /sapinst_sm/smd/SMD711_01_IM_AIX_PPC64/COMMON/INSTALL/SAPVM.SAR (version 2.01)
x sapjvm_5
x sapjvm_5/jre
x sapjvm_5/jre/bin
x sapjvm_5/jre/bin/java
x sapjvm_5/jre/bin/keytool
x sapjvm_5/jre/bin/policytool
x sapjvm_5/jre/bin/kinit
x sapjvm_5/jre/bin/klist
x sapjvm_5/jre/bin/ktab
x sapjvm_5/jre/bin/rmiregistry
x sapjvm_5/jre/bin/rmid
x sapjvm_5/jre/bin/tnameserv
x sapjvm_5/jre/bin/orbd
x sapjvm_5/jre/bin/servertool
x sapjvm_5/jre/bin/unpack200
x sapjvm_5/jre/bin/pack200
x sapjvm_5/jre/lib
x sapjvm_5/jre/lib/applet
x sapjvm_5/jre/lib/ppc64
x sapjvm_5/jre/lib/ppc64/server
x sapjvm_5/jre/lib/ppc64/server/libjvm.so
SAPCAR: checksum error in sapjvm_5/jre/lib/ppc64/server/libjvm.so (error 12). No such file or directory
TRACE 2011-11-21 13:46:11.590
FSPath(/tmp/sapinst_exe.13631492.1321899048/SAPCAR) done
TRACE 2011-11-21 13:46:11.590
ChildApplication(/tmp/sapinst_exe.13631492.1321899048/SAPCAR).getReturnCode(true)
TRACE 2011-11-21 13:46:11.591 [syuxctask.cpp:560]
CUnixProcessManager::waitpid(pid_t pid, int * pStatus, int options)
lib=syslib module=syslib
Child process 22151394 returned 12
TRACE 2011-11-21 13:46:11.592
FSPath(/tmp/sapinst_exe.13631492.1321899048/SAPCAR) done
TRACE 2011-11-21 13:46:11.592
ChildApplication(/tmp/sapinst_exe.13631492.1321899048/SAPCAR).getReturnCode() done: 12
TRACE 2011-11-21 13:46:11.593
FSPath(/tmp/sapinst_exe.13631492.1321899048/SAPCAR) done
TRACE 2011-11-21 13:46:11.594
ChildApplication(/tmp/sapinst_exe.13631492.1321899048/SAPCAR).getStatus()
TRACE 2011-11-21 13:46:11.595
FSPath(/tmp/sapinst_exe.13631492.1321899048/SAPCAR) done
TRACE 2011-11-21 13:46:11.595
ChildApplication(/tmp/sapinst_exe.13631492.1321899048/SAPCAR).getStatus() done: TST_FINISHED
TRACE 2011-11-21 13:46:11.596
FSPath(/tmp/sapinst_exe.13631492.1321899048/SAPCAR) done
TRACE 2011-11-21 13:46:11.596
Returncode of /tmp/sapinst_exe.13631492.1321899048/SAPCAR: 12
TRACE 2011-11-21 13:46:11.597
FSPath(/tmp/sapinst_exe.13631492.1321899048/SAPCAR) done
ERROR 2011-11-21 13:46:11.598
CJSlibModule::writeError_impl()
MUT-03011 Execution of the command "/tmp/sapinst_exe.13631492.1321899048/SAPCAR -x -v -i -f /sapinst_sm/smd/SMD711_01_IM_AIX_PPC64/COMMON/INSTALL/SAPVM.SAR, sapjvm_5" finished with return code 12. Output:
SAPCAR: processing archive /sapinst_sm/smd/SMD711_01_IM_AIX_PPC64/COMMON/INSTALL/SAPVM.SAR (version 2.01)
x sapjvm_5
x sapjvm_5/jre
x sapjvm_5/jre/bin
x sapjvm_5/jre/bin/java
x sapjvm_5/jre/bin/keytool
x sapjvm_5/jre/bin/policytool
x sapjvm_5/jre/bin/kinit
x sapjvm_5/jre/bin/klist
x sapjvm_5/jre/bin/ktab
x sapjvm_5/jre/bin/rmiregistry
x sapjvm_5/jre/bin/rmid
x sapjvm_5/jre/bin/tnameserv
x sapjvm_5/jre/bin/orbd
x sapjvm_5/jre/bin/servertool
x sapjvm_5/jre/bin/unpack200
x sapjvm_5/jre/bin/pack200
x sapjvm_5/jre/lib
x sapjvm_5/jre/lib/applet
x sapjvm_5/jre/lib/ppc64
x sapjvm_5/jre/lib/ppc64/server
x sapjvm_5/jre/lib/ppc64/server/libjvm.so
SAPCAR: checksum error in sapjvm_5/jre/lib/ppc64/server/libjvm.so (error 12). No such file or directory
TRACE 2011-11-21 13:46:11.599 [iaxxejsbas.hpp:413]
handleException<ESAPinstJSError>()
Converting exception into JS Exception EJSException.
The logInquirerOutStepError-NW_DiagnosticsAgent-ind-ind-ind-ind-0-0-NW_DiagnosticsAgent_GetSid-ind-ind-ind-ind-1-0-NW_getJavaHome-ind-ind-ind-ind-4-0.xml says are below
$ cat logInquirerOutStepError-NW_DiagnosticsAgent-ind-ind-ind-ind-0-0-NW_DiagnosticsAgent_GetSid-ind-ind-ind-ind-1-0-NW_getJavaHome-ind-ind-ind-ind-4-0.xml
<?xml version="1.0" encoding="utf-8"?>
<stepMessages componentTyp="NW_getJavaHome|ind|ind|ind|ind" componentInstance="|NW_DiagnosticsAgent|ind|ind|ind|ind|0|0|NW_DiagnosticsAgent_GetSid|ind|ind|ind|ind|1|0|NW_getJavaHome|ind|ind|ind|ind|4|0" step="unpackSAPJVM">
<configuration>
<property name="CPUCount">16</property>
<property name="CPUFamily">IBM6000</property>
<property name="INSTPARA_DB">IND</property>
<property name="INSTPARA_PRODUCT">NetWeaver</property>
<property name="INSTPARA_PRODUCT_VERSION">06</property>
<property name="INSTPARA_START_DIR">/tmp/sapinst_instdir/SMD_NW711/INSTALL/STANDALONE/SMD/INST</property>
<property name="OSType">AIX_64</property>
<property name="OSUname">AIX palatine 1 6 00F65A064C00</property>
<property name="OSVersion"></property>
<property name="RamSize">20480</property>
<property name="RealOSBits">64</property>
<property name="SAPInst ABI version">712</property>
<property name="SAPInst latest changelist">1068035</property>
<property name="SAPInst used source locations">/bas/710_REL/src</property>
<property name="SAPInst version of used kernel">710_REL</property>
<property name="SwapSize">20480</property>
</configuration>
<firstErrorMessage>
<message type="error" timestamp="2011-11-21 13:46:11.992">Could not get value for property .</message>
</firstErrorMessage>
<lastErrorMessage>
<message type="error" timestamp="2011-11-21 13:46:11.992">Could not get value for property .</message>
</lastErrorMessage>
<messageStack>
<message type="trace" timestamp="2011-11-21 13:46:11.990"> Call block:CallBackInCaseOfAnErrorDuringStepExecution function:CallTheLogInquirer is validator: true</message>
<message type="warning" timestamp="2011-11-21 13:46:11.992">Could not get property IDs of the JavaScript object.</message>
<message type="error" timestamp="2011-11-21 13:46:11.992">Could not get value for property .</message>
<message type="trace" timestamp="2011-11-21 13:46:12.97">Target node does not exists and (mode & ISyNode::MISSING) ==> I will copy/move.</message>
<message type="trace" timestamp="2011-11-21 13:46:12.97">Moved /tmp/sapinst_instdir/SMD_NW711/INSTALL/STANDALONE/SMD/INST/logInquirerOutStepError-NW_DiagnosticsAgent-ind-ind-ind-ind-0-0-NW_DiagnosticsAgent_GetSid-ind-ind-ind-ind-1-0-NW_getJavaHome-ind-ind-ind-ind-4-0.xml to /tmp/sapinst_instdir/SMD_NW711/INSTALL/STANDALONE/SMD/INST/logInquirerOutStepError-NW_DiagnosticsAgent-ind-ind-ind-ind-0-0-NW_DiagnosticsAgent_GetSid-ind-ind-ind-ind-1-0-NW_getJavaHome-ind-ind-ind-ind-4-0.1.xml</message>
<message type="trace" timestamp="2011-11-21 13:46:12.142">A child process has been started. Pid = 22151402</message>
<message type="trace" timestamp="2011-11-21 13:46:12.215">Child process 22151402 returned 0 </message>
<message type="trace" timestamp="2011-11-21 13:46:12.244">A child process has been started. Pid = 22151404</message>
<message type="trace" timestamp="2011-11-21 13:46:12.327">Child process 22151404 returned 255 </message>
<message type="warning" timestamp="2011-11-21 13:46:12.328">Could not run /usr/sbin/lsattr -l aio0 -E -O successfully. Either the return code was != 0 or the process terminated abnormally.</message>
<message type="trace" timestamp="2011-11-21 13:46:12.358">A child process has been started. Pid = 22151406</message>
<message type="trace" timestamp="2011-11-21 13:46:12.457">Child process 22151406 returned 0 </message>
</messageStack>
</stepMessages>
$
Has anyone faced this issue?
RegardsThank you Ken
We have got enough space under /tmp, the issue is resolved after a reboot of the server, we rebooted the server and then started the same installation it worked.
Now again, when I try to install the hostagent, it gives me the below error:
INFO 2011-11-23 09:10:51.414 [syuxcaccmg.cpp:305]
bool CSyAccountMgtImpl::isExisting(ISyAccountMgt::eAccountType accountType, iastring sName)
lib=syslib module=syslib
Account 206 already exists.
INFO 2011-11-23 09:10:51.416 [syuxcaccmg.cpp:305]
bool CSyAccountMgtImpl::isExisting(ISyAccountMgt::eAccountType accountType, iastring sName)
lib=syslib module=syslib
Account sapinst already exists.
WARNING 2011-11-23 09:10:51.427 [syuxcgroup.cpp:146]
<anonymous namespace>::for_each_user lib=syslib module=syslib
System call failed. Error 3 (No such process) in execution of system call 'getpwent' with parameter (), line (143) in file (syuxcgroup.cpp), stack trace: iaxxejsctl.cpp: 272: EJS_ControllerImpl::executeScript()
iaxxejsbas.hpp: 450: EJS_Base::dispatchFunctionCall()
iaxxejsexp.cpp: 178: EJS_Installer::invokeModuleCall()
syxxbuser.cpp: 242: *** syslib entry point CSyUser::isMember(const iastring & 'sapinst') const ***
syuxcuser.cpp: 664: bool CSyUserImpl::isMember(const iastring & sName) const
syuxcgroup.cpp: 404: PSyAccountIterator CSyGroupImpl('212')::getMembers() const
syuxcgroup.cpp: 102: <anonymous namespace>::for_each_user
INFO 2011-11-23 09:10:51.439 [syuxcaccmg.cpp:237]
bool CSyAccountMgtImpl::isExisting(ISyAccountMgt::eAccountType accountType, iastring sName)
lib=syslib module=syslib
Account sapadm already exists.
INFO 2011-11-23 09:10:51.449 [syuxcaccmg.cpp:305]
bool CSyAccountMgtImpl::isExisting(ISyAccountMgt::eAccountType accountType, iastring sName)
lib=syslib module=syslib
Account 206 already exists.
INFO 2011-11-23 09:10:53.189 [syuxcpath.cpp:371]
CSyPath::createFile() lib=syslib module=syslib
Creating file /tmp/sapinst_instdir/SMD_NW711/LM/INST/services.SAPtmp.
WARNING[E] 2011-11-23 09:10:54.72 [syxxc_services_entry.cpp:286]
CSyServicesEntryParser::parsePort() const lib=syslib module=syslib
FSL-03009 Unexpected token in /etc/services entry 'x11 6000-6063/tcp # X Window System' at line 7633, column 7: Conversion of port number string to integer failed.
WARNING[E] 2011-11-23 09:10:54.73 [syxxc_services_entry.cpp:286]
CSyServicesEntryParser::parsePort() const lib=syslib module=syslib
FSL-03009 Unexpected token in /etc/services entry 'x11 6000-6063/udp # X Window System' at line 7634, column 7: Conversion of port number string to integer failed.
WARNING[E] 2011-11-23 09:10:54.91 [syxxc_services_entry.cpp:286]
CSyServicesEntryParser::parsePort() const lib=syslib module=syslib
FSL-03009 Unexpected token in /etc/services entry 'ircu 6665-6669/tcp # IRCU' at line 7809, column 7: Conversion of port number string to integer failed.
WARNING[E] 2011-11-23 09:10:54.91 [syxxc_services_entry.cpp:286]
CSyServicesEntryParser::parsePort() const lib=syslib module=syslib
FSL-03009 Unexpected token in /etc/services entry 'ircu 6665-6669/udp # IRCU' at line 7810, column 7: Conversion of port number string to integer failed.
INFO 2011-11-23 09:10:54.521 [syuxccuren.cpp:1068]
INFO 2011-11-23 09:11:36.615
CJSlibModule::writeInfo_impl()
Output of /tmp/sapinst_exe.10617084.1322057387/SAPCAR -x -v -i -R ./hostagent -f /sapinst_sm/smd/SMD711_K_UI_AIX_PPC64/DBINDEP/SAPHOSTAGENT.SAR,:
SAPCAR: processing archive /sapinst_sm/smd/SMD711_K_UI_AIX_PPC64/DBINDEP/SAPHOSTAGENT.SAR (version 2.01)
x hostagent.lst
x hostagent.mf
x hostexecstart
x installsapinit.sh
x ldappasswd
x ldapreg
x librfccm.o
WARNING[E] 2011-11-23 09:11:36.632
CJSlibModule::writeError_impl()
MUT-03010 Execution of the command "/tmp/sapinst_exe.10617084.1322057387/SAPCAR -x -v -i -R ./hostagent -f /sapinst_sm/smd/SMD711_K_UI_AIX_PPC64/DBINDEP/SAPHOSTAGENT.SAR," finished with status TST_ERROR.
WARNING[E] 2011-11-23 09:11:36.647
CJSlibModule::writeError_impl()
MUT-03010 Execution of the command "/tmp/sapinst_exe.10617084.1322057387/SAPCAR -x -v -i -R ./hostagent -f /sapinst_sm/smd/SMD711_K_UI_AIX_PPC64/DBINDEP/SAPHOSTAGENT.SAR," finished with status TST_ERROR.
WARNING 2011-11-23 09:11:36.887 [syixcsyinf.cpp:572]
<anonymous-namespace>::runLsattr lib=syslib module=syslib
Could not run /usr/sbin/lsattr -l aio0 -E -O successfully. Either the return code was != 0 or the process terminated abnormally.
ERROR 2011-11-23 09:11:37.26 [sixxcstepexecute.cpp:969]
FCO-00011 The step unpack with step key |NW_SAPHostAgent|ind|ind|ind|ind|0|0|unpack was executed with status ERROR .
WARNING 2011-11-23 09:11:37.106 [iaxxejshlp.cpp:150]
Could not get property IDs of the JavaScript object.
ERROR 2011-11-23 09:11:37.107 [iaxxejsctl.cpp:492]
FJS-00010 Could not get value for property .
WARNING 2011-11-23 09:11:37.400 [syixcsyinf.cpp:572]
<anonymous-namespace>::runLsattr lib=syslib module=syslib
Could not run /usr/sbin/lsattr -l aio0 -E -O successfully. Either the return code was != 0 or the process terminated abnormally.
Any idea on the above error? -
Setting up of Transports Management System in EP7.0
Hi Experts!!!!!
Can you please provide the documents or links for configuring the transport management system for EP 7.0 Systems.
Regards,
Vamshi.Vamshi,
These could be helpful.
http://help.sap.com/saphelp_nw04/helpdata/en/44/b4a0137acc11d1899e0000e829fbbd/frameset.htm
http://help.sap.com/printdocu/core/print46c/en/data/pdf/bcctstms/bcctstms.pdf
Reward points for handy posts!
Cheers,
Sandeep -
I can not make a "Byte Code Adapter Installation"
When I open meets both paragraphs in step Managed System Configuration is somewhat obscure situations that do not allow the automatic configuration Introscope agent and Introscope Manager
Please help to resolve a number of questions that might help me complete the setup :
1. Why has the status of Enterprise Manager : <No Enterprise Manager configured> ( see picture)
I set up Enterprise Manager in accordance with the installation instructions and complied with all the setting items . Since without any configuration can be associated with the appearance of this status ?
2 . Why Server Node is empty detail settings ?
JDK Location:
Enterprise Manager Host:
Enterprise Manager Port:
Introscope Agent Name:
Introscope Agent Profile:
Autoprobe Directives:
Wily Version:
Introscope Agent Version:
Introscope Agent Log Location:
3 . What a mistake ($ MC: DIAG_WILY_MSG: 032 : L), which appears when I click configuration "Configure Introscope Agent Setup ...", and what it can be linked ? ( see picture )
And the last question , which is also linked to the process of automatic configuration and refers to a phrase from the instruction (Introscope Version 9
Installation Guide For SAP July 2012) points out "Automated Installation of the Introscope Agent via SMD"
there is such an item:
2 . Deploy ISAGENTJ5 *. SCA which is the Introscope Java Agent 9 with SDM to Solution Manager. You may need to deploy also ISAGENT *. SCA which is Introscope Java Agent 8.
However, nowhere does it say where exactly ( on what the absolute path ) I must perform unloading and then what to do with this dischargeThe problem was resolved a small manipulation - on stage Basic Configuration,
point 3 "Configure CA Introscope"
I forgot to add to the list of CA Introscope Enterprise Managers link to my manager.
Thus it is necessary to take into account that the path should be correct (usually for linux - /usr/sap/ccms/apmintroscope) and the directory should be applied appropriate privileges.
Then in paragraph "Byte Code Adapter Installation" - there are all the necessary data, and it starts to work correctly -
Error in Managed system configuration.
Hi Folks,
In Solman 7.1 i am configuring my Java system in managed system configuration on the last phase of configuration which is "Check Configuration" i got the below error...
Can any one guide me on this....
I installed the Diagnostic agent as well as willy inter scope.
Regards,
Anil.check the note which describes your problem
1776959 - Solution Manager 7.1 Manged System configuration. Error: Timezone from managed system could not be retrieved: Timezone of J2EE Engine (GMT+01:00) does not match the timezone of the diagnostics agent (Europe/Berlin)
Resolution
Open the instance.properties file of the J2EE Engine on the managed system
Locate the parameter "-Duser.timezone=" and its value
If the -Duser.timezone is not set the JVM uses GMT
Set the -Duser.timezone parameter in the JVM of the SMD Agent. If there was no "-Duser.timezone in the J2EE's instance.properties file use the timezone that was indicated in the error message e.g. GMT+01:00 (from the above error message, this might differ on your environment) To do this:
Locate the smd.properties file (for newer agents the files is called: smdagent.properties)
The path is: .../usr/sap/<DiagnosticAgentSID>/SMDA<SYSNumber>/SMDAgent/smdagent.properties
The -Duser.timezone= parameter of the Diagnostics Agent and the SAP J2EE engine need to be set to the same timezone. That means the string needs to be the same for both parameters
e.g.
If the -Duser.timezone= parameter of the J2EE engine is set to -Duser.timezone="GMT+01:00"
set the Diagnostics Agent parameter to:
smdagent.javaParameters=-DP4ClassLoad=P4Connection -Xmx256m -Xms256m -Duser.timezone="GMT+01:00"
Restart the Agent
Re-run the "Configuration Check" in the "Managed System Configuration"
Please make sure that the time zone configuration is correct according to the SAP recommendations: http://wiki.sdn.sap.com/wiki/display/Basis/Timezone+changes+best+practices -
Technical Systems in Managed System Configuration greyed .
Hi,
I upgraded ST-SER to 701_2010_1 SP0 and in the process of upgrading
this tool I had to also patch other components like ABAP,BASIS etc as
pre-requisites for this.
As this involved all the components to be patched, I
executed the initial,Basic configuration in solman_setup and everything
is fine.
In Initial I executed only the read SLD and skipped the other steps as
the other steps have been already executed after install of solution
manager .
In Basic Configuration I have executed all steps and everything has
executed successfully.
The problem is in Managed system configuration.
I have the Wily Introscope Manager Console showing all the statistics
of Agents and all Agents are attached.
The problem I see is first thing is the technical setting in the
Managed system diagnostics are greyed why is it ?
Second is when I execute the Managed system Diagnostics configuration , the first step Wily host agent fails all other steps are okay.
The error in this step is "No connection to any Wily Enterprise Manager"
Appreciate any advise.
Thanks,
MisbaHello Diego,
I started getting this error only after I upgraded the tools, even now the Wily is up and running and I can see the dashboard with all the live diagnostics graphs and statistics for ABAP & JAVA. All the steps have executed successfully except this one step. Even trusted RFC's are okay. This was an established system with all configurations.
So I am surprised what I am missing. Can you please explain to me more about how I can see " http://<ip>:<port>/SMD under "managed systems" ->Introscope Agent ".
All Agents are attached and in Agent adminstration I can see all the Agents online.
Thanks,
Misba
Maybe you are looking for
-
Error msg Could not find the main class.Program will exit. in jar execution
Hello, I have created a jar so that I can used it in the webapp. but when I click on it it says "Could not find the main class.Program will exit." I searched a lot in the net and found that it has to do with the manifest file. I even updated the mani
-
I got a new 8900 replacement (under warranty) and I know this worked on my old phone but somehow it's not working on this new one. Inside the Call log, menu >> options>>general options>> Show "My Number " = NO But my number still shows up whenever i'
-
Who else has been losing battery on their new iPhone 5
-
Hello, I want to populate value field(VALUT) at customer line item to store some date in that field but i could not populate that at customer line item as i am able to do it only at GL line item.Please let me know fi you have any suggestio
-
Controlling amount of space inserted with tab key
Currently I get a style="margin-left: 40px;" added when I press the tab key. How can I change that amount to an additional 24px for each successive pressing of the tab key?