Managed System Configuration

Dear Team,
While doing managed system configuration for AS JAVA system (only used for BI JAVA) we are getting error as "Solman System prerequisite are not met" ST-A/PI 01P_700 is not installed.
When Checked in Solman system ; However the ST-A/PI is higher version than what is asked for. It has version of ST-A/PI 01R_700.
Our solman is at 7.1 SPS 08
Please suggest how to go ahead.
Regards,
King Arthur

Dear Divyanshu,
I have done managed system configuration for ABAP only stack on NW 7.01 ECC and it went successful.
However at that time my ST-A/PI was on lower version than ST-A/PI 01R_700 (i.e. somewhere on P or Q version)
Now I am trying to do for Managed system which is Only JAVA stack....and is based on NW 7.41.

Similar Messages

I can not make a "Automated Installation of the Introscope Agent" (Managed System Configuration, p.7)

I can not make a "Byte Code Adapter Installation"
When I open meets both paragraphs in step Managed System Configuration is somewhat obscure situations that do not allow the automatic configuration Introscope agent and Introscope Manager
Please help to resolve a number of questions that might help me complete the setup :
1. Why has the status of Enterprise Manager : <No Enterprise Manager configured> ( see picture)
I set up Enterprise Manager in accordance with the installation instructions and complied with all the setting items . Since without any configuration can be associated with the appearance of this status ?
2 . Why Server Node is empty detail settings ?
JDK Location:
Enterprise Manager Host:
Enterprise Manager Port:
Introscope Agent Name:
Introscope Agent Profile:
Autoprobe Directives:
Wily Version:
Introscope Agent Version:
Introscope Agent Log Location:
3 . What a mistake ($ MC: DIAG_WILY_MSG: 032 : L), which appears when I click configuration "Configure Introscope Agent Setup ...", and what it can be linked ? ( see picture )
And the last question , which is also linked to the process of automatic configuration and refers to a phrase from the instruction (Introscope Version 9
Installation Guide For SAP July 2012) points out "Automated Installation of the Introscope Agent via SMD"
there is such an item:
2 . Deploy ISAGENTJ5 *. SCA which is the Introscope Java Agent 9 with SDM to Solution Manager. You may need to deploy also ISAGENT *. SCA which is Introscope Java Agent 8.
However, nowhere does it say where exactly ( on what the absolute path ) I must perform unloading and then what to do with this discharge

The problem was resolved a small manipulation - on stage Basic Configuration,
point 3 "Configure CA Introscope"
I forgot to add to the list of CA Introscope Enterprise Managers link to my manager.
Thus it is necessary to take into account that the path should be correct (usually for linux - /usr/sap/ccms/apmintroscope) and the directory should be applied appropriate privileges.
Then in paragraph "Byte Code Adapter Installation" - there are all the necessary data, and it starts to work correctly

Understanding and using Logical Components for Managed System configuration

Experts.....
I am embarking on a fresh installation of SolMan 7 EhP1 SPS25 and after a few bugs along the way, I am finally nearing the end of including the first Managed System. Somewhat related to {forum:id=10293771] I am hoping I can get some advice, but specifically with regards to Logical Components.
General question - I have a slide from SAP that shows a picture from Product->System->Instance->Logical System (client)->Logical Component. I am confused because it shows that Client 100 of a given ABAP system could be assigned to Logical Component A, whereas Client 200 of the same system could be assigned to Logical Component B. This seems wrong to me?
I am at the last step of the managed systems configuration wizard : "create logical components" and only want to ensure that I set things up to hopefully ensure that later usages (Maintenance Optimizer, etc) will handle things correctly!!!
- Our SAP landscape is not very complex
1. only ERP and EP (Dev/Test/Prod).
2. We are utilizing HR Self Service (XSS).
3. The ERP ABAP systems are on Netweaver 7.01.
4. EhP4 has been installed, however we only activated the HCM business functions. Therefore SAP_HR is on 604 whereas SAP_APPL is on 600. I think this might be driving some of the confusion in SMSY
For the DEV ABAP system I am trying to configure:
1. The system is showing up in two products : "SAP ERP" and "SAP ERP Enhancement Package" with the header data for both showing "EHP4 FOR SAP ERP 6.0 / NW7.01" and "SAP ERP 6.0"
2. Under "SAP ERP" the "product instance selection" shows only "SAP NW - Adobe Docu. Service" and "SAP ECC Server" as relevant
3. Under ""SAP ERP Enhancement Package" the "product instance selection" shows only "Human Capital Mgmt" as relevant by default. I manually flagged the development portal system as "relevant" for "SAP XSS (Self Services)"
4. The RCA DBA Cockpit system is complaining "No data available for extractor activation. Please check product mapping and Software Components in SMSY"
5. In the Managed System wizard, there is no logical component for any of the "EHP4 FOR SAP ERP 6.0 / NW7.01" selections
From what I can tell, I think this is correct:
1. Create a Z_EHP4 logical component and assign the DEV/QAS/PRD systems to them
2. Also assign the DEV/QAS/PRD to the existing SAP logical component "SAP ERP ECC SERVER"???
3. For the Solutions, my plan is to create
a. Non-Production ERP : with the dev/test erp/ep systems, but test system as the leading system
b. Production ERP with the prod erp/ep systems only
Thanks for any advice/guidance to help me avoid future problems!!
Edited by: Eric Poellinger on Jun 15, 2011 6:32 PM

