** End-to-End Monitoring - RFC destination error while save config in RWB

Hi Friends,
We have 2 RFC destinations in our XI server. 1) PMI<client>001 2) PMI<client><client>800. First one is for XI server. Next one is for Sender/Receiver System.
We want to activate End-to-End Monitoring in RWB. For this, when I save configuration, it throws the following error.
Incorrect RFC Destinations: When the configuration is saved, an RFC destination is created on the monitoring server for each XI component to enable end-to-end monitoring of the respective XI component. However, the test call failed for the destinations listed. Therefore, you must check the call and the authorization on the monitoring server for the destinations concerned, by using transaction SM59. Also check whether RFC user used for the destination is maintained in the relevant XI component. Note that a component can only be monitored when its RFC destination is maintained correctly.
I have checked the user in the above destinations. For the first destination, we have assigned PIRWBUSER of XI system. Test Connection is OK, but unable to login remote. At the same time, PIRWBUSER is not locked.
For the second destination, I have assigned some login user of sender/receiver system. Test connection is OK. Able to login remotely.
There is no RFC user in our XI system. (I tried using RFCUSER* thru SU01 tcode).
There is no PIRWBUSER in the Sender/Receiver System.
In RWB, Configuration, 3 components are there. 1) XIIntegrationServer 2) Business System (for Sender/Receiver System) 3) XI Adapter Framework. I selected last two. (First one is already selected). Monitoring Level : Medium (for all 3). Send and Receive Check box is selcted for the last two.
So, what could be the problem for the above error?
Could you kindly clarifiy friends.
Thanking you
Kind Regards,
Jeg P.

Hi friends,
I have one RFC Destination PMI<sysid>001. (Abap Connction) in my XI system. This destination is for  XI server. Connection Test is OK. Remote Logon by using the PIRWBUSER is also ok.
In the 'Configuration' tab of the Runtime Workbench, when we select 'Save Configuration', (Business System and Adapter Framework is not activated) with the default activation for XI Integration Server, the system throws the following error.
Incorrect RFC Destinations: When the configuration is saved, an RFC destination is created on the monitoring server for each XI component to enable end-to-end monitoring of the respective XI component. However, the test call failed for the destinations listed. Therefore, you must check the call and the authorization on the monitoring server for the destinations concerned, by using transaction SM59. Also check whether RFC user used for the destination is maintained in the relevant XI component. Note that a component can only be monitored when its RFC destination is maintained correctly.
When we save configuration, an one more destination is automatically created in the name as below.
PMI<sysid>001<yyyymmdd>. For Example, PMIPID00120080207. 
When we test  newly created RFC destination, connection is OK, but not able to remot login using the same user PIRWBUSER.
The difference between old and new RFC destination, in old, we have selected Load Balancing is 'Yes', but in the new it is 'No'. The system also tells the error below.
Name or Password is incorrect (repeat logon) - PMIPID00120080207
But, still remote login is possible in the old RFC destination using the PIRWBUSER.
So, What could be the problem ...?
Kindly reply, friends.

