Solution Manager 7.1 SOLMAN_SETUP - Setup Extractor Framework fails

Hi.
I'm perfoming SOLMAN_SETUP on a fresh Solution Manager 7.1 and I'm running in a strange error while performing Basic Configuration->Step 5 -> Setup Extractor Framework.
A failure occured while trying to initialize the extractor framework (E2E_EFWK_WIZARD_BASIC)
Details
A failure occured while trying to initialize the extractor framework (E2E_EFWK_WIZARD_BASIC)
!! Exception : EFWK_SETUP_ERROR(Abap cause=No Technical System for SolMan ABAP found in Lands)
In SMSY the solman prod. system has already been created (name = SID) and looks fine. Local SLD<->LMDB sync is running, no migration SMSY->LMDB has been made.
Any ideas?
Cheers, Tobias

hi,
I checked the box for Diagnastic. However it does not work. Still it could not identify the Solution Manager ABAP technical system.
Would appreciate any help on this.
The Error is:
Message:
A failure occured while trying to initialize the extractor framework (E2E_EFWK_WIZARD_BASIC)
Details
A failure occured while trying to initialize the extractor framework (E2E_EFWK_WIZARD_BASIC)
!! Exception : EFWK_SETUP_ERROR(Abap cause=No Technical System for SolMan ABAP found in Lands)
Exception:
com.sap.mw.jco.JCO$AbapException: (126) EFWK_SETUP_ERROR: EFWK_SETUP_ERROR
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1512)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3937)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3570)
at com.sap.sup.admin.setup.SolManRfcAdapter.extractorBasicConf(SolManRfcAdapter.java:1511)
at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:569)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:445)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:674)
at com.sap.sup.admin.setup.ws.SetupWrapper._diagSetup(SetupWrapper.java:279)
at com.sap.sup.admin.setup.ws.SetupWrapper.diagSetup(SetupWrapper.java:21)
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 com.sap.engine.services.webservices.runtime.JavaClassImplementationContainer.invokeMethod(JavaClassImplementationContainer.java:76)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:174)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:81)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:90)
at SoapServlet.doPost(SoapServlet.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) 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)

Similar Messages

Sap Solution Manager 7.1 Solman_Setup problem

Hello
I have installed SOLMAN 7.1 (SID = HSM) and Portal NW 730 (SID = HPP) . I have configured Solman Basic and System Preparation steps. Portal (HPP) system has SDM 7.30 Diagnostic on it and configure to SOLMAN system. Isee all agent on Agent Administrator on SOLMAN_WORKCENTER. But when i checked Managed System Configuration Page see couple errors;
- All technical Systems Status are RED LED.
- Portal System (HPP) Status Errors;
- 'HPPJAVA': No Path found in Server Node 'HPPJAVA~6421250'.
- The definition of Technical System 'HPPJAVA' is not correct: 'HPPJAVA': No Path found in Server Node 'HPPJAVA6421250'
- SOLMAN (HSM) Status Error;
for ABAP;
- 'HSM~ABAP': No Instance found
- 'HSM~ABAP': Technical System must have a Central Service Instance
- The definition of Technical System 'HSMABAP' is not correct: 'HSMABAP': No Instance found
- The definition of Technical System 'HSMABAP' is not correct: 'HSMABAP': Technical System must have a Central Service Instance.
for JAVA;
- 'HSM00001~JAVA': No Diagnostics relevant Software Component Version found.
- 'HSM00001JAVA': No Path found in Server Node 'HSM00001JAVA~2614750'.
- 'HSM00001JAVA': No Path found in Dispatcher Node 'HSM00001JAVA~2614700'
- The definition of Technical System 'HSM00001JAVA' is not correct: 'HSM00001JAVA': No Diagnostics relevant SoftwareComponent Version found
How can i solve these problems?

Hello,
The links provided to you are for 7.0 EHP1.
I'm expert in Diagnostics, I kindly ask you to review these links:
http://service.sap.com/instguides
-> SAP Components
-> Release 7.1
You can find all documentation there.
Also in the Wikis: always use the home page to read the links you are entering. So you need to access
http://wiki.sdn.sap.com/wiki/display/SMSETUP/
There you can see several pages for 7.1 release.
The right procedure is to use transaction SOLMAN_SETUP to set ALL your Solution Manager 7.1.
And you are partially right, SMSY does not need to be maintained manually as the LMDB is now used and will maintain the SMSY automatically. In the setup process it will let you choose if you want to transfer content from SMSY to LMDB, but this is only a one time procedure, this update is not standard.
Please rely on SOLMAN_SETUP, it is very good and it has everything documented and organized.
Don't hesitate to reply here or to open a message for SAP.
Best regards,
Guilherme Balbinot

