SOLMAN 7.1 Managed system(Maintain RFC's Step)

Hi All,
I am performing Managed System Configuration for PI system.
In the Maintain RFC's step I am facing below error.
SOLMAN (7.1 sp12). Kindly help me by suggesting how to resolve this issue.
I am attaching screen shots. If these can help
Error during connection to system PID / 100: Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=20 thRc=236 SAP gateway connection failed. Is ).
Thanks and Regards,
Solman Starter

Similar Messages

Solman 7.1 Managed system config for Dual stack

Hi All,
While running the step "WEB Services logical port creation" we are receiving a warning.
Message: Activity disabled : creation of communication user SM_COLL_XXX has not been flagged as being successful.
Details: Activity disabled : creation of communication user SM_COLL_XXX has not been flagged as being successful.
Please make sure the 'User and Roles' activity is executed successfully before executing this activity
When i check in "Create users" step. SM_COLL_XXX is Green led. I did not created this user from solman. I provided existing user. So whats the issue here..?
Please assist.
Thanks,
Rohan

I have the same problem as in the title.
create user log:
User SM_COLL_SMM registered
E:CL_DIAGSTP_MESSAGE:483 solman_admin
note 1659367 can implement
There are ways to solve the problem?

Managed System Configuration Super User Issue

Hi folks ,
I have a strange error in Solman SP8 Managed System Config .
In Step 5 : "Enter System Parameters" , for entering super user , it throws an error even though the user credentials are valid.
This happens for some of the managed systems only . The error says : " Issue with connection to system <SID> <Client>".
It does not seem to be using the right RFC and I feel it is checking for the user in 000 client , regardless of which client we give . Because if we give 000 credentials it works.
Please help . As without this I cannot save any of the system parameters like Load Balancer URL etc.
Thanks,
Shaswat

I have seen this exact issue when my IE cached the page and was stuck with the client 000 RFC's selected on step 3. I just exit managed sys config and clear my cache and start solman_setup again. To avoid this all together I set my IE to check for newer versions of stored pages every time I visit page. (under internet options -> general -> browsing history -> tempory internet files)
Then
In step 3 create the user to avoid security issues or auditor problems later on. This way the SM_ADMIN_XXX will have the proper roles required. Please note (The user is not authorized to use a Trusted RFC (authorization object S_RFCACL). To authorize the user, assign the role SAP_SM_S_RFCACL manually).
Confirm there is no error and hit next. For an explicit save.
Now go to step 5 and select the client that the RFC's were created on and hit test credentials.
This should solve your issue.

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

Connect two Solution Manager systems.

Hello,
We are planning to couple two Solution Manager systems.
We want to get all the alerts ABAP+JAVA(Root Cause) from one Solution Manager to the other.
What are te steps to take?
Connect the SLD's?
Connect the systems thru RFC?
Point all the agents to the 2 Solution Manager systems?
Regards,
Mike Geluk

Hello,
It is possible.
For SLD, two options:
- Each Solution Manager can use its own SLD. Then you must define the other server in the SLD, and vice-versa.
- Each Solution manager can connect to a central SLD where the two are defined.
The rest is just like any other managed system configuration: follow the steps in solman_setup.
Best regards,
Guiilherme

Error during Managed system setup "Wilyhost Agent" type

