Unable to setup DBAcockpit connection in managed System Conf.

Hi Guys,
I am trying to set up DbaConnection in managed System Conf for local solman system.
Its Showing red status and also the fields are not changeable now.
I am on kernal 720 level 300.
error shows the No DBSL lib found and gives the note number 1458291.
I have already downloaded the latest verion of dbsl (324) and extracted in C:\usr\sap\PDI\SYS\exe\uc\NTAMD64.
I have already applied the note 1604209 but still the same error.
i am solman 7.1 sp06 with MSSQL 2008 R2.
Please advice how to proceed.
Thanks

Hi,
Please kindly check in 'Agent Administration' if SMD Agent is running and
conected to SolMan if you can't see the Agent please check if it is
visible in SLD, if it is please connect it to SolMan and then run
setup again. Otherwise please uninstall SMD Agent and install it again
conecting it directly to your SolMan using HTTP Connection via Message
Server.
You may want to refer to the 'Diagnostics Agent Setup Guide' available at
https://service.sap.com/diagnostics should be very helpful.
As per the mentioned note: Please refer to SAP note 1232928
You switch to the DBA Cockpit that has the authorizations to
configure the back end, and you uninstall the back end there. You can
then reinstall the back end in the new instance.
You can see on "Screen Performance -> Performance Warehouse ->
Configuration" which DBA Cockpit currently has the authorizations to
change the back end. The SAP system ID of the relevant DBA Cockpit is
specified there in the line for the "Monitoring DBA Cockpit".
You need to switch to the dba cockpit that has authorizations to
change the backend system then uninstall the backend, and then you can
do this configuration step without the above error.
Hope this helps.
Cheers
SH

Similar Messages

Unable to open RFC connection to SAP System NSP

Hi all,
During installation i am getting an error which is as follows,
"Unable to open RFC connection to SAP System NSP.
Solution: Start the system."
And the second problem is that there are no connections shown in SAPGUI.
Please help me out.
Thanking you,
Kranthi

HI Kranthi,
Have you checked this thread NW Preview Installation error?
Regards

Can SMD be setup to monitor the Managing System?

