Managed System Configuration - Software version and OS is not accepting

Dear
When i try to setup the PI system in solman 7.1 - Managed system configuration, below the error msg.
Please help to sort it the problem
Regards
Jay

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

Similar Messages

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.

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

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

SolMan 7.1 SP10: Managed Systems Configuration: client 000 OK, client 100 error

Hello,
after installing SolMan 7.1 SP10 successfully I also completed the steps "System Preparation" and "Basic Configuration".
Now I'm connecting the managed ABAP systems to the Solution Manager by performing step "Managed Systems Configuration".
After several other ABAP systems I'm now connecting our productive CRM 7.0 EHP1 system "CM3" (SAP_BASIS 702).
I also connected the CRM development and CRM quality assurance system without a problem.
For client 000 everything worked fine, the RFC destinations were created and a green light is shown.
Now the problem is to connect the productive client 100:
The log for Activity RFC Connection says:
The corresponding dev_rfc tracefile says:
**** Trace file opened at 20140326 164911 W. Europe Standard Time, by disp+work
**** Versions SAP-REL 720,0,523 RFC-VER U 3 1468763 MT-SL
======> Name oder Kennwort ist nicht korrekt (Wiederholen Sie die Anmeldung)
ABAP Programm: SAPLSM_SETUP_API (Transaction: )
Called function module: FUNCTION_EXISTS
User: SOLMAN_ADMIN (Client: 001)
Destination: 0050568713C71ED3AD9FC4F78AC9D9EB (Handle: 16, DtConId: 27FEB4E356BCF14F99EB0050568713C7, DtConCnt: 1, ConvId: 64734943,{27FEB4E3-56BC-F14F-99EB-0050568713C7})
EPP RootContextId: 0050568713C71ED3AD9FB7AD4C4859EB, ConnectionId: 0050568713C71ED3AD9FB784232C59EB, ConnectionCnt: 1
EPP TransactionId: BDFDB4E3626AF14899EB0050568713C7
But both users taken to execute this step (SAP Solution Manager Administrator "SOLMAN_ADMIN" and Managed System Configuration User "SM_ADMIN_SM3") exist and have the correct provided password.
Does anyone have a clue?
Kind regards
Rüdiger Höckel

Hello Ranjith,
thanks for your quick response.
The ST-A/PI software component is the same on all systems: 01Q_700 #2.
SolMan system: SM3
CRM systems: CM0 (ok), CM1 (ok), CM3 (problem with client 100, client 000 OK).
I also tried the recommendation found in the SAP Community Network
(http://scn.sap.com/thread/3483642) but this didn't help either:
1.Delete system from LMDB.
2.Delete system from SLD of solman.
3.Re- register the system to SLD of solman(rz70 for AS ABAP)
[the LMDB synchronizes with the SLD every 10 minutes, system CM3 is visible again in the LMDB]
4.Now follow the steps in managed system configuration.
The wizard worked fine for client 000 but throws this error for client 100.
I use all the latest installation and configuration guides.
For this step I'm using the guide "Managed System Configuration" that is available in the SOLMAN_SETUP wiki.
https://websmp206.sap-ag.de/~sapidb/011000358700001120342013E.pdf
Kind regards
Rüdiger
P.S. In total I have already connected eight systems (SAP_BASIS 700 to 731) but this is the first system that gives an error.

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

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

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

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.

Syntax error in program CL_AC_METRIC_REPOSITORY=======CP When going to managed system configuration in solman 7.1

Dear SAP Gurus,
Good Morning.
I'm getting error in managed system configuration in solman 7.1. Error is like
The system preparation and Basic configuration in working fine, but when we are going to click the managed system configuration Error getting like this.
Solution Manager Version : 7.1
SP Level : SP5
Thanks in Advance.
Regrads,
Kumar BN

Hello Kumar,
I would suggest moving this discussion to this space in SCN: http://scn.sap.com/community/it-management/alm/solution-manager
That will help get you a quicker response.
Thank you,
Kristen

MAnaged system configuration error in solution manager

Hi,
While doing managed system configuration getting the error, below versions are using.
MDM 7.1 SP10 Import server and Solution manager 7.1 SP10.
Can anyone help me?.
Regards
Chandra

Two cases you have
1) Satellite system
Re-install The DIA agent and give correct (port numbers )SLD details
Once you re-install the DIA agent, run Rz70 from satellite system
data will pull from satellite system to central SLD.
2)Run SLD check from Solman system , check its successful or not
Go to LMDB and check satellite system
After re-Synchronize technical system from SLD
Thanks ,
Rahul yedapally