Hello All,
Managed system setup finished with one error. Iam using this for selfmonitoring (solman itself as managed system)
Error msg as follows.
0 Wilyhost Agent(s) from host inbbssun02 are connected to the EM.
Wilyhost Agent configuration finished without errors, but on Enterprise Manager (TDCTBI.india.tcs.com:6001) no Wilyhost Agent was detected from host inbbssun02. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
I checked jvm_SMDAgent.out. and log as follows.
/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Introscope Agent Release 8.0.2.0 (Build 470970)
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Using Java VM version "Java HotSpot(TM) 64-Bit Server VM 1.4.2_20-rev" from S
un Microsystems Inc.
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Trying to load agent profile based on system property "com.wily.introscope.ag
entProfile"
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Trying to load file from /usr/sap/SMD/J98/SMDAgent/applications.config/com.sa
p.smd.agent.application.wilyhost/IntroscopeSapAgent.profile
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Loaded file from /usr/sap/SMD/J98/SMDAgent/applications.config/com.sap.smd.ag
ent.application.wilyhost/IntroscopeSapAgent.profile
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging is turned off
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.heartbeatInterval i
s set to 1800
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.dataChunk is set to
500
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.numberTimeslices is
set to 3000
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Looking for agent profile property "introscope.agent.extensions.directory" to
locate the extensions directory.
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] The agent extensions directory /usr/sap/SMD/J98/SMDAgent/applications.config/
com.sap.smd.agent.application.wilyhost/ext was successfully located
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Introscope Agent startup complete.
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] The Agent will attempt to determine its name.
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Using the Agent name "SAP HostAgent J98" based on the value of the System Pro
perty "com.wily.introscope.agent.agentName".
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Initial agent name set to SAP HostAgent J98
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent.Isengard] Initiating connection attempts to the Introscope Enterprise Manager.
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent.Isengard] The Agent reconnection delay is set to 15 second(s).
1/06/10 02:55:30 PM IST [INFO] [IntroscopeAgent] Started Error Reporting service
[p4://inbbssun02:50004] Agent ready.
1/06/10 02:55:34 PM IST [INFO] [IntroscopeAgent.IsengardServerConnectionManager] Connected Agent to the Introscope Enterprise
Manager at TDCTBI.india.tcs.com:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory. Host = "inbbssun02", Proce
ss = "SAP HostAgent Process", Agent Name = "SAP HostAgent J98".
Is there any seperate setting for wilyhost agent connection to EM ?
Regards,
Shyam

I have restarted the agent at OS level and it appears in the Agent Admin page.
I then re-ran the Managed System Config for this system and receive the same error.
I have looked at the jvm_smdagent.out file on the wilyhost and found the following errors
1/11/10 05:37:02 AM CET [INFO] [IntroscopeAgent] Looking for agent profile property "introscope.agent.extensions.directory" to locate the extensions directory.
1/11/10 05:37:02 AM CET [INFO] [IntroscopeAgent] The agent extension property "introscope.agent.extensions.directory" is not set. No extensions will be loaded.
1/11/10 05:37:02 AM CET [INFO] [IntroscopeAgent] Introscope Agent startup complete.
1/19/10 12:34:08 PM CET [WARN] [IntroscopeAgent.IsengardServerConnectionManager] The Introscope Agent is sending data to the Introscope Enterprise Manager too slowly. Keeping the connection alive.
The agent on the solution manager box is version 7.0 and the version od the agent on the PI box is 7.11
Regards
Stephen

Registering with the WebEx Data Center and the Cisco WebEx Node Management System

Dear guys, ...
Please help,
i want to implement to webex node ASR1000, i have read in "Configuring the Cisco Webex Node for ASR 100.pdf", there is prerequisites to implement it, that is "Registering with the WebEx Data Center and the Cisco WebEx Node Management System"
Can someone tell how to "Registering with the WebEx Data Center and the Cisco WebEx Node Management System"
Are there any step by step documentation to "Registering with the WebEx Data Center and the Cisco WebEx Node Management System"?
Thank you
BR

You should have received a PAK Key with your order. Go to Cisco licensing and enter the PAK Key as this will start the process. Once the PAK Key is validated a screen will be displayed to enter your request for ASR 100 integration. It normally takes a few days to a couple of weeks to get the information back from WebEx needed to configure your ASR.
If you did not get a PAK Key contact your WebEx rep to get the process started to integrate your ASR to your WebEx site.
Hope this helps
John

Error in RFC & to Solution Manager System

Hi,
Error in RFC & to Solution Manager System
can anyone tells me why this error occurs???
With regards
kulwinder

FYI
We have just had same issue thaat in certain scenarios with RFC communication BACK to Solution Manager from Satellite system we got the error. We resolved this by looking at the RFC user used in the BACK connection (i.e. SOLMAN<SID>) on the Solution Manager and changing the user type from communications.
Hope this helps someone else, I spent ages digging around for an answer to such a simple fix
Paul

The definition of the READ RFC to the managed system could not be found. Pl

Hi there,
i try to setup a managed system on our Solution manager for E2E Analysis... but the Setup gave me a sort of errors
The definition of the READ RFC to the managed system could not be found. Please make sure to run the RFC creation assistant in SMSY, as described in setup documentation
and
No RFC Read User (SOLMANSOX001 or SM_SID) was found at ABAP Host=HOST sys=00 client=001 for roles assignment. Please make sure you have run the RFC creation assistant for this system, in SMSY. If a user name different from the default 'SM_<SID>' or 'SOLMAN<SID><CLIENT>' was specified in the SMSY RFC creation assistant, you need to assign by hand the following roles & profiles to the Read RFC User : SAP_SATELLITE_E2E (role), S_AI_SMD_E2E (profile)
So which documentation means the setup where is described how to create the RFC Destinations with SMSY.. Thanks
Regards
Edited by: Bjoern Bayerschmidt on May 17, 2010 5:45 PM

Hello,
The documentation is located at [Help|http://help.sap.com/saphelp_smehp1/helpdata/en/b3/64c33af662c514e10000000a114084/frameset.htm]
Then navigate Basic Settings > Solution Manager System Landscape > Create Systems > Generate RFC Connections
You can:
Assign an existing RFC destination to a client with Assign and Check RFC Destinations.
Generate RFC destinations for your managed systems
Change existing RFC connections.
Delete RFC destinations.
Resolve RFC Generation Errors
I hope you find this information helpful.
Regards,
Paul

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.

Error in RFC SM_DM1CLNT800_BACK to Solution Manager System Message no. STMWFLOW025

Hi,
I am facing an issue in our Test landscape. One of our team member uninstalled solman system which was connected to all other system. CHarms was partly configured in it, so other technical team used to reach to solman for creating TR# and also release the TR from Solman. Now that the system was removed abruptly we are facing this issue and I have checked few things as below:
1) Checked for domain link entries in STMS and TP profile file, could not find anything. Nor there is any option to delete domain link as there is for create
2) Checked the RFC its was working as new Solman with the same host name and other details has been brought back with out any settings yet in it.
3) I deleted the RFC SM_DM1CLNT800_BACK in the managed system and had a backup copy created before deleting it. But still get the error "Error in RFC SM_DM1CLNT800_BACK to Solution Manager System" in more help I see this Message no. STMWFLOW025
4) Message no. STMWFLOW025 - It gives me an indication that this is something to do with the domain link and the Workflow of the TMS.
5) Checked BCOS_CUST table and it has an entry for this RFC. - Should I be removing this entry and will this resolve the issue?
I need help in resolving this issue and also if one of you could share a blog for the proper configuration removal process of a managed system from Charms and ITSM I think it would be very helpful. I could only find process and step towards configuration and not how to unconfigure the system.
Thanks in advance
Ashish

