Roles issue after patched PCK SP14

I udpated pck from sp9 to sp14, now I want to Assign roles in Security Provider, but function is disabled, How to enable it? I installed successfully last time. but at that time, sap team in my company installed both a ABAP system and java system. they can assign the role using a gui tool without using visual admin. now the system is all java -based. it must use visual admin to assign roles. but how to do it? who help me?
Message was edited by: Spring Tang

it is so easy, but i ignore it:), there is a toolbar button on the upper side, click it to change the state to Midify state

Similar Messages

  • ALV table issue after patching.

    Hi Experts.
    In our applications, there is a button. On click of that button an ALV list will be displayed in the POP-UP.
    First time when we click the button this works fine. After that the ALV list does not get displayed in the POU-UP.
    Every time we have to re login and do the process.
    Note: This is happening only after patching.
    Thanks.

    Hi i have attached the piece of code. This code is written in DOINIT Method of the view in which the ALV is embedded. Everytime the table lt_locations will have the data which needs to be displayed in the ALV. The ALV gets displayed only first time and next time if we click the button, the ALV list is not displayed.
    DATA lo_nd_srlocations TYPE REF TO if_wd_context_node.
    DATA lo_el_srlocations TYPE REF TO if_wd_context_element.
      DATA ls_srlocations    TYPE wd_this->element_srlocations.
      DATA it_srlocations    TYPE wd_this->elements_srlocations.
      DATA lt_srlocations    TYPE STANDARD TABLE OF zxr_locations.
      navigate from <CONTEXT> to <SRLOCATIONS> via lead selection
      lo_nd_srlocations = wd_context->get_child_node( name = wd_this->wdctx_srlocations ).
      get element via lead selection
    lo_el_srlocations = lo_nd_srlocations->get_element(  ).
    SELECT  * FROM zxr_locations INTO TABLE lt_srlocations.
      DATA lo_nd_locations TYPE REF TO if_wd_context_node.
    DATA lo_el_locations TYPE REF TO if_wd_context_element.
    DATA ls_locations TYPE wd_this->element_locations.
        DATA lt_locations TYPE wd_this->elements_locations.
    navigate from <CONTEXT> to <LOCATIONS> via lead selection
      lo_nd_locations = wd_context->get_child_node( name = wd_this->wdctx_locations ).
    get all declared attributes
      lo_nd_locations->get_static_attributes_table(
        IMPORTING
          table = lt_locations ).
    lo_nd_srlocations->bind_table( lt_locations ).
    lo_nd_srlocations->bind_table( lt_srlocations ).
      DATA lo_cmp_usage TYPE REF TO if_wd_component_usage.
      lo_cmp_usage =   wd_this->wd_cpuse_alv_srlocations( ).
      IF lo_cmp_usage->has_active_component( ) IS INITIAL.
        lo_cmp_usage->create_component( ).
      ENDIF.
      DATA lo_interfacecontroller TYPE REF TO iwci_salv_wd_table .
      lo_interfacecontroller =   wd_this->wd_cpifc_alv_srlocations( ).
      DATA lo_value TYPE REF TO cl_salv_wd_config_table.
      lo_value = lo_interfacecontroller->get_model(
    data lr_column_settings type REF TO if_salv_wd_column_settings.
    *data lr_table_settings type ref to if_salv_wd_table_settings.
    lr_column_settings ?= lo_value.
    *lr_table_settings ?= lo_value.
    lr_column_settings->delete_column( 'MANDT' ).

  • CTI OS Toolkit issue after patching CTI OS 7.5.8

    Hi all,
    We are setting up the UCCE 7.5.1, and we have patched the system with ICM 7.5.8 and CTI OS
    7.5.8. We have also patched the agents' PC with CTI OS 7.5.8.
    Our developer has actually customized the CTI OS Toolkit softphone, to intergrate it with
    a 3rd party application. It was running fine before patching the agents' PC with CTI OS
    7.5.8. The customized CTI OS Toolkit could start up after the agents' PCs were patched.
    When I tried to uninstalled CTI OS 7.5.8 from the PCs, then it works fine again. What
    could be the problem here? Are there any additional steps that I need to take note after
    patching CTI OS 7.5.8?
    I also noticed that after running the software patch, the CTI OS Softphone would be
    replaced.
    Appreciate any help and advice on this.
    Thanks & Regards,
    Eric

    The client patches are meant to be applied to the out of the box software. How is the patch supposed to know how to update your custom software? If you are trying to apply the patch onto a customized desktop then you are overwriting or breaking that customization. Your developer needs to apply the new software release to his custom code and provide a patch for you. The previous release remains backwards compatible so there's no rush.

  • Issue after patching after SQL instance with SP3

    Hi All,
    I have recently patched one of 2008 SQL instance in my environment with SP3 and after applying the patch I can see that the version got changed to 10.0.5500, but when checked summary logs I'm seeing below message. Could some one please let me know what are
    the steps to be followed to get this issues fixed.
    I have checked few things from my end and was able to see that uninstalling the sp3 which is applied should fix this and roll it  back to its previous version which was sp2, but what I'm concerned is the missing .msi file. How can i fix this missing
    msi file thing?
    Error Message logged in summary.txt file
    Overall summary:
      Final result:                  The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
      Exit code (Decimal):           -2068709373
      Exit facility code:            1202
      Exit error code:               3
      Exit message:                  The cached patch file "C:\Windows\Installer\6c1c7e81.msp" is missing. The original file for this cached file
    is
    "sql_engine_core_inst.msp", which can be installed from "Service Pack 3 for SQL Server 2008 (KB2546951) (64-bit)", version 10.3.5500.0.  For more information about how
    to resolve this problem, see “Steps to resolve missing media issue with SQL Server 2008” (http://go.microsoft.com/fwlink/?LinkId=144387) in the Microsoft Knowledge
    Base.
      Start time:                    2015-03-21 12:31:47
      End time:                      2015-03-21 12:32:39
      Requested action:              Patch
    Thanks in Advance, Kranthi

    Hi All,
    Got the fix for this issue from the below video which is very much in detail.
    http://blogs.msdn.com/b/sqlserverfaq/archive/2012/05/08/missing-msi-s-msp-s-error-during-sql-server-patching.aspx

  • Digitial Signature issues after patching Acrobat 9.5 to 9.5.1.

    After installing the security patch on Acrobat 9.5 Digital signing is not working correctly.  Users are getting error - Bad Format.  Machine that was not patched works fine with a imported digital signature.  Is there a fix for this problem. 

    While that is a good answer to my question; it is not a good solution to my situation since it is a corporate license that has to be reinstalled by our IT department. That is a very cumbersome process and puts me, as an end-user testing this new product, in a poor situation and effectively shuts down my production for an unspecified time frame when the trial expires.

  • Solaris 10 on Intel DP35DP with E-SATA issue after patching

    My trusty Intel DP35DP, sata controller set to to AHCI, has 5 sata and 1 E-SATA port.
    I've ignored it for a while, meaning haven't patched it. It currently has a Sata rpool
    disk and a second Sata disk for data. While doing some cleanup, I attached an external
    E-SATA 2TB disk, carved off 200G and added another zpool. worked great.
    I was looking forwarded to patching, so setup a new BE, patched it, activated it
    and booted it. Solaris griped that it couldn't find the E-SATA disk. Rolled back to
    the previous BE. tweaked a few things in the new patched env, no go. roll back
    again.
    The kernel patch the E-SATA is working on is 141445-09. pca reports I need
    to apply 142910-17 and 144489-09. When I boot to that environment, I can
    no longer see or enumerate the E-SATA disk?
    Ideas?

    My trusty Intel DP35DP, sata controller set to to AHCI, has 5 sata and 1 E-SATA port.
    I've ignored it for a while, meaning haven't patched it. It currently has a Sata rpool
    disk and a second Sata disk for data. While doing some cleanup, I attached an external
    E-SATA 2TB disk, carved off 200G and added another zpool. worked great.
    I was looking forwarded to patching, so setup a new BE, patched it, activated it
    and booted it. Solaris griped that it couldn't find the E-SATA disk. Rolled back to
    the previous BE. tweaked a few things in the new patched env, no go. roll back
    again.
    The kernel patch the E-SATA is working on is 141445-09. pca reports I need
    to apply 142910-17 and 144489-09. When I boot to that environment, I can
    no longer see or enumerate the E-SATA disk?
    Ideas?

  • All adapter issue after patch XI SP16

    Hi,
    I did patch the following by SDM from SP15 -> SP16
    SAPBASIS16_0
    SAPXIAF16P_2
    SAPXIAFC16P_5
    SAPXICONS16_0
    SAPXIPCK16_0
    SAPXITOOL16P_3
    and when i get to adapter monitoring(http://sapxid:50000/mdt/amtServlet) , i can not see all of adapter only except for JPR.
    and actually adapters are not running
    visual administrator, i can see XI all of Adapters started
    does anyone know?

    Hi,
    just have a look at question 3 (adapters section)
    on the XI FAQ page and this will solve your problem
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

  • Repository connect issue after MDM Patch Upgrade

    MDM Expert
    We recently upgraded our MDM patch from SP06 5.5.63.73 to SP06 5.5.65.91
    after patch upgrade we are not able to connect to repository.SAP is saying that we have wong NLS Character set.It should be 'UTF8' or 'AL32UTF8'
    We checked and found that we do not have character set as per SAP Recommendation but everything was working fine before upgrading the patch.As per SAP in new Patch MDM is lokking for Unicode Character set
    SAP is asking to create new DB Instance for MDM.
    If we create new instance for MDM then how we are going to use our existing repository.Our environment is clustered environment and name of MDM DB instance is also mentioned in cluster.We have to use same Instance name.We are also using oracle failsafe
    Creating new instance seems to be risky for Production environment.Currently we are applying the Patch in Sandbox Environment
    has anyone of you faced this problem while upgrading MDM patch, if yes then how you resolve the issue
    Please help
    Thanks
    Deelip

    Solution provided by sAP

  • Error message while runing the Synch Job in Background job after Patch Upgd

    Friends
    We are 5.3 GRC CC on Windows 2003 and ECC 6.0  BI 7.0
    We just upgraded the patches to 12 for GRC CC and ran the Synch job in background....
    Eveytime we run the Synch job for Usre Roles and profiles or Batch Risk Analysis in Background, job finishes until 99 percent and then gives "Error" Message...
    Heres is the job history..:
    2010-09-26 13:14:25 Started Incremental Batch Risk Analysis 09262010 started :threadid: 0
    2010-09-26 13:18:06 Failed Error while executing the Job for Object(s) :PPORTELLA:[NWMss][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint 'PK__VIRSA_CC_COMPROL__5CE34ED1'. Cannot i... (see log for details)
    2010-09-26 13:18:14 Failed Error while executing the Job for Object(s) :RCHAPMAN:[NWMss][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint 'PK__VIRSA_CC_COMPROL__5CE34ED1'. Cannot in... (see log for details)
    2010-09-26 13:18:02 Failed Error while executing the Job for Object(s) :OJONES:[NWMss][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint 'PK__VIRSA_CC_COMPROL__5CE34ED1'. Cannot inse... (see log for details)
    2010-09-26 13:19:21 Failed Error while executing the Job for Object(s) :YPATEL:[NWMss][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint 'PK__VIRSA_CC_COMPROL__5CE34ED1'. Cannot inse... (see log for details)
    2010-09-26 13:49:42 Failed Error Job not completed
    Did anyone has the same issue after the patch upgrade ?
    Pranav
    The version info for the GRC CC..
    Version: AC-RAR 5.3_12.0
    Build ID: 05140510

    Hi I do get a error while scheduling Background job in RAR 5.3 , Please help me out...........waiting for your reply
    Apr 13, 2012 7:38:59 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    Apr 13, 2012 7:39:00 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    Apr 13, 2012 7:39:01 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    Apr 13, 2012 7:39:02 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    Apr 13, 2012 7:39:03 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    Apr 13, 2012 7:39:04 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:06 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    Apr 13, 2012 7:39:06 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:07 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    Apr 13, 2012 7:39:07 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:08 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    Apr 13, 2012 7:39:08 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:09 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    Apr 13, 2012 7:39:09 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:10 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    Apr 13, 2012 7:39:10 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:11 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    Apr 13, 2012 7:39:11 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:12 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    Apr 13, 2012 7:39:12 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:13 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    Apr 13, 2012 7:39:13 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:14 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    Apr 13, 2012 7:39:15 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:16 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    Apr 13, 2012 7:40:16 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:17 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    Apr 13, 2012 7:40:17 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:18 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    Apr 13, 2012 7:40:18 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:19 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    Apr 13, 2012 7:40:19 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:20 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    Apr 13, 2012 7:40:20 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:21 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    Apr 13, 2012 7:40:21 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:22 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    Apr 13, 2012 7:40:22 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:23 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    Apr 13, 2012 7:40:23 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:24 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    Apr 13, 2012 7:41:24 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:25 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    Apr 13, 2012 7:41:25 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:26 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    Apr 13, 2012 7:41:26 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:27 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    Apr 13, 2012 7:41:27 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:28 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    Apr 13, 2012 7:41:28 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:29 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    Apr 13, 2012 7:41:29 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:30 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    Apr 13, 2012 7:41:30 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:31 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    Apr 13, 2012 7:41:31 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:42:32 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    Apr 13, 2012 7:42:32 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:42:33 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    Apr 13, 2012 7:42:33 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:42:34 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    Apr 13, 2012 7:42:34 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?dae

  • Big Button become Small Button after patching system

    Hello experts,
    we have a produktiv running WD ABAP application, which runs on computers with touchscreens.
    Because of that we developed the applicatin with big buttons (standard Ui element button with a big image) so that our user can hit it with their finger. now after patching our systems the buttons are small again and the big image in the button is cut.
    Does anybody know how we can increase the size of the buttons?
    Regards

    Hi,
    I presume you have upgraded your system from SP<=13 to SP>=14. We have a same problem after we have patched our system.
    There was a problem with the alignment of the images when large images were used. Therefore SAP rectified the same in rendering corrections from SP13 which were available in SP14. As a result of which button size remains small even if you use large image.
    You can not use theme editor to change the button sizes or image sizes. The only option is to raise an SAP ticket. SAP is already working on the issue as I had raised a ticket for the same. Hope to have a  fix very soon. But I suggest you also raise an OSS ticket.
    Regards
    Rohit Chowdhary

  • Authorization issue after the Support packs upgrade

    We're having problem on authorization issue after the SP upgrade.
    One issue if "You are not authorized to call up line item display" using FCH1 and FS10N tcodes.
    And the SU53 showing problem on S_TCODE FAGLL03.
    How are we going to solve this issue? We dont want to add this missing auth object on all our finance roles.
    Thank you in advance.

    How can i send you the trace file? What is your email address?
    If I were you, I won't do that. Did you not ever sign some confidentiality agreement? I wonder.
    Anyhoo... (copy right @ David)
    What are the objects been caught in category RC=4, RC=12?
    Relate them with functional aspect of the transaction (error screen)
    Edited : You can paste RC=4, RC=12 objects here without customer specific value if you want to.
    Regards,
    Arpan Paik
    Edited by: P Arpan on Aug 23, 2011 2:36 PM

  • ARM approval error after upgrading to SP14: Database error while using the secure store.

    Dear GRC experts,
    After upgrading GRC 10 to SP14, assigning manual passwords during the approval of a request, the approval process is failing.
    Here is the scenario; your advice will be appreciated.
    Task: Manually assign passwords to multiple systems contained in the request
    Where: On the access request, go to “User System Details” tab
    Issue: After approving/submitting the request, the error “Database error while using the secure store” is generated
    Logs: Nothing on transactions SLG1 or ST22; however ST11 shows the error attached below:
    This is the failed approval of the request:
    Other scenarios executed as a workaround, and passed the password assignment this time:
    The approval will work if only one password is assigned to any of the given systems. The rest of the systems get an auto-generated
    password.
    ARM also accepts multiple passwords when the requestor assigns passwords on the “User System Details” prior submitting a
    request. The GRC admin can approve once reached for system approval.
    AS FYI, “Confirm Password” is only required when creating the request but not on any other stage.
    System information:
      -Netweaver 7
      -GRCFND_A SP14
      -GRCPINW SP13
    Regards,
    Gustavo

    SAP just delivered a note to fix this issue. The number is 2022294.

  • Issues after Upgrade from Oracle 10.1.0.5 to 10.2.0.5 in Windows Server2003

    Good Morning Good People,
    I have run in to some issues after upgrading my 10.1.0.5 database to 10.2.0.5. Initially after the firtst upgrade from 10.1.0.5 to 10.2.0.0 one has to run Critical Patch set 4 to get to 10.2.0.5. Well after initial up grade everything worked fine. I could connect to the database from within the server as well as remotely through SQL*PLUS client. However, after completeing the patch I'm still able to connect to the database from within the server, but remotely i get the following error:
    ORA-12514 : TNS Listener does not currently know of service requested in connect descriptor.
    I also get Error ORA-12505: TNS:listener does not currently know of SID given in connect descriptor The Connection descriptor used by the client was: (description=(address=(host=mcquery2)(protocol=tcp)(port=1521))(connect_data=(sid=mcquery)(server=dedicated)))
    I've tried serval different things to trouble shoot the issue but nothing seems to work.
    If anyone has run into s similar issue please help. This is ruining my weekend! LOL!
    Edited by: user10835577 on Aug 29, 2010 9:15 AM

    From the client or the server?
    SERVER:
    tnsnames.ora:
    MCQUERY=
    (DESCRIPTION=
    (ADDRESS=
    (PROTOCOL=TCP)
    (HOST=10.36.27.184)
    (PORT=1521)
    (CONNECT_DATA=
    (SERVICE_NAME=MCQUERY)
    listener.ora
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = D:\oracle\product\10.1.0\Db_1)
    (PROGRAM = extproc)
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 10.36.27.184)(PORT = 1521))
    FROM REMOTE SQLPLUS Client:
    tnsnames.ora
    MCQUERY=
    (DESCRIPTION=
    (ADDRESS=
    (PROTOCOL=TCP)
    (HOST=10.36.27.184)
    (PORT=1521)
    (CONNECT_DATA=
    (SERVICE_NAME=MCQUERY)
    listener.ora
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = D:\oracle\product\10.1.0\Client_3)
    (PROGRAM = extproc)
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = cotsdot370.cotsdot.dom)(PORT = 1521))
    (ADDRESS = (PROTOCOL = TCP)(HOST = 10.36.27.184)(PORT = 1521))
    Thanks,
    Malcolm
    Edited by: user10835577 on Aug 29, 2010 12:01 PM

  • Startup after patching (9654983) ORA-32004

    I patched a nearly identical system before this one with no issues however after patching this one
    on attempting to startup I get :
    ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance.
    ORA-24324: service handle not initialized
    ORA-24323: value not allowed
    ORA-01092: ORACLE instance terminated. Disconnection forced.
    What gives?
    Thanks for any and all help in advance,
    Brian

    ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance.
    ORA-24324: service handle not initialized
    ORA-24323: value not allowed
    ORA-01092: ORACLE instance terminated. Disconnection forced.
    What gives? Check the alert.log to identify the obsolete parameter and remove it.
    OR
    Check V$OBSOLETE_PARAMETER to see the matching on and remove it.
    Then,startup the database.
    -Anantha

  • Performance Issues after an Upgrade

    Hello!
    We are experiencing performance issues after we upgraded to a new version of Hyperion (11.1.2.1). At this point, I am not too sure about the actual causes for this degrade in performance but I am trying to narrow down the causes and need your inputs. Please help me with your ideas.
    1) What could be the causes/factors for the performance to degrade after an upgrade?
    2) Does the performance of a script depend on the user credentials i.e. who is launching the script? Whether it’s the super admin of the application/application owner or an application specific admin?
    3) Does the performance of the scripts depend on the place you are launching it from? For example - will the performance differ if it’s launched from MaxL Vs EAS?
    Please let me know your thoughts on this.
    Thanks,
    - Krrish

    There are a number of bugs 12600557, 12675485, 12669814, 12698488 logged in for 11.1.2.1 - If you use Internet Explorer 8 and have data forms designed to use a large number of sparse dimension members in rows or columns, you may experience performance degradation when opening the data forms.
    This has been fixed in Oracle Hyperion Planning, Fusion Edition Release 11.1.2.1 Patch Set Update (PSU): 11.1.2.1.101 which is available on My Oracle Support as Patch 12666861.
    HTH-
    Jasmine.

Maybe you are looking for

  • Device Manager coming up with a lot of issues. (Base System Device, etc.)

    Hi Everyone, Just got a new prebuilt/custom gaming rig and I'm coming up with some issues in my Device Manager. The tower came all set up with Win8 but I decided to wipe/reinstall the OS on a new 120g SSD that I bought. I installed a fresh win8 x64 w

  • Linux Download Page appears broken.

    Hi. I've been attempting to download Skype for Linux. I can get to the download page with no problem. I'm presented with a list of Linux distributions, from a pop down list. This is as far as things go.  No download commences, and there is no downloa

  • Skype suspended my account indefinitely for making...

    Skype name: (redacted to protect privac) Was told that my credits are expiring and when I tried to login to re-activate them, I couldn't. Tried several times and even contacting their email support but to no avail. Tried to reset my password, that fa

  • Ordered processing required from Oracle 11g on Linux to BizTalk Server

    Need a viable solution enabling ordered processing (OP) of messages from Oracle 11g on Linux allowing for ordered delivery to subscribers in BizTalk over MSMQ. We are currently running BizTalk 2010 (with Adapter Pack 2010) and are using ordered deliv

  • Rotate Dynamic text and make dynamic text go vertical

    Hello I am working on a visual customizer flash app in actionscript 2.0. Looking for good tutorials or examples of how to rotate dynamic text as well as how to make it vertical. Currently all the dynamic embedded text changes colors and size. Any hel