Solution Manager 7.1 Basic Configuration error

Hi guys
I'm having problems with accessing the basic config wizard via spro, i'm also having the same issue trying to run "solman_setup" and "workcenter". For both issues i get "Internet Explore cannot open the webpage". The ITS is activated along with the ther services. If there's any settings that I"ve missed your help will be very much appreciated and please let me know if you need more information from me.
Thank you.

Hi ,
I suppose you are not having problems with the FQHN in other web screens, so DNS should be fine.
if this is a Microsoft Windows system I would try this workaround.
note 677118
(*) One quick solution is to update the hosts file on each
     work station. (Only an option for small installations.)
     File:          \WINNT\system32\drivers\etc\hosts
     Add new line: 10.17.73.210   hostname.domain.ext
     This must be done per workstation.
regards, Javier

Similar Messages

Solman 4.0 basic configuration error

Hi Experts,
While i'm performing initial configuration part 2 (auto configuration) in solman 4.0, i'm getting some error. Plz help me to fix
Basic Configuration Error
Message no : IMG_FASTCONF015
Diagnosis
Solution Manager Basic Configuration Error
Procedure
check the messages in application log.
object: SOLAR
subobject: SOLMAN_CONFIG
Thanks
Ram

Hi,
Thanks for your quick reply
Problem class important------------Basic Configuration error
Technical Data
Message type ---------- E (Error)
Message Class---------- IMG_FASTCONF (IMG Quick Configuration Error Messages)
Message number-------015
Message variable 1-------
Message variable 2-------
Message variable 3-------
Message variable 4-------
Message Attributes
Level of detail ----------
Problem class-------- 2 (important)
Sort criterion ---------
Number--------------------1
Thanks
Ram

Solution Manager 4.0 Re-Configuration

hi everyone,
I am trying to re configure my Solution manager 4.0. I have deleted my previous business client 100, and created a new one using
client copy 000. I now have a fresh client 100 in my solman, SOLCLNT100. My problem now is, in tcode SMSY, there is still
existing systems which i cannot delete. Whenever i try to delete my QAS in the systems tab, it shows me this message,
You cannot delete the system as long as it is still used in logical components. How do i delete this logical component assignment if
i have deleted everything already including my systems in tcode DSWP/SOLUTION_MANAGER? I want to delete this logical assignment
so i can re configure my SOLMAN.
many thanks

Dear Raguraman,
I m getting same error in Solman.I m trying to implimnet that note in solman but giving message This note is note valid correction instruction.
i m pasting the dump here.
Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED
Exception              CX_SY_REF_IS_INITIAL
Date and Time          07.06.2010 13:00:37
Short text
Access via 'NULL' object reference not possible.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSMSY_ACTUALIZE_DATA" had to be terminated because
it has
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
caught in
procedure "SMSYAD_GET_DATA_FROM_LCR" "(FUNCTION)", nor was it propagated by a
RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
You attempted to use a 'NULL' object reference (points to 'nothing')
access a component (variable: "ACCESSOR").
An object reference must point to an object (an instance of a class)
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.
How to correct the error
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"OBJECTS_OBJREF_NOT_ASSIGNED" "CX_SY_REF_IS_INITIAL"
"SAPLSMSY_ACTUALIZE_DATA" or "LSMSY_ACTUALIZE_DATAU14"
"SMSYAD_GET_DATA_FROM_LCR"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
The exception must either be prevented, caught within proedure
"SMSYAD_GET_DATA_FROM_LCR" "(FUNCTION)", or its possible occurrence must be
declared in the
RAISING clause of the procedure.
|    To prevent the exception, note the following:
Please suggest me how to solve this.
Regards
Ashok

The URL in Solution Manager for SRM Standard Configuration

Hi Experts,
We all know that after SRM 5.0, all standard configuration guid are presented as URL in SAP Solution Manager like below:
http://help.sap.com/SCENARIOS_BUS2005/helpdata/EN/ac/136341acd3001de10000000a155106/frameset.htm
My question is: is there any other way to find these configuration url? If I don't have solution manager enviroment, how can I find these urls? Many thanks.