Solution Manager help-desk VAR setup

I am setting up help desk in Solution Manager 4.0
The guide tells me to to execute report: AI_SDK_CF_GET_SUSR_VAR_CUST
When I try to execute it in transaction se38 I get the following error:
RFC_system_error Function module BCSN_Z001_VARS_SUSER_LIST not found.
Can anyone tell me what is causing this error and how to fix it?
Could my RFC connection be the problem?
Thank you SAP Master.

Hi,
/people/federico.babelis2/blog/2006/04/14/service-desk-configuration-guide-for-dummies
hope this helps you bit..
Praveen

SAP Solution Manager 4.0 Install on iSeries V5R4M0 fails on STEP 40 of 40

During Step 40 of 40 of Solution Manager 4.0 install on iSeries running i5/OS V5R3M0 failed with the following error:
ERROR 2006-08-18 10:00:57 [iaxxgenimp.cpp:728]
showDialog()
FCO-00011 The step fixTemplate400 with step key
|NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Configuration|ind|ind|ind|ind|5|0|NW_Call_Offline_CTC|ind|ind|ind|ind|7|0|fixTemplate400
was executed with status ERROR .
TRACE [iaxxgenimp.cpp:657]
showDialog()
<html><head></head><body><p>An error occurred while processing service
<b>SAP Solution Manager 4.0 > SAP Systems > IBM DB2 UDB for i
TRACE [iaxxgenimp.cpp:1093]
showDialog()
waiting for an answer from gui
***********End of Data*******************
Searching OSS Notes, there is no reference to the FCO-00011 error code

Hello Loli,
I think it was me, who misunderstood.
Now I followed your recommendations, increased virtual memory on the sapinst machine, restarted the pc and the installation and it completed successfully. Thank you very much.
Sorry that I can't give you points for the helpfull answer, because this is not my thread.
Kind regards,
Jürgen Scheckelhoff.

Solution Manager 7.1 SOLMAN_SETUP - BPO Dashboard Setup stays on red LED

Hi.
We have another strange behaviour in Solman 7.1 Setup->Basic Configuration->Automatic Activities. Step "BPO Dashboard Setup" was first red LED because "Cube 0SM_BPMRH is not active and will now be activated automatically" and then "System status failed for system" without further information in the log.
Now if we execute the step again, the Job AGS_BPO_DASHBOARD finishs successfully, but nonetheless the LED stay red. Also the log below the Automatic Activities list is not updated and has still the two old messages from above in it. I think we refreshed pretty much all buttons on the website and cleared the browser cache.
And by the way: I can't find the mentioned cube in RSA1, isn't this the place where all the cubes should be listed?
Any ideas?
Cheers, Tobias

Hi,
My ST level is on SP08 and the note above can't be implemented. The BPO Dashboard Setup is still in RED icon.
What should I do to resolve this?
screenshot below:
Thank you!
Regards,
AJ

Solution Manager 7.1 SP10- Alert Management Reporting no input

Hello there,
we use the Solution Manager 7.1 SPS 10 for System Monitoring (with customer specific tempaltes and SAP Standard templates), the PI/PO MOnitoring an some other Features.
By the way if we start the dashboard for "Alert Management Reporting" we don't get any data.
Also we can't select the managed objects.
In the "BI Diagnostic Center" there is the overview for the Reporting Scenarios. We see our Scenarios "System Reporting" and "End USer Experience Moitoring" active. When i select "Alert management Reporting" and try to click the Button "Scenario Setup" nothing happens.
Is this a bug?
Can anybody help me get the Alert Management Reporting Dashboard run?
Thanks and kind regards
torsten

Hi Torsten,
Please follow the instructions of the note 1862024.
The ALM extractor is scheduled within the "Technical Monitoring"
setup in SOLMAN_SETUP, step 7. Before in the scope selection you need to
select the solution manager system. If the extractors are already
active, you'll need to deactivate (also uncheck the "keep
custom settings if checked), then restart SOLMAN_SETUP and re-activate.
Kind regards,
Roland

