Database configuring problem in setup of managed systems in SMD

Hello,
i'm doing the setup of a CRM 5.0 in SMD Abap+Java and the setup results returns following:
"Database configuration problem" with the exception:
java.lang.NullPointerException
     at com.sap.smd.server.manager.SMDPluginProperties.setProperty(SMDPluginProperties.java:114)
     at com.sap.smd.agent.plugins.database.ConfigurationTask.configureCustomProperties(ConfigurationTask.java:242)
     at com.sap.smd.agent.plugins.database.ConfigurationTask.configureProperties(ConfigurationTask.java:370)
     at com.sap.smd.agent.plugins.database.ConfigurationTask.execute(ConfigurationTask.java:124)
     at com.sap.sup.admin.setup.AppCfgTasks.configureDbApp(AppCfgTasks.java:115)
     at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:202)
     at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:217)
     at com.sap.sup.admin.setup.SapCluster.setup(SapCluster.java:461)
     at com.sap.sup.admin.setup.SapCluster.access$000(SapCluster.java:26)
     at com.sap.sup.admin.setup.SapCluster$SetupRunner.run(SapCluster.java:669)
     at java.lang.Thread.run(Thread.java:534)
Anybody knows which can be the problem?
Thanks a lot
Carlos

Hi Shriraj,
ensure that the installation path is correct. I only put /urs/sap/<SID> and you must put /usr/sap/<SID>/DV***/.
In my case with that the setup returns all in green.
I hope it helps you
Regards
Carlos

Similar Messages

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

Database Configuration problem

I am brand new to Crystal (1 week) so bear with me please.
I have created a crystal report from an access database. Although this access database doesn't have any security itself one of its tables is linked to a SQL server through ODBC. When i create a report in Crystal using the Access database it works great. When i publish this report to the server it wants some type of login information.
Under Database configuration (CMC) for the report i seem to have two options.
1)Use original database logon information from the report.
    Server = Location of my access database
    Database = ""
    User: ?
    PW:?
or
2) Use custom database logon information specified here.
     Select a database driver
    Server: ? Is this the SQL server or the server where my access database is contained?
     Database: ? same question
     User: ? Is this the sql user?
I have tried both can't get it to work. What login information does it want? Does it want the sql login information? What am i missing? Any help would be great. I know this is a lot of questinons but i am stumped.
thanks

Hi Jesse,
Because your .mdb file doesn't require a password, I would check if Page server can access to .mdb file first. When viewed from Enterprise, Page Server needs to be able to access to .mdb file. Where is .mdb file located? If it is on the network share, Page Server service needs to run under the user account which has access to the share. By default it is running under System Account.
Test the report in Crystal Reports on the server(not from a client machine). If you can refresh it successfully, check what user account is logged on the server, then use the user account for Page serer service. Restart Page Server and test the report from Enterprise.
Hitomi

Problem of setuping a source system in bi 7.0

Dear All,
I'm now using BI 7.0, and when I wants to setup a souce system in the folder SAP, I found a problem. The system appears in BI folder with a strange icon. I don't know why, can anybody explain it and give a solution?
Thanks a lot.

I've searched sap notes and found , I should import support package 01 into BI, however, I've imported support package 09....Why

Error setting up new Managed System in SMD

