SMD: no data for E2E Workload Analysis are shown

[Former Member]

Hi!

I am using SAP Solution Manager with SP15.

After several configuration SMD configuration steps I cannot see the data under E2E Workload Analysis.

When I run the SMD wizard for the portal solution all the steps besides the first one are running without error.

The error I get:

Type: Wilyhost agent

Message: Retrieving list of Enterprise Managers failed: No Enterprise Managers configured for Queries

Step Wilyhost Agent Details

Created destination E11_JC00_server0

Created action SAP GC|E11_JC00_server0 - SAP GC|E11_JC00_server0

Created 1 action(s).

Retrieving list of Enterprise Managers failed: No Enterprise Managers configured for Queries

Exceptions

java.sql.SQLException: No Enterprise Managers configured for Queries

at com.sap.sup.admin.wily.jdbc.EMOverview.getQueryEMgrs(EMOverview.java:224)

at com.sap.sup.admin.wily.jdbc.EMOverview.populateAgentCache(EMOverview.java:377)

at com.sap.sup.admin.wily.jdbc.EMOverview.checkAgentCache(EMOverview.java:423)

at com.sap.sup.admin.wily.jdbc.EMOverview.getAgentEMgrs(EMOverview.java:242)

at com.sap.sup.admin.wily.hostagent.Setup.emCanBeAccessed(Setup.java:417)

at com.sap.sup.admin.wily.hostagent.Setup.executeSetup(Setup.java:90)

at com.sap.sup.admin.setup.AppCfgTasks.configureEPAgent(AppCfgTasks.java:109)

at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:309)

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)

Any helpful information concerning the solution the problem above will be appreciated.

regards

Thom

[Former Member]

It is a old question

[Former Member]

Hi,

When I am re-starting the Wily EM (Version 7.2) it gives the below log -

Running Enterprise Manager with IHOME=.

Running Enterprise Manager with JAVAPATH=/usr/sap/SMZ/ccms/wilyintroscope/jre

java version "1.5.0_08"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_08-b03)

Java HotSpot(TM) Server VM (build 1.5.0_08-b03, mixed mode)

Database was not normally closed: start recovery

Recovery completed

Database was not normally closed: start recovery

Recovery completed

log4j:ERROR Failed to flush writer,

java.io.InterruptedIOException

at java.io.FileOutputStream.writeBytes(Native Method)

at java.io.FileOutputStream.write(Unknown Source)

at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(Unknown Source)

at sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(Unknown Source)

at sun.nio.cs.StreamEncoder$CharsetSE.implFlush(Unknown Source)

at sun.nio.cs.StreamEncoder.flush(Unknown Source)

at java.io.OutputStreamWriter.flush(Unknown Source)

at com.wily.org.apache.log4j.helpers.QuietWriter.flush(Unknown Source)

at com.wily.org.apache.log4j.WriterAppender.subAppend(Unknown Source)

at com.wily.org.apache.log4j.RollingFileAppender.subAppend(Unknown Source)

at com.wily.org.apache.log4j.WriterAppender.append(Unknown Source)

at com.wily.org.apache.log4j.AppenderSkeleton.doAppend(Unknown Source)

at com.wily.org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(Unknown Source)

at com.wily.org.apache.log4j.Category.callAppenders(Unknown Source)

at com.wily.org.apache.log4j.Category.forcedLog(Unknown Source)

at com.wily.org.apache.log4j.Category.log(Unknown Source)

at com.wily.util.feedback.backend.log4j.Log4JBackend.log(Log4JBackend.java:139)

at com.wily.util.feedback.ADefaultModuleFeedbackChannel.doLog(ADefaultModuleFeedbackChannel.java:545)

at com.wily.util.feedback.ADefaultModuleFeedbackChannel.logbottleneck(ADefaultModuleFeedbackChannel.java:524)

at com.wily.util.feedback.ADefaultModuleFeedbackChannel.log(ADefaultModuleFeedbackChannel.java:479)

at com.wily.util.feedback.ADefaultModuleFeedbackChannel.error(ADefaultModuleFeedbackChannel.java:313)

at com.wily.util.event.ListenerTracker.sendEventToOneListener(ListenerTracker.java:148)