Hi
The issue is now resolved, this is how I did it.
1) Removed entries from BCOS_CUST from client 000 for OSS_MSG which was pointing to the RFC name
Then got another error:
No RFC connection to the central lock information management system.
The project lock functionality is active in the local system, but there is no RFC connection to the Solution Manager system.
2a) Ran the report in SA38 TMW_CONTROL_PROJECT_LOCK with selection for Deactivate the "project lock functionality".
2) Filled the "Deactivate Project Lock" field with "X" then clicked EXECUTE.
Problem got Solved.
Thanks
Ashish

Quick help - Is SAPHOSTAGENT Mandatory for managing system (solman) ?

Hi All,
Quick question, Is SAPHOSTAGENT Mandatory for managing system (solman) ?
No data in infocube OSMD_PE2D (JAVA MEMORY USAGE) and i'm trying to narrow down the problem. Therefore, i want to know is SAPHOSTAGENT Mandatory for managing system (solman) ?
Thanks,
Nicholas Chang

Hi All,
I've figured out that DAA and SAPHOSTAGNET is needed for SOLMAN EHP1 SPS > 20 as the diagram depicted in AgentInstallation.pdf, from Note 1365123 - Installation of Diagnostics Agents.
and i've resolved the problem where data is populated in OSMD_PE2D and JAVA MEMORY USAGE data and etc is appearing in WA and EWA.
Step performed:
1) before rerun diagnostic system setup, ensure RFC for SELF_DEST for BW source system is working fine and importantly, all field should be empty in technical settings, logon & security and etc. Perform RFC and authorization check.
2) rerun diagnostic system setup and ensure all result returned green, and check CCMSBI_SETUP_E2E log. Ensure it completed successfully. ( you need to adjust WEBADMIN & SOLMANDIAG RFC by putting in the gateway host and port to avoid intermittent RFC error, also enlarge RFC resource in table E2E resources)
3) go to TX rstco_admin and ensure status is activation successful.
4) follow sapnote 1259109 and upload the latest xml according to your solman version.
5) Install object accordingly by following note 1342231 & 1110013 (the note specify the bugs happen in SPs18, whilst my solman version is EHP1 SPs27 and i was reluctant to apply at the first place. But upon checking, most of the objects mentioning in the note that required installed are not installed!)
6) Rerun managed system setup
7) Check infocube OSMD_PE2D after 1 hour or 1 day?? unsure as i checked after one day.
Cheers,
Thanks,
Nicholas Chang.

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 in Solman 7.1 sp11??