Hi,
we get the following error after trying to setup a new (Java)-System:
DataCollect Initial Data Collect ERROR for host xyz
Step DataCollect Details
Initial Data Collect ERROR for host xyz
!! Exception : An error occurred while uploading the Configuration Data from host [xyz] !(cause=java.lang.Exception [DataCollectorClientUtil_xyz] Error collecting initial configuration files on host [xyz])
Exceptions
com.sap.sup.admin.scheduler.exception.FatalTaskExecutionException: An error occurred while uploading the Configuration Data from host [xyz] !
at com.sap.sup.admin.scheduler.task.remote.config.InitialConfigGatherTask.process(InitialConfigGatherTask.java:72)
at com.sap.sup.admin.scheduler.config.DataCollect.execute(DataCollect.java:138)
at com.sap.sup.admin.setup.AppCfgTasks.runInitialDataCollect(AppCfgTasks.java:57)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:348)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:304)
at com.sap.sup.admin.setup.SapCluster.setup(SapCluster.java:736)
at com.sap.sup.admin.setup.SapCluster.access$000(SapCluster.java:28)
at com.sap.sup.admin.setup.SapCluster$SetupRunner.run(SapCluster.java:1000)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.Exception: [DataCollectorClientUtil_xyz] Error collecting initial configuration files on host [xyz]
at com.sap.smd.agent.plugins.datacollector.util.DataCollectorClientUtil.collectInitialConfigurationData(DataCollectorClientUtil.java:315)
at com.sap.sup.admin.scheduler.task.remote.config.InitialConfigGatherTask.process(InitialConfigGatherTask.java:67)
... 8 more
Caused by: com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: [DataCollector] Error during collectInitialConfigurationData() on host [xyz]; nested exception is:
com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: Error installing template files in the working directory; nested exception is:
com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: No cca_systemlandscape.xml file found
at com.sap.smd.agent.plugins.datacollector.DataCollectorService.collectInitialConfigurationData(DataCollectorService.java:684)
at com.sap.smd.agent.plugins.datacollector.DataCollectorServicep4_Skel.dispatch(DataCollectorServicep4_Skel.java:290)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:716)
... 1 more
Caused by: com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: Error installing template files in the working directory; nested exception is:
com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: No cca_systemlandscape.xml file found
at com.sap.smd.agent.plugins.datacollector.DataCollectorService.installTemplateFiles(DataCollectorService.java:792)
at com.sap.smd.agent.plugins.datacollector.DataCollectorService.collectInitialConfigurationData(DataCollectorService.java:710)
at com.sap.smd.agent.plugins.datacollector.DataCollectorService.collectInitialConfigurationData(DataCollectorService.java:654)
... 5 more
Caused by: com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: No cca_systemlandscape.xml file found
at com.sap.smd.agent.plugins.datacollector.DataCollectorService.installTemplateFiles(DataCollectorService.java:766)
... 7 more
in file SMDAgentApplication.0.log of the server, that hosts the system and the SMD agent, I get:
Nov 27, 2008 2:22:57 PM [Thread[Thread-25,5,main]] Error      DataCollectorService@40c5f303: collectInitialConfigurationData()
[EXCEPTION]
com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: Error installing template files in the working directory; nested exception is:
     com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: No cca_systemlandscape.xml file found
     at com.sap.smd.agent.plugins.datacollector.DataCollectorService.installTemplateFiles(DataCollectorService.java:792)
     at com.sap.smd.agent.plugins.datacollector.DataCollectorService.collectInitialConfigurationData(DataCollectorService.java:710)
     at com.sap.smd.agent.plugins.datacollector.DataCollectorService.collectInitialConfigurationData(DataCollectorService.java:654)
     at com.sap.smd.agent.plugins.datacollector.DataCollectorServicep4_Skel.dispatch(DataCollectorServicep4_Skel.java:290)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
     at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:716)
     at java.lang.Thread.run(Thread.java:534)
Caused by: com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: No cca_systemlandscape.xml file found
     at com.sap.smd.agent.plugins.datacollector.DataCollectorService.installTemplateFiles(DataCollectorService.java:766)
     ... 7 more
Nov 27, 2008 2:23:03 PM [Thread[Thread-35,5,main]] Warning    com.sap.smd.wily.hostagent.action.SapOsColAction - launchDaemon(): launchDaemon: saposcol exited with -1
the mentioned cca_systemlandscape.xml that should be located in usr\sap\SMD\J98\SMDAgent\applications.config\com.sap.smd.agent.application.datacollector is 0 byte.
where should this file be generated/has its source?
kr, achim