Hi Dinesh,
Thank you for your reply. I checked this site before(maybe one year ago). At that time, there was no configuration guide for 5.0. Now it's great...
My question is there any place contained those urls in solution manager. I can't find those urls in any configuration guide. SAP make such a configuration online help, why it doesn't open for those peopel who don't use solution manager. It confused me...
Anyway, thank you very much for your reply.

Solution Manager 4.0 SR1 installation error

Hi there,
I am getting eblow error for Solution Manager 4.0 SR1 installation on aix-ora.
Any help much appreciated. Thanks.
Regards
Anil
INFO       2008-05-19 14:15:56 [syuxccuren.cpp:119]
           CSyCurrentProcessEnvironmentImpl::removeEnvironmentVariable
Removed environment variable SAPDATA_HOME from current process environment.
INFO       2008-05-19 14:15:58 [iaxxgenimp.cpp:630]
           showDialog()
Execute step PrepareOraCreateTablespace of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0.
ERROR      2008-05-19 14:15:59 [iaxxejsbas.cpp:178]
           EJS_ErrorReporter
FJS-00003 TypeError: sapdataNodeInfo[idx] has no properties (in script NW_Onehost|ind|ind|ind|ind, line 51567: ???)
ERROR      2008-05-19 14:15:59 [iaxxgenimp.cpp:728]
           showDialog()
FCO-00011 The step PrepareOraCreateTablespace with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|PrepareOraCreateTablespace was executed with status ERROR .

Why not use SR3 release? It contains MANY more fixes and will prevent you from the need of installing a bunch of support packages after your installation...
For your error: please check ora_sql_result.log
Markus

Configuration SAP Solution Manager TCode-SOLMAN_SETUP Initial Configuration

Hi,
I am running the TCode: Solman_Setup for Basic Configuration in Solman 7.0 EHP1.
In "Initial Configuration" -> Technical Configuration after clicking Configure button facing following error. Pls Suggest.
System SM1 does not exist & E::000
Regards
Praveen K

E::000 basically means that the system is trying to show an error message "000" from a specific error message set.This problem is caused by a program error. If the authorization check fails, no relevant error message is displayed.
have you created any system by the name SM1 in SMSY?
Regards,
Rajeev

Solution Manager Self check gives an error

Hi all,
After installing diagnostics on SM 4.0 SPS 13 i have run a self check.
Everything is ok except for one issue. This is an issue with a task from the task scheduler:
3084] The Task Collect Configuration Data (nw01) failed during its processing!
[EXCEPTION]
com.sap.sup.admin.scheduler.exception.FatalTaskExecutionException: 1 error(s) occured during abap configuration data collect on monitored host [nw01]. Check logs for details.
     at com.sap.sup.admin.scheduler.task.remote.config.ConfigGatherTask.process_AbapConfiguration(ConfigGatherTask.java:340)
     at com.sap.sup.admin.scheduler.task.remote.config.ConfigGatherTask.process(ConfigGatherTask.java:148)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.smd.server.exec.asio.AsioInvocationHandler$1.call(AsioInvocationHandler.java:87)
     at com.sap.smd.server.util.concurrent.FutureResult$1.run(FutureResult.java:90)
     at com.sap.smd.server.exec.asio.AsioInvocationHandler$AsioRunner.run(AsioInvocationHandler.java:266)
     at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:45)
     at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:785)
     at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.Exception: Error collecting abap system [sid:NW1] [install:0020255009].
     at com.sap.sup.admin.upload.abapconfig.provider.AbapConfigurationProvider.collectAbapConfigurationContent(AbapConfigurationProvider.java:332)
     at com.sap.sup.admin.upload.abapconfig.provider.AbapConfigurationProvider.collectAbapConfiguration(AbapConfigurationProvider.java:266)
     at com.sap.sup.admin.upload.abapconfig.provider.AbapConfigurationProvider.collectAndStoreAbapConfiguration(AbapConfigurationProvider.java:199)
     at com.sap.sup.admin.scheduler.task.remote.config.ConfigGatherTask.process_AbapConfiguration(ConfigGatherTask.java:287)
     ... 11 more