Using HR data in R/3 to create business partners in Solution Manager

Is it OK for me to setup Solution Manager to automatically download HR data from R/3 to create the Business Partners (employee role) in Solution Manager?
We have setup SAP CRM 4.0 to automatically download the HR data and create Business Partners (employee role) in CRM. Since Solution Manager has the CRM component in it, I assume we can do it as well in Solution Manager.
Regards,
Mel Calucin
Bentley Systems

We did it, i don't see the problem...

Problem with BI activation in Solution Manager

Hello SAP experts.
I have problem with BI Content Activation in Solution Manager solman_workcenter - test management - settings - Bi reporting
The customizing in client 010 is ok. I have BW client 001. RFC connections
are ok. After activation of BW content in workcenter only new job in sm37
has been planned but the button Status Report has not appeared. I installed
newest add-on SAPK-70405INBICONT.
Detailed description:
After customizing in:
SPRO-Basic Data-BW Setup
and
SPRO-Scenario-Specific Settings - Test Management - BW-based Reporting.
The Activation of BW content in transaction solman_workcenter - Test
Management - Settings - BI Reporting Settings the message appears:
"Test Workbench Reporting - BI Content not active", after pressing save:"Settings of Test Workbench Reporting saved"
and
"Activation of BI Content for Test Workbench Reporting started".
In test evaluation the button Status report doesnt show. After repeated
activation appears the same message as in beginning: Test Workbench
Reporting - BI Content not active.
Thank you

Hi Marian,
Could you please provide me with details on how to setup test workbench reporting. I have a BW system external to Solution Manager. I have setup the RFC conncections and all is okay. I have also setup the source system in BW and installed the web templates. However, when activating the content via solman_workcenter - test management - settings, I get the following error:
Content Activation Log
Log for Setup ID 20100819135323
20100819 135323[ERROR ]: Current Status: ERROR
20100819 135323[INFO ]: Job CCMS_BI_SETUP successfully scheduled
20100819 135323[ERROR ]: Incorrect system setting: standard transport is active
20100819 135323[ERROR ]: Change system settings or set user parameters RSOISCONTENTSYSTEM and RSOSTANDARDCTOACTIVE
20100819 135323[ERROR ]: Prerequisites check failed
20100819 135323[ERROR ]: Jobname/count: CCMS_BI_SETUP 13532300
I am sure there is something wrong in my setup but I cannot figure out what it is. A step by step help on how to do it will be greatly appreciated.
Regards,
Rue.

Job Scheduling in Solution Manager - Error creating Periodic Job

Hi all,
I am in the process of testing the Job Scheduling functionality using the Solution Manager. I have setup the criteria manager, ec. in the satellite system, and done the config in Solman as well.
I am able to successfully setup up a 'on-time' job.
it's only when I try to setup a periodic job, I end up getting following error
Any thoughts? Is there any piece of config that's missing? All the SICF services needed for this functionality are running fine.
Thanks for the help.
500 Internal Server Error
Error when processing your request
What has happened?
The URL https://fsspsm.target.com:/sap/bc/webdynpro/sap/wd_ags_ejr_job_req_gaf_app was not called due to an error.
Note
The following error text was processed in the system PSM : Message was not created
The error occurred on the application server fsspsmap01_PSM_00 and in the work process 1 .
The termination type was: ERROR_MESSAGE_STATE
The ABAP call stack was:
Function: BAPI_NOTIFICATION_CREATE of program SAPLDSWP_NOTIF
Method: MSG_SUBMIT of program CL_DSMOP_BSP_NOTI_MODEL=======CP
Method: SUBMIT_REQ_CRM_DATA of program CL_AGS_EJR_JOB_REQUEST_FACTORYCP
Method: SUBMIT of program CL_AGS_EJR_JOB_REQUEST_FACTORYCP
Method: PROCESS_SCENARIO_PERIODIC of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
Method: PROCESS_JOB_SCENARIO of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
Method: IF_AGS_EJR_JSM_PROC_FPM_CTRL~AFTER_PROCESS_EVENT of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
Method: AFTER_PROCESS_EVENT of program /1BCWDY/K54G9RCMK7J4Z427H49S==CP
Method: IWCI_IF_FPM_APP_CONTROLLER~AFTER_PROCESS_EVENT of program /1BCWDY/K54G9RCMK7J4Z427H49S==CP
Method: CALL_UIBB_PROCESS_EVENT of program CL_FPM========================CP

