Perform Risk Analysis on Request - Not available via WebService call?

Hi,
I'm using AC 5.3 and using the SAPGRC_AC_IDM_SUBMITREQUEST to submit a request to CUP.
At CUP I have configured to 'Perform Risk Analysis on Request'.
This does work, when I create a request using the CUP Web Interface.
The same request made through the CUP Web Service request doesn't fire up the RIsk Analysis.
Is it a bug, a feature, a limitation or did I miss something?
Regards
Holger

Hi Harleen,
yes, the SAPGRC_AC_IDM_RISKANALYSIS Web Service call work as well and comes back with risk information.
But this is a different story.
When starting a manual request and a risk occurs, the approver does see the risk in the approval form.
When starting the rquest through the WebService and a risk occurs, the approver does not see a risk and must start a manual risk analysis to be informed about existing risks.
This feature is very bad, because it limits the functionality drastically.
Is there a way to make this an enhancement request?
KInd Regards
Holger

Similar Messages

  • GRC 5.3: CUP asks to perform risk analysis even when there are no risks in request

    Hi All,
    We recently upgraded from GRC 5.3 SP13 to SP22.
    The one issue which we are facing after upgrade is that now CUP is forcing approvers to do Risk Analysis, even when there are no risks in the CUP Request, that is Risk Tab is Green.
    Previously approvers were able to approve requests without doing risk analysis, if there were no risks in the request.
    CUP used to force them to do risk analysis only when there were risks associated with requests.
    But now, it is forcing approvers to perform risk analysis, even if there are no risks, i.e. approvers are not able to approve requests without any risks without doing risk analysis.
    Please advise.
    Thanks
    Aditi

    Hi,
    Can you check if any change is made in Configuration -> Workflow -> Stage -> Approvers
    Regards,
    Claudio

  • ARQ: A requester is able to perform risk analysis even after submitting a request???

    Hi,
    A requester is able to perform risk analysis even after submitting a request. May I know how I can restrict this?
    Regards,
    Faisal

    Hi Faisal,
    you can restrict by removing authorization. Basically authorization object GRAC_RA with ACTVT 16 (Execute) is used to execute the risk analysis.
    Hope this helps.
    Regards,
    Alessandro

  • Risk Analysis On Request Submission property config

    Hi,
    We have configured the New and Change access request to go through a Role Owner Approval in CUP. As to enable the role owners aware of the reported risks with an access request when it lands in their Inbox, we have enabled the Risk Analysis config:  'Risk Analysis On Request Submission' to Yes. This setting makes the system to perform Risk Analysis using the RA webservice on ALL requests.
    But we are not enforcing the Risk analysis and mitigation in all systems that are provisioned through GRC CUP. The property seems global and hence we are looking for a work around to bypass the RA on requests for some systems or rather a system specific setting.
    Is there any tweak available with GRC 5.3 SP08 to achieve this?
    As of now, we don't maintain the RAR rules for the systems where risk analysis is non-mandatory, but notice that the system is unnecessarily performing RA amounting to inefficient utilization of  resources.
    Any help would be greatly appreciated.
    Thanks, Anil

    Anil,
    There will be a few seconds extra for each system not included in risk analysis, but it should realize very quickly that there are no rules for that system (and that it can't even connect to pull authorizations if it is a dummy system).
    Sorry there isn't a better answer, but it's the way it is built.
    Tyler

  • Can not start instance SAP - ABAP Database is not available via R3trans

    Dear all !
    My OS : Linux RHEL 4U7 32bit
    Oracle 10G R2 32bit 10.2.0.2
    when system running but  power off suddenly
    and when power on ->
    i am having problem as below when i start instance SAP (Databse Oracle Started)
    Step 1 : I login user (ora<sid>) of Oracel to start up database
    Database startup -> OK
    then i tried to shutdown database -> OK too
    and start up again -> OK
    Query -> OK
    I think Database do not problem
    Step 2: start listener -> OK
    Step 3: i login user (<sid>adm) and startup instance SAP (command : startsap r3) with error:
    Checking SED Database
    ABAP Database is not available via R3trans
    Starting SAP-Collector Daemon
    11:11:48 10.02.2010   LOG: Effective User Id is root
    This is Saposcol Version COLL 20.90 700 - Intel x86 with Linux, PL:75, Aug 29 2006
    Usage:  saposcol -l: Start OS Collector
            saposcol -k: Stop  OS Collector
            saposcol -d: OS Collector Dialog Mode
            saposcol -s: OS Collector Status
    The OS Collector (PID 6870) is already running .....
    saposcol already running
    ABAP Database SED must be started first
    Please help me to resolve this problem
    Thanks for your advice

    Dear all !
    1. output of tnsping SED :
    TNS Ping Utility for Linux: Version 10.2.0.2.0 - Production on 11-FEB-2010 13:51:24
    Copyright (c) 1997, 2005, Oracle.  All rights reserved.
    Used parameter files:
    /oracle/SED/102_32/network/admin/sqlnet.ora
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (COMMUNITY = SAP.WORLD)(PROTOCOL = TCP)(HOST = sapsed)(PORT = 1527))) (CONNECT_DATA = (SID = SED) (GLOBAL_NAME = SED.WORLD)))
    OK (0 msec)
    2. output startsap_.log
    Checking SED Database
    ABAP Database is not available via R3trans
    Starting SAP-Collector Daemon
    saposcol already running
    ABAP Database SED must be started first
    ---> output above repeats many
    3. output trans.log
    4 ETW000 R3trans version 6.14 (release 700 - 18.09.06 - 09:35:00).
    4 ETW000 unicode enabled version
    4 ETW000 ===============================================
    4 ETW000
    4 ETW000 date&time   : 11.02.2010 - 13:49:36
    4 ETW000 control file: <no ctrlfile>
    4 ETW000 R3trans was called as follows: R3trans -d
    4 ETW000  trace at level 2 opened for a given file pointer
    4 ETW000  [dev trc     ,00000]  Thu Feb 11 13:49:36 2010                             159  0.000159
    4 ETW000  [dev trc     ,00000]  db_con_init called                                    27  0.000186
    4 ETW000  [dev trc     ,00000]  create_con (con_name=R/3)                             55  0.000241
    4 ETW000  [dev trc     ,00000]  Loading DB library '/usr/sap/SED/SYS/exe/run/dboraslib.so' ...
    4 ETW000                                                                              63  0.000304
    4 ETW000  [dev trc     ,00000]  load shared library (/usr/sap/SED/SYS/exe/run/dboraslib.so), hdl 0
    4 ETW000                                                                           16430  0.016734
    4 ETW000  [dev trc     ,00000]  Library '/usr/sap/SED/SYS/exe/run/dboraslib.so' loaded
    4 ETW000                                                                              56  0.016790
    4 ETW000  [dev trc     ,00000]  function DbSlExpFuns loaded from library /usr/sap/SED/SYS/exe/run/dboraslib.so
    4 ETW000                                                                              41  0.016831
    4 ETW000  [dev trc     ,00000]  Version of '/usr/sap/SED/SYS/exe/run/dboraslib.so' is "700.08", patchlevel (0.73)
    4 ETW000                                                                              94  0.016925
    4 ETW000  [dev trc     ,00000]  function dsql_db_init loaded from library /usr/sap/SED/SYS/exe/run/dboraslib.so
    4 ETW000                                                                              38  0.016963
    4 ETW000  [dev trc     ,00000]  function dbdd_exp_funs loaded from library /usr/sap/SED/SYS/exe/run/dboraslib.so
    4 ETW000                                                                              68  0.017031
    4 ETW000  [dev trc     ,00000]  New connection 0 created                              44  0.017075
    4 ETW000  [dev trc     ,00000]  0: name = R/3, con_id = -000000001 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
    4 ETW000                                                                              46  0.017121
    4 ETW000  [dev trc     ,00000]  db_con_connect (con_name=R/3)                         38  0.017159
    4 ETW000  [dev trc     ,00000]  find_con_by_name found the following connection for reuse:
    4 ETW000                                                                              37  0.017196
    4 ETW000  [dev trc     ,00000]  0: name = R/3, con_id = 000000000 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
    4 ETW000                                                                              39  0.017235
    4 ETW000  [dev trc     ,00000]  Oracle Client Version: '10.2.0.2.0'                  480  0.017715
    4 ETW000  [dev trc     ,00000]  -->oci_initialize (con_hdl=0)                         42  0.017757
    4 ETW000  [dev trc     ,00000]  Client NLS settings: AMERICAN_AMERICA.UTF8          3789  0.021546
    4 ETW000  [dev trc     ,00000]  Logon as OPS$-user to get SAPSR3's password           48  0.021594
    4 ETW000  [dev trc     ,00000]  Connecting as /@SED on connection 0 (nls_hdl 0) ... (dbsl 700 110706)
    4 ETW000                                                                              51  0.021645
    4 ETW000  [dev trc     ,00000]  Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
    4 ETW000                                                                              43  0.021688
    4 ETW000  [dev trc     ,00000]    0 UTF8                                                      1  0x9511ea0  0x951750c  0x9516d94
    4 ETW000                                                                              40  0.021728
    4 ETW000  [dev trc     ,00000]  Allocating service context handle for con_hdl=0       40  0.021768
    4 ETW000  [dev trc     ,00000]  Allocating server context handle                      52  0.021820
    4 ETW000  [dev trc     ,00000]  Attaching to DB Server SED (con_hdl=0,svchp=0x9516d20,svrhp=0x9528504)
    4 ETW000                                                                              88  0.021908
    4 ETW000  [dboci.c     ,00000]  *** ERROR => OCI-call 'OCIServerAttach' failed: rc = 12505
    4 ETW000                                                                            4712  0.026620
    4 ETW000  [dbsloci.    ,00000]  *** ERROR => CONNECT failed with sql error '12505'
    4 ETW000                                                                              49  0.026669
    4 ETW000  [dev trc     ,00000]  Try to connect with default password                  62  0.026731
    4 ETW000  [dev trc     ,00000]  Connecting as SAPSR3/<pwd>@SED on connection 0 (nls_hdl 0) ... (dbsl 700 110706)
    4 ETW000                                                                              39  0.026770
    4 ETW000  [dev trc     ,00000]  Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
    4 ETW000                                                                              56  0.026826
    4 ETW000  [dev trc     ,00000]    0 UTF8                                                      1  0x9511ea0  0x951750c  0x9516d94
    4 ETW000                                                                              47  0.026873
    4 ETW000  [dev trc     ,00000]  server_detach(con_hdl=0,stale=0,svrhp=0x9528504)
    4 ETW000                                                                              37  0.026910
    4 ETW000  [dev trc     ,00000]  Detaching from DB Server (con_hdl=0,svchp=0x9516d20,srvhp=0x9528504)
    4 ETW000                                                                              37  0.026947
    4 ETW000  [dev trc     ,00000]  Deallocating server context handle 0x9528504          45  0.026992
    4 ETW000  [dev trc     ,00000]  Allocating server context handle                      48  0.027040
    4 ETW000  [dev trc     ,00000]  Attaching to DB Server SED (con_hdl=0,svchp=0x9516d20,svrhp=0x9528504)
    4 ETW000                                                                              60  0.027100
    4 ETW000  [dboci.c     ,00000]  *** ERROR => OCI-call 'OCIServerAttach' failed: rc = 12505
    4 ETW000                                                                            1538  0.028638
    4 ETW000  [dbsloci.    ,00000]  *** ERROR => CONNECT failed with sql error '12505'
    4 ETW000                                                                              41  0.028679
    4 ETW000  [dblink      ,00431]  ***LOG BY2=>sql error 12505  performing CON [dblink#3 @ 431]
    4 ETW000                                                                             131  0.028810
    4 ETW000  [dblink      ,00431]  ***LOG BY0=>ORA-12505: TNS:listener does not currently know of SID given in connect descriptor [dblink#3 @ 431]
    4 ETW000                                                                              39  0.028849
    2EETW169 no connect possible: "DBMS = ORACLE                           --- dbs_ora_tnsname = 'SED'"
    thansk for your help
    Edited by: myfriend280985 on Feb 11, 2010 7:53 AM

  • MS-7252 bank interleave requested, not available

    I have the above motherboard K9NGM I recently upgraded the BIOS from 3.1 to the latest distributed via MSI Live update to allow me to install Vista RC1 for testing. Recently I have noticed the following message displayed whilst the system is booting.
    "Bank interleave requested, not available" or something similar as it is the last message on screen before it switches into the O/S boot.
    I have 2 X Giel 512 Mb DDR2 667 Mhz memory modules installed as in the instructions (one in the green socket and one in the orange socket) can anyone suggest a reason for this message, will it slowing my system down ?

    before you flashed your bios does your system stabile? Also try to avoid not to used any of liveupdate utilities especially on bios flashing as it could kill your system without notice and best method to flashed it using the floppy. Maybe you've a bad bios flashing.

  • URGENT :ABAP Database is not available via R3trans

    Checking ADA db Database
    ABAP Database is not available via R3trans
    Starting SAP-Collector Daemon
    11:47:14 13.03.2008 LOG: Effective User Id is root
    This is Saposcol Version COLL 20.95 700 - v2.00, Intel x86 with Linux, 2007/02/16
    Usage: saposcol -l: Start OS Collector
    saposcol -k: Stop OS Collector
    saposcol -d: OS Collector Dialog Mode
    saposcol -s: OS Collector Status
    The OS Collector (PID 17267) is already running .....
    saposcol already running
    Running /usr/sap/DEV/SYS/exe/run/startdb
    Trying to start database ...
    Log file: /home/devadm/startdb.log
    Database already running
    /usr/sap/DEV/SYS/exe/run/startdb completed successfully
    Starting SAP Instance SCS00
    Startup-Log is written to /home/devadm/startsap_SCS00.log
    Instance Service on host sap-devel started
    Instance on host sap-devel started
    Starting SAP Instance DVEBMGS01
    Startup-Log is written to /home/devadm/startsap_DVEBMGS01.log
    Instance Service on host sap-devel started
    Instance on host sap-devel started.
    checked with command r3trans -d-v.
    the following error is displayed.
    This is R3trans version 6.14 (release 700 - 10.09.07 - 09:57:00).
    unicode enabled version
    2EETW169 no connect possible: "maybe someone set invalid values for DIR_LIBRARY ('/usr/sap/DEV/SYS/exe/run') or dbms_type ('ADA')"
    R3trans finished (0012).
    any suggestions
    thnx and regards

    Hi,
    can you please show us the content of the R3trans logfile, created by the R3trans -x command?
    Please note that if you're an official SAP customer you should open a OSS message for your issue, if not already done so. Please read [this thread|MaxDB/liveCache Forum: target audience and relevant support;.
    Additionally, please refrain from using things like 'URGENT'. More on this can be read [here|Welcome and Rules of Engagement;.
    Thanks & regards,
    Roland

  • J2EE database not available via test

    Hi Experts,
    I have installed NW 7.0 portal Ehp2 system on Solaris cluster with logical name  . Now when I try to start SAP with the startsap script . it is not starting the database (Oracle) . It just checks whether DB is running and giving message J2EE database not available via test , and asking to check JdbCon.log .
    This is Bootstrap log
    com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
            at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:384)
            at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:132)
            at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)
            at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:150)
            at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:214)
            at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:46)
            at com.sap.engine.bootstrap.Synchronizer.<init>(Synchronizer.java:76)
            at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:474)
            at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:156)
            at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:946)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:331)
            at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    Caused by: java.sql.SQLException: ORA-01034: ORACLE not available
    ORA-27101: shared memory realm does not exist
    SVR4 Error: 2: No such file or directory
    If I start db manually , then runnig startsap , it runs fine . And also stopsap script , wont stop database .
    I checked listener.ora,tnsnames.ora, user profiles, environment variables, permissions etc , nothing found wrong .
    When I execute startj2eedb as sidadm , it starts db .
    Can you please throw some light on this issue
    Regards,
    Nibu Antony

    Yes, it is all logical hostname .
    For more clarification on the issue
    bash-3.2$ startsap <logical hostname>
    Checking <SID> Database
    J2EE Database is not available via  test
    See logfile /usr/sap/<SID>//JdbcCon.log
    Starting Startup Agent sapstartsrv
    Instance Service on host hostname<SID>p1 started
    Starting SAP Instance SCS00
    Startup-Log is written to /usr/sap/<SID>//startsap_SCS00_hostname<SID>p1.log
    Instance on host hostname<SID>p1 started
    Starting Startup Agent sapstartsrv
    Instance Service on host hostname<SID>p1 started
    Starting SAP Instance JC01
    Startup-Log is written to /usr/sap/<SID>//startsap_JC01_hostname<SID>p1.log
    Instance on host hostname<SID>p1 started
    Starting SAP-Collector Daemon
    12:38:20 13.03.2014     LOG: Using PerfDir (DIR_PERF) = /usr/sap/tmp
    * This is Saposcol Version COLL 21.04 720 - V3.83 64Bit
    * Usage:  saposcol -l: Start OS Collector
    *         saposcol -k: Stop  OS Collector
    *         saposcol -d: OS Collector Dialog Mode
    *         saposcol -s: OS Collector Status
    * Starting collector (create new process)
    saposcol on host hostname<SID>p1 started
    bash-3.2$ sqlplus / as sysdba
    SQL*Plus: Release 11.2.0.3.0 Production on Thu Mar 13 12:38:34 2014
    Copyright (c) 1982, 2011, Oracle.  All rights reserved.
    Connected to an idle instance.
    here is the logs
    JdbcCon.log
    Start: Thu Mar 13 12:36:48 AST 2014
    Error: Couldn't connect to DB
    java.sql.SQLException: ORA-01034: ORACLE not available
    ORA-27101: shared memory realm does not exist
    SVR4 Error: 2: No such file or directory

  • Portal Installation Error: J2EE Database is not available via test

    When starting SAP with startsap I get this error
    Checking EZP Database
    J2EE Database is not available via test
    See logfile JdbcCon.log
    In the JdbcCon.log:
    Start: Fri Nov 20 08:25:28 MST 2009
    Error: Couldn't connect to DB
    java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
    The listener is up & running. I can tsnping to the EZP. The database is up & running
    This is a new portals instance on AIX
    hostname: ezpdb01-lp
    OS: AIX 6.1
    Oracle: 10.2.0.4
    Any advice?

    Hi Bill,
    Your are able to execute command start SAP succefully by using host
    ezpdb01
    I am using the correct hostname...
    listener.ora
    HOST = ezpdb01-lp
    tnsnames.ora
    HOST = ezpdb01-lp
    UNIX - hostname
    ezpdb01-lp
    1)
    ezpdb01-lp:ezpadm 7> startsap ezpdb01-lp
    no start profiles found
    2)
    ezpdb01-lp:ezpadm 7> startsap ezpdb01
    I get the same error in JdbcCon.log
    Start: Tue Dec 01 08:45:53 MST 2009
    Error: Couldn't connect to DB
    java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
    1. Now first step take backup of tnsname.ora & listner.ora
    2. Edit hostname present from ezpdb01-lp to ezpdb01 in both the file.
    3. Now try to start sap with command
    startsap ezpdb01
    , if still error exits then pls paste the contain present in sqlnet.ora.
    Thanks
    Anil

  • J2EE Database is not available via  test

    Hello my friends,
    I've got a problem with my SAP NW/DB2 installation. When i want to start sap, i get the following output:
    si4host:si4adm 13> startsap si4host
    Checking DB6 db Database
    ABAP Database is not available via R3trans
    Checking DB6 db Database
    Error: java.io.FileNotFoundException: JdbcCon.log (Permission denied)
    J2EE Database is not available via  test
    See logfile JdbcCon.log
    Starting SAP-Collector Daemon
    This is Saposcol Version COLL 20.86 640 - V1.12 for Linux
    Usage:  saposcol -l: Start OS Collector
            saposcol -k: Stop  OS Collector
            saposcol -d: OS Collector Dialog Mode
            saposcol -s: OS Collector Status
    The OS Collector (PID 14643) is already running .....
    saposcol already running
    Running /usr/sap/SI4/SYS/exe/run/startdb
    /usr/sap/SI4/SYS/exe/run/startdb completed successfully
    Checking DB6 db Database
    ABAP Database is running
    Starting SAP Instance SCS01
    Startup-Log is written to /home/si4adm/startsap_SCS01.log
    Instance on host itpc1f41009 started
    Starting SAP Instance DVEBMGS00
    Startup-Log is written to /home/si4adm/startsap_DVEBMGS00.log
    Instance on host itpc1f41009 started
    IGS on host itpc1f41009 started
    The server runs on suse 9.3.
    Anybody know how to solve this?
    Greetings
    Chantal

    Hi
    This is a common problem .Actually ur database pwd is not same mentioned in the configtool----
    secure store.
    Change the database password and update the same in the secure store of configtool.
    Restart the engine.Your problem will be solved.If you have any confusion about how to change the pwd in secure store.Feel free to contact

  • Database is not available via R3trans

    Hi,
    We are moving the CI to the different server keeping the database on the same server, it is dual stack BI system, SCS instalaltion went fine, for the CI installation, we got to the error while bringing up the CI , it is not able to connect to the database
    startsap r3
    Checking BXT Database
    Database is not available via R3trans
    Database BXT must be started first
    But
    R3trans -d
    This is R3trans version 6.14 (release 701 - 26.01.09 - 12:46:00).
    unicode enabled version
    R3trans finished (0000).
    The trans.log doesn't give any error
    The listener is up on the database and listening to the port as the R3trans -d went through.
    Please let me know if there is anything can be done, i am banging my head for a week now, I have tried the profile parameters and resetting the db users passwords also.

    Hi,
    Thanks all for replying,
    The Dev logs are not generated as of now, so can't paste them,
    Copied the lastest version of kernel, but it didn't work.
    Put the tnsname and schema profile, dbms\type was already there, But it didn't work too.
    Any other suggestions
    VJ

  • V51 not available via FOTA.

    v51 now available on OVI Suite. But it's not available via FOTA. Is this update available for FOTA?
    Product code is 0578314
    Glad to help
    Solved!
    Go to Solution.

    Availability on FOTA and Ovi Suite /NSU is variable over product codes and is largely dependent on the Regional Nokia Center and/or the Network Carrier.
    So basically the only ones who can answer your question are those with the same carrier and product code.
    Availability on FOTA and Ovi Suite /NSU is variable over product codes and is largely dependent on the Regional Nokia Center and/or the Network Carrier.
    So basically the only ones who can answer your question are those with the same carrier and product code.
    If you find my post helpful please click the green star on the left under the avatar. Thanks.

  • CUP Risk Analysis results are not shown, continues processing request

    We have several users that complain the risk analysis in CUP never finishes. Requests do not contain risks or huge amount of risks which could explain a long runtime.
    With one user we checked, the user is never getting the risk analysis result on his screen. Sitting together with the user shows that the progress bar at bottom of IE is completing analysis, however the screen is not updated to show the risk analysis result and continues to show the processing circle.
    On other pc's CUP risk analysis result is shown as expected, so it must be some issue in local PC Internet Explorer settings.
    Environment used is Windows XP with IE 8. GRC version is 5.3.
    Have any of you experienced the same? And is there a solution available that will resolve this issue, by e.g. correcting settings in IE 8?

    Hello!
    If you want to successfully use GRC 5.3 with IE8, you have two options:
    1) Change a parameter in the server
    2) use the compatibility mode.
    3) Update NW
    refer to [Note 1347768 - Web Dynpro and Microsoft Internet Explorer Version 8.0|https://service.sap.com/sap/support/notes/1347768]
    I dismiss option 2, because it requires to change in every end user computer, so I've been working with option 1 without problems. Bear in mind that NW 7.01 is supported:  [Note 1433940 - Access Control compatibility on Netweaver Java server 7.01|https://service.sap.com/sap/support/notes/1433940]
    Cheers!
    Diego.

  • Error while performing Risk Analysis at user level for a cross system user

    Dear All,
    I am getting the below error, while performing the risk analysis at user level for a cross system (Oracle) user.
    The error is as follows:
    "ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.connector.exceptions.BaseResourceException: Cannot get connection for 120 seconds. Possible reasons: 1) Connections are cached within SystemThread(can be any server service or any code invoked within SystemThread in the SAP J2EE Engine), 2) The pool size of adapter "SAPJ2EDB" is not enough according to the current load of the system or 3) The specified time to wait for connection is not enough according to the pool size and current load of the system. In case 1) the solution is to check for cached connections using the Connector Service list-conns command, in case 2) to increase the size of the pool and in case 3) to increase the time to wait for connection property. In case of application thread, there is an automatic mechanism which detects unclosed connections and unfinished transactions.RC:1
    Can anyone please help.
    Regards,
    Gurugobinda

    Hi..
    Check the note # SAP Note 1121978
    SAP Note 1121978 - Recommended settings to improve peformance risk analysis.
    Check for the following...
    CONFIGTOOL>SERVER>MANAGERS>THREADMANAGER
    ChangeThreadCountStep =50
    InitialThreadCount= 100
    MaxThreadCount =200
    MinThreadCount =50
    Regards
    Gangadhar

  • Full Synch risk analysis job is not running good

    Hi
    Recently we have started user_full_synch_risk_analsysis job is running but with many error..
    I have checked the SLD it is running, JCO also tested good..checked in debugger...tried to look the data..working good..
    but the log saying "can not extract the data from DEV system"
    it is skipping each userid risk analysis saying the above error and it continuing with other userIDs.. Please help
    INFO:  Job ID:18 : Exec Risk Analysis
    Sep 27, 2010 7:51:38 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
    INFO:  Job ID:18 : Analysis starts: XRPM_PM2
    Sep 27, 2010 7:53:04 AM com.virsa.cc.comp.BgJobInvokerView onActionsearchObj
    INFO: Number of users matched:132
    Sep 27, 2010 7:58:30 AM com.virsa.cc.xsys.meng.MatchingEngine matchActRisks
    WARNING:  Error :
    com.virsa.cc.dataextractor.dao.DataExtractorException: Cannot extract data from system (DEV); for more details, refer to ccappcomp.n.log
         at com.virsa.cc.dataextractor.bo.DataExtractorSAP.searchUser(DataExtractorSAP.java:551)
         at com.virsa.cc.dataextractor.bo.DataExtractorSAP.userIsIgnored(DataExtractorSAP.java:529)
         at com.virsa.cc.xsys.meng.MatchingEngine.getObjActions(MatchingEngine.java:682)
         at com.virsa.cc.xsys.meng.MatchingEngine.matchActRisks(MatchingEngine.java:112)
         at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:1104)
         at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:297)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchRiskAnalysis(BatchRiskAnalysis.java:1047)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1331)
         at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:402)
         at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:264)
         at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:240)
         at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:80)
         at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:436)
         at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1225)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
         at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:480)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
         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:299)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Sep 27, 2010 7:58:30 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine riskAnalysis
    WARNING:  Job ID:18 : Failed to run Risk Analysis
    java.lang.Exception: Cannot extract data from system (DEV); for more details, refer to ccappcomp.n.log
         at com.virsa.cc.xsys.meng.MatchingEngine.matchActRisks(MatchingEngine.java:118)
         at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:1104)
         at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:297)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchRiskAnalysis(BatchRiskAnalysis.java:1047)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1331)
         at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:402)
         at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:264)
         at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:240)
         at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:80)
         at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:436)
         at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1225)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
         at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:480)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
         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:299)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Sep 27, 2010 7:58:30 AM com.virsa.cc.xsys.bg.BatchRiskAnalysis performBatchRiskAnalysis
    WARNING: Error: while executing BatchRiskAnalysis for JobId=18 and object(s):XRPM_PM2: Skipping error to continue with next object: Cannot extract data from system (DEV); for more details, refer to ccappcomp.n.log
    Sep 27, 2010 7:58:30 AM com.virsa.cc.xsys.bg.BgJob updateJobHistory
    FINEST: --- @@@@@@@@@@@ Updating the Job History -
    2@@Msg is Error while executing the Job for Object(s) :XRPM_PM2:Cannot extract data from system (DEV); for more details, refer to ccappcomp.n.log
    Sep 27, 2010 7:58:30 AM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
    INFO: -
    Background Job History: job id=18, status=2, message=Error while executing the Job for Object(s) :XRPM_PM2:Cannot extract data from system (DEV); for more details, refer to ccappcomp.n.log
    Sep 27, 2010 7:58:30 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine riskAnalysis

    Dear Harikrishna,
    Please mention what is your Support pack. This is an identified bug for SP12 especially synchronizing the users from the backend and doing the risk analysis at the user level. We had the same problem. But for some reason we are now able to do the synchronization from the backend but the management reports are getting updated.

Maybe you are looking for