Caused by: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Table does not exist in database.
     at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:455)
     at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1442)
     at com.sap.mw.jco.JCO$Client.execute(JCO.java:3979)
     at com.sap.mw.jco.JCO$Client.execute(JCO.java:3416)
     at com.sap.sup.admin.upload.abapconfig.provider.AbapConfigurationProvider.collectAbapConfigurationContent(AbapConfigurationProvider.java:321)
     ... 14 more
Category: /Applications/AdminConsole/Scheduler
Location: com.sap.sup.admin.scheduler.JmsScheduler
Application: sap.com/tcwebadministratorscheduler~ejb
Thread: SAPEngine_Application_Thread[impl:3]_33
Data Source: D:\usr\sap\SO1\DVEBMGS01\j2ee\cluster\server0\log\defaultTrace.trc
Message ID: 00188BF8D663002D0000002B00000BC0000443721D1DD31C
Argument Objects: com.sap.sup.admin.scheduler.exception.FatalTaskExecutionException: 1 error(s) occured during abap configuration data collect on monitored host [nw01]. Check logs for details.
at com.sap.sup.admin.scheduler.task.remote.config.ConfigGatherTask.process_AbapConfiguration(ConfigGatherTask.java:340)
at com.sap.sup.admin.scheduler.task.remote.config.ConfigGatherTask.process(ConfigGatherTask.java:148)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.smd.server.exec.asio.AsioInvocationHandler$1.call(AsioInvocationHandler.java:87)
at com.sap.smd.server.util.concurrent.FutureResult$1.run(FutureResult.java:90)
at com.sap.smd.server.exec.asio.AsioInvocationHandler$AsioRunner.run(AsioInvocationHandler.java:266)
at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:45)
at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:785)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.Exception: Error collecting abap system [sid:NW1] [install:0020255009].
at com.sap.sup.admin.upload.abapconfig.provider.AbapConfigurationProvider.collectAbapConfigurationContent(AbapConfigurationProvider.java:332)
at com.sap.sup.admin.upload.abapconfig.provider.AbapConfigurationProvider.collectAbapConfiguration(AbapConfigurationProvider.java:266)
at com.sap.sup.admin.upload.abapconfig.provider.AbapConfigurationProvider.collectAndStoreAbapConfiguration(AbapConfigurationProvider.java:199)
at com.sap.sup.admin.scheduler.task.remote.config.ConfigGatherTask.process_AbapConfiguration(ConfigGatherTask.java:287)
... 11 more
Caused by: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Table does not exist in database.
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:455)
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1442)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3979)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3416)
at com.sap.sup.admin.upload.abapconfig.provider.AbapConfigurationProvider.collectAbapConfigurationContent(AbapConfigurationProvider.java:321)
... 14 more
Arguments: com.sap.sup.admin.scheduler.exception.FatalTaskExecutionException: 1 error(s) occured during abap configuration data collect on monitored host [nw01]. Check logs for details.
at com.sap.sup.admin.scheduler.task.remote.config.ConfigGatherTask.process_AbapConfiguration(ConfigGatherTask.java:340)
at com.sap.sup.admin.scheduler.task.remote.config.ConfigGatherTask.process(ConfigGatherTask.java:148)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.smd.server.exec.asio.AsioInvocationHandler$1.call(AsioInvocationHandler.java:87)
at com.sap.smd.server.util.concurrent.FutureResult$1.run(FutureResult.java:90)
at com.sap.smd.server.exec.asio.AsioInvocationHandler$AsioRunner.run(AsioInvocationHandler.java:266)
at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:45)
at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:785)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.Exception: Error collecting abap system [sid:NW1] [install:0020255009].
at com.sap.sup.admin.upload.abapconfig.provider.AbapConfigurationProvider.collectAbapConfigurationContent(AbapConfigurationProvider.java:332)
at com.sap.sup.admin.upload.abapconfig.provider.AbapConfigurationProvider.collectAbapConfiguration(AbapConfigurationProvider.java:266)
at com.sap.sup.admin.upload.abapconfig.provider.AbapConfigurationProvider.collectAndStoreAbapConfiguration(AbapConfigurationProvider.java:199)
at com.sap.sup.admin.scheduler.task.remote.config.ConfigGatherTask.process_AbapConfiguration(ConfigGatherTask.java:287)
... 11 more
Caused by: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Table does not exist in database.
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:455)
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1442)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3979)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3416)
at com.sap.sup.admin.upload.abapconfig.provider.AbapConfigurationProvider.collectAbapConfigurationContent(AbapConfigurationProvider.java:321)
... 14 more
DSR Component: n/a
DSR Transaction: 36b0a6f2c04711dca06700188bf8d663
DSR User: n/a
Message Code: n/a
Session: 0
Transaction: n/a
User: J2EE_GUEST
Host: so1
System: SO1
Instance: 01
Node: Server 0 1_17087
Regards,
Koen Engelen

