Error when running the setup for monitored system Wily

[Former Member]

Dear All,

First of all a little background.

The system where it goes wrong was an old portal system with dual stack, this has been removed and replaced with a java only portal (so no JC01 but J01 )

We had the system in Solution Manager 7.1 but after the move it didn't work anymore so we needed to change this.

I reran the setup for monitored systems in solution manager and filled in all the requested information and the lights became green. Except for 1, being step 7 the "configure automaticly"

here when I run it it comes with a failure on:

Byte Code Adapter Installation

Error message is:

Wily introscope setup for TS:SID-JAVA - host:<server> - server node:12235750

Introscope Agent Configuration	Remote Operation Failed
Detailed Information	The wily agelet is running in 700 mode
Logical host name handling is on	Remote Operation Succeeded
Detailed Information	Operation Failed -SID - 12235750: - java.rmi.RemoteException: Problem getting VMManager; nested exception is: com.sap.smdagent.vmmanager.VMManagerP4Exception: com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException: Access is denied to SAP System sid SID/01]: check the connection credentials.More details about the error in agent 'server' log file (SMDAgentApplication.X.log).; nested exception is: com.sap.engine.services.security.exceptions.BaseLoginException: Error during authentication. For more information see the remote server traces.

Any ideas on this?

[former_member185239]

Hi  Christian,

Please follow the below link

http://scn.sap.com/thread/3297200

More ever in step 4 (crucial step), You need to provide the java user having the MY_SAP* role so that it can logon to the system.

You find the sapnote for this am not getting it

With Regards

Ashutosh Chaturvedi

[Former Member]

Have you checked agent 'server' log file (SMDAgentApplication.X.log) and remote server traces for additional info?

Regards,

Roman

[Former Member]

Hi Roman

When I look at the SMD agent logging on the server to be monitored by solution manager I see

#1.5 #E4115BE7AD64001900000F61000009000004D50C0E3C30C7#1360147661785#SMDloggerSystem##SMDloggerSystem#######Thread[ExRun:OutsideDiscovery_1,5,OutsideDiscovery:ExecTG]##0#0#Info##Plain###Reading JStartup environment...#

#1.5 #E4115BE7AD64001900000F62000009000004D50C0E3C315C#1360147661786#SMDloggerSystem##SMDloggerSystem#######Thread[ExRun:OutsideDiscovery_1,5,OutsideDiscovery:ExecTG]##0#0#Info##Plain###'SAPLOCALHOST' found, The value 'AP-EHV01-SAP' will be used to determine the Agent name.#

#1.5 #E4115BE7AD64001900000F63000009000004D50C0E3C36A3#1360147661787#SMDloggerSystem##SMDloggerSystem#######Thread[ExRun:OutsideDiscovery_1,5,OutsideDiscovery:ExecTG]##0#0#Info##Plain###InetAddress Resolving for 'AP-EHV01-SAP' - FQN: ap-ehv01-sap.its.centric.lan SQN: AP-EHV01-SAP IP: 10.5.199.110#

#1.5 #E4115BE7AD64001900000F64000009000004D50C0E3C3AF5#1360147661788#SMDloggerSystem##SMDloggerSystem#######Thread[ExRun:OutsideDiscovery_1,5,OutsideDiscovery:ExecTG]##0#0#Info##Plain###InetAddress Resolving for localhost - FQN: ap-ehv01-sap.its.centric.lan SQN: AP-EHV01-SAP IP: 10.5.199.110#

#1.5 #E4115BE7AD64001900000F65000009000004D50C0E3C3C67#1360147661788#com.sap.smd.e2edcc.host##com.sap.smd.e2edcc.host#######Thread[ExRun:OutsideDiscovery_1,5,OutsideDiscovery:ExecTG]##0#0#Info##Plain###[PhysicalHostPushJob] Check cached host information.#