General question - I have a slide from SAP that shows a picture from Product->System->Instance->Logical System (client)->Logical Component. I am confused because it shows that Client 100 of a given ABAP system could be assigned to Logical Component A, whereas Client 200 of the same system could be assigned to Logical Component B. This seems wrong to me?
Client 100 could be assigned to any number of logical components, client 200 could be assigned to those same ones or none of them. A logical component is just a grouping of systems used to accomplish some task in SolMan.
For example with ChaRM you could have 2 logical components.
ZCHARM_DEV development (100) -> QA (200) -> prod (300)
ZCHARM_SEC security (900) -> QA (200) -> prod(300)
One is used to show the path for moving development changes to prod, the other for security changes. 200 belongs to both, but 100 only to one.
Set them up in whatever way meets you needs. It looks like for you, you could just use the default one and assign your clients to the various system roles. Not all functionality in SolMan uses the logical components though.

Link SAP PI 7.3 to SolMan 7.1 - error during managed system configuration

All,
I installed my diagnostics agent twice with different options:
- Direct P4 connection via Java EE Dispatcher Node with port 5xx04
- P4 connection via SCS message server with port 81xx
In both cases I get an error during the managed system configuration of SAP PI 7.3: Remote error : Connection to P4 port of managed system failed.
I'm a bit confused with the step Enter System Parameters. In the Java parameters section, I can only enter port 39xx. if not, I get an error.
Also, I marked and unmarked the option concerning the ABAP user store, but the error persists.
Please advice.
Thanks a lot.

Hi Allam,
I checked the KBA and I think now, I have the correct HTTP port.
The error I now get is S:CL_DIAGSTP_MESSAGE:483
When I take the next step, Configure Automatically, I get this error during the Byte Code Adapter Installation phase when I open the Java URL stated in the navigation column:
DIAG_WILY_MSG:157:S - com.sap.smdagent.vmmanager.VMManagerP4Exception: com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException: Access is denied to SAP System sid: check the connection credentials.More details about the error in agent 'sappi' 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 idea?
Thanks.

Configuration Check Error in Managed System Configuration

Hi dear experts,
I come across a problem as the screenshot shows blew:
I check some relevant information, but no issues found:
1.
DEWDFLSSC5062:/usr/sap/hostctrl/exe # ./saphostexec -status
saphostexec running (pid = 7094)
sapstartsrv running (pid = 7097)
10:46:34 24.06.2014 LOG: Using PerfDir (DIR_PERF) = /usr/sap/tmp
saposcol running (pid = 7130)
DEWDFLSSC5062:/usr/sap/hostctrl/exe # cat host_profile
SAPSYSTEMNAME = SAP
SAPSYSTEM = 99
service/porttypes = SAPHostControl SAPOscol SAPCCMS
DIR_LIBRARY = /usr/sap/hostctrl/exe
DIR_EXECUTABLE = /usr/sap/hostctrl/exe
DIR_PROFILE = /usr/sap/hostctrl/exe
DIR_GLOBAL = /usr/sap/hostctrl/exe
DIR_INSTANCE = /usr/sap/hostctrl/exe
DIR_HOME = /usr/sap/hostctrl/work
service/admin_users = daaadm
service/logfile_000 = /tmp/s
service/logfile_001 = /usr/sap/DAA/SMDA97/SMDAgent/log/smdagent_trace*.trc
service/logfile_002 = /usr/sap/DAA/SMDA97/SMDAgent/log/smdagent_trace.*.trc
service/logfile_003 = /usr/sap/DAA/SMDA97/SMDAgent/log/smdagent_trace.trc
And the version of hostagent is up-to-date.
2.The URL
- http://<SMDhost>:1128/SAPOscol/?wsdl
- http://<SMDhost>:1128/SAPHostControl/?wsdl
can be accessed.
3.The step 3 in managed systems configuration is executed successfully.
4.I have even uninstalled and re-installed the SMD and hostagent, and change the alert_timeout parameter in T-code DMD, but the issue insisted.
5.Only a few SMDs in my landscape, so I think the parameter MaxThreadCount, InitialThreadCount, MinThreadCount should be no problem.
Now I have no idea how to proceed, please give me some advice, thank you in advance.
Best Regards,
Pany Pan