Hello,
This is the basic Job Scheduling functionality and not the Redwood Job scheduling, correct?
Have you performed the IMG Activiteis in SPRO?
See the following Help link:
http://help.sap.com/saphelp_sm70ehp1_sp23/helpdata/en/c5/7edcbd58ce4e29bc1baf1c4761d71f/frameset.htm
Change a job
You can change the scheduling of a job as long as it has not been completed. Proceed as follows:
Make changes.
Note
When you change a periodic job, the system searches for the changeable successor and only changes this successor.
If there is more than one changeable job with the same name, the system does not change any of these jobs.
End of the note.
Save your entries.
To release the job in the target system, select Release.
You go to the transaction SM37 in the target system.
You just may want to ensure HTTP Services have been enabled. I realize you said the services workin SICF, but this needs to be verified as 500 Internal Server Error most often means the HTTP services are not activated.
Regards,
Paul

How to monitor BI & PI using Solution Manager 4.0

Hi, we have installed Netweaver 04S SR2 SP11 BI & PI components. We want to use Solution Manager 4.0 to setup monitoring for these 2 systems. Any guide or documentation will be greatly appreciated.
Thanks in advance.
Arshish

Hi Arshish,
To setup monitoring you will first have to include these systems in the system landscape of SAP solution Manager 4.0 in transaction SMSY.
The steps in the order are :
1. Create Server ( Server name ,IP and Fully qulaified Host name)
2.Create Database (Give the database you are using)
3.Then you have to create the system itself. and give the information as required.You will be able to do it when you will go through it.
Then you have to generate the RFC's from solution manager to satellite systems and back.These RFC's have to be trusted.Assign role SAP_S_RFCACL or profile S_RFCACL to the users in SOLMAN as well as satellite system.
Follow these steps and create a Logical component for the system that you have added.
Follow these steps first.More information can be found out on
service.sap.com\solutionmanager
or you can look for the RKT'S on service marketplace.If you need any furthur assistance do reply back.
please award points if found helpful
Best Regards
Amit

Display SXMB_MONI XML errors in Solution Manager (CEN)

Hello All,
Requirement is to display the XML error messages in SXMB_MONI in our Solution Manager (CEN)? Could you please let me know the major steps that would be involved on the same?
Please share your thoughts!
Thank You,
Antarpreet

My apologies not reading it properly....
Solution manager also usess the same concepts of the CCMS as we do it in XI, so you can setup the XI envinorment details in solution manager and try to capture the alerts....
Here are the Steps:
Prereq:
All Satellite systems connected from Solution Manager on the "Transaction SMSY" screen.
Prepare RFC connections between Solution Manager and Satellite systems for data collection ( RZ20 Data collection RFCs)
Steps:
1. Register "SAPCCMSR" and "SAPCCM4.X" on Sattilite Systems to report ABAP and Java stacks in local systems and report to Solution manager System
2. On Solution Manager System ( Acting as Central System) configure CCMS monitoring sets fromRZ20.
3. RZ21 --> configure CCMS pings alert monitoring.
all info with step by step guide avalible from Solution Manager configuration guides and http://service.sap.com/rkt
( This ref from solution manager forum)
check this link also:
http://www.scribd.com/doc/7858198/Solution-Manager-SAP-NW2004S-Monitoring-Setup-Guide-SP12

Solution Manager: Connection via Service Connection???

Hello,
I would like to connect the solution manager with a customer system via an exististing service connection, there is no solution manager installed on the customer's system. Is this possible? Is it possible to find any documentation about this?
Regards,
Britta

Hello,
You can run TCD DSWP
Then clcik the Solution Landscape button
Then Clcik the Service Connection link
Then click the Solution Manager drop down menu and select setup connection
Then fill in the details:
Product System
Description
Installation Number
Systen ID
System Number
Service Connection type
The support Service Connection types are reference at http://service.sap.com/connectiontypes and for each connection type the corresponding Note is provided.
This setup will allow you to create service connections to OSS on Solution Manager
Once you have setup the connection you will still navigate to Service Connections, only you will use the Connection Drop down menu button to select Open Connection.
Regards,
Paul

Steps for solution manager sizing

Hi,
I could not see sizing for SAP solution manager in Sizing tool.
Pls let me know of where i can find it