Hello, We have been working off and on for the last few months
installing Wily Introscope, which in turn required E2E RCA, which in
turn required SMD to be installed. Since virtually all of our systems
are on a relatively low pl of the kernel, 114, we also installed the
latest SP and kernel to our Solution Manager system. So, the SM system
is at 7.00 pl 146, and SPS 16 (it's a dual-stack UNICODE system).
However, every other of our almost 27 ABAP stacks are at pl 114,
unfortunately.
We had read, via SAPNet note 1126859, that the MANAGED system must be
at least at kernel 7.00 pl 121. As I saidl, only our MANAGING SM
system is at that level. So we thought that we'd try to have SM
monitor itself, in the context of SMD and Wily Introscope.
Unfortunately, we got stuck at setting up the trusted RFCs for the SM
system to monitor itself. SAP AG's instructions for setting up the
trusted RFCs is in the following guide: Root Cause Analysis
Installation and Upgrade Guide (v3.30 - July 2008), section
6.3.2 "Setup RFC Destinations to Managed Systems". Transaction SMT1
doesn't permit 2 RFCs with the same target <sid>.
So, our questions:
1. Can a MANAGING system also be a MANAGED system?
2. If so, would you kindly clarify how to configure the RFCs for that
scenario? Or perhaps we don't use RFCs in this scenario?
For now, we will move on and try to setup Wily/SMD for a Java-stack
system we have available (Portal).

Hi Felipe Pitta,
The Managing system can be managed, for that include your Solman in a solution and proceed all the needed activities like Agent installation, Wily agent setup etc as you do for the managed systems.
You need to create RFCs to the BI client of the solman if you are the same BI component which is available in Solman (001 is your BI client) or RFCs should be created for the BI system which you are using.
WEBADMIN RFC will be created automatically during SMD Agent installation.
By this your solman's data will be collected.
For furthur clarifications pls revert back
regards
Naveen kumar

DBACOCKPIT Connection for SAP systems with SAP Router

Hello!
We are trying to integrate all the remote SAP systems and their databases (primarily Oracle) into DBACOCKPIT of SAP Solution Manager 7.1.
Our SAP Solution Manager is running on Windows with Oracle 11.2.0.2
The most SAP systems (Unix and Windows) can only be reached from SAP Solution Manger over the SAP Router connection.
It means no direct ping from Solution Manager server to the Server of managed system will work.
Question
Is it possible to integrate such SAP systems (with SAP Router) into DBACOCKPIT of Solution Manager?
According to sap note 1265134 only the DBCON-connection will be required.
By doing so (tcode SOLMAN_SETUP), we get TNS errors.
Do we miss some additional steps (adapting tnsnames.ora of SOLMAN with the entry of managed system), etc.?
Thank you!
regards

SAP-SDN wrote:
> We of course can reach these systems via SM59.
>
> The question still is whether or not the several SAP systems with Oracle that can be reached from Solution Manager over SAP Router can be integrated into DBACOCKPIT of SAP Solution Manager in order to gather/ analyze performance data?
Systems can be reached via SM59, then what's the problem ?
In fact, this 'is' the standard procedure. This is as normal as you could have Solution manager in same 'network' with rest of the remote systems.
Answer should be yes, you can manage several remote sap systems from sap solution manager dbacockpit.
Thanks

Do we need to setup traditional ABAP Transport Management System on XI?

I was confused that do we need to setup ABAP transport Management System on XI, since the IR and ID object will use CMS or File to transport between DEV->QAS->PRD. If we still need, could you pls let me know why we need it?
one more question is: if we maintained some parameter in XI dev, say, we maintained Integration Server patameter to let system can moniter Syn message, if we want this paramter used in XI QAS, is that the only way to maintain it mannully in QAS, or we have other way to make it? thank you for your help

Zhang,
You are absolutely correct. You transport all your ID and IR objects using CMS or File transports.
But lets suppose you have developed some zprograms or abap mapping in XI. This basically reside on the ABAP stack. So for this objects to transport we will follow the procedure what we do normally to transporting the R3 objects. So what ever you develop on the ABAP stack we need to transport to QA and to Prod using ABAP transport system.
---Satish

Error While running Setup Wizard in SolMan Managed Systems

Hello,
I am getting the error listed below while I am trying to setup an Agent in SolMan Diag.
While I am running Setup Wizard, I am giving the message server port (50100) the same as I am getting from the systeminfo page: http://<My Server Name>:50100/sap/monitoring/SystemInfo.
When I change this port with 50104 which is my P4 port, It takes it and then gives me a message that "P4 port is unknown".
Any input?
Regards,
Ray
Failure with Message Server
An error occured while communicating with Message Server <My Server Name>:50100 through the host <My Server Name>: Error to retrieve the process from Message Server (detail: com.sap.bc.proj.jst
artup.impl.JStartupClusterControlExceptionImpl: The message server did not respond within 60 sec. Please check if the message server is running and if the socket connection has been established.); nes
ted exception is:
com.sap.bc.proj.jstartup.impl.JStartupClusterControlExceptionImpl: The message server did not respond within 60 sec. Please check if the message server is running and if the socket connection has bee
n established.(cause=com.sap.bc.proj.jstartup.impl.JStartupClusterControlExceptionImpl The message server did not respond within 60 sec. Please check if the message server is running and if the socket
connection has been established.)
Please check Message Server host/port, or enter the P4 ports in cluster table.

Hi furious
I have the same error , and finally I am find the solution, this error due to the enterprise admin permission, so go to main configuration tree (as shown on screenshot) click properties, click enterprise admin, click advance, again click enterprise
admin, click edit and select "this object and all descendant object" on Applies to option (as per screenshot) and select full control
after that you prepare your organization and It will works
cheers....................

Solman_admin password changes results in errors during managed system setup

Hello all,
I am trying to get Solman 4.0 EHP 1 to work, but get numberous problems.
Currently I have 6 messages at SAP, but no solution yet.
Situation:
Solman 4.0
SAP_BASIS     701     0003
SAP_ABA     701     0003
ST-PI     2008_1_700     0000
PI_BASIS     701     0003
SAP_BW     701     0003
CRMUIF     500     0001
SAP_AP     700     0014
BBPCRM     500     0013
CPRXRPM     400     0014
BI_CONT     704     0002
ST     400     0019
ST-A/PI     01L_CRM570     0000
ST-ICO     150_700     0016
ST-SER     701_2008_2     0002
So, it is uptodate.
The problem:
Changing the solman_admin password results in errors during connecting a managed system.
In the inital setup the solman_admin is created with a pasword.
After the basic setup I setup some managed systems.
In the meantime I had to change the password of solman_admin
I am logged in with solman_admin and do solman_setup to setup the managed system.
During the setup a process tries to logon back to the solman using solman_admin and the incorrect password.
This is the logging:
Step SSO Details
Found SID for SSO ACL entry : MSD
Found login.ticket_client for SSO ACL entry : 000
The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (823 bytes)
A failure occured while connecting to ABAP stack on localhost sys=70 client=300 user=SOLMAN_ADMIN
!! Exception : Password logon no longer possible - too many failed attempts
A failure occured while importing ABAP SSO ticket certificate in ABAP stack
!! Exception : java.lang.NullPointerException
Java SSO ticket certificate of MSD was imported in ABAP PSE of kswv024.mob.local (client 300)
The Java SSO ticket certificate was successfully imported in ABAP System PSE, and the ACL updated accordingly (SID=MSD LoginTicketClient=000)
Anyone else has this problem?
gr
Sander

Just for clarification it's Solman 7.0 EHP1 correct?
Also you may want to unlock the following user:
localhost sys=70 client=300 user=SOLMAN_ADMIN
Then if you navigate (in solution manager) to TCode solman_workcenter -> "Root Cause Analysis" tab ->"Agent Administration" menu item on the left -> "Applications Configuration" tab -> under the Agent Applications - Configuration menu on the left select "com.sap.smd.agent.application.global.configuration" -> Change the "Scope" drop down in the frame to the right to the SMD agent that you are using for "localhost sys=70 client=300" -> Click the "edit" button to the right of the Scope drop down box -> now find the entry below that lists "SOLMAN_ADMIN" as the user and find the corresponding password entry and update it with the new password that you changed it to -> click save and try the managed setup again.
Hope this helps, please let me know and we can go from there.

Is it possible to connect a DEV System to more than one SAP Solution Manage

Hello,
My system DEV is already connected to a first SAP Solution Manager, I would also like to reconnect the same system so that it communicates and will be monitored by a second SolMan.
Is it possible to do so and the do the operation involve any risks ?
Thanks for your help
Regards
Ben

Hello,
This is possible in many scenarios. Often this is done to distribute load, for example on Solution Manager will do the Service Desk Function, one may do ChaRM, one may be doing Monitoring & Reporting, one may be doing Diagnostics.
In these cases a managed ssytem can be connected to many Solution Manager systems.
However as Mateus has pointed out, you cannot connect one managed to two Solution Managers and do SMD on both Solution
Manager systems, but you can have more than one Solution Manager doing Diagnostics.
Even in the case of EWA, while you can connect a Managed system to multiple Solution Manager systems and have then generate a report, one of the Solution Manager systems must be defined as the Master.
So the specific scenario may place some restrictions on connecting a managed system to more than one Solution Manager,
but for most instances it can be done.
Regards,
Paul

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

SMSY Data Source changes after performing Managed System Config

Hello everyone,
I am working with Solman EHP1 SPS26. I have setup up my central SLD to push system data to my Solman local SLD which is then retrieved from Landscape Fetch to SMSY. Initially, everything seemed to be working and all data sources reported SLD.
However, once I performed the Managed System Confirguration wizard for a particular technical system, that systems data source would change to TMS/RFC under SMSY. It's actually not even that consistent. For example, the server says source is RFC, the product system says TMS/RFC and some of the product instances still say SLD.
Is this normal for this to happen after connecting a managed system? Will these systems still be updated via the SLD considering SMSY_SETUP is configured to use the SLD?
Anyone's help would be greatly appreciated.
Alex

Hello,
If you notice in SMSY this is not an editable field.
It is reporting the last datasource used.
Thefore when you made a change via managed system setup that became the last data source used.
So yes it is normal to see this change.
If you have configured the datasource to be the SLD, it should continue to update these systems.
Where you need to watch out is making manual changes in SMSY, as the SLD can view this as a different system to the SID it knows and will generate systems with known SIDs appended with a suffix variable to distinguish it, as the SLD will not overwrite manual changes, and will create new systems instead.
But the field in SMSY reflects the last data source used.
Hope this helps some.
Regards,
Paul

How to add managed system in Wily introscope system

Hi All,
Can anyone provide the document on how to add managed system in Wily Introscope?
With Regards
Ashutosh

Hello,
The documentation for WilyIntroscope is located at
http://service.sap.com/diagnostics
> Media Library
Here you can find user guides and installation guides for WilyIntroscope.
But the overview is you install Enterprise Manager on a server that becomes the EM Server and then IS Agents on the managed system. There is an installation guide for EM and this ISAGENT setup is part of managed system setup in Solman_setup.
Your tools to manage are Webview and Workstation, and there is documentation for these at the above mentioned link as well.
Regards,
Paul

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.

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

No P4 connection could be established to SID during managed systems setup

Hi,
I get the following error when executing managed systems setup Create Users request.
No P4 connection could be established to BJR
No configuration found for key (BJR/sapj2ee/msgserver/host). DETECTED Self-managing scenario. You need to first adapt the connectivity of Diagnostics Agent used for the Managed system BJR, before you could proceed with this setup. Therefore change the Agent connection type for the BJR relevant Diagnostics Agent to P4 Dispatcher, before you run again this setup. This connection update has to be performed in the Agent Administration under Agent Connectivity. You could access the Agent Administration from the Root Cause Analysis Work Center when logged as Solution Manager Administrator.
I have deleted and manually recreated SM_ADMIN_SOL, SAPSUPPORT and SM_COLL_SOL users, but still get the same issue.
Message server ports etc are correct. Screenshot below.
I have reviewed OSS note 1678469 but not resolved the issue.
Any ideas will be appreciated.
Regards
Tariq

Hi,
As stated please review how do you register dia agent in solution manager, you can check in step 4 assign diagnostic agent in solman_setup.
further review the below doc for dia agent registration via P4 port Diagnostics Agents - SAP Solution Manager Setup - SCN Wiki
Thanks
Jansi

How to install EASY DMS (Document Management System) setup in windows 7

Dear Experts,
Recently we have started a project to establish document management system in SAP. So, i have downloaded easydms7.1sp04 from the servicemarketplace service.sap.com/swdc and setup is successfully installed in windows Xp and unable to install successfully in windows 7.
The SAP is upgraded in our company to release ERP6 EHP6.
In windows Xp the DMS is accessing to all the systems in the landscape( DEV, QAS, PRD).
But, In windows 7 it is only accessing the production system and if creating manually the systems prompting the error about RFC and hosts in windows 7.

Hi Sir,
As mentioned earlier it is prompting me the error
Logon Failed (RFC_ERROR_LOGON_FAILURE)
Name or Password is incorrect (repeat logon)
But it is accessing only the production system in windows 7 but not all the 3 systems which are in landscape. I dont know how can it proceed to logon to the production system only with out other systems .
Thanks in advance
Regards,
Easwar

Unable to setup DBAcockpit connection in managed System Conf.

Similar Messages

Maybe you are looking for