Hi Pany
Kindly check the below two sapnote
1935653 - Error "A timeout occured during the execution of the OS Command Console" when performing a Managed System Configuration - Solution Manager 7.1
1865122 - Solution Manager 7.10 Configuration Check errors : "A timeout occured during the execution of the OS Command Console" "An unexpected error occured"
Moreover , you need to check/verify/maintain the parameter in configtool
ThreadManager -> MaxThreadCount
Total number of Diagnostics Agents * 2 + 50
1250
ThreadManager -> InitialThreadCount
Total number of Diagnostics Agents * 1.5
900
ThreadManager -> MinThreadCount
Total number of Diagnostics Agents
600
ConnectionManipulator -> maxSoTimeOutConnections
Total number of Diagnostics Agents * 1.35
810
ConnectionManipulator -> MaxParallelUsers
Total number of Diagnostics Agents + 50
650
In Diagnostics Agent Troubleshooting - SAP Solution Manager Setup - SCN Wiki
guide check the section Required Solution Manager Java Stack Settings (Scalability)
I face the same issue , which got resolved by maintaining the above parameters, maxthreadCount,
minthreadcount , maxSoTimeOutConnections.
With Regards
Ashutosh Chaturvedi

Error in Managed system configuration.

Hi Folks,
In Solman 7.1 i am configuring my Java system in managed system configuration on the last phase of configuration which is "Check Configuration" i got the below error...
Can any one guide me on this....
I installed the Diagnostic agent as well as willy inter scope.
Regards,
Anil.

check the note which describes your problem
1776959 - Solution Manager 7.1 Manged System configuration. Error: Timezone from managed system could not be retrieved: Timezone of J2EE Engine (GMT+01:00) does not match the timezone of the diagnostics agent (Europe/Berlin)
Resolution
Open the instance.properties file of the J2EE Engine on the managed system
Locate the parameter "-Duser.timezone=" and its value
If the -Duser.timezone is not set the JVM uses GMT
Set the -Duser.timezone parameter in the JVM of the SMD Agent. If there was no "-Duser.timezone in the J2EE's instance.properties file use the timezone that was indicated in the error message e.g. GMT+01:00 (from the above error message, this might differ on your environment) To do this:
Locate the smd.properties file (for newer agents the files is called: smdagent.properties)
The path is: .../usr/sap/<DiagnosticAgentSID>/SMDA<SYSNumber>/SMDAgent/smdagent.properties
The -Duser.timezone= parameter of the Diagnostics Agent and the SAP J2EE engine need to be set to the same timezone. That means the string needs to be the same for both parameters
e.g.
If the -Duser.timezone= parameter of the J2EE engine is set to -Duser.timezone="GMT+01:00"
set the Diagnostics Agent parameter to:
smdagent.javaParameters=-DP4ClassLoad=P4Connection -Xmx256m -Xms256m -Duser.timezone="GMT+01:00"
Restart the Agent
Re-run the "Configuration Check" in the "Managed System Configuration"
Please make sure that the time zone configuration is correct according to the SAP recommendations: http://wiki.sdn.sap.com/wiki/display/Basis/Timezone+changes+best+practices

SQL Error 0 during DBACockpit setup in Managed System Configuration

