SAP GUI 7.20 PL5 - Does NOT start

Hi there,
I just installed PL5 for SAP GUI for Windows 7.20. I hoped this would fix the problem with the centralized saplogontree.xml as said in several notes.
But after I installed the patch, the GUI doesnt start anymore. The screen with the version number and the two people appears and after a few seconds disappears. The GUI doesnt start and I cant connect to our systems. There is no process running the GUI. I tried to reboot too, no success.
Any ideas? Possibly a bug?!
Anyone else having problems with the patch?

After I corrected the adress for the saplogon.ini in the saplogontree.xml file on the webserver the GUI starts up normally. My fault was that I typed in the absolute path "http:://domain.tld/saplogon.ini" instead of just "domain.tld/saplogon.ini". The XML-file then linked to http://http://domain.tld/saplogon.ini
After I corrected the entry, the GUI starts normal.
Regards,
Jann

Similar Messages

  • Upgrade SM 7.0 to EhP1 - Windows service SAP SID _ inst.no does not start

    Hi gurus,
    I have to upgrade our Solution manager 7.0 (Windows 2003 32-bit, NW 7.0 SP15, Kernel SP185, non-unicode) to the latest SP of EhP1. I downloaded the upgrade and update guides and followed them.
    1. Updated to SPAM 700 SP38.
    2. Stopped the server and updated the Kernel to 32-bit non-unicode 7.01 SP69.
    3. I tried to start the services SAPOSCOL and SAP<SID>_00 and both did not started sayin the application is broken and needs reinstall.
    4. I downgraded to Kernel 23-bit non-unicode 7.01 SP55 and tried again - the service SAPOSCOL started but the service SAP<SID>_00 did not.
    5. I downgraded  to Kernel 23-bit non-unicode 7.01 SP15 and tried again - the same as with SP55.
    6. I restored the original Kernel and the server started normally.
    The update guide says I first should update SPAM and the Kernel and after that run SAINT to import the EhP1 components selected in MOPZ.
    I found a suggestion to run SAINT import before the Kernel upgrade - should I do it?
    How can I resolve the problem?
    Thanks everyone!
    Petar

    Thank you Paul!
    I finally found [another thread|How to Upgrade kernel 7.0 to 7.01; with similar problem solved by SAP note 684106. It solved my problem too.
    I will try to continue update from the current state but will have in mind if something goes wrong your advice. I will write later for the results.
    Regards,
    Petar

  • SAP GUI Scripting Wizzard Windows7 does not work

    Dear Experts,
    I am quite a novice when it comes to SAP GUI scripting (let alone any other development), therefore my question might be rather stupid. After my PC was migrated from XP to Windows 7 it is no longer possible to use the SAP GUI scripting wizzard. When you select it from the menue, simply nothing happens.
    Does anyone have an idea what I need to do to have this useful tool back on my PC?
    We are running SAP GUi 7.1
    Thanks for your help
    Theo

      Here is SAP GUI wizard replacement tool...its in auto IT - enjoy
    http://www.autoitscript.com/forum/topic/149540-sapwizardudf/
    I had the tech guys here install ,  the latest GUI patch level 15,
    and the script development tools not working issue has been fixed
    They (SAP?) removed the 'script development tools' menu option!?
    I have not installed the MS hotfix, but
    My question is,  it true the 'Script development tools' is gone?
    Other methods
    a) This (free) non SAP solution seems to work however...any other ideas?
    Scripting Tracker Lite
    http://scn.sap.com/docs/DOC-32728
    b) The Activate GuiXT tool in SAP GUI also does give you some clues in the element window
    and could be an alternative way , to get control names.
    eg a radio button is R[P_CONTROL_ID] when it should be radP_CONTROL_ID
    c) The SAP script recording and playback ,  to a vbs script will give you the control names also, if you edit the script.
    You must of course have GUI scripting on in rz11
    I can't read this note https://service.sap.com/sap/support/notes/1633639 - need a password!

  • NSP (SAP NW2004s ABAP AS 7.00 SP8) does not start anymore

    Hi all,
    I installed SAP NW2004s ABAP Trial Version SP8 and was able to work
    with it. Since today I get a timeout error when starting the Application Server.
    I tried to start the MaxDB instance with the SAP MMC but I do not know
    the user and/or password for the MaxDB User (I did not change the
    "Standard-User" provided during installation; unfortunately I do not remeber
    the credentials)
    Any ideas:
    - why the application server does not start anymore ?
    - what the credentials of the SAP DB Administrator are ?
    Thank you in advance for your help,
    Axel

    Hi Axel,
    this is a 90 day trial, though maybe you're already used it three month?
    the database used to run under control, control (usr, password), btu that changes from time to time....
    Regards,
    Benny

  • SAP MMC does not start and red in color

    Hi Gurus,
    We are in a process of installing EhP4 and there were lots of errors. We reverted back to old version.
    After moving back to old state i.e., EhP3, system does not start.
    1. SAPosCol does not start acutomatically in the service
    2. sapmmc does not show database details
    3. When I try to start the server through SAPMMC, all esmart03 0, esmart03 1 turns to red.
    Please let me know how i can fix this problem.
    I want to post screen shot, but i am not sure how i can post the same here.
    Thanks in advance.
    Regards
    Shreeshail

    Thanks Sunny for your reply.
    We had taken system system backup (complete "E" drive) where SAP server is installed. I had to stop EhP4 process as we got a requirement to bringup NWBC.
    We restored the "E" drive content and then restarted the SAP server.
    After that servies did not start and MMC does not show up Database details.
    Do i need to create services and MMC to fix the issues??
    Thanks in advance.
    Regards
    Shreeshail

  • SAP does not start-gives error message

    This error has just started.
    When I click the SAP icon, it does not start and it gives the error message
    E - SAP - SAP Business One - SAP Business One
    The color palette file couldn't be properly loaded
    Thanks

    Hi.
    Have You installed something recently on that machine?
    Regards.

  • SAP Does not start after backup complition

    Dear All,
    Since last two times when we put Offline whole database + Redolog
    backup, after complition of backup SAP Does not start.
    I have tried to start SAP Manually, but didn't start.
    To start SAP we have to restart the SERVER.
    Attached please find backup log.
    Thanks and Regards,
    Nirav

    Thanks you all for quick response.
    Backup log is pasted at end of message. Wile you please guide me where dev_disp log is located.
    I am taking backup through DB13.
    When I got this problem. Database was not started. But at O/S level SMON is running. Shutdown normal or transactional was not working. I have to shutdown abort. and start the database.
    SAP services are also running at O/S level.
    I have doubt about work process.
    Thanks
    Nirav
    BR0051I BRBACKUP 7.00 (24)
    BR0055I Start of database backup: beamxrbx.aft 2009-05-06 04.00.05
    BR0484I BRBACKUP log file: /oracle/PRD/sapbackup/beamxrbx.aft
    BR0477I Oracle pfile /oracle/PRD/102_64/dbs/initPRD.ora created from spfile /oracle/PRD/102_64/dbs/spfilePRD.ora
    BR0083W Compression rates out of date - run BRBACKUP with option '-k only'
    BR0101I Parameters
    Name                           Value
    oracle_sid                     PRD
    oracle_home                    /oracle/PRD/102_64
    oracle_profile                 /oracle/PRD/102_64/dbs/initPRD.ora
    sapdata_home                   /oracle/PRD
    sap_profile                    /oracle/PRD/102_64/dbs/initPRD.sap
    backup_mode                    ALL
    backup_type                    offline_force
    backup_dev_type                tape
    compress                       hardware
    tape_copy_cmd                  dd
    cpio_flags                     -ovB
    cpio_in_flags                  -iuvB
    dd_flags                       obs=64k bs=64k
    dd_in_flags                    ibs=64k bs=64k
    rewind                         mt -f $ rew
    rewind_offline                 mt -f $ offl
    tape_size                      102400.000 MB
    tape_address                   /dev/rmt/0mn
    tape_address_rew               /dev/rmt/0m
    volume_backup                  PRDB01,PRDB02,PRDB03,PRDB04,PRDB05,PRDB06,PRDB07,PRDB08,PRDB09,PRDB10,
                                   PRDB11,PRDB12,PRDB13,PRDB14,PRDB15,PRDB16,PRDB17,PRDB18,PRDB19,PRDB20,
                                   PRDB21,PRDB22,PRDB23,PRDB24,PRDB25,PRDB26,PRDB27,PRDB28,PRDB29,PRDB30
    expir_period                   29
    tape_use_count                 100
    exec_parallel                  0
    system_info                    prdadm/oraprd rlsdbi HP-UX B.11.31 U ia64
    oracle_info                    PRD 10.2.0.2.0 8192 7547 46814166 rlsdbi UTF8 UTF8
    sap_info                       700 SAPSR3 0002LK0003PRD0011Q21439814270013NetWeaver_ORA
    make_info                      hpia64 OCI_102 Apr 21 2007
    command_line                   brbackup -u / -jid ALGOF20090506040000 -c force -t offline_force -m all -p initPRD.sap -a -c force -p initPRD.sap -sd
    BR0116I ARCHIVE LOG LIST before backup for database instance PRD
    Parameter                      Value
    Database log mode              Archive Mode
    Automatic archival             Enabled
    Archive destination            /oracle/PRD/oraarch/PRDarch
    Archive format                 %t_%s_%r.dbf
    Oldest online log sequence     7544
    Next log sequence to archive   7547
    Current log sequence           7547             SCN: 46814166
    Database block size            8192             Thread: 1
    Current system change number   46815598         ResetId: 674927195
    BR0118I Tablespaces and data files
    Tablespace     TS-Status  F-Status  File                                                       Size   Id.     Device  Link    Type       MaxSize     IncrSize  BlkSize
    PSAPSR3        ONLINE*    ONLINE+   /oracle/PRD/sapdata1/sr3_1/sr3.data1                 2097160192    4  1073872902  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/PRD/sapdata1/sr3_2/sr3.data2                 2097160192    5  1073872902  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/PRD/sapdata1/sr3_3/sr3.data3                 2097160192    6  1073872902  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/PRD/sapdata1/sr3_4/sr3.data4                 2097160192    7  1073872902  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/PRD/sapdata1/sr3_5/sr3.data5                 2097160192    8  1073872902  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/PRD/sapdata2/sr3_10/sr3.data10               2097160192   13  1073872903  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/PRD/sapdata2/sr3_6/sr3.data6                 2097160192    9  1073872903  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/PRD/sapdata2/sr3_7/sr3.data7                 2097160192   10  1073872903  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/PRD/sapdata2/sr3_8/sr3.data8                 2097160192   11  1073872903  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/PRD/sapdata2/sr3_9/sr3.data9                 2097160192   12  1073872903  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/PRD/sapdata3/sr3_11/sr3.data11               2097160192   14  1073872904  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/PRD/sapdata3/sr3_12/sr3.data12               2097160192   15  1073872904  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/PRD/sapdata3/sr3_13/sr3.data13               2097160192  
    BR0143I Backup type: offline_force
    BR0113I Files will be compressed by hardware
    BR0130I Backup device type: tape
    BR0102I Following backup device will be used: /dev/rmt/0mn
    BR0103I Following backup volume will be used: PRDB25
    BR0289I BRARCHIVE will be started at the end of processing
    BR0134I Unattended mode with 'force' active - no operator confirmation allowed
    BR0208I Volume with name PRDB25 required in device /dev/rmt/0mn
    BR0280I BRBACKUP time stamp: 2009-05-06 04.00.07
    BR0226I Rewinding tape volume in device /dev/rmt/0m ...
    BR0351I Restoring /oracle/PRD/sapbackup/.tape.hdr0
    BR0355I from /dev/rmt/0mn ...
    BR0241I Checking label on volume in device /dev/rmt/0mn
    BR0242I Scratch volume in device /dev/rmt/0mn will be renamed to PRDB25
    BR0280I BRBACKUP time stamp: 2009-05-06 04.00.08
    BR0226I Rewinding tape volume in device /dev/rmt/0m ...
    BR0202I Saving /oracle/PRD/sapdata2/sr3700_7/sr3700.data7
    BR0203I to /dev/rmt/0mn ...
    #FILE..... /oracle/PRD/sapdata2/sr3700_7/sr3700.data7
    #SAVED.... sr3700.data7  PRDB25/43
    BR0280I BRBACKUP time stamp: 2009-05-06 04.20.17
    BR0063I 40 of 62 files processed - 82240.312 MB of 120066.277 MB done
    BR0204I Percentage done: 68.50%, estimated end time: 4:29
    BR0001I **********************************________________
    BR0202I Saving /oracle/PRD/sapdata2/sr3700_8/sr3700.data8
    BR0203I to /dev/rmt/0mn ...
    #FILE..... /oracle/PRD/sapdata2/sr3700_8/sr3700.data8
    #SAVED.... sr3700.data8  PRDB25/44
    BR0280I BRBACKUP time stamp: 2009-05-06 04.20.42
    BR0063I 41 of 62 files processed - 84640.320 MB of 120066.277 MB done
    BR0204I Percentage done: 70.49%, estimated end time: 4:29
    BR0001I ***********************************_______________
    BR0202I Saving /oracle/PRD/sapdata3/sr3700_10/sr3700.data10
    BR0203I to /dev/rmt/0mn ...
    #FILE..... /oracle/PRD/sapdata3/sr3700_10/sr3700.data10
    #SAVED.... sr3700.data10  PRDB25/45
    #FILE..... /oracle/PRD/sapdata1/system_1/system01.dat
    #SAVED.... system01.dat  PRDB25/60
    BR0280I BRBACKUP time stamp: 2009-05-06 04.27.07
    BR0063I 57 of 62 files processed - 119850.445 MB of 120066.277 MB done
    BR0204I Percentage done: 99.82%, estimated end time: 4:27
    BR0001I **************************************************
    BR0202I Saving /oracle/PRD/origlogA/log_g11m1.dbf
    BR0203I to /dev/rmt/0mn ...
    #FILE..... /oracle/PRD/origlogA/log_g11m1.dbf
    #SAVED.... log_g11m1.dbf  PRDB25/61
    BR0280I BRBACKUP time stamp: 2009-05-06 04.27.14
    BR0063I 58 of 62 files processed - 119900.446 MB of 120066.277 MB done
    BR0204I Percentage done: 99.86%, estimated end time: 4:27
    BR0001I **************************************************
    BR0202I Saving /oracle/PRD/origlogB/log_g12m1.dbf
    BR0203I to /dev/rmt/0mn ...
    #FILE..... /oracle/PRD/origlogB/log_g12m1.dbf
    #SAVED.... log_g12m1.dbf  PRDB25/62
    BR0280I BRBACKUP time stamp: 2009-05-06 04.27.22
    BR0063I 59 of 62 files processed - 119950.447 MB of 120066.277 MB done
    BR0204I Percentage done: 99.90%, estimated end time: 4:27
    BR0001I **************************************************
    BR0202I Saving /oracle/PRD/origlogA/log_g13m1.dbf
    BR0203I to /dev/rmt/0mn ...
    #FILE..... /oracle/PRD/origlogA/log_g13m1.dbf
    #SAVED.... log_g13m1.dbf  PRDB25/63
    BR0280I BRBACKUP time stamp: 2009-05-06 04.27.29
    BR0063I 60 of 62 files processed - 120000.448 MB of 120066.277 MB done
    BR0204I Percentage done: 99.95%, estimated end time: 4:27
    BR0001I **************************************************
    BR0202I Saving /oracle/PRD/origlogB/log_g14m1.dbf
    BR0203I to /dev/rmt/0mn ...
    #FILE..... /oracle/PRD/origlogB/log_g14m1.dbf
    #SAVED.... log_g14m1.dbf  PRDB25/64
    BR0280I BRBACKUP time stamp: 2009-05-06 04.27.36
    BR0063I 61 of 62 files processed - 120050.449 MB of 120066.277 MB done
    BR0204I Percentage done: 99.99%, estimated end time: 4:27
    BR0001I **************************************************
    BR0202I Saving /oracle/PRD/origlogA/cntrl/cntlrPRD.dbf
    BR0203I to /dev/rmt/0mn ...
    #FILE..... /oracle/PRD/origlogA/cntrl/cntlrPRD.dbf
    #SAVED.... cntlrPRD.dbf  PRDB25/65
    BR0280I BRBACKUP time stamp: 2009-05-06 04.27.42
    BR0063I 62 of 62 files processed - 120066.277 MB of 120066.277 MB done
    BR0204I Percentage done: 100.00%, estimated end time: 4:27
    BR0001I **************************************************
    BR0280I BRBACKUP time stamp: 2009-05-06 04.27.44
    BR0304I Starting and opening database instance PRD ...
    BR0280I BRBACKUP time stamp: 2009-05-06 04.28.10
    BR0305I Start and open of database instance PRD successful
    BR0117I ARCHIVE LOG LIST after backup for database instance PRD
    Parameter                      Value
    Database log mode              Archive Mode
    Automatic archival             Enabled
    Archive destination            /oracle/PRD/oraarch/PRDarch
    Archive format                 %t_%s_%r.dbf
    Oldest online log sequence     7544
    Next log sequence to archive   7547
    Current log sequence           7547             SCN: 46814166
    Database block size            8192             Thread: 1
    Current system change number   46815880         ResetId: 674927195
    BR0056I End of database backup: beamxrbx.aft 2009-05-06 04.28.11
    BR0280I BRBACKUP time stamp: 2009-05-06 04.28.13
    BR0053I BRBACKUP completed successfully with warnings
    BR0280I BRBACKUP time stamp: 2009-05-06 04.28.13
    BR0291I BRARCHIVE (action ID aeamxrbx) will be started with options '+beamxrbx.aft,42106018475,PRDB25,62 -jid ALGOF20090506040000 -d tape -c force -p initPRD.sap -sd'
    BR0280I BRBACKUP time stamp: 2009-05-06 04.31.42
    BR0292I Execution of BRARCHIVE (action ID aeamxrbx) finished with return code 0

  • ASMCA GUI does not start

    asmca gui does not start with the fresh 11gr2 installation on AIX 6.1. The ASM instance is up. I don't see any error messages in the asm alert logs. The display is set correctly and xclock works.
    Where else to check? I need to create the new disk group before i can create the database.
    export ORACLE_HOME=<GRID_HOME>
    export ORACLE_SID=+ASM1
    asmca
    is what i tried.

    Hi,
    Set all the environment variables for Oracle and try to run ASMCA again.
    ORACLE_BASE=/u01/app/oracle; export ORACLE_BASE
    ORACLE_HOME=/u01/app/11.2.0/grid_crs; export ORACLE_HOME
    ORACLE_TERM=xterm; export ORACLE_TERM
    PATH=$ORACLE_HOME/bin:$PATH; export PATH
    LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib; export LD_LIBRARY_PATH
    CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib; export CLASSPATH
    Regards,
    Levi Pereira

  • Server Does not start after backup complition

    Dear All,
    We are facing following problem some times after backup completion.
    Our Setup is : SAP ECC 6, Oracle 10g, HP-UX 11.31.
    We are scheduling the whole database offline + archive log backup during night.
    After completion of backup the SAP does not start. I have checked the following things.
    1. Database is started : OK.
    2. SAP related services at O/S level : OK
    3. Listener is OK
    4. No startup log generated related to SAP
    But I am not able to connect to SAP thru SAP GUI.
    If I tried to start SAP using startsap it will not respond for long time. Even I have tried to startsap after shutting down database, kill all SAP related services at O/S level. But startsap doesn't respond.
    When I restart the server, after that I am able to start SAP.
    Is there any memory fragmentation related problem ?
    Before some time same thing is happened with our production server, but at that time I have deleted Archivelog files manually before tacking backup. In this case if I take backup "whole database offline + archive log " then server doesn't start. At that time also I have to restart the server. So the Problem is identified.
    But in this case i.e on our Quality Server not able to trace out problem.
    Thanks in Advance,
    Nirav

    Hi,
    Yes the problem is related to memory. I think during the backup  memory is allocated but not release after completion of database backup.
    in case of archive log backup what option your are using means are you using save and delete option  or other.
    In the case of the production server archive log backup you to use to the option  save and delete.
    Please also check wheather core file getting gernerated should be deleted frquently from work folder.
    Thanks & Regards,
    Vidyadhar K

  • Message bean does not start automatically during application server startup

    I have a message bean that does not start up during application server startup. I am able to successfully start the application manually using the visual admin tool.I searched the logs and found the following error. The error references the "QueueConnectionFactory" is not deployed or is not started. I have check and the "QueueConnectiopnFactory" is deployed. Is this a problem with the application trying to start before the "QueueConnectionFactory"? Is thier a way to define a dependency on my application not to start until the "QueueConnectionFactory" has been started, if so can how would I define this dependency. Please provide and example.
    Thanks,
    Bill
    #1.5 #001CC4695AD8001A000000100000079C00045DB6C93D4DAD#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Connecting Model Repository ...#
    #1.5 #001CC4695AD8001A000000110000079C00045DB6C93D4E1D#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Checking source path: halliburton.com/hal~usrgrpap#
    #1.5 #001CC4695AD8001A000000120000079C00045DB6C93D4EAC#1228939548538#System.err##System.err#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Error##Plain###[RunTask] The source file/path doesn't exist: halliburton.com/hal~usrgrpap#
    #1.5 #001CC4695AD8001A000000130000079C00045DB6C93D4EF5#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Opening connection to MMR ...#
    #1.5 #001CC4695AD8001A000000140000079C00045DB6C93D69D0#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Start local transaction ...#
    #1.5 #001CC4695AD8001A000000150000079C00045DB6C93D6B5A#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Commit ...#
    #1.5 #001CC4695AD8001A000000160000079C00045DB6C93D6C8B#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Running task 'com.sap.ip.mmr.db.tasks.TaskUndeployFromDB' ...#
    #1.5 #001CC4695AD8001A000000170000079C00045DB6C93D8E6C#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Close connection to Model Repository ...#
    #1.5 #001CC4695AD8001A000000180000079C00045DB6C93D8EE5#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###done.#
    #1.5 #001CC4695AD80018000000000000171400045DBBE9BCCED0#1228961568691#com.sap.engine.services.connector##com.sap.engine.services.connector######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error##Plain###ResourceObjectFactory.getObjectInstance(), Error: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    #1.5 #001CC4695AD80018000000010000171400045DBBE9BCE3CD#1228961568691#com.sap.engine.services.jndi##com.sap.engine.services.jndi######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Warning#1#/System/Audit#Java###Exception #1#com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    ... 24 more
    #1.5 #001CC4695AD80018000000030000171400045DBBE9BDBF4A#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#deploy_5029##Exception in operation startApp with application halliburton.com/halusrgrpap.#2#startApp#halliburton.com/halusrgrpap#
    #1.5 #001CC4695AD80018000000040000171400045DBBE9BDC46C#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation startApp with application halliburton.com/hal~usrgrpap.
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:394)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:367)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    ... 12 more
    Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    ... 16 more
    Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    ... 19 more
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    ... 20 more
    Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    ... 24 more
    #1.5 #001CC4695AD80018000000060000171400045DBBE9BE0AF5#1228961568769#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Plain###
    Operation startApp over application halliburton.com/hal~usrgrpap finished with errors on server 105677750. For more detailed information see traces of Deploy Service.#
    #1.5 #001CC4695AD80018000000080000171400045DBBE9BE27D1#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#ejb_2119##Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.#1#com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP#
    #1.5 #001CC4695AD80018000000090000171400045DBBE9BE2842#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    ... 16 more
    Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    ... 19 more
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    ... 20 more
    Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    ... 24 more
    #1.5 #001CC4695AD80019000000000000171400045DBBEB38B908#1228961593581#com.sap.jpe.engine.impl.common.AnalyzerModel#sap.com/com.sapportals.supportplatform#com.sap.jpe.engine.impl.common.AnalyzerModel#Administrator#67####43c8e9d0c72911ddcedd001cc4695ad8#SAPEngine_Application_Thread[impl:3]_38##0#0#Error##Plain###Exception while loading class: com.sapportals.supportplatform.plugins.portal.connectors.ConnectorGatewayServiceCheck
    java.lang.NoClassDefFoundError: com/sapportals/portal/prt/resource/ResourceException
                    at java.lang.Class.getDeclaredConstructors0(Native Method)
                    at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
                    at java.lang.Class.getConstructor0(Class.java:1930)
                    at java.lang.Class.newInstance0(Class.java:278)
                    at java.lang.Class.newInstance(Class.java:261)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadClass(PluginCollector.java:881)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:387)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:274)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadPluginsFromJarFile(PluginCollector.java:169)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadFromExtDirectory(PluginCollector.java:121)
                    at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:411)
                    at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:399)
                    at com.sapportals.supportplatform.SupportPlatform.init(SupportPlatform.java:81)
                    at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:59)
                    at java.security.AccessController.doPrivileged(Native Method)
                    at javax.security.auth.Subject.doAs(Subject.java:379)
                    at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:141)
                    at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
                    at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
                    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)

    I though the same thing, but XE LISTENER is running on localhost and port 1522. On the other hand XE have local_listener explicitly set to the very same connection descriptor. Even XE installation was second on this server.
    I've could change that yes, but the startup script doesn't seemed to have this mind.
    Regards,
    Sve

  • My jcontrol does not start

    Hi,
    When i logged into Visutal Administrator, It asked me to change the password. I had Changed the administrator password there and the same updated in the secure store as follows:
    1. Start the Config Tool by executing the /usr/sap/<SID>/<Instance name>/j2ee/configtool/configtool script file.
    2. Select secure store.
    3. Select the admin/password/<SID> entry.
    4. Enter the J2EE Engine administrator user new password in the Value field and choose Add.
    5. Choose File -> Apply to save the data.
    6. Restart the J2EE Engine
    but after this, my server is not starting and jcontrol does not start.
    find the log file of jcontrol:
    [Thr 3124] Mon Oct 12 15:29:44 2009
    [Thr 3124] *** ERROR => invalid return code of process [bootstrap] (exitcode = 66) [jstartxx.c   1642]
    [Thr 3124] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc = 66)
    [Thr 3124] JControlCloseProgram: started (exitcode = 66)
    [Thr 3124] JControlCloseProgram: good bye... (exitcode = 66)
    If i opens my config tool and it shows only secure store, gives an error message as
    Error occured while working with the configurations(scanning)
    MSg: Error while connecting to DB
    My login to SAP<SID>DB is getting failed.... (am using SQLSERVER DB)
    could anyone help me in solving this issue
    Regards
    Sunil Chiluveru

    hi
    Please also see this log file jvm_bootstrap
    Bootstrap MODE:
    <INSTANCE GLOBALS>
    determined by parameter [ID0124325].
    Exception occurred:
    com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!
         at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:476)
         at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:146)
         at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:971)
         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:324)
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    ==[ Caused by: ]==----
    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:364)
         at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:129)
         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:149)
         at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)
         at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)
         at com.sap.engine.bootstrap.Synchronizer.<init>(Synchronizer.java:74)
         at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:473)
         at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:146)
         at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:971)
         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:324)
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    Caused by: java.sql.SQLException: [SAP_NWmss][SQLServer JDBC Driver][SQLServer]Login failed for user 'SAPNSPDB'.
         at com.sap.nwmss.jdbc.base.BaseExceptions.createException(Unknown Source)
         at com.sap.nwmss.jdbc.base.BaseExceptions.getException(Unknown Source)
         at com.sap.nwmss.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
         at com.sap.nwmss.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
         at com.sap.nwmss.jdbc.sqlserver.tds.TDSLoginRequest.processReplyToken(Unknown Source)
         at com.sap.nwmss.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
         at com.sap.nwmss.jdbc.sqlserver.tds.TDSLoginRequest.submitRequest(Unknown Source)
         at com.sap.nwmss.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
         at com.sap.nwmss.jdbc.base.BaseConnection.connect(Unknown Source)
         at com.sap.nwmss.jdbc.base.BaseConnection.setupImplConnection(Unknown Source)
         at com.sap.nwmss.jdbc.base.BaseConnection.open(Unknown Source)
         at com.sap.nwmss.jdbc.base.BaseDriver.connect(Unknown Source)
         at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:608)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285)
         at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:306)
         ... 14 more
    [Bootstrap module]> Problem occurred while performing synchronization.

  • JControl.exe does not start...Database Initialisation Problem...MS SQL

    Hi,
    I was wondering if anyone has any idea on why JCONTROL.exe does not start. I am currently installing NW04s EP7. The DB is on another host and te SCS and CI are on a different host. I am going throught the installation when I get the following error fro the Bootstrap file.
    I have already done the following steps:
    1. entered the SAP<SID>DB password
    2. SQL is started and running on the second host.
    3. The bootstrap.propeties files look the same as any other file EP system on our network
    [Mar 7, 2007 5:32:35 PM  ] [Bootstrap module]> Problem occurred while performing synchronization.
    [Mar 7, 2007 5:35:45 PM  ] -
    [Mar 7, 2007 5:35:45 PM  ] Bootstrap MODE:
    [Mar 7, 2007 5:35:45 PM  ] <INSTANCE GLOBALS>
    [Mar 7, 2007 5:35:45 PM  ]  determined by parameter [ID0117060].
    [Mar 7, 2007 5:35:45 PM  ] -
    [Mar 7, 2007 5:35:46 PM  ] Exception occurred:
    com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!
         at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:422)
         at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
         at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:814)
         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:324)
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    ==[ Caused by: ]==----
    com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred: Secure Store lib Dir does not exist
    PC04315\sapmnt\ET1\SYS\global\security\lib\tools
         at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:212)
         at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)
         at com.sap.engine.bootstrap.Synchronizer.<init>(Synchronizer.java:60)
         at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:419)
         at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
         at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:814)
         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:324)
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    [Mar 7, 2007 5:35:46 PM  ] [Bootstrap module]> Problem occurred while performing synchronization.
    Many thanks,
    Adil Zafar

    ==[ Caused by: ]==----
    com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred: Secure Store lib Dir does not exist
    PC04315\sapmnt\ET1\SYS\global\security\lib\tools
    Do you have strong encryption on your current system?

  • MII UDS does not start automatically on server reset

    Hi,
    MII UDS does not start automatically on server reset, although it was set as automatically start.
    What could be the reason of this problem?
    Thanks.

    Hi,
    Is the runtime mode is set to service?
    Have you referred this document?
    [Programatically Starting and Stopping an SAP xMII UDS Executable Instance|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b0f460c3-7f92-2910-02af-b608f92977c3]
    Regards,
    Musarrat
    Edited by: Musarrat Husain on Jul 6, 2011 8:27 PM

  • J2EE 5 sneak preview:Server does not start

    Hi,
    I need some help since after installation of the sneak preview 5 I could not start the server.
    The db and the central instance are running but not the server.
    1)I get always time out error"StartWait
    FAIL: process jstart.exe J2EE Server not running
    The WAS is installed on a USB2 hard disk.
    2)Furtheremore I cannot operate on the SAP management Console since I get Authorization error.
    I installed the was with windows user IT/paceg
    which is by Domain IT accessible even if I am not in the Domain.
    Anyone can help me,please?
    thanks
    Bye,
    Giamma
    ===================================================
    ============== Starting System JP1 ================
    ===================================================
    =============== Starting database instance ...
    Servizio richiesto già avviato.
    Ulteriori informazioni sono disponibili digitando NET HELPMSG 2182.
    The MaxDB Database Starter, Version 7.6.00.33
    Copyright 2000-2006 by SAP AG
    OK
    ============== Starting central services instance ...
    09.10.2006 12:37:21
    Start
    OK
    09.10.2006 12:37:21
    StartWait
    OK
    ============== Starting java instance ...
    09.10.2006 12:37:21
    Start
    OK
    09.10.2006 12:38:36
    StartWait
    FAIL: process jstart.exe J2EE Server not running
    ============== Start operation timed out !
    Premere un tasto per continuare . . .

    Just for update:
    The error means that the message server is not able to translate the IP address into the hostname (reverse name lookup). If this fails the Startup Framework cannot connect to the message server and the server does not start. Please check the network setup on this host.
    Replay:
    thanks to all.
    all is done:Just insert my loopback ip 10.10.0.10 in file host resolving on my host name romnb120.
    Regards Galin

  • J2EE Engine does not start

    Hi All.
    I installed a Dialog instance.
    After the installation of the license key on the central instance, the dialog J2EE Engine does not start anymore.
    Here it is the std_server0.out log:
    stdout/stderr redirect
    node name   : server0
    pid         : 1298548
    system name : PRP
    system nr.  : 10
    started at  : Mon Sep  3 19:07:54 2007
    [Thr  1] Mon Sep  3 19:07:55 2007
    [Thr  1] MtxInit: -2 0 0
    JVMST080: verbosegc is enabled
    JVMST082: -verbose:gc output will be written to stderr
    ^MSAP J2EE Engine Version 7.00   PatchLevel is starting...
    ^M
    Loading: LogManager ... 1887 ms.
    Loading: PoolManager ... 3 ms.
    Loading: ApplicationThreadManager ... 452 ms.
    Loading: ThreadManager ... 428 ms.
    Loading: IpVerificationManager ... 16 ms.
    Loading: ClassLoaderManager ... 16 ms.
    Loading: ClusterManager ... 392 ms.
    Loading: LockingManager ... 140 ms.
    Loading: ConfigurationManager ... 4656 ms.
    Loading: LicensingManager ... 28 ms.
    Loading: CacheManager ... 311 ms.
    Loading: ServiceManager ...
    <AF[1]: Allocation Failure. need 536 bytes, 0 ms since last AF>
    <AF[1]: managing allocation failure, action=0 (959472304/1073740288)>
      <GC(1): GC cycle started Mon Sep  3 19:08:13 2007
      <GC(1): freed 64170704 bytes, 95% free (1023643008/1073740288), in 136 ms>
      <GC(1): mark: 123 ms, sweep: 13 ms, compact: 0 ms>
      <GC(1): refs: soft 0 (age >= 32), weak 0, final 475, phantom 0>
    <AF[1]: completed in 159 ms>
    Loading services.:
      Service cross started. (72 ms).
      Service file started. (156 ms).
      Service memory started. (160 ms).
      Service userstore started. (24 ms).
      Service timeout started. (51 ms).
      Service runtimeinfo started. (8 ms).
      Service trex.service started. (90 ms).
      Service jmx_notification started. (77 ms).
      Service p4 started. (182 ms).
      Service classpath_resolver started. (99 ms).
      Service deploy started. (9491 ms).
      Service MigrationService started. (28 ms).
      Service bimmrdeployer started. (6 ms).
      Service log_configurator started. (21621 ms).
      Service locking started. (3 ms).
      Service http started. (772 ms).
      Service naming started. (1518 ms).
      Service failover started. (23 ms).
      Service appclient started. (29 ms).
      Service javamail started. (87 ms).
      Service ts started. (70 ms).
      Service jmsconnector started. (80 ms).
      Service licensing started. (10 ms).
      Service iiop started. (141 ms).
      Service connector started. (119 ms).
      Service configuration started. (31 ms).
      Service webservices started. (463 ms).
      Service dbpool started. (8765 ms).
    Sep 3, 2007 6:08:47 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_54] Fatal: Initialization of UME
    persistence adapter "PRIVATE_DATASOURCE" failed.
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME i
    nitialization failed.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization f
    ailed.
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:379)
            at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
            at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
            at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
            at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
            at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
            at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: null
            ume.db.connection_pool_type=SAP/BC_UME
            ume.db.connection_pool.j2ee.xatransactions_used=false
            ume.db.connection_pool.j2ee.is_unicode=FALSE
            ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
            at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.init(DataBasePersistence.java:865)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:363)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
            at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:222)
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:286)
            ... 6 more
    com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME i
    nitialization failed.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization f
    ailed.
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:379)
            at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
            at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
            at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
            at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
            at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
            at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: null
            ume.db.connection_pool_type=SAP/BC_UME
            ume.db.connection_pool.j2ee.xatransactions_used=false
            ume.db.connection_pool.j2ee.is_unicode=FALSE
            ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
            at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.init(DataBasePersistence.java:865)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:363)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
            at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:222)
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:286)
            ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Sep 3, 2007 6:08:47 PM              com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_54] Fatal: Critical shutdown was
    invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Anyone can help?
    Thanks,
    Marco

    Hi all,
    after some corrections, now the problem is changed.
    Here you can find the std_server0.out:
    <b>com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME i
    nitialization failed.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization f
    ailed.
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:379)
            at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
            at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
            at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
            at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
            at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
            at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Connect to SAP gateway failed
    Connect_PM  TYPE=A ASHOST=SAPPRP-DB SYSNR=10 GWHOST=SAPPRP-DB GWSERV=sapgw10 PCS=1
    LOCATION    CPIC (TCP/IP) on local host with Unicode
    ERROR       partner 'SAPPRP-DB:sapgw10' not reached
    TIME        Fri Sep  7 15:01:11 2007
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -10
    MODULE      nixxi.cpp
    LINE        2764
    DETAIL      NiPConnect2
    SYSTEM CALL connect
    ERRNO       79
    ERRNO TEXT  A remote host refused an attempted connect operation.
    COUNTER     1
            at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
            at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:363)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
            at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:222)
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:286)
            ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Sep 7, 2007 2:01:11 PM              com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_55] Fatal: Critical shutdown was
    invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.</b>
    Thanks all,
    Marco

Maybe you are looking for