Error found in RFC (target) and respective logon\logons are disabled.

Hi All,
So we have a requirement to use trusted connections for our EAM configuration and after setting up FFUser when the user login in to the system and execute GRAC_SPM we automatically get the message "Error found in RFC (Plugin System) and respective logon\logons are disabled."  We saw note 1777094 that suggest to update validity and password of RFC user, but because this is a trusted connection there is no "RFC User" or in other words the user is the "Current user" of the session and note 1652880 is suggested as a possible fix for Non trusted RFC.  Can anyone point me in the direction of what the issue is here?
we automatically get the message

Hi Santosh,
Our problem was a mixture of not understanding correctly RFC objects and also when to use trusted vs standard connections.  As shown in this link http://help.sap.com/saphelp_nw70/helpdata/en/6b/af429b12e9214d9a2d6cba921b162f/content.htm auth objects related to RFC are actually not included on the SAP profile (that was one of our problems) so our configuration for S_RFC was incorrect.  Also using trusted connections is not mandatory any more to use EAM so at the end using Standard connections was a better approach.  Hope that helps.

Similar Messages

  • I plugged in my ipod the other day, and it says you are disabled for 23,238,968 mins. what can i do?

    I plugged in my ipod and it said you are disabled for 23,423,324 minutes, what can i do?

    You have two choices: either wait until October 6, 2058, or restore it as a new device.
    If you choose the latter follow these instructions: iOS: How to back up your data and set up your device as a new device
    If you choose the former it will be a Sunday, should you wish to plan for it.

  • Create users under Administration Server Create user and Refresh users options are disabled

    We have installed and configured 11.1.2.2 successfully, Essbase in standalone mode.
    When we try to create users under Administration Server Create user and Refresh users options are disabled. Please let me know how to create EAS users?
    Thanks,
    Satheesh.

    Please find below response.
    1.You can create users from EAS console using maxl, if you have not externalized the users .
    When we create using Maxl it will create for 'ESSBASE Servers' users but we want to create additional administrator users under 'Administrator Services' --> 'Users'. At the moment default 'Admin' users is created under 'Administrator Services' --> 'Users'.
    2.  you have installed your essbase in a stand -alone mode  , then the option of creating users will be enabled and you can give appropriate provision to applications.
    Yes. But the create users is disable for Admin.
    3. Through which url are you accessing EAS console is it http://Servername:19000/workspace/index.jsp ?
    http://prod-server:10080/easconsole/console.html
    Please suggest.

  • Error in the RFC LCRSAPRFC and SAPSLDAPI

    Hi,
    The RFC LCRSAPRFC and SAPSLDAPI TCP/IP connection to strike up and all SOAP interfaces stops in XI environment.
    Yesterday the same problem occur. I checked if user is lock but not locked. Just after I restarted the environment (stopsap and starsap) and I made refresh full cache http://brjgs916:50100/CPACache/refresh?mode=full
    the RFC´s TCP/IP LCRSAPRFC/SAPSLDAPI back to work.
    The problem is intermittent occurs almost all days.
    I found and implemented the notes 314530 and 316877 but I think this notes cannot solve this problem.
    My XI environment is kernel 700 patche level 95 and Stack ABAP and Java
    11, HP-UX with Oracle 10g.
    Thanks so much for your attention
    Douglas Brisola

    Is the SLD running on the same server?
    We had a similar issue and the hardware the SLD was running on was, er, unreliable!  The availability is much better these days!

  • Gmail says my browser is unsupported but yet Google just updated it and all my extensions are disabled. Whats up? Driving me nuts.

    I am getting the followinf when going into Gmail
    Some important features may not work in this version of your browser, so you have been redirected to the Basic HTML version. Upgrade to a modern browser, such as Google Chrome.
    When I go to upgrade to a modern browser it tells me:
    If you're using a supported browser,'''''''''(which I am) '''''''''but see a message in Gmail that your browser is unsupported, you may be using an extension that interferes with browser detection. Try disabling your browser extensions to resolve the problem.
    All my extensions are disabled. and I want to use firefox gmail and see all my features. What gives?

    You can check for problems caused by a possibly corrupted user agent.
    See:
    *https://support.mozilla.org/kb/Finding+your+Firefox+version
    *https://support.mozilla.org/kb/websites-incorrectly-report-firefox-outdated-or-in
    *http://kb.mozillazine.org/Resetting_your_useragent_string_to_its_compiled-in_default

  • Errors found when using tar and ACL's

    Having difficulties with TAR and ACLs, and wondering if anyone had seen this before.
    Here's the scenario: create a few directories and a few files. Tar it up and extract the files. Now assign some ACL's to them (some default for directories), tar it up, and extract the files. Permissions should remain the same. Under most circumstances they are.
    Now repeat the procedure, but put a default directory ACL on the parent directory where the TAR is created. What happens is that the group permissions for anything un-tared gets trashed.
    Here's a script to test it out.
    Create a dummy user (I called mine foobar) -- required for setting ACL's. Run the script with the "-d" option at first. Things appear good. You can compare the permissions on the bottom for each file/directory.
    Run the script with the "-s" option setting default ACL's on the parent.
    #!/usr/bin/sh
    ROOTDIR=/export/home/christian/config
    TESTDIR=/export/home/christian
    USER_X="oam"
    # Run the script once with normal permissions (no ACL's) in the test directory (where tar is located)
    # --> ./test.sh -d
    # look at the result (ls -l) of .../sub1dir, .../sub1dir_acl, and /sub1dir_orig
    # They should be relatively the same:
    # --> rwxrwxrwx permissions on directories
    # --> rw-rw-rw- on files
    # Now run the script but set the parent directory of the script (where the TAR's are located) to have default ACL's
    # --> /opt/MMSsyscnf/sub2dir/test/test.sh -s
    # Now look at the result (ls -l) of .../sub1dir, .../sub1dir_acl, and /sub1dir_orig
    # They are COMPLETELY skewed. Both times we tried to untar the files, ACL's wound up
    # all over the place and permissions were not set correctly.
    # --> rwxrwxrwx permissions ONLY on original directory (not the product of an UNTAR)
    # --> rwxr--rwx permissions on directories created by untar
    # --> rw-rw-rw- on files ONLY on original directory (not the product of an UNTAR)
    # --> rw-r--rw- on files created by untar
    # ****** Why is group affected by this, but "other" is not?! It's gotta be a bug!
    # MAIN
    ACTION="NOPREP"
    while [ -n "$1" ]
    do
    if [ "ABC$1" = "ABC-d" ]; then
    #flag set to try and remove default directory ACL's
    setfacl -d u:$USER_X $TESTDIR
    setfacl -d d:u:$USER_X $TESTDIR
    setfacl -d d:u::,d:g::,d:m:,d:o: $TESTDIR
    elif [ "ABC$1" = "ABC-s" ]; then
    setfacl -r -m d:u::rw-,d:g::r--,d:o:---,d:m:rwx $TESTDIR
    setfacl -r -m d:u:$USER_X:rw- $TESTDIR
    setfacl -r -m u:$USER_X:r-x $TESTDIR
    fi
    shift;
    done
    # clean up previous run of the test
    rm -r $ROOTDIR
    # create files/directories
    mkdir $ROOTDIR
    mkdir $ROOTDIR/sub1dir
    mkdir $ROOTDIR/sub1dir/sub2dir
    mkdir $ROOTDIR/sub1dir/sub2dir/sub3dir
    #set permissions
    chmod 777 $ROOTDIR
    chmod 777 $ROOTDIR/sub1dir
    chmod 777 $ROOTDIR/sub1dir/sub2dir
    chmod 777 $ROOTDIR/sub1dir/sub2dir/sub3dir
    # create files
    echo "" > $ROOTDIR/sub1dir/sub2dir/file1.txt
    echo "" > $ROOTDIR/sub1dir/sub2dir/sub3dir/file2.txt
    chmod 666 $ROOTDIR/sub1dir/sub2dir/file1.txt
    chmod 666 $ROOTDIR/sub1dir/sub2dir/sub3dir/file2.txt
    # tar/zip the files:
    /usr/bin/tar -cvf $ROOTDIR/tarBeforeACLs.tar $ROOTDIR/sub1dir
    /usr/bin/gzip $ROOTDIR/tarBeforeACLs.tar
    # move the directory (so we keep the original as a template of what things should look like)
    mv $ROOTDIR/sub1dir $ROOTDIR/sub1dir_orig
    # untar/zip the files:
    /usr/bin/gunzip $ROOTDIR/tarBeforeACLs.tar
    /usr/bin/tar -xvf $ROOTDIR/tarBeforeACLs.tar
    ls -lR $ROOTDIR
    # Ok. These have been tested to be the exact same.
    echo "********************************************************************************"
    echo "********************************************************************************"
    echo "********************************************************************************"
    # Let's try using ACL's now
    # --> directories (owned by root) must be acessible to OAM user.
    # --> files (owned by root) must be read/writable by user OAM when created in the directories
    setfacl -r -m u:$USER_X:r-x $ROOTDIR/sub1dir
    setfacl -r -m u:$USER_X:r-x $ROOTDIR/sub1dir/sub2dir
    setfacl -r -m u:$USER_X:r-x $ROOTDIR/sub1dir/sub2dir/sub3dir
    setfacl -r -m u:$USER_X:rw- $ROOTDIR/sub1dir/sub2dir/file1.txt
    setfacl -r -m u:$USER_X:rw- $ROOTDIR/sub1dir/sub2dir/sub3dir/file2.txt
    setfacl -r -m d:u::rw-,d:g::r--,d:o:---,d:m:rwx $ROOTDIR/sub1dir
    setfacl -r -m d:u:$USER_X:rw- $ROOTDIR/sub1dir
    setfacl -r -m d:u::rw-,d:g::r--,d:o:---,d:m:rwx $ROOTDIR/sub1dir/sub2dir
    setfacl -r -m d:u:$USER_X:rw- $ROOTDIR/sub1dir/sub2dir
    setfacl -r -m d:u::rw-,d:g::r--,d:o:---,d:m:rwx $ROOTDIR/sub1dir/sub2dir/sub3dir
    setfacl -r -m d:u:$USER_X:rw- $ROOTDIR/sub1dir/sub2dir/sub3dir
    # here are things as they stand
    ls -lR $ROOTDIR
    echo "********************************************************************************"
    echo "********************************************************************************"
    echo "********************************************************************************"
    # tar/zip the files:
    /usr/bin/tar -cvfp $ROOTDIR/tarAfterACLs.tar $ROOTDIR/sub1dir
    /usr/bin/gzip $ROOTDIR/tarAfterACLs.tar
    # move the directory (so we keep the directory that was applied ACL's)
    mv $ROOTDIR/sub1dir $ROOTDIR/sub1dir_acl
    # untar/zip the files:
    /usr/bin/gunzip $ROOTDIR/tarAfterACLs.tar
    /usr/bin/tar -xvfp $ROOTDIR/tarAfterACLs.tar
    # here are things after we've untared them
    ls -lR $ROOTDIR
    echo "********************************************************************************"
    echo "********************************************************************************"
    echo "********************************************************************************"
    getfacl $ROOTDIR/sub1dir_orig $ROOTDIR/sub1dir_acl $ROOTDIR/sub1dir
    echo "********************************************************************************"
    getfacl $ROOTDIR/sub1dir_orig/sub2dir $ROOTDIR/sub1dir_acl/sub2dir $ROOTDIR/sub1dir/sub2dir
    echo "********************************************************************************"
    getfacl $ROOTDIR/sub1dir_orig/sub2dir/sub3dir $ROOTDIR/sub1dir_acl/sub2dir/sub3dir $ROOTDIR/sub1dir/sub2dir/sub3dir
    echo "********************************************************************************"
    getfacl $ROOTDIR/sub1dir_orig/sub2dir/file1.txt $ROOTDIR/sub1dir_acl/sub2dir/file1.txt $ROOTDIR/sub1dir/sub2dir/file1.txt
    echo "********************************************************************************"
    getfacl $ROOTDIR/sub1dir_orig/sub2dir/sub3dir/file2.txt $ROOTDIR/sub1dir_acl/sub2dir/sub3dir/file2.txt $ROOTDIR/sub1dir/sub2dir/sub3dir/file2.txt
    echo "********************************************************************************"
    Any ideas?

    UFSDUMP has some limitations, including being on a file system that is read-only. Yes, I could force it on a read-write FS, but I normally stay away from big sticker labels found in man pages when I encounter them. :-(
    What I was originally after was a script that makes a backup of application configuration files before I modify them. Thus, I tar/zip the directory.
    These config files/directores have ACL's attached to them to allow various roles to access them (group permissions are not fine-grain enough). However, when I ran through a couple of tests, I came across a scenario that overwrote the original permissions. Tested it on Solaris 10 and Solaris 9, and both fail.
    So now (very late into the feature design) I'm VERY concerned about using ACL's on Solaris, and wonder what other side-effects there are that I'm not aware of. Can't seem to find a bug report on it, so I thought I'd ask around to see if it was just the behaviour of the TAR/ACL that I'm not quite getting, or if it really is a bug.
    /chris

  • Error in BPM: "COMMUNICATION FAILURE" during JCo call. Error opening an RFC

    hello experts
    i am receiving the above error incase of BPM scenario where i am having a Transform step and synchronous RFC step.
    i referred to the few threads discussing such problems and was trying to find whether my mapping is correct and i tested my mappings using my payload which looks good.
    When looked into the Mapping trace of the BPM "Show container" i found error ""COMMUNICATION FAILURE" during JCo call. Error opening an RFC connection" and it seems that when BPM is attempting to call interface mapping it is throwing this error.
    Thanks in advance.
    Regards
    rajeev

    hi,
    I think no problen with the mapping part,
    jco connection requird when xi try to stablish the connection with the adapter .
    please look the link provided.
    Setup and test SAP Java Connector outbound connection
    please also check the following parameter at the exchange profile
    com.sap.aii.rwb.server.centralmonitoring.r3.ashost
    com.sap.aii.rwb.server.centralmonitoring.r3.client
    com.sap.aii.rwb.server.centralmonitoring.r3.sysnr
    com.sap.aii.rwb.server.centralmonitoring.httpport
    these parameter must be given properly.
    if every thing is ok than and problem still exist than try to restart the system.
    for us after restarting its worked fine.
    regards,
    navneet

  • Difference between RFC, SYSTEM and AUDIT users?

    Hi All,
    Can you highlight the main differences between the following users:
    RFC
    SYSTEM
    AUDIT
    how do their functions differenciate them ?
    Thanks in advance,
    Diwakar

    RFC User
    RFC user is basicly used to receive status messages. An RFC user has to be created in all the system clients where messages needs to be recieved. An RFC user can also be used for receiving messages using SMTP plug-in.
    The RFC User is an sap user of type System and that's why no person can logon with this user on SAP System.
    Following is thr procedure to create RFC User, remember the purpose is to recieve messages including status messages as well.
    Creation of RFC User
    Go to  Tools > Administration > User Maintenance > Users.
    Enter a name, for example MAIL_ADMIN.
    Select "New"
    On the Logon data tab page, select the user type System.
    Enter a password.
    On the Profiles tab page, enter the authorization profile S_A.SCON. This profile minimizes the risk of misuse, even if the communication system does not store the password is encoded form.
    Select "Save"
    Both RFC user and a System user are of type System only. Now the difference, depends upon the profile and authorization of the user.
    Audit users are of type dialog, and can be used by a person to logon to system. There might be many roles assigned to this user. My understanding is that an Audit User is not a standard sap type user but just a dialog user and can be created with a conventional method of creating any other dialog users with a specific profile and authorizations.
    Still to confirm, Can you please tell us, how many types of users does it shown in 4.6c at the time of user creation?
    Best Regards,
    Amol Bharti

  • Album View and Cover Flow View are not available in iTunes 7

    Hi,
    When I connect my iPod, in the iTunes 7, the options for Album view and Cover Flow View are disabled for the song list on my iPod. I only have a list view for them. However, at the same time, the songs on the library can be viewed in any of the three (3) views.
    What might be the possible reason and is there any options to view your iPod songs in Cover Flow View in iTunes (while it is connected)?
    Please solve this query of mine.

    It just simply not a feature. You might think about requesting it here:
    http://www.apple.com/feedback/itunesapp.html

  • Pan and Volume Sliders are disabled

    Hello there! My Pan Button and my volume slider are disabled in GarageBand '08. Everything is up-to-date with my new MacBook I've just bought last week. The same thing happens to a friend who has upgraded from Tiger to Leopard.
    Is someone has problem with this issue? Is there a solution?
    Unfortunately, the show must go on...
    Thanks!

    http://www.bulletsandbones.com/GB/GBFAQ.html#pandisabled
    http://www.bulletsandbones.com/GB/GBFAQ.html#voldisabled

  • RFC connection error between BW 3.5 and ECC 6.0

    Hi gurus,
    We've defined an RFC destination between BW 3.5 and ECC 6.0. Connection test  (SM59) is ok, but authorization one fails and ALEREMOTE users block. These users on both systems have good profiles. We look ST22 and find a runtime error on CALL_FUNCTION_REMOTE_ERROR. We've cleaned source system on BW and RFC destination and we've created one more time, but error doesn't disappear. We've looked OSS but don't find anything.
    Any idea? Is there any other place (users, RFC) where we have to change user password on system?
    Thanks a lot!
    Regards,
    Iván.
    Edited by: Iván Cabezas Castillo on Nov 6, 2009 12:09 PM

    Solved!
    This is because of the incompatibility of password handling between
    640 and 700 systems.
    We have to use a maximum 8 character long password with only capital letters (numbers are also allowed) for the user "ALEREMOTE".
    1. Change the password for the user in SAP R/3.
    2. Maintain the password in SAP BW for the RFC destination (transaction SM59 - Logon/Security tab)
    3. Authorization test is now successful.
    (SM59 - Test - Authorization).
    Regards!

  • Getting error in XI"RFC Program Not Found"

    Hi All,
    I am getting error in SXMB_MONI "RFC Program not found via SAP XI".
    So please suggest me what is the problem behind this..For these SAP XI and R/3 i made 3 to 4 RFC program but only 1 RFC program name not getting Via SAP XI.
    Thanks
    Amit

    Hi,
    I am calling RFC FM via SAP XI.
    Main Records are coming from siebel and recevied by SAP XI and XI will do some changes in records and calling REC FM from SAP R/3.
    Problem is siebel to xi records coming fine but xi to sap R/3 error message coming "Program not Found".
    Thanks
    Amit

  • UCM Log in error : Error 404--Not Found From RFC 2068 Hypertext Transfer Pr

    i am not able to get ucm login page , admin and manage server is up and there is no error in logs . but iam getting below error in login page
    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.

    Hi ,
    This is an indication that ECM cs.ear deployment has failed for some reason . To get the exact reason either check ucm_server1.log or start the server from command line and there the errors will be shown.
    Copy the core part and post it .
    Thanks
    srinath

  • Regarding Error handling and customisation in RFC, Idocs and Proxy

    Hi,
    I wanted to compare RFC, Proxy and Idocs on the basis of the amount of customisation required in ECC when sending data from ECC to XI using the above stated means and also the error handling provided in these methods.
    Please let me know in detail if possible.
    Regards,
    Sampada

    Hi ,
    Check this blog to know when to use which adapter:
      /people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
    we use proxy in sap 6.0 version or higher.
    Basically used for adapter less communication
    & very high volume of data has to be transfered.
    Step for Configuration fo IDOC in R/3
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (IDX1)
    a) Select create new button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Load Meta Data for IDOC (IDX2)
    a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1.
    SAP R/3
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (We21)
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Create Partner Profile (WE20)
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system.
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang.
    e) Click on the + button to select the message type.
    f) Select Partner no. and LS which ever create above.
    g) Select Message type
    h) Select Process code related to the Message type.
    I) save.
    In SLD – System Landscape Directory
    TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
    Ts for Third Party (Logical system):-
    BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
    BS for Third Party (Logical system):-Enter the XI logical system name.
    In Transaction SALE
    Define and Assign the logical system name.
                                                                                    Regards,
                                                                                    Vinod.

  • Error:No Jco RFc metadata found

    Hi Moderator,
    Pls don't block this question ,previously also ,I have closed the questionin another forum but you blocked here.
    Closed the questionin another forum as I think that this is appropriate forum.
    =========================================================
    Hi All,
    We are using ESS MSS on SAP EP 7.0 SP 15 and using ERP 6.0 EHP 3 .
    In Portal while navigating to ESS -> leave_>apply leave we are getting this error
    The initial exception that caused the request to fail, was:
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: no jcoMetadata found for RFC function 'PT_ARQ_ACCOUNTS_GET_CE'! Please verify, that your model is consistent with the ABAP backend:
    Detail information
    ==============
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: failed to create or init instance of model 'com.sap.xss.hr.lea.model.LeaveRequestAdaptiveModel' in scope APPLICATION_SCOPE with instanceId 'null'
    at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getOrCreateModelInstanceFromScopeMaintainer(WDModelFactory.java:341)
    at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getModelInstance(WDModelFactory.java:155)
    at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getModelInstance(WDModelFactory.java:102)
    ==============
    These are the details:
    WebDynpro Content
    SAP_ESS 603 SP3
    SAP_MSS 600 SP14
    SAPPCUI_GP 603 SP3
    Business Package
    BP_ERP5COM 1.31 SP3
    BP_ERP5ESS 1.31 SP3
    BP_ERP5HRA 1.11 SP7
    BP_ERP5MSS 1.31 SP3
    These are the details of ABAP backend
    SAP_HR 600 29 SAPKE60029
    EA-FINSERV 603 2 SAPK-60302INEAFINSRV
    EA-HR 603 3 SAPK-60303INEAHR
    EA-APPL 603 2 SAPK-60302INEAAPPL
    Pls suggest how to resolve this.Is this related to Version mismatch of support packs.
    I have checked the Jco RFC.All are working fine.
    Regards
    Ajay

    Hi Ajay,
       I am facing the same issue and am trying to follow the note that you had suggested. The note says to create the dummy RFCs "PT_ARQ_ACCOUNTS_GET_CE", "PT_ARQ_REQLIST_GET_CE" and PT_ARQ_READ_CE_SWITCH, But doesn't say which package I should save the RFC/structures/table types in. I tried saving them in EA-HR, but got the following error. "EA-HR cannot be extended."
    Please help.
    Regards,
    JS.

Maybe you are looking for