Hi All,
I'm getting SQL Error 0 during DBA Cockpit setup in Managed system configuration. I'm trying to connect MsSQL 2005 from Linux system(Solution Manager 7.1 SP10). I have installed necessary ODBC and microsoft drivers. Any suggestions will be appreciated.
Regards,
Pragadees

If I've understood you correctly, you are trying to setup a remote database connection from an SAP Solution Manager system running on Linux with a database which is NOT MSSQL to a database which is MSSQL running on Windows.
In that case have you checked these SAP notes ?
1265134 - DBA Cockpit: Connecting a remote database
1388700 - SolMan 7.0 EHP1 Database Warehouse for MSSQL
Regards
RB

Technical Systems in Managed System Configuration greyed .

Hi,
I upgraded ST-SER to 701_2010_1 SP0 and in the process of upgrading
this tool I had to also patch other components like ABAP,BASIS etc as
pre-requisites for this.
As this involved all the components to be patched, I
executed the initial,Basic configuration in solman_setup and everything
is fine.
In Initial I executed only the read SLD and skipped the other steps as
the other steps have been already executed after install of solution
manager .
In Basic Configuration I have executed all steps and everything has
executed successfully.
The problem is in Managed system configuration.
I have the Wily Introscope Manager Console showing all the statistics
of Agents and all Agents are attached.
The problem I see is first thing is the technical setting in the
Managed system diagnostics are greyed why is it ?
Second is when I execute the Managed system Diagnostics configuration , the first step Wily host agent fails all other steps are okay.
The error in this step is "No connection to any Wily Enterprise Manager"
Appreciate any advise.
Thanks,
Misba

Hello Diego,
I started getting this error only after I upgraded the tools, even now the Wily is up and running and I can see the dashboard with all the live diagnostics graphs and statistics for ABAP & JAVA. All the steps have executed successfully except this one step. Even trusted RFC's are okay. This was an established system with all configurations.
So I am surprised what I am missing. Can you please explain to me more about how I can see " http://<ip>:<port>/SMD under "managed systems" ->Introscope Agent ".
All Agents are attached and in Agent adminstration I can see all the Agents online.
Thanks,
Misba

Software Prerequisites in managed system configuration are not fulfilled

Hello dear Forum,
I'm facing a problem when I configure a PI system in managed system configuration. I register the Netweaver PI AS ABAP technical system to solman's SLD directly(run RZ70), and collect the information of the Netweaver PI AS JAVA from the PI's sld. I don't know whether it matters.
The following error occurs when I Check Prerequisites:
J2EE-FRMW does not fulfill the prerequisites (installed: 7.11 SP0, expected: 7.11 SP001)
But I don't know how to find J2EE-FRMW 7.11 SP001 and do some update, please give me some advice.
Best regards and thanks for your help,
Pany

Hi Pany,
Steps to follow
- Rename the J2EEFRMW01_5-20002637.zip file to J2EEFRMW01_5-20002637.SCA.
-telnet localhost 5$$08
-logon with the user administrator
- deploy /software/j2eefrmwpatch/J2EEFRMW01_5-20002637.SCA version_rule=all
- Once it is done , then trigger the data to the SLD
- Checked the software component in SLD
- Resync the LMDB with SLD
- Then performed the activity of manage system Configuration.
With Regards
Ashutosh Chaturvedi

Warnings in Managed System Configuration

Dear all,
We are in the process of connecting a satellite system to Solman 7.1 and to monitor its datas.
So in Managed system configuration for system, we are facing some warnings in step 8 and step 11.
In step 8(Configure Automatically),Generate System level metrics ended with a warning i.e "The Diagnostic Agent for Introscope Enterprise manager could not be found"
In step 11,(Configuration),Configuration check ended with warnings.
i.e Errors found during the last 20 run for extractor
Kindly suggest on how to proceed further.
Thanks,
Regards,
Hasan

Hello Diego,
Sorry for the late reply..
Yea the Enterprise Manager is running.
When i tried the URL which you had given, it is displaying as 404 not found.
Also when i start the Diagnostic agent in the SOLMAN, it is getting started and it is showing green LED in MMC, but when I try to connect the Diagnostic Agent to Solman in Basic configuration step, it is turning yellow and displays as,
""Access denied by the Managing System
Check username/password
Managing System details:
host hllsap12
port 8103
Last operational status 272"
After this the Diagnostic agent turns to yellow in MMC also..
Kindly advice,
Thank You,
Regards,
Hasan