Hi All,
Can anybody please help me with my question?
Regards,
Koen

Trying to open solution manager and get the following error

SAPinst is getting started.
Please be patient ...
starting gui server process:
sapinstport: 21200
guiport    : 21212
guistart   : true
command    : "C:\Program Files\Java\j2re1.4.2_12/bin\javaw.exe" -cp "D:/Profiles/MIKERA/LOCALS1/Temp/sapinst_exe.2680.1191283370\jar\instgui.jar;D:/Profiles/MIKERA/LOCALS1/Temp/sapinst_exe.2680.1191283370\jar\inqmyxml.jar" -Xmx256M -Dsun.java2d.noddraw=true SDTServer config=jar:sdtserver.xml guiport=21212 sapinsthost=localhost sapinstport=21200 guistart=true
guiengine: call to bind() for socket 21200 1804 failed . No error
103 guiengine.connection.failed 21200, 881
Exit status of child: 1

Hi Mike,
seems like the gui can't bind to the tcp socket. Try killing all processes or reboot the server and try again. If it still fails run a netstat -an command to see what application is blocking the socket/port.
Thomas

Solution Manager 7.1 Integration into SAP Landscape

Hi All
I have a few questions for all the SAP Solution Manager experts out there and for anyone that would like to take a stab at these questions. An organization would like to implement a 3 system landscape for the following SAP Applications; SAP ERP, SAP CRM, SAP SRM, SAP Portal, SAP XI, SAP BI (SAP BW and SAP BOBJ) as well as SAP Solution Manager. They want to use all the functionality that is available in Solution Manager. The questions that I pose is as follows;
     1. How many Solution Manager systems must one implement? A 3 system landscape or will a 2 system landscape suffice? Bearing in mind that    functionality such as CHARM will be implemented.
     2. Where will the productive SLD reside? How would this SLD connect to the Solution Manager Systems?
     3. To which Solution Manager System will all the diagnostic agents connect to?
Your expert input would gladly be appreciated and points awarded accordingly.
Regards
Deen

Hi Deena,
I good approach would be to use a two system landscape.
Where - all sandbox and development systems are connected to develpoment solman.
and - all other systems, like quality, pre-prod, and prod are connected to production solman.
For CHARM, this is sufficient. Keep the hardware specs on the higher side of production solman.
You should use a separate SLD instance on your solution manager. WHY, incase you need to update the SP level, as SLD needs to be on the highest level, outage from SOLMAN or PI would be avoided.
You can also use, SLD of Solution manager, SYNC you dev sld with prod sld - uni directional sync - eg for stack generation.
SLD connect to your solution manager during solman_setup basic configuration and preparation of your landscape through LMDB.
Check.
SLD and LMDB Topology: Replacing the Source SLD for the LMDB
https://help.sap.com/saphelp_sm71_sp05/helpdata/en/a5/971735dd184f5c8d943c6cf423d13a/content.htm
Connect diagnostic agents to your producitve solution manager.
For more please reply back.
Good Luck !!
Regards,
Divyanshu

Solution Manager EHP 1 SP22 - DBA Cockpit Configuration Wizard

Hi,
When trying to "Configure DBA Cockpit" in Managed System Configuration ,I got the below error .
We are on Oracle 10.2.0.4.0 and Solution Manager SP22.
Database history :Not supported for this DB platform
Extractors activation :The DB performance warehouse is not available, thus the DB extractors were not activated
Please let me know if i need to perform any more additional steps.
Thanks in advance.....
Srini