Helpfull notes:
987835 - How to define Solutions in SMSY for Diagnostics
986350 - SM Diagnostics: "Monitored setup" fails during data collect

Installing/configuring the InfoSphere Optim Performance Manager system

I am looking at the InfoSphere Optim..... to install. I have not used this tool before and am skeptical. Since the Control Center is deprecated it looks like this is the replacement. Is this tool an additional cost to license or is it available to customers who have advanced enterprise editions?
Can this be run on a standard Windows PC or I should ask will it run well? I would install this onto my work PC and use it for my production (EHP & Netweaver BW) systems. Is there a quick setup guide or does this need to be installed via SAP install?
Lastly, what is the ramp up time that it will take to obtain performance recommendations out of the tool?
Thanks to all.
Len Jesse.
Knowledge is to be shared.

Found this. Can be closed.

Setting up Managed system in SMD

I ran the SAPINST and installed the agent on the other system. WHen I try to connect to it, with the Setup Wizard for SMD I get the message below. I can see the system in the SLD on my solution manager.
The agent is started on the other system, i have checked that.
No Diagnostics Agent available at this time
Please install or start an SMD Agent for avphux51

Hello,
Please make sure you have completed the starting of SMD agent also after the setup, u can find it in the guide.
also check the p4 or Https port number is correctly mentioned.
The user and pass mostly would be that of SMDadmin, created during the setup, or u can use SIDADM which will wrk fine.
sometimes root needs to be used as even sidadm can be restricted in ur envt. ( just in case).
Regards,
Kaustubh.

Failed to push XML template when setup SMD Managed system