Managed system configuration, step:Check Prerequisites

hi firends,
We've updated our SLM system up to SP13 and import finished success.
When we starts managed system conf from menu SOLMAN_SETUP - Managed System Configuration - Configure System - Check Prerequisites, execution return error that system prerequisites are not fullfilled.
But from menu Status all SP's are correct
Additionally screenshot added to attachment
please help me to resolve this problem.
P.S. all other steps in Managed system conf wizard finished Success.
Thanks in advance
Shahin

Hi Matthias,
Please review SAP Note 1571442 as it might be helpful in resolving this error message.

Managed system Configuration Diagnostics Prerequisites check fail

Dear All,
My solman_setup initial configuration part and basic configuration part all passed without error. And when I do the managed system configuration part , first I choose the solution manager itself and the client 001 to config , and then the maintain connection passed OK , but in the next step , check Prerequisites, it fails. The Navigation Button just open a link to the SAP Service Market Place, and the IMG documentation just let me to see the note 1010428. The deatl part of the execuation result of the Prerequisites open a page but with error statement as below :
Service cannot be reached
What has happened?
URL https://sapsolmgr.centurydsp.com:8000/webdynpro/dispatcher/sap.com/tcsmdnavigation/StandaloneApp call was terminated because the corresponding service is not available.
Note
The termination occurred in system SM2 with error code 404 and for the reason Not found.
The selected virtual host was 0 .
What can I do?
Please select a valid URL.
If you do not yet have a user ID, contact your system administrator.
ErrorCode:ICF-NF-https-c:000-u:SAPSYS-l:E-i:SAPSOLMGR_SM2_00-v:0-s:404-r:Notfound
HTTP 404 - Not found
Your SAP Internet Communication Framework Team
Any comment will be appreciated.
Enddy.

Hello Enddy,
This sounds as if you have yet to configure the HTTP services in SPRO or have misconfigured them. Please review your configuration for the HTTP Services as it should resolve your issue.
Please review the diagnostics URL to see if it helps you out:
http://service.sap.com/diagnostics
Also, please review the following SAP Notes which will also guide you through diagnostics and solution manager setup/installation:
1010428 End-to-End Diagnostics
1145779 SAP Solution Manager 7.0 Installation
1163836 Solution Manager Diagnostics required for troubleshooting
Also pay attention to the relevant notes listed on the bottom of these. If you follow these documents, I'm sure you will have your issue resolved.
Hope this helps you out!
Thanks,
Mark

Managed System Configuration step Assign Diagnostics Agent

Dear Experts,
We've newly instaled solution manager system 7.0 Ehp1 via latest sp stack 25 on aix 6.1, we've completed initial and basic configuraiton successfully via solman_setup, and instaled wily introscpe on same host with solution manager system,
Now i am trying to managed system configuration for solution manager system via solman_setup step Assign Diagnostics Agent as demo link below
https://service.sap.com/~sapidb/011000358700001735062008E
I opend http://>SOLMANHOST>:<SOLMANPORT>/smd/go/ADMIN_AGENT
>> Agent Candidates Management
>> Connection Parameters
>> Custom SLD Parameters > Aply and the selected the SMD instance then trying to attached via password SMD_ADMIN
But agent registration is waiting, SMD_ADMIN user is creating when i execute intial configuration, after i change the intial password, password is correct, so why the agent state is waitng status, i also push sld Setting for all from SMD view tab,
I've also try to restart SMD agent, /usr/sap/SMD/J98/SMDAgent/log/SMDSystem.0.log file after restart
Oct 28, 2010 11:07:25 AM [Thread[main,5,main]] Info       Starting SMDAgent ...
Oct 28, 2010 11:07:25 AM [Thread[main,5,main]] Info       ===> Establishing connection to server 'ms://ccisolman:8101/P4
Oct 28, 2010 11:07:28 AM [Thread[Connector,5,main]] Info       Smd connector is disabled because no SLD association and no credentials found.
Oct 28, 2010 11:07:32 AM [Thread[SLD-Registration,1,main]] Info       [SLDReg] Next try to push instance data in SLD is Thu Oct 28 23:07:32 EEST 2010
Best Regards