at com.wily.util.event.EventPump.immediateDeliverEventIfListenerNotDead(EventPump.java:152)

at com.wily.util.event.EventPump.immediateDeliverTargetEventAsync(EventPump.java:135)

at com.wily.util.event.EventPump.access$500(EventPump.java:23)

at com.wily.util.event.EventPump$Posting.deliver(EventPump.java:518)

at com.wily.util.event.EventPump$EventPumpThread.run(EventPump.java:760)

************************************

************************************

Introscope Enterprise Manager failed to start because:

A socket port was already in use (see the log for the port number)

Press 'Enter' to acknowledge....

Any idea on this issue ??

[raguraman_c]

Hi,

Pl. read rules of forum. Only one question per post.

Moreover, this is not your post!!.

I wonder,what is stopping you to create a separate post. I see one more question in this post by Kobby Bryant.

Post a separate thread, your question will be duly answered.

Feel free to revert back.

--Ragu

[Former Member]

Hi,

I'm trying to setup Diagnostics server(E2E)

failes with error

Failed to access RFC meta data of E2E_EFWK_WIZARD_CREATE_BTC_HK on ABAP Host=XXXXXX sys=00 client=100 user=DDIC.

No E2E_EFWK_WIZARD_CREATE_BTC_HK dest were created in solman as well as in BI systems,

Please guide.

Thanks in advance

[markus_doehr2]

If your BI is a separate system the setup won't be completed automatically by using the setup wizard. Some manual adaptions have to be made.

I suggest you create an OSS call and let the support people explain you what you need to do.

Markus

[Former Member]

hi,

how can i use a client in solman itself as a BI client( then what will be the source system)..

Thanks in advance

[markus_doehr2]

Please follow the SPRO - default IMG - all steps are listed there.

Markus

[Former Member]

Hi,

Thanks successfully completed DS setup.

while running managed system setup it says

jstartup/recorder missing (for what we use this parameter).

Also if i'm using new SMD agent(7.2) do i need to install EP agents also(i read in some docs that we no need to install EPA).

I'm on solman SPS15, Portals 12.

Please guide

Thanks in advance

[markus_doehr2]

Check http://service.sap.com/diagnostics - the E2E setup guide has the complete parameter you need to enter in the Java instance profile (and restart).

Markus

[Former Member]

Also check note 1159369, although it didn't work for me; because I got the same error in the proposed self-check...

If anyone else has some idea... it would be great...

Fermín.

[Former Member]

Looks like that username or password is wrong. In SMD go to Wily & NWA" in "Advanced Setup and for username and passwrod enter Admin/Amin89. Save it and try it again.

Hope this helps.

Labinot

[Former Member]

Hi Thom

I'm getting the same error also with SP15. I've found an error in the log IntroscopeEnterpriseManager.log;

Failed to start SNMP Agent com.wily.introscope.spec.server.beans.snmp.SnmpException: SNMP Agent failed to start on port "161" using "Introscope-Madvirt01" MIB. Caused by: monfox.toolkit.snmp.engine.SnmpTransportException: Address already in use: Cannot bind

It looks it cannot start Introscope EM.

Do you have an error like this?

Have you find something else to fix this?

Regards,

Fermí

[Former Member]

Hi

Please check the port of enterprise manager, by default it will be port number 6001.

Chnge port o 6001 and check.

Regards

Ramesh / Prakash

[Former Member]

Hi!

As mentioned, earlier I solved the problem.

I do not know whether it is/was the solution, but I have updated th EP Server version from 7.1 to 7.2 and restarted the Server wizard. After this all the steps were green.

Meanwhile this successfull server wizard installation I could not see any data under E2E Workload analysis.

regards,

THom

[Former Member]

Hi!

Thanks everybody for your answers.

It looks the problem, as mentioned before, was the wrong user/password in tab Wily/NWA in SMD diagnostics tab.

Also there was a strange thing; after I fixed this; the Introscope byte code setup for the managed system still said that there was not Introscope EM connection; I had to restart de Java stack of Solution Manager to fix it. It sounds strange... but it is working finally.

Thanks everybody.

Kind regards,

Fermín.