Hi,
when I setup a managed system in SMD, I receive the warning:
XML Templates pushed : 0 successful, 1 failed
Failed to push XML template to sv50761/TP4/10 (sv50761.RUV.DE) : com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad Attribute value(:main:, row:10, col:79)(cause=com.sap.engine.lib.xml.pars
er.ParserException XMLParser: Bad Attribute value (:main:, row:10, col:79))
(Data Collect may fail due to missing templates)
Do you still want to proceed ? (Setup operations may fail due to warnings above)
when I check the xml-templates, at the mentioned row, there's the database-information: it shows "9.00.3068#" (a binary value, instead of #)
when I check the database in SMSY there's "9.00.3068#" in version as well, I can't change it there manually, because datasource is TMS/RFC.
In SLD the Version vor the database is displayed correct: 9.00.3068 (without #).
Where does the # occur & how to delete it? How can we setup managed systems without the warning?
kr, achim

Just came across this issue and this snote fixed it.
Note 1156714 - Failure to push XML templates during Diagnostics Setup

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.

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

RCS Managed system setup

Hi,
Do we need to re run managed system setup wizard, each time system stack or EHP is updated ? or even when solman stack is updated ?
Reason: We recently updated solman to SPS27 after which I dont see any data collection happening specially for User Load for ABAP systems
and none for java
BR,
Shyam

Hello,
Run transaction solman_setup and check in the OVERVIEW what are the Open Activities listed in Basic and Initial Configuration.
All activities there must be redone, grey, red or green.
In these tasks there will be the Diagnostics Configuration. This step includes setting the Maintenance Mode ON and OFF, which will stop all agents and deploy the new software to them (the so-called agelets that are delivered centrally from Solman LM-SERVICE to the managed system's SMD Agent).
This is all you must execute after a LM-SERVICE upgrade.
Therefore there's no reason to rerun the whole setup wizard, as it may cause issues with wrong parameters in the setup wizard. If the managed system is working perfectly and this is only an upgrade, it is not recommended to do the setup wizard again.
Best regards,
Guilherme
Edited by: Guilherme Balbinot on Jul 15, 2011 8:37 AM
Edited by: Guilherme Balbinot on Jul 15, 2011 8:41 AM

Configuration of EWA reports for java systems.

Hello,
I am facing a problem with configuration of EWA reports for SAP NW Portal.
I have already configured EWA for abap systems, and those are running good on weekly basis. but i have problem with configuration of reports for java systems.
So far, i have installed an SMD agent and CA on my EP-satellite system. I have also configured and SMD server on my Sollution Manager and registered the SMD agent on SMD server and installed Willy Introscope on SMD server.
I am using a central SLD which is running on different host as Solution Manager. I did all the configuration (smsy_setup, configuration of sld_data_supplier etc... )
I have also created the system in SMSY, matched the smsy with SLD and assigned Logical component to java system.
So far, so good according to manuals but when i want do define data collection in the SMD for Gargage Collection (task in scheduler) i cannot see host of my portal system.
I can see only the hosts (scheduler tasks ) of all abap system for which the EWA reports have already been generated.
Am i missing something?
Some configuration in SMD?
My solution manager is running on Sap NW 7.0, SPS16,
Sattelite system NW 7.0 EP, SPS 6 (planning to SPS 19)
Thank you for your advices!!!

Hi Suveer,
I did the configuration before. I forgot to mention it.
I found this errors in Diagnostic Setup, maybe this could be the cause of the issue.
Step BI Details
Cannot invoke CCMSBISETUP on host localhost
!! Exception : An exception occured during the execution of this function 'CCMSBI_RUN_SIMPLE_SETUP_IN_BTC'.(cause=com.sap.sup.admin.abap.rfc.exception.RfcExecutionException The function named 'CCMSBI_RUN_SIMPLE_SETUP_IN_BTC' doesn't exist!)
Exceptions
com.sap.sup.admin.abap.rfc.exception.RfcExecutionException: An exception occured during the execution of this function 'CCMSBI_RUN_SIMPLE_SETUP_IN_BTC'.
at com.sap.sup.admin.abap.rfc.function.RfcFunction.execute(RfcFunction.java:92)
at com.sap.sup.admin.setup.AbapSysRfcAdapter.setupBIConfiguration_ccmsBiSetup(AbapSysRfcAdapter.java:743)
at com.sap.sup.admin.setup.AbapSysRfcAdapter.setupBIConfiguration_ccmsBiSetup(AbapSysRfcAdapter.java:727)
at com.sap.sup.admin.setup.ManagingServices.startCcmsBiSetup(ManagingServices.java:2686)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:334)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:304)
at com.sap.sup.admin.setup.wizard.monitoring.ConfirmationView.setupSMDServer(ConfirmationView.java:378)
at com.sap.sup.admin.setup.wizard.monitoring.ConfirmationView.onActionSetupServer(ConfirmationView.java:211)
at com.sap.sup.admin.setup.wizard.monitoring.wdp.InternalConfirmationView.wdInvokeEventHandler(InternalConfirmationView.java:278)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.sup.admin.abap.rfc.exception.RfcExecutionException: The function named 'CCMSBI_RUN_SIMPLE_SETUP_IN_BTC' doesn't exist!
at com.sap.sup.admin.abap.rfc.function.RfcFunction.execute(RfcFunction.java:62)
... 37 more
And also this one>>
Step RFC Details
Failed to create TCP/IP RFC on ABAP side (SM59)
!! Exception : Source system cannot be set to Unicode , error key: RFC_ERROR_SYSTEM_FAILURE
Exceptions
com.sap.aii.proxy.framework.core.BaseProxyException: Source system cannot be set to Unicode , error key: RFC_ERROR_SYSTEM_FAILURE
at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
at com.sap.sup.admin.setup.abapproxy.tcpiprfc.TcpIpRfcProxy_PortType.inst_Create_Tcpip_Rfcdest(TcpIpRfcProxy_PortType.java:16)
at com.sap.sup.admin.setup.ManagingServices.createTcpIpRFC(ManagingServices.java:663)
at com.sap.sup.admin.setup.ManagingServices.createTcpIpRFC(ManagingServices.java:637)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:300)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:304)
at com.sap.sup.admin.setup.wizard.monitoring.ConfirmationView.setupSMDServer(ConfirmationView.java:378)
at com.sap.sup.admin.setup.wizard.monitoring.ConfirmationView.onActionSetupServer(ConfirmationView.java:211)
at com.sap.sup.admin.setup.wizard.monitoring.wdp.InternalConfirmationView.wdInvokeEventHandler(InternalConfirmationView.java:278)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
And in the troubleshooting setup for managed systems, i can see that no initial upload was found form the SMD agent which is running on Java System.
Thanks a lot for your remarks