"Database Performance Warehouse was not set up"
"Not supported for this DB platform"
For Oracle databases there is no support for Database Performance Warehouse in EHP1. With EHP2 the Oracle platform will be supported as well with some reports in the Solution Manager UI.
Basically the database performance warehouse is a project to collect and extract performance data to the SAP Solution Manager BI system. Once the data was loaded in to this BI you can use DBA Cockpit for detailed analysis. In EHP2 of SAP Solution Manager you will be able to also use the SAP Solution Manager UIs to analyze the database performance and workload.
If you are more interested in this feature you are very welcome to have a look at some articles available in SDN:
https://www.sdn.sap.com/irj/sdn/db6
For now you have full support for DB2 for LUW and MS SQL Server platforms and a more limited set of reports for SAP MaxDB and DB2/z.
I hope this clarifies your question.

SMD Configuration on MDM 7.1 with Solution Manager 7.01 SP19

Hi,
Kindly let me know if someone has faced issue with configuring SMD on SMD 7.1 with Solution Manager 7.01 SP19. Presently I have configured that and System is being shown in Wily Introscope Webview but Saposcol is greyed out in that.
Also system is not showing any data in Introscope Dashboard. Any guess for this?
Earlier while I was configuring SMD, error related to null installation directory (...Invalid root directory: /usr/sap/SID/null ) were occuring. After that when I created a softlink for saposcol service from /usr/sap/hostctrl/exe/saposcol to /usr/sap/SMD/SMDA97/exe.
Still no data and still in SMD Agent logs saposcol service warning is there.
Thanks & Regards,
Manish Singh

Hi Jansi,
Thanks for the reply..
Here is our scenario. SAPOSCOL was not there in /usr/sap/SMD/SMDA97/exe first place. So I made the softlink from /usr/sap/hostctrl/exe/saposcol to /usr/sap/SMD/SMDA97/exe and than re-ran setup again but still of no use.
Our Soltuion Manager saposcol version and MDM saposcol version is same. Below is the SMD Agent log of MDM server:
Apr 20, 2011 2:36:19 PM [Thread[Thread-22,5,main]] Error      com.sap.smd.wily.hostagent.config.AgentConfigVO - finalizeDestination(): Initialization failed
[EXCEPTION]
com.sap.smd.wily.hostagent.PermanentException: Error: cannot connect to destination SapHostControl_Default. Probably saphostctrl is not installed. This error can be ignored if saposcol is available.
at com.sap.smd.wily.hostagent.saphostcontrol.SapHostControlDestination.open(SapHostControlDestination.java:98)
at com.sap.smd.wily.hostagent.config.AgentConfigVO.finalizeDestination(AgentConfigVO.java:85)
at com.sap.smd.wily.hostagent.config.AgentConfigXmlHandler.endElement(AgentConfigXmlHandler.java:174)
at com.sap.engine.lib.xml.parser.handlers.SAXDocHandler.endElement(SAXDocHandler.java:156)
at com.sap.engine.lib.xml.parser.XMLParser.scanEndTag(XMLParser.java:1953)
at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1846)
at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2442)
at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1843)
at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2845)
at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:165)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245)
at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java:260)
at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:271)
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at com.sap.smd.wily.hostagent.config.AgentConfigParser.parseXml(AgentConfigParser.java:59)
at com.sap.smd.wily.hostagent.SapAgent.loadConfiguration(SapAgent.java:430)
at com.sap.smd.wily.hostagent.SapAgent.start(SapAgent.java:93)
at com.sap.smd.wily.hostagent.WilyHostService.startAgent(WilyHostService.java:118)
at com.sap.smd.wily.hostagent.WilyHostServicep4_Skel.dispatch(WilyHostServicep4_Skel.java:168)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:721)
at java.lang.Thread.run(Thread.java:664)
Caused by: javax.xml.rpc.soap.SOAPFaultException: Method 'SOAP-ENV:Envelope' not implemented: method name or namespace not recognized
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.buildFaultException(MimeHttpBinding.java:747)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.processDocumentFault(MimeHttpBinding.java:870)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1451)
at com.sap.smd.agent.wsclients.saposcol.SAPOscolStub.getCpuConsumption(SAPOscolStub.java:142)
at com.sap.smd.agent.wsclients.saposcol.SAPOscolStub.getCpuConsumption(SAPOscolStub.java:157)
at com.sap.smd.wily.hostagent.saphostcontrol.SapHostControlDestination.open(SapHostControlDestination.java:94)
... 25 more
Apr 20, 2011 2:36:19 PM [Thread[Thread-22,5,main]] Warning    com.sap.smd.wily.hostagent.SapAgent - startActions(): Action SAPOsColWs
[EXCEPTION]
com.sap.smd.wily.hostagent.TransientException: Destination not available:SapHostControl_Default
at com.sap.smd.wily.hostagent.saphostcontrol.SapHostControlAction.init(SapHostControlAction.java:74)
at com.sap.smd.wily.hostagent.SapAgent.startActions(SapAgent.java:396)
at com.sap.smd.wily.hostagent.SapAgent.start(SapAgent.java:94)
at com.sap.smd.wily.hostagent.WilyHostService.startAgent(WilyHostService.java:118)
at com.sap.smd.wily.hostagent.WilyHostServicep4_Skel.dispatch(WilyHostServicep4_Skel.java:168)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:721)
at java.lang.Thread.run(Thread.java:664)
Apr 20, 2011 2:36:20 PM [Thread[Thread-22,5,main]] Warning    com.sap.smd.wily.hostagent.action.SapOsColAction - launchDaemon(): saposcol exited with 255***********************************************************************
This is Saposcol Version COLL 21.01 711 - AIX v12.01 5L-64 bit 090324
Usage: saposcol -l: Start OS Collector
        saposcol -k: Stop OS Collector
        saposcol -d: OS Collector Dialog Mode
        saposcol -s: OS Collector Status