hi
pls chk again your sld parameters and check the correct user name, password entered in agent connection management under CUSTOM SLD(in agent candidates management)
jansi

Managed system configuration step 8: No Admin User Id provided for TS SID

Hello experts,
I face the following problem in step 8 of managed system configuration (Configure automatically, SolMan 7.1 SPS 3):
All Activities fail (except Activate services) with the following Details message:
No Admin User Id provided for TS <SID> (ABAP)
Any hint?
Thanks and best regards, Basti

Hi Sunny,
I don't find anything where I can provide the user information. It just uses the actual user (SOLMAN_ADMIN). Can you tell me where to provide the user for this step?
Managed system configuration -> step 8 Configure automatically -> SSO Setup
Thank you, Basti

Managed System Configuration ! The table does not contain any data !

Hi,
In Sol Man Setup , Managed System Configuration, in phase 6 - Create Logical Componets -
There is no Product Version and Product Instance Available.
The message is : " The table does not contain any data "
How can correct this problem ?
Thanks

Hi,
while creating new Logical Component via SMSY , you need to specify Product first.
e.g. if you managed system is ERP 6.0 , select Product as SAP ERP
once you select Product , it automatically fetches information for product Version and Main Instance depending upon Product field input.
Please check and let us know if issue still persits.
Thanks,
Rupali

Managed system Configuration : The JMX metrics of this Host / Byte Code Adapter are missing

Hi Friends
While Configuring EP system with SOLMAN 7.1 SP12 it is giving below message in self Diagnosis Phase.
1. Solman system is already having ISAGENT version 8 and 9 installed (but Managed system is having 8)
2. I have followed the automatic Process as below
==========================================
Automated Installation of the Introscope Agent via SMD
The Solution Manager provides an application that performs the setup of the Introscope
byte code agent for Java automatically. This section explains the steps to run the setup.
Before you can run the Introscope agent setup, the setup wizard for the managed system
must have been executed.
1.
2.
3.
4. Launch the Introscope Setup application: SAP Solution Manager Configuration 
Managed Systems Configuration  Step 7 Configure Automatically  Automatic
Activity “Byte Code Adapter Installation”  “Open Java URL” (only available in edit
mode). Your screen will look similar to the image below:
5. Check the Enterprise Manager Settings at the top of the screen. These are the
connection parameters that will be used by the agent to connect to the Enterprise
Manager.
6. In the pane Introscope Agent Setttings, select the system that you want to instrument
with the agent. Check “select all” and click “Retrieve Current Settings”. This will display
the current status of the agent setup.
7. To initially setup or update the agents, click Setup Introscope Agent …. This will open
the setup dialog as shown below. Select the desired agent version (by default only one
available) and choose the profile. Next, check the desired instrumentation areas, and,
in the case of AIX, review the AIX settings to match your environment (J9 or classic
mode).
8. Finally, hit Apply to perform the necessary changes in the agent configuration. Agent
config files will be adapted and the Java VM parameters will be set as required for the
managed system.
================================================================
3. Restarted SAP but error still present.
Please help to resolve the issue.
Thanks

Found the solution :
1819577 - Workload Analysis data missing for Java systems when using ISAGENT 8.2.4.0
Cause
l This issue has been identified as product defect and documented in note 1273028
Resolution
l As mentioned in note 1273028, update to ISAGENT 8.2.4 Patch 1 timestamp: 2012-06-26, please proceed as described below)
1. Enable the Maintenance Mode in the Agent Administration UI (http://solmanserver:port/smd/AgentAdmin)
2. Deploy the file to the Solution Manager JAVA stack using the Software Deployment Manager (SDM)
3. Disable the Maintenance Mode in the Agent Administration
4. Execute again the activity 'Byte Code Adapter Installation' of the step 'Configure Automatically' in the 'Managed System Configuration' for the
affected systems. This activity will deploy the new version of the
Introscope JAVA agent in the managed system servers and reconfigure the JVM parameters to use the new version of Introscope JAVA
Agent;
5. Check from Introscope Agent Admin if "IS Agent State" contains value "Running but needs restart"
6. Restart the affected managed system(s)
Finally Solution is update your SOLMAN system patch ISAGENT 8.2.4.0 from patch 0 to 1 via SDM.
Thanks
Mukesh

Managed System Configuration

Similar Messages

Maybe you are looking for