SMD Error in managed system type PI 7.1 EHP1 Step Logical Ports error

Hi people,
Solution Manager Ehp1 7.0 SPS24
I am currently runnig the wizard setup for managed System, everything is fine but when I run for PI 7.1 I get the following error:
Fri Sep 10 20:29:48 2010 Logical Ports A failure occured while creating the logical port for JAVA XI : PORT_NOT_CREATED
Step Logical Ports Details
A failure occured while creating the logical port for JAVA XI : PORT_NOT_CREATED
!! Exception : PORT_NOT_CREATED
Exceptions
com.sap.mw.jco.JCO$AbapException: (126) PORT_NOT_CREATED: PORT_NOT_CREATED
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1511)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3980)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3514)
at com.sap.sup.admin.setup.SolManRfcAdapter.createXIlogicalPort(SolManRfcAdapter.java:185)
at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:427)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:335)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:549)
at com.sap.sup.admin.setup.SapCluster.setup(SapCluster.java:1695)
at com.sap.sup.admin.setup.SapCluster.access$000(SapCluster.java:35)
at com.sap.sup.admin.setup.SapCluster$SetupRunner.run(SapCluster.java:1965)
at java.lang.Thread.run(Thread.java:534)
Any ideas?
Thanks in advance

Hi everyone,
Thanks everyone.
Guilherme, finally I understand what really happens. "Refresh" is not working properly in the Setup Wizard.
First I have done what I can:
System    Type      Managed Products                    Product Instances
DPI           ABAP     SAP Netweaver PI 7.1               Application Server ABAP (I could not select PI at the same time)
DPI           JAVA     SAP Netweaver PI 7.1               Application Server Java + Process Integration
But, when I refresh the browser Internet Explorer appears the following:
System    Type      Managed Products                    Product Instances
DPI           ABAP     SAP Netweaver PI 7.1               Application Server ABAP + Process Integration
DPI           JAVA     SAP Netweaver PI 7.1               Application Server Java + Process Integration
And then I do not get the error anymore. (I have to repeat step 2 in the wizard "Check Prerequisites for Diagnostics)
And If I run transaction SMSY, I can see how PI is mantained since the wizard refresh SMSY.
Product Instance Selection tab:
Application Server ABAP (Flag selected: relevant)
Process Integration (Flag selected: Also Installed, Technical System[ DPI, Java])
Application Server Java (Flag selected: relevant, Technical System[ DPI, Java])
So, if I use this configuration in the SMSY, when I run "solman_setup", configuring DPI (My PI7.1), when I run "Configure Diagnostics", the wizard shows ABAP + PI as expected.
Thanks a lot Guilherme!!

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

Missing Greeting Management System

Hi all,
I am trying to configure custom AutoAttendant using Greeting Management System.
When I go to CiscoUnityExpress VoiceMail > CallHandling, I am not seeing "Greeting Management Call-in number" feature or setting.
Can anyone tell me to solve this problem?

Unity Express Greeting Management System and Emergency Alternate Greeting Configuration Example:
http://www.cisco.com/en/US/products/sw/voicesw/ps5520/products_tech_note09186a008025c5e0.shtml

Database configuring problem in setup of managed systems in SMD

Similar Messages

Maybe you are looking for