Hi All,
I have done new installation of solman 7.1 and upgraded to sp11.
I did system preparation and basis configuration in solman_setup.
I have one query how to add ERP production system to SLD and how to do managed system configuration for that.
I want to add ERP Production system and Managed configuration for that and MOPZ,EWA configuration ERP Production system.
Please help me in this...
Here i attached screen shot for your reference.
Presently in managed system Only Solman system is visible.
Thank in Advance
Chandra

Hi,
Please chekc th ebelow guide
Step By Step Process to configure SLD, MOPZ & EWA in Solution Manager 7.1 SP 8
https://websmp104.sap-ag.de/~iron/fm/011000358700000209862011E/012002523100005267752014WRK2?TMP=1407918324257#bkm_show1_…
go to Configuration of SAP Solution Manager
Normally y this demo and guide will be available http://service.sap.com/rkt-solman
#sapadmin:: How to assign Product System in SOLMAN 7.1 & How LMDB, SLD, SMSY and Landscape Verification work in SOLMAN7.1
Normally after addition in SLD ,system will adding the system in LMDB ,then added in smsy automatically. check the Job LMDB*
Update the CR content in SLD , check th below note fpor the smae.
Note 669669 - Updating the SAP Component Repository in the SLD
LMDB FQA:
Landscape Management Database (LMDB) – FAQ
Product system Editor in LMDB:
New in SP05: Product System Editor in the Landscape Management Database of SAP Solution Manager 7.1
Maintenance of Product in the System Landscape - SAP Solution Manager Setup - SCN Wiki
Rg,
Karthik

Managed System Configuraiton Issue in SolMan 7.1

Hi Experts,
In solution manager 7.1, during Managed system configuration in phase "Configure Automatically" am getting an error while executing the step 'Activate Services' .
Error log says-->Function module W3_PUBLISH_SERVICE does not exist.
I checked function module W3_PUBLISH_SERVICE which exists in SolMan 7.1 but its not available in managed system.
Please help to overcome on this issue.
Thanks,
Rakesh

Hi,
To use the functionality of report W3_PUBLISH_SERVICE on managed system
you need to import SAP BASIS 701 SP02.
Actually, function module W3_PUBLISH_SERVICE is delivered since
support packages below:
SAP_BASIS 701 SAPKB70102
SAP_BASIS 710 SAPKB71007
SAP_BASIS 711 SAPKB71101
So, to import this object is necessary upgrade the system at least to
SAP_BASIS 701 SP 02.
Unfortunately it is not possible to import only this specific object
regarding all dependecies that it necessary to import to the system
to make it consistent.
Also check notes:
1233316 and 1309047
So you have following options as per note: 1309047:
1. Import SAP_BASIS >= 701 Support Package 1 into the managed systems.
2. If SAP_BASIS is not of a higher release than 700, the service must
    be manually activated and this results in a warning in the log.
    Manually activate the service /default_host/sap/bc/bsp/sap/system in
    transaction SICF in the managed system. The error message mentioned
    above is still displayed, since, due to the missing function module,
    the service activity cannot be checked on the managed system.
So if you manually activate this service, the error will also exists
because the automatical mode cannot get a sucessful result and you
manually perform this step instead, and you can ignore this and go on
the configuration.
Thanks
Vikram

SOLMAN 7.1 Managed system(Maintain RFC's Step)

Similar Messages

Maybe you are looking for