Similar Messages

  • RFC destination error while importing a client request

    Dear Experts,
    We are trying to import a Client Export from our Prd system to Development System and we are unable to import the request as it pops up a RFC destination error.
    We have checked the RFC in the Dev QAS and PRD related to TMSADM and all of them are working fine
    FYI, We are able to release the transports from the development system and it can be moved till qas and prd . So the TMS Configuration is also good.
    The data file and co file in the backend of development is the same size as that of the Prd system.
    I am really stuck . Kindly suggest a solution . Please find the screenshots while importing
    Regards,
    Suratharajan .S

    Hi Suratha,
    Goto STMS->system overview and select the Communication tab.
    Maintained the Instance number of the ASD system.
    Once you maintained the instance number , you will able to see it in the RFC ASD.DOMAIN_ASD.
    Also distribute the configuration after entering the instance number.
    With Regards
    Ashutosh Chaturvedi

  • Monitor RFC Destinations

    Hi guys,
    Couldn't find a way simply monitor RFC destinations with CCMS monitor. Specifically, I've RFC destination type T (http)
    can't find a way to monitor it.
    Please advice,
    Dimitry

    Hi
            Availability can be implemented using the RFC availability check for specific RFC destinations.
            Monitoring of specific and critical RFC destinations can be done by using the standard CCMS MTE
            class CCMS_RFCDest_Availability_Col
            Using the methods described above, alerts can be generated in the CCMS monitoring transactions
    As specified above note 1069130 will help you in achieving it.
    Thanks
    Amit

  • Interface RFC destination Error

    Hi, while testing our interfaces we get this error, Stack>Error: Transaction IDX1: Port HED_020, client , RFC destination contain errors
    We have checked IDX1 and SM58/59 and cant find any error.
    Has anybody come across this before?
    Thanks

    Where do you get this error? In MONI or in SM58?
    Make sure that the User Id in the RFC destination has the authoizations to post Idoc's.
    Make sure that the receiver Idoc adapter has a valid Port name and RFC destination values as created in IDX1 and SM59
    Regards
    Bhavesh

  • Third Party (Garnishment) checks - RFC destination error

    We have an issue with our testing of Third Party Garnishment checks.  We have a split system, with our HCM system residing separately from the remaining ECC modules.
    We are getting an error in regards to the printing of the checks in A/P.
    The posting is working fine
    the vendor account is cleared
    However, It’s not creating a check # or check form.
    We can do other check runs in this client fine; it’s just the 3PR runs that cause the error.
    The text of the error message is as follows:  An RFC destination could not be specified for the logical system HPQCLNT210.
       We have exhausted our resources here looking into the RFC connection and the partner profile and we cannot find anything wrong with them.
    Can someone offer suggestions on what else we could check?  Thanks so much.

    Hi David,
    Did you check below is set-up correctly.
    - Use transaction SM59 to create an RFC destinations for the remote system.
    - Use transaction BD54 to create the logical system.
    - Use transaction BD97 to link the RFC destination created in SM59 with the logical system created in BD54.
    Also, check entries in TBLSYSDEST is  filled with correct system name HPQCLNT210. Generally this error occurs when system name is incorrect in TBLSYSDEST.
    Thanks,
    Ameet

  • RFC destination error in posting 3rd party payment in 4.7 FI system

    Hi,
    We are running in to a problem when we are processing a payment via transaction F110S in our R/3 4.7 system for Financials. We are integrating our Financial system with ECC6.0 for HCM. We receive 3rd party invoice from HCM successfully via ALE and post it in 4.7 system. When we try to process payment against this invoice, apparently 4.7 system is trying to communicate with ECC 6.0 system and issuing an error and the payment processing gets cancelled. It generates a clearing document with out a check.
    The error says "An RFC destination could not be specified for the logical system HD1CLNT014
        Message no. B1550
    Diagnosis
        An RFC destination should be specified for the logical system
        HD1CLNT014. This could not be done in this case. HD1CLNT014 is not your
        local logical system and this system is not included in the relevant
        Customizing tables.
    Procedure
        Check:
            -   RFC destination
               -Port definition
             -oubound partner profile of message type SYNCH for this logical system
    We checked our configuration for all Logical system and RFC destination and everything seems fine.
    Any help in this regard is appreciated.
    Thanks
    Kesav

    Hi David,
    Did you check below is set-up correctly.
    - Use transaction SM59 to create an RFC destinations for the remote system.
    - Use transaction BD54 to create the logical system.
    - Use transaction BD97 to link the RFC destination created in SM59 with the logical system created in BD54.
    Also, check entries in TBLSYSDEST is  filled with correct system name HPQCLNT210. Generally this error occurs when system name is incorrect in TBLSYSDEST.
    Thanks,
    Ameet

  • RFC destination error in SM58

    Hi,
    We are getting an error in SM58 "P85040 does not exist".
    What could be the  reason for this error in PI system?
    When I checked, there is no RFC destination configured with the name P85040. Also there is no communication channel configured with the RFC destination parameter P85040.
    Kindlly help.
    Thanks,
    John

    Hi John,
    The reason can be the host name you are assigning is not existing.
    In RFC destination the host name is for that particular client which is pointing to IP address not to the logical system. You can choose name of RFC destination same as of your logical system.
    You can get the host name by login to SAP system and the using MENU ... System->Status and in lower right corner you can find it.
    Sachin
    Edited by: Sachin Dhingra on Dec 18, 2008 1:18 PM

  • RFC DEstination Error

    After creating the Destination in sm59 I tested the connection.
    When testing the connection, it gives the result as
    Connection type:    R/3 connection                                                                               
    Logon:                      2  msec                        
       0  KB:                    0  msec                        
      10  KB:                    1  msec                        
      20  KB:                    1  msec                        
      30  KB:                    1  msec                        
    I'm trying to create a rfc destination to php in the same system with the same hostname in which SAP is also running...I'm working with ides.
    but when I try to run my php file inside sapclasses in www directory it gives an error as
    SAPRFC extension not loaded
    Message: This script use SAPRFC extension module for PHP and the extension isn't loaded. You can download it with installation instructions from http://saprfc.sourceforge.net. If you have already the extension compiled and installed, check your php.ini configuration

    Here's a full text of the error I receive
    <b>Error when processing your request
    What has happened?
    The URL http://<host_server>.com:<port>/sap/bw/BEx was not called due to an error.
    Note
    The following error text was processed in the system BQ1 : com.sap.engine.services.rfcengine.RFCException: Incoming call is not authorized
    The error occurred on the application server <host_server> and in the work process 0 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Form: IF_RSRD_F_DISTRIBUTOR_RT~DISTRIBUTE of program CL_RSRD_DISTRIBUTOR_KM========CP
    Form: EXECUTE_NODES of program CL_RSRD_SETTING===============CP
    Form: EXECUTE_NODES of program CL_RSRD_SETTING===============CP
    Form: EXECUTE_NODES of program CL_RSRD_SETTING===============CP
    Form: EXECUTE of program CL_RSRD_SETTING===============CP
    START-OF-SELECTION of program RSRD_BROADCAST_PROCESSOR
    What can I do?
    If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system BQ1 in transaction ST22.
    If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server <host_server> in transaction SM21.
    If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server <host_server>. In some situations, you may also need to analyze the trace files of other work processes.
    If you do not yet have a user ID, contact your system administrator.
    Error code: ICF-IE-http-c:100-u:COLLINS -l:E-s:BQ1-i:<host_server>_BQ1_00 -w:0-d:20051012-t:121010-v: RABAX_STATE-e:CALL_FUNCTION_REMOTE_ERROR
    HTTP 500 - Internal Server Error
    Your SAP Internet Communication Framework Team
    </b>

  • RFC destination error in transport

    Hello,
    We are trying to import a transport into our BW QA system and we keep getting return code 8 with the following text:
    BW RFC destination <systemname> is not maintained in the source system
    Message no. R3078
    The transport contains cubes and three ODSs.  After the transport fails and I check the QA system, the cubes are active, but the ODSs are not.
    I searched SDN and found another thread explaining the same problem and I tried everything suggested there.  I looked in RSA1 --> Mapping of the source system names, and the BW DEV and QA systems are listed.  I also looked in SM59 and checked the RFC connection, and that is ok as well. 
    Does anyone have any suggestions?
    Thanks
    Charla

    I have searched OSS further and found that the contents of my RSLOGSYSDEST table are off. 
    The contents are as follows:
    Src System    RFC Destination
    AWQ100          AWP100
    QAT100          QAT
    I believe that in the above table, the AWP100 should be AWQ100.  I looked at this table in our production environments, and in those cases the Src system entry and RFC Destination entry are the exact same, so I think this should be the case in our AWQ100 system as well.
    Just curious if anyone knows if there is a program I can use to modify this table. 
    Thanks
    Charla

  • Error while saving config in MSY

    Hi,
    I am working on taking MSA 5.0 SP7 go-live. I am working in MDW. I posted a SDN post long back regarding the custom partner functions in MSA and got it resolved (followed the note 521871). I am trying to do the same in the PROD system and i am facing errors:
    -> When i goto Cross-Component Settings->Relationship Categoty-> click on NEW i am getting the errors:
      1. 'MTBLLFW-The attribute destination of the business object
          relation type is not valid'.
      2. 'MTBLLFW-the attribute source of the business object relation
          types is not valid'
    But it is allowing me to add an entry. When i save my customer entry i am getting the error :
      3. 'UI_CORE_SAVE_FAILED_STA-Errors while saving'.
    I ran the consolidated prefill for 5.0 and SP07. I followed the same procedure as i did in DEV. In DEV i never got these errors. I was able to create them in the first attempt.
    If anyone has any idea please let me know.
    Thanks in advance,
    Karuna.

    Hi,
    did you already check i.e. compare the customizing subscriptions for both DEV MDW and PROD MDW sites?
    Also you should check & compare the download monitor for CDB load in the CRM system(s).
    I assume sth is missing there (see also your other post).
    Regards,
    Wolfhard

  • Error while testing Adapter through RWB with payload

    Hi all,
    While testing Adapter engine through RWB with payload, i get the below error
    Error while sending message: com.sap.aii.af.ra.ms.api.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't retrieve outbound binding for the given P/S/A values: FP=;TP=;FS=ec6clnt001;TS=com_avaya_java_bs;AN=StartNotification_MI_sync;ANS=http://www.tcs.com/sap/xi/AVAYAPoC;"
    Can any body please suggest the possible reason and solution for the same.
    Regrads,
    Kulwant

    Hi
    verify the receiver agreement and  also check it out whether receiver message interface is configured properly or not?
    or
    open ID and goto tools tab in that click on
    test configuration by providing your Business service and interface details along with the payload it displays the error message.
    regards
    Suryanarayana

  • Error while configuring Config Tool

    HI,
    I tried to change the JVM settings using config tool but it is giving an error and the config tool is automatically closing.can anybody help me to resolve this problem.
    Error Occured...
    Error occurred while working with Configuration.
    com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access: ,
    at com.sap.engine.core.configuration.impl.persistence.rdbms.UpdateProcessor.flush(UpdateProcessor.java:294)
    at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.commitConfigurationHandler(ConfigurationCache.java:1217)
    at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.commit(ConfigurationHandlerImpl.java:833)
    at com.sap.engine.configtool.batch.task.ChangeInstancePropsTask.go(ChangeInstancePropsTask.java:118)
    at com.sap.engine.configtool.batch.task.TasksThread.run(TasksThread.java:46)
    Caused by: com.sap.dbtech.jdbc.exceptions.BatchUpdateExceptionSapDB: [-3018]: Invalid numeric parameter(input position 8)
    at com.sap.dbtech.jdbc.CallableStatementSapDB.executeBatch(CallableStatementSapDB.java:608)
    at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1102)
    at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1066)
    at com.sap.engine.core.configuration.impl.persistence.rdbms.DBAccessDefault.execUpdateEntryBatch(DBAccessDefault.java:1180)
    at com.sap.engine.core.configuration.impl.persistence.rdbms.UpdateProcessor.flush(UpdateProcessor.java:261)
    ... 4 more
    Regards,
    Kiran.

    Hello Bhogi,
    Look at this thread:
    Re: CRITICAL: Error occured while working with configuring .in WAS deployto It deals with the same problem. Check if you are not using java 1.5.
    Best Regards
    Vyara

  • Error while congiguring config tool

    HI,
    I tried to change the JVM settings using config tool but it is giving an error and the config tool is automatically closing.can anybody help me to resolve this problem.
    Error occurred while working with Configuration.
    com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access: ,
    at com.sap.engine.core.configuration.impl.persistence.rdbms.UpdateProcessor.flush(UpdateProcessor.java:294)
    at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.commitConfigurationHandler(ConfigurationCache.java:1217)
    at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.commit(ConfigurationHandlerImpl.java:833)
    at com.sap.engine.configtool.batch.task.ChangeInstancePropsTask.go(ChangeInstancePropsTask.java:118)
    at com.sap.engine.configtool.batch.task.TasksThread.run(TasksThread.java:46)
    Caused by: com.sap.dbtech.jdbc.exceptions.BatchUpdateExceptionSapDB: [-3018]: Invalid numeric parameter(input position 8)
    at com.sap.dbtech.jdbc.CallableStatementSapDB.executeBatch(CallableStatementSapDB.java:608)
    at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1102)
    at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1066)
    at com.sap.engine.core.configuration.impl.persistence.rdbms.DBAccessDefault.execUpdateEntryBatch(DBAccessDefault.java:1180)
    at com.sap.engine.core.configuration.impl.persistence.rdbms.UpdateProcessor.flush(UpdateProcessor.java:261)
    ... 4 more
    Regards,
    Kiran.

    This error may be due to following
    1) DB may not be running. So check that
    2) DB Configuration on WAS is not correct. Check userid/password
    Try login to DB using the SQL Client using following userid/password
    SAPJ2EDB/abcd1234 (if it's sneak preview version and you haven't changed the default passowrds.
    Regards,
    Piyush
    ps: pls mark useful answers.

  • Monitor red with errors while status is green

    Errors originated when our production environment ran out of space. Since then more space is added resolving that issue.  However, the monitor still remains with errors. The current production issue occurs when flat files are loaded via full loads; job shows successful, data is loaded in DSO, data is visible through reports, but monitor shows errors. 
    SM37 shows this error:
    <b>Check: No successful initialization of the delta update took place
    Init. select. for field name  currently running in request REQU_44CQ39DOX2Q85U97AKNKNMVOD
    Error in generated init. package ZPAK_440UCB93QLW06PEMJ24OWYRQ5 for DSO LROTPD; no update                            
    Report RSODSACT1 ended with errors
    Job cancelled after system exception ERROR_MESSAGE</b>
    Thank you for you assistance,
    Mustafa

    Hello Mustafa,
    One of the new features offered in Netweaver 2004s is the ability to set reports to include red requests in addition to the green an yellow ones.  You might want to check the setting of the reports you are running.  To do that, go to RSRT, enter the query name, and check the query properties.  The value you're looking for is the "Data Integrity" setting.  If the setting is "9 - All complete InfoProvider", it will include your red requests in the report.
    Regards,
    Adam

  • From RFC 2068 Error while testing ADF Application in Weblogic Server

    Hi All,
    Created an ADF application and Deployed this application to Weblogic server.
    I am getting the below error After deploy into weblogic server while running the application
    I am able to run this application well in JDeveloper using the IntegratedWebLogicServer.
    The Application is successfully deployed to the Web Logic server.
    While creating the domain, I have extended the Oracle JRF classes.
    Error
    Error 404--Not Found
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.5 404 Not Found
    The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
    If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
    JDeveloper Version : 11.1.1.3.0
    Weblogic Version : 10.3.3.0
    Thanks
    Satish

    HI John,
    In The web.xml i added /faces/TestPG
    This is URL in Weblogic Server
    http://10.146.2.232:7001/TestDeployee-ViewController-context-root/faces/TestPG
    Thanks
    Sathish

Maybe you are looking for

  • Where Can I Get a Zen Xtra 60 GB Case/Pouch With Window??!!!!!!!

    I've searched endlessly! Creative does not have any in stock so I used the ''notify me when available'' option. And sadly, after writing to Creative's customer support, I was told that they don't even know when the will get more of these in stock. Eb

  • Update the on-hand quantities through Data Loader

    Dear All, I need to update the on-hand quantities of some number of Items (5000 items). I hope I can do this with Data Loader, but which is the screen that I need to go and update the stock. Is the way, or any other alternate way that I can accomplis

  • Downloaded cds are not given names, just track 1, 2 etc.

    All dowloaded cds are not given names, just track 1, 2 etc. So frustrating. These are not burned cds, but cds bought at a store. Help!

  • Single Signon in WLP 4.0 ?

    Hi, Can someone help me with a step-by-step description on how to achieve single signon between a number of portals (same deployment)? We have some problems getting it to work properly, and I think I have thoroughly confused myself :-) - Jan

  • Multichannel multisample read timestamp for CCP

    I have been using multichannel multisample 2D Dbl CAN read vi to acquire data from my CCP functions. This is almost the same as what is shown in the NI CCP toolset examples. However, now I want to read the timestamps, but when I select the multichan-