Managed System Configuration Error for MDM 7.1 SP09

Greetings, Needed your expert advise. We are getting an error while configuring our MDM Servers (Version 7.1.08.196) in Solution Manager. As suggested in SAP Note 1798643 , I have manually filled the required details and transferred through sldreg.exe to SLD. Now when i try to perform Managed System Configuration, it is throwing the below error. The definition of Technical System '~MDM' is not correct: '~MDM': No Path found in Installed Technical System 'SID~MDM~'. I'm not sure how to manually update the Install Path for our MDM Servers. Since, the data to LMDB is automatically supplied, I might not be able to manually edit anything. Could you please advise if there is any step to solve this issue. Thanks, Haseeb Ahmed.

Dear ,
Haseeb,
I had the exact same problem with MDM managed system setup . I was on MDM 7.1 SP10.
1940337 - RCA template for Solution Manager 7.10 SP10
This note should resolve your problem. This note has the updated template for MDM.
It did for mine
Thanks
Amit

Change Management System configuration

Dear Experts.
I have some problem with Change Management System configuration, probably it hasn't installed properly,
but I cannot tell certain description of the problem to the BASIS administrator.
The problem is the following:
At first, then I logon into CMS by the first time, in the tab Domain Data obligatory input fields CMS User and CMS Password are the empty. Whitch username anew password values I should input in those input fields?
The other problem is then I'm trying to create the new Track: in the tab Track Data input Id and Name of the Track,
and pushing the Save Button, in the left table it doesn't appear. And then I trying to add Software Components to the Track, pushing the button Add SC, but the component list is empty.
Edited by: Sergey Tuzov on Apr 25, 2008 11:28 AM

We has found the problem issue by our self.
The user account for CMS has no role with permission to SLD component access.
Therefore, there was no access to SLD resources: software component and others.
Thanks' for you attention to my topic.

Transport Management System Configuration

Hi,
I have a question here, on Transport Management System.
We have new 64 bit boxes. I first migrated our dev SCM 4.0 box from 32 bit to 64 bit, it asked for being a Domain Controller. Configured it as a Domain Controller, and continued with the upgrade and completed the upgrade.
Now, I am going to the second box (QAS). I have performed the migration from 32 bit to 64 bit. Now, when I login to this box, in my understanding, TMS should offer to make this system part of the already existing domain right? It doesn't happen that way. It is forming itself again as a domain controller. After some changes and update configurations on both the boxes, the QAS box now says, "Waiting to be added into the domain by the domain controller" something similar to this. But, when I go and login to the domain controller (DEV), it doesn't show anything there.
In the QAS system when I go to the System Overview, I see both the systems but, they both show under the two different transport groups. I am totally confused here. Am I doing something wrong here? The only problem I see here is, the domain controller (DEV) is on SCM 5.0 as it is already upgraded from SCM 4.0 but the QAS is still in SCM 4.0 and waiting to be upgraded. Do you think this could be a potential problem? If so, what is the solution to continue with the upgrade because, I am sure the upgrade won't work without the Transport Management System configured properly.
Please help.
Thank you.

Hi Gus,
Thank you for the prompt response. Thank you.
There are couple of things to be considered before following your suggestion.
1. Our QAS box is in Kernel 6.40 (32 bit) and my DEV (upgraded) is in Kernel 7.00 (64 bit). In this kind of heterogeneous environment, I am sure the R3trans versions should be different. Is it possible to configure the transport management using the shared transport directory (Transport Group)?
2. Now, when I login to the QAS box, as I said in my previous message, I see two entries. One it should the APD (Domain Controller) with a different transport group. And I see the APQ in a different transport group. The problem here is, I cannot edit or delete any of the entries in the APQ - STMS because, it keeps saying all changes could be made only in the domain controller. A point to be noted here is, even though it shows two different transport group, it points to the same transport domain 'DOMAIN_APD'. Another thing to be noted here is when I look at the domain controller (APD), I don't see an entry for APQ or any awaiting approval requests.
Kindly suggest what needs to be done here.
Thank you.

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.

Managed System Configuration - Software version and OS is not accepting

Similar Messages

Maybe you are looking for