#1.5 #E4115BE7AD64001900000F66000009000004D50C0E3C3D31#1360147661789#com.sap.smd.e2edcc.host##com.sap.smd.e2edcc.host#######Thread[ExRun:OutsideDiscovery_1,5,OutsideDiscovery:ExecTG]##0#0#Info##Plain###[PhysicalHostPushJob] end.#

#1.5 #E4115BE7AD64001C00000B82000009000004D50C0E444CBD#1360147662317#com.sap.smd.e2edcc.db##com.sap.smd.e2edcc.db#######Thread[ExRun:OutsideDiscovery_3,5,OutsideDiscovery:ExecTG]##0#0#Info##Plain###[DatabaseInfoPushJob] Check cached database information for Database[ECQ][ECQ][mss]#

#1.5 #E4115BE7AD64001C00000B83000009000004D50C0E444DA3#1360147662317#com.sap.smd.e2edcc.db##com.sap.smd.e2edcc.db#######Thread[ExRun:OutsideDiscovery_3,5,OutsideDiscovery:ExecTG]##0#0#Info##Plain###[DatabaseInfoPushJob] Database information do not require update.#

#1.5 #E4115BE7AD64001C00000B84000009000004D50C0E444E95#1360147662317#com.sap.smd.e2edcc.db##com.sap.smd.e2edcc.db#######Thread[ExRun:OutsideDiscovery_3,5,OutsideDiscovery:ExecTG]##0#0#Info##Plain###[DatabaseInfoPushJob] Check cached database information for Database[ECQ][EPQ][mss]#

#1.5 #E4115BE7AD64001C00000B85000009000004D50C0E444F47#1360147662317#com.sap.smd.e2edcc.db##com.sap.smd.e2edcc.db#######Thread[ExRun:OutsideDiscovery_3,5,OutsideDiscovery:ExecTG]##0#0#Info##Plain###[DatabaseInfoPushJob] Database information do not require update.#

#1.5 #E4115BE7AD64001C00000B86000009000004D50C0E444FE3#1360147662317#com.sap.smd.e2edcc.db##com.sap.smd.e2edcc.db#######Thread[ExRun:OutsideDiscovery_3,5,OutsideDiscovery:ExecTG]##0#0#Info##Plain###[DatabaseInfoPushJob] end.#

#1.5 #E4115BE7AD6400350000036C000009000004D50C0E906A63#1360147667304#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/15,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization##

#1.5 #E4115BE7AD64004700000017000009000004D50C0F7556AC#1360147682303#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/15,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization##

#1.5 #E4115BE7AD64001A0000072C000009000004D50C105A43DB#1360147697304#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/15,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization##

#1.5 #E4115BE7AD6400150000076A000009000004D50C113EBC7E#1360147712274#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ExRun:WILYHOST_SCHEDULER_4,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.AbstractAction - run(): Action SAP GC|EPQ_JC01_server0 not running because status is WAITING_FOR_DESTINATION##

#1.5 #E4115BE7AD64004700000018000009000004D50C113EC9DC#1360147712277#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/60,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem VMC Overview: No Authorization##

#1.5 #E4115BE7AD64003B00000373000009000004D50C113EEEC5#1360147712287#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ AbapSystem/60,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Database: No Authorization##

#1.5 #E4115BE7AD64001A0000072D000009000004D50C113F2C4C#1360147712303#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/15,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization##

#1.5 #E4115BE7AD64001200000789000009000004D50C122420B7#1360147727305#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/15,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization##

#1.5 #E4115BE7AD64001400000744000009000004D50C13091160#1360147742305#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/15,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization##

#1.5 #E4115BE7AD640024000003F3000009000004D50C13EDFBD4#1360147757304#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/15,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization##

#1.5 #E4115BE7AD640013000007D5000009000004D50C14D2740C#1360147772274#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ExRun:WILYHOST_SCHEDULER_6,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.AbstractAction - run(): Action SAP GC|EPQ_JC01_server0 not running because status is WAITING_FOR_DESTINATION##

#1.5 #E4115BE7AD64003800000363000009000004D50C14D28102#1360147772278#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/60,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem VMC Overview: No Authorization##