hi,
taken from
[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b442d4ea-0c01-0010-a8ad-a4c2eaaf6b76]
it is told :
Do you have a rule of thumb concerning sizing?
For small and medium sized companies, there is no need to set up a high-end server if it is only used for the SAP Solution Manager and its monitoring functions. A small/medium-sized server is sufficient. However, this is dependent on your needs and future plans. The following sizing proposal is based on a standalone server with SAP Solution Manager only.
- For basic setup: 1 CPU current standard (min. 1 GHz), 1GB RAM, 50 GB hard disk space
- For advanced setup: 2 CPUs current standard (min. 1 GHz), 2 GB RAM, 50 GB hard disk space
The basic setup of SAP Solution Manager is defined as only having SAP EarlyWatch Alert and service level reporting, configured on the satellite systems and up to 5 users working at the same time on the SAP Solution Manager.
The advanced setup of the SAP Solution Manager requires additional steps after the basic setup is complete. The advanced features cover the configuration of system monitoring and/or business process monitoring. For further information, please refer to the sizing proposals for SAP Solution Manager 3.1 on the SAP Service Marketplace.
hope it help you.
rgds,
Alfonsus Guritno

Solution Manager 7.1 SP4: Session Timeout during SOLMAN_SETUP

Hello Experts,
We recently installed Solution Manager 7.1 SP4 on Linux/Oracle. We also completed the System Preparation and Basic Configuration part of the SOLMAN_SETUP wizard as well (which includes applying the Central Correction Note and other steps).
During the Managed System Setup Part, as soon as we click on the Configure System for a managed system - a new window opens up and immediately we get the below timeout messages:
This session will terminate due to inactivity in 0:00 minutes
To continue working in this session, choose 'Continue Session'
The above is immediately followed by the actual session timeout message:
This session terminated due to inactivity.
Click Close Popup
or to start new session, press F5.
Now even if we press F5/Refresh, the same cycle repeats.
I already checked the ICM timeout parameters as mentioned in the Guide and further findings with regards to ITS update as in thread WEBGUI Timeout immediately after logging in
Applying the latest kernel patch also did not help. The strange issue is that the session timeout occurs only the LMDB related services, wherease normal services like WEBGUI etc work fine.
Please suggest if anyone came across this issue, especially after update to SP04.
Thanks and Regards,
Srikishan

Hi,
Thanks, I will check the note steps and close this thread accordingly.
Perhaps I need to hone my notes searching skills !
Regards,
Srikishan

Solman_setup and central&local solution manager SLD

Hello,
I'm configuring our solution mananger system with transaction solman_setup. The local SLD of the solution manager will also be the central SLD of all our systems. After finishg the basic configuration in solman_setup, and go to "managed system configuration", I can only see the only solution manager system, as ABAP and as JAVA, but no more systems (right, as I haven't defined more systems).
I cannot create more ABAP system with the link "maintain technical systems", the ABAP option when I select create isn't there.
If I create another type of system as a test, for example, third party, the transaction SMSY can see this new system, but the SLD in http://<my_solution_manager_system>:50000/sld doesn't show this new system at all.
Where must I create the systems? and how can I connect the SLD and the SMSY transaction? Should I "add SLD" at the Administration in http://<my_solution_manager_system>:50000/sld and put the suolution manager itsefl system?
Thanks in advance for your help and best regards,
Ana

Hi,
To ensure a system is registering into the SLD and synchronising with SMSY, go to transaction RZ70 and define the Host and Service.
Also, set up a user for accessing the SLD in transaction SLDAPICUST. The user has to exist in the Java stack to log into the SLD.
Also ensure your RFCs are correctly set up for LCRSAPRFC and SAPSLDAPI as per this link:
https://cw.sdn.sap.com/cw/docs/DOC-37953?treeid=DOC-7936
Then use transaction SLDCHECK to ensure your connection is working.
Finally enable SLD synchronisation into SMSY by transaction SMSY > Goto > Setup System Landscape Maintenance. Define the same host and port of your SLD and schedule the data transfer.
This should pick up the system once the landscape_fetch background job executes into SMSY.
You can use this approach for all your managed systems and is the most logical way to connect systems to the SLD.
Regards,
-Rohan

Solution Manager 7.1 SOLMAN_SETUP - Setup Extractor Framework fails

Similar Messages

Maybe you are looking for