The OS Collector (PID 1552388) is already running .....
Apr 20, 2011 2:36:23 PM [Thread[SAPOsCol,5,main]] Error      com.sap.smd.wily.hostagent.action.AbstractAction - run(): Action throws exception, will be terminated: SAPOsCol
[EXCEPTION]
java.lang.NullPointerException:
at com.sap.smd.wily.hostagent.action.SapOsColAction.reportProperty(SapOsColAction.java:293)
at com.sap.smd.wily.hostagent.action.SapOsColAction.dumpSection(SapOsColAction.java:239)
at com.sap.smd.wily.hostagent.action.SapOsColAction.processXml(SapOsColAction.java:164)
at com.sap.smd.wily.hostagent.action.SapOsColAction.doRun(SapOsColAction.java:417)
at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:53)
at com.wily.EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:728)
at java.lang.Thread.run(Thread.java:664)
Our MDM is 7.1 version and Solution Manager is 7.01 (EHP1) with SP19 so we should configure our MDM system as 7.1 version which we did but still data is not coming in Wily properly. Its not showing SID name under the hostname in Wily Introscope and neither is MDM Servers (Master Data Import Server, Master Data Server & Master Data Syndication Server under SID).
Now the interesting thing is that if we configure our MDM server as 5.5 version with Solution Manager and do the configuration than its showing in Wily but in that case MDM Cockpit doesn't work.
We want both to work Wily as welll as MDM Cockpit since our MDM and Solman version matches for both configuration.
Any ides or help steps to do that?
Thanks,
Manish Singh

Managed System Configuration: SSO setup failed for Solution Manager 7.1 sp11

Hi Folks,
While doing Managed System Configuration for Soman system i am getting error in SSO Setup
Currently I am in
8. Configure Automatically :Single Sign On Setup
This is i am going for managed System (Solution Manager System Itself)
Below is error log..
SSO setup failed : a problem occured while attempting to add login modules for ticket authentication
Screen shot attached.
Found SID for SSO ACL entry : SMP
Found login.ticket_client for SSO ACL entry : 000
The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tc~webadministrator~solmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (619 bytes)
The SSO ticket Certificate <OU=J2EE,CN=SMP> has been successfully imported into ticket Keystore
SSO setup failed : a problem occured while attempting to add login modules for ticket authentication
SSO setup failed : error while updating login modules : Caller not authorized.; nested exception is:
java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
The SSO ticket Certificate <CN=SMP> has been successfully imported into ticket Keystore
SSO setup failed : a problem occured while attempting to add login modules for ticket authentication
SSO setup failed : error while updating login modules : Caller not authorized.; nested exception is:
java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Exception
java.rmi.RemoteException: Caller not authorized.; nested exception is:
java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:160)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
at com.sap.engine.services.security.exceptions.BaseSecurityException.writeReplace(BaseSecurityException.java:349)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:910)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1024)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1344)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1316)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1260)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1065)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:282)
at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:147)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:338)
... 8 more
Regards,
San

Hi Sandeep,
It seems authorization issue. Please check the below SAP Note :
1988642 - Warning 'caller not authorized' in Step 'Single Sign On Setup'
Hope this helps.
Thanks & Regards,
Nisha

Solution manager optimizer configuration

hi
     I am in solution manager 4.0 optimizer configuration step here i face an error when i type the t code solution_manager it displays the appropriate screen then i click on new button
here i entered the
                                solution name     sandbox landscape
                                       language      english
then when i click on continue button here nothing is happening actually it has to go to the next screen but the screen stands as if, nothing is happening   no reponse at all
support pack updated to stack 09
internet explorer 7 version is installed and all prerequisite is done
please help me
regards
senthil

Hi,
Can you tell what the error is? I may be able to help you.
Amol

Runtime Errors Raise Exception in Solution Manager

Hi Guru's,
While I try to excute the transaction solman_issue_mgnt in solution manager for issue tracking, runtime errors occurs.
Error analysis
    A RAISE statement in the program "CL_GUI_HTML_VIEWER============CP" raised the
     exception
    condition "CNHT_ERROR_PARAMETER".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
Could anyone suggest me on this issue.
regards,
Guna

Hi Juan,
As per the note, everything was fine there. We have SAP_Basis 700 with SP16.
Earlier it was worked fine. Now only we are facing this issue while excuting the t-code solman_issue_mgmt.
regards,
Guna

Patch approval error getting from solution manager

Hi,
We are getting error while downloading patch approval from solution manager. As reference below error, I have checked this note 982045 & put valid user id & password of the service market place there but error is getting same. Here following error screen as mentioned below. please suggest us.
Regards
Abhijit

Hi,
Thanks for sharing these note but after using this note 1178684, we are facing this error as follows.
trc file: "dev_rout", trc level: 1, release: "700"
Fri Feb 28 16:37:05 2014
SAP Network Interface Router, Version 38.10
command line arg 0: saprouter
command line arg 1: -r
main: pid = 4072, ppid = 0, port = 3299, parent port = 0 (0 = parent is not a saprouter)
Fri Feb 28 16:37:06 2014
reading routtab: './saprouttab'
*** ERROR => SNC field without SNC active, skip line 2 [nirout.cpp   7767]
*** ERROR => SNC field without SNC active, skip line 3 [nirout.cpp   7767]
*** ERROR => SNC field without SNC active, skip line 4 [nirout.cpp   7767]
*** ERROR => SNC field without SNC active, skip line 5 [nirout.cpp   7767]
*** ERROR => SNC field without SNC active, skip line 6 [nirout.cpp   7767]
Fri Feb 28 16:37:43 2014
*** ERROR => SncPEstablishContext() failed for target='p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE' [sncxxall.c 3379]
*** ERROR => SncPEstablishContext()==SNCERR_GSSAPI [sncxxall.c 3345]
      GSS-API(maj): Miscellaneous failure
      GSS-API(min): Invalid password (PIN)
    Unable to establish the security context
    target="p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE"
<<- SncProcessOutput()==SNCERR_GSSAPI
*** ERROR => NiSncIInitHdlSecurity: SncProcessOutput failed (rc=-4;0206E3B0) [nisnc.c      1098]
*** ERROR => NiSnc2Connect C1/-1, 194.39.131.34 (rc=-17) [nirout.cpp   2816]
*** ERROR => NiRClientHandle: NiRExRouteCon for C1/-1 'solman' failed (rc=-17) [nirout.cpp   2243]
Regards
Abhijit

Solution Manager 7.1 Basic Configuration error

Similar Messages

Maybe you are looking for