#1.5 #E4115BE7AD6400350000036D000009000004D50C14D2AC4B#1360147772289#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ AbapSystem/60,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Database: No Authorization##

#1.5 #E4115BE7AD640024000003F4000009000004D50C14D2E7FE#1360147772304#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/15,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization##

#1.5 #E4115BE7AD64001A0000072E000009000004D50C15B7D6A8#1360147787304#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/15,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization##

#1.5 #E4115BE7AD64001700000716000009000004D50C169CC3DF#1360147802305#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/15,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization##

#1.5 #E4115BE7AD64001600000783000009000004D50C1781B073#1360147817305#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/15,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization##

#1.5 #E4115BE7AD640024000003F5000009000004D50C18661536#1360147832270#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ AbapSystem/300,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Enqueue: No Authorization##

#1.5 #E4115BE7AD64003B00000374000009000004D50C186624AD#1360147832274#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ExRun:WILYHOST_SCHEDULER_12,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.AbstractAction - run(): Action SAP GC|EPQ_JC01_server0 not running because status is WAITING_FOR_DESTINATION##

#1.5 #E4115BE7AD64001400000745000009000004D50C18662DDD#1360147832276#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/60,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem VMC Overview: No Authorization##

#1.5 #E4115BE7AD64004700000019000009000004D50C18663CB0#1360147832280#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ AbapSystem/60,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Database: No Authorization##

#1.5 #E4115BE7AD640013000007D6000009000004D50C18669B19#1360147832304#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/15,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization##

#1.5 #E4115BE7AD6400120000078A000009000004D50C194B8D83#1360147847304#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/15,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization##

#1.5 #E4115BE7AD64001A0000072F000009000004D50C1A307A32#1360147862304#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/15,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization##

#1.5 #E4115BE7AD640024000003F6000009000004D50C1B15670D#1360147877305#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/15,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization##

#1.5 #E4115BE7AD64003700000371000009000004D50C1BF9DEB6#1360147892275#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ExRun:WILYHOST_SCHEDULER_10,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.AbstractAction - run(): Action SAP GC|EPQ_JC01_server0 not running because status is WAITING_FOR_DESTINATION##

#1.5 #E4115BE7AD640013000007D7000009000004D50C1BF9E256#1360147892276#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/60,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem VMC Overview: No Authorization##

#1.5 #E4115BE7AD64003800000364000009000004D50C1BF9FAC7#1360147892282#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ AbapSystem/60,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Database: No Authorization##

#1.5 #E4115BE7AD640024000003F7000009000004D50C1BFA50CD#1360147892304#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/15,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization##

#1.5 #E4115BE7AD64001A00000730000009000004D50C1CDF3FDC#1360147907304#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/15,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization##

#1.5 #E4115BE7AD64001700000717000009000004D50C1DC42D43#1360147922305#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/15,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization##

#1.5 #E4115BE7AD64001600000784000009000004D50C1EA91D5D#1360147937305#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/15,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization##

#1.5 #E4115BE7AD640024000003F8000009000004D50C1F8D97E2#1360147952275#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/60,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem VMC Overview: No Authorization##

#1.5 #E4115BE7AD64003B00000375000009000004D50C1F8D9897#1360147952276#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ExRun:WILYHOST_SCHEDULER_12,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.AbstractAction - run(): Action SAP GC|EPQ_JC01_server0 not running because status is WAITING_FOR_DESTINATION##

#1.5 #E4115BE7AD6400120000078B000009000004D50C1F8DA968#1360147952280#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ AbapSystem/60,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Database: No Authorization##

#1.5 #E4115BE7AD64001600000785000009000004D50C1F8E0BC1#1360147952305#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/15,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization##

#1.5 #E4115BE7AD64001900000F67000009000004D50C1FDD7881#1360147957510#com.sap.smd.e2edcc.host##com.sap.smd.e2edcc.host#######Thread[ExRun:OutsideDiscovery_1,5,OutsideDiscovery:ExecTG]##0#0#Info##Plain###[PhysicalHostPushJob] wakeup#

#1.5 #E4115BE7AD64001900000F68000009000004D50C1FDD7B4C#1360147957511#com.sap.smd.e2edcc.host##com.sap.smd.e2edcc.host#######Thread[ExRun:OutsideDiscovery_1,5,OutsideDiscovery:ExecTG]##0#0#Info##Plain###[PhysicalHostPushJob:getComputerSystemFromSMDAgent] Accessing host information from the SMD Agent.#

#1.5 #E4115BE7AD64001900000F69000009000004D50C1FFC9058#1360147959547#SMDloggerSystem##SMDloggerSystem#######Thread[ExRun:OutsideDiscovery_1,5,OutsideDiscovery:ExecTG]##0#0#Info##Plain###Reading JStartup environment...#

#1.5 #E4115BE7AD64001900000F6A000009000004D50C1FFC90FA#1360147959547#SMDloggerSystem##SMDloggerSystem#######Thread[ExRun:OutsideDiscovery_1,5,OutsideDiscovery:ExecTG]##0#0#Info##Plain###'SAPLOCALHOST' found, The value 'AP-EHV01-SAP' will be used to determine the Agent name.#

#1.5 #E4115BE7AD64001900000F6B000009000004D50C1FFC98F4#1360147959549#SMDloggerSystem##SMDloggerSystem#######Thread[ExRun:OutsideDiscovery_1,5,OutsideDiscovery:ExecTG]##0#0#Info##Plain###InetAddress Resolving for 'AP-EHV01-SAP' - FQN: ap-ehv01-sap.its.centric.lan SQN: AP-EHV01-SAP IP: 10.5.199.110#

#1.5 #E4115BE7AD64001900000F6C000009000004D50C1FFC9E2B#1360147959551#SMDloggerSystem##SMDloggerSystem#######Thread[ExRun:OutsideDiscovery_1,5,OutsideDiscovery:ExecTG]##0#0#Info##Plain###InetAddress Resolving for localhost - FQN: ap-ehv01-sap.its.centric.lan SQN: AP-EHV01-SAP IP: 10.5.199.110#

#1.5 #E4115BE7AD64001900000F6D000009000004D50C1FFC9F9C#1360147959551#com.sap.smd.e2edcc.host##com.sap.smd.e2edcc.host#######Thread[ExRun:OutsideDiscovery_1,5,OutsideDiscovery:ExecTG]##0#0#Info##Plain###[PhysicalHostPushJob] Check cached host information.#

#1.5 #E4115BE7AD64001900000F6E000009000004D50C1FFCA061#1360147959551#com.sap.smd.e2edcc.host##com.sap.smd.e2edcc.host#######Thread[ExRun:OutsideDiscovery_1,5,OutsideDiscovery:ExecTG]##0#0#Info##Plain###[PhysicalHostPushJob] end.#

#1.5 #E4115BE7AD64001C00000B87000009000004D50C201BFC95#1360147961606#com.sap.smd.e2edcc.db##com.sap.smd.e2edcc.db#######Thread[ExRun:OutsideDiscovery_3,5,OutsideDiscovery:ExecTG]##0#0#Info##Plain###[DatabaseInfoPushJob] wakeup#

#1.5 #E4115BE7AD64001C00000B88000009000004D50C20266202#1360147962287#com.sap.smd.e2edcc.db##com.sap.smd.e2edcc.db#######Thread[ExRun:OutsideDiscovery_3,5,OutsideDiscovery:ExecTG]##0#0#Info##Plain###[DatabaseInfoPushJob] Check cached database information for Database[ECQ][ECQ][mss]#

#1.5 #E4115BE7AD64001C00000B89000009000004D50C202662E2#1360147962287#com.sap.smd.e2edcc.db##com.sap.smd.e2edcc.db#######Thread[ExRun:OutsideDiscovery_3,5,OutsideDiscovery:ExecTG]##0#0#Info##Plain###[DatabaseInfoPushJob] Database information do not require update.#

#1.5 #E4115BE7AD64001C00000B8A000009000004D50C202663DC#1360147962288#com.sap.smd.e2edcc.db##com.sap.smd.e2edcc.db#######Thread[ExRun:OutsideDiscovery_3,5,OutsideDiscovery:ExecTG]##0#0#Info##Plain###[DatabaseInfoPushJob] Check cached database information for Database[ECQ][EPQ][mss]#

#1.5 #E4115BE7AD64001C00000B8B000009000004D50C2026648D#1360147962288#com.sap.smd.e2edcc.db##com.sap.smd.e2edcc.db#######Thread[ExRun:OutsideDiscovery_3,5,OutsideDiscovery:ExecTG]##0#0#Info##Plain###[DatabaseInfoPushJob] Database information do not require update.#

#1.5 #E4115BE7AD64001C00000B8C000009000004D50C202665BA#1360147962288#com.sap.smd.e2edcc.db##com.sap.smd.e2edcc.db#######Thread[ExRun:OutsideDiscovery_3,5,OutsideDiscovery:ExecTG]##0#0#Info##Plain###[DatabaseInfoPushJob] end.#

#1.5 #E4115BE7AD64001700000718000009000004D50C2072FB14#1360147967306#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/15,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization##

#1.5 #E4115BE7AD6400470000001A000009000004D50C2157E720#1360147982305#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/15,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization##

#1.5 #E4115BE7AD6400350000036E000009000004D50C223CD468#1360147997306#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/15,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization##

#1.5 #E4115BE7AD64001600000786000009000004D50C23214A5F#1360148012275#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/60,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem VMC Overview: No Authorization##

#1.5 #E4115BE7AD640013000007D8000009000004D50C23215133#1360148012277#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ExRun:WILYHOST_SCHEDULER_6,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.AbstractAction - run(): Action SAP GC|EPQ_JC01_server0 not running because status is WAITING_FOR_DESTINATION##

#1.5 #E4115BE7AD6400150000076B000009000004D50C23215C45#1360148012280#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ AbapSystem/60,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Database: No Authorization##

#1.5 #E4115BE7AD6400350000036F000009000004D50C2321BE48#1360148012305#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/15,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization##

#1.5 #E4115BE7AD6400470000001B000009000004D50C2406ACA5#1360148027305#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstance/15,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Warning##Java###com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization##

and in another log

Feb 6, 2013 12:03:32 PM [Thread[ECQ AbapSystem/60,5,WILYHOST_SCHEDU...] Warning    com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Database: No Authorization

Feb 6, 2013 12:03:32 PM [Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstanc...] Warning    com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization

Feb 6, 2013 12:03:47 PM [Thread[ECQ|ap-ehv01-sap_ECQ_00 AbapInstanc...] Warning    com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup - processResponseTimes(...): Error for ActionItem Work processes|Dispatcher Queue: No Authorization

[Former Member]

Mmmm tried it again this morning and got a totally different error than the one above

Now I am getting an error on path but the path is there....

DetailedInformation.FailedtocreateIntroscopeAgentConnectorat:E:\usr\sap\DAA\SMDA98\SMDAgent\applications.config\com.sap.smd.agent.application.wily\BytecodeAgent\ISAGENT.8.2.3.5-2011-09-13\wily\connectors(DetailedInformation.java:12)

DetailedInformation.STDOUT:(DetailedInformation.java:13)

DetailedInformation.STERR:Thesystemcannotfindthepathspecified.(DetailedInformation.java:14)

  Check Context

Managed systems setup | Managed System Setup Activities | SYSTEM =<SID>~JAVA

[Former Member]

Hi Christian,

you posted that your System characteristics changed : "this has been removed and replaced with a java only portal (so no JC01 but J01 )".

I had this issue several times, too, especially older Java-based Systems being upgraded "into this new instance naming convention".

To resolve this issue, check you landscape Parameters in SOLMAN_SETUP. There you can Change "JC" to "J".

Regards,

Dirk Osburg