Solution Manager 7.1 SOLMAN_SETUP -> Setup Extractor Framework fails

[tobiasharmes]

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

[allam_drebes · Accepted solution]

Hi Tobias,

Check if the solman is really defined in LMDB.

The failure occurs since the solution manager itself is not known to the LMDB when the setup was performed.

BR,

Allam

[Former Member · Accepted solution]

Hello Tobias,

Check the job -SAP_LMDB_LDB_0000000001 in SM37 successfully completed or not.

It helps for E2E and incremental synchronization from SLD to LMDB.

Once job is completed. Assign the BI system or client in Basic configuration step.

Again run the step 5. Confoguration Automatically.

Rg,

Karthik

[tobiasharmes · Accepted solution]

Hi Karthik.

Indeed, the Job SAP_LMDB_LDB_0000000001 failed due to low table space in customers Oracle DB. After the job ran through the setup step could be completed.

Thank you!

Cheers, Tobias

[changzheng_zhao]

Just want to share my experience. We had exact same issue when running the activity Setup Extractor Framework in Basic Configuration. The different thing is that we have completed the SLD -> LMDB synchronization with no errors.

After tried different things, e.g. disabling the LMDB cache, restart Solution Manager system, etc. we finally found that the root cause is that the Solution Manager system <SID>~ABAP was not marked as Diagnostics relevant in LMDB.

To fix this, start transaction LMDB, select your Solution Manager system under Technical System tab and click Maintain button. Select Software under the Navigation Tree on left hand. On the right hand, check the check box under column Diagnostics Relevant for Product Instance "Solution Manager 7.1: Solution Manager ABAP Stack". Save your changes and rerun the activity Setup Extractor Framework. It should be able to be completed successfully.

Hope this is helpful to others who met this issue.

[former_member199694]

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)

[changzheng_zhao]

Try to check the content of Landscape API cache table LAPI_TECH_INST. If the technical system of Solution Manager is not in the table content, please run report RLAPI_MANUAL_NAMESPACE_RESYNCA to sychronize the cache.