Stuck in Start Up Window

Hi Everyone.
Last night I had to force shut down my computer by holding the power button because it got frozen. But when I tried to reboot, I got stuck in the start up menu with the apple icon and the spinning wheel. I tried to SafeBoot it, but I couldn't even get a loading bar to appear. I tried restarting holding option + command + p + r (I forget what this does, but I read somewhere to try it). I heard the two chimes, but nothing changed, still stuck on the start up page. This morning, was the same. I left it running for a while and eventually the apple icon even disappeared and was replaced by a 0 with a slash through it.
I have a Macbook Pro Running Mountain Lion
Any suggestions?
Thanks!

Gray screen issue, run through this list of fixes,
..Step by Step to fix your Mac
if you don't have a backup of your data off the machine, then see if holding Shift Key upon boot will get you in to do that.
By #8 you should be fixed, and third party programs not working, make sure you have the lastest version and compatible with your OS X version before installing it.

Similar Messages

  • Stuck at "starting login window" and Disk Utility won't fix it...

    I downloaded some security updates, and since restarting my computer as required, I have never been able to start it up since. It gets stuck on the "starting login window" screen, with the little blue bar still shimmering and mouse still moving, but just won't ever load the login screen, even after hours.
    I've seen a few other people have had this problem, and tried to follow some of the recommendations, with no joy. I tried several times to repair the disk permissions with Disk Utility, but it has an internal error saying it lost the connection to the disk manager, or something similar.... when I try to repair the disk, it fails saying something about "overlapped extent allocations" and an "invalid node structure".
    I can start up in single-user mode, and doing a fsck had the same result.
    What can I do??? Some people suggested an Archive and Install manoeuvre, but I'm scared of losing all my files! Will it erase them all? Do I have to back up all my files before doing this? How can I back them up if my computer won't start?
    I know almost nothing about computers - all I know I have found in the past few days searching through these discussion boards trying to find an answer! I have an important essay due on Monday which is stuck in my computer, so I'm a little scared!
    I'm using Mac OS X Panther or something.... not sure how to find out exactly which one, as my computer won't start!
    Any help would be greatly appreciated!
    iBook G4    

    Hi, you have some serious directory damage there, and it was probably there before the updates. An Archive and Install would not be recommended. If you did that you would likely have more problems then you have right now.
    If it were me I'd run Diskwarrior and Tech Tool Pro on it. DW for the invalid node structure and Tech Tool Pro for the Overlapped Extent Allocation. But you probably would have to buy both of them, and there's no guarantee either one will fix it.
    Apple doc.#25770, talking about Overlap..... says the easiest way to fix it is to Erase and Install. If you are running 10.3.9 and had access to a retail Tiger disk, you could try booting up on it and running Disk Utility. Tigers DU has the ability to fix Overlap.... sometimes, Panther's does'nt.
    This is the best way to Erase and Install. First backup all your important stuff, if you can, as the following will erase everything on your drive; it will be unrecoverable. Put your install disk in your Mac and Restart while holding down the C key. In Tiger, When you get to the install screen, don't click install and go to the title bar at the top of the screen and click on Utilities (in earlier OS's click on the installer menu).
    Click on Disk Utility and choose the hard drive you want your OS on. Then click on the Erase tab. In Tiger, click on the Security Options button near the bottom (it's similiar for Panther and Jaguar).
    Once in there choose Zero Out Data (write zero's in earlier versions). This will map out any bad blocks on your drive and bring it back to almost new condition (providing there's nothing wrong mechanically with it, bad bearings, defective or damaged surface, etc.).
    Once this is done, go back to the install screen and begin the "Erase and Install" installation. This will put a factory fresh system on a clean hard drive.
    Cheers!
    DALE

  • Cannot install Windows 7 Pro; gets stuck on "Starting Windows" screen

    I have read dozens of posts on this topic but none has helped yet.
    My system has Windows 8 with UEFI. I want to install Windows 7 Pro on another partition. I have turned off Secure Boot in the UEFI/BIOS. When I try to install Windows 7 Pro from a DVD it shows "windows is loading files" and then gets stuck on "Starting Windows"
    for ever. This happens even when no USB peripherals are attached.
    I have already wasted many days on this. I hope someone can help.
    Thanks!

    Hi friends of the internet
    I have been reading several forums regarding the issue of installing windows 7 (64 bit) to a computer that have had windows 8 installed previously or just a GPT formatted disk.
    My Case:
    Windows version installed: Windows 7 Professional N with Service Pack 1 (x64) or Windows 7 Professional (x64)
    Computer used: Samsung laptop
    Model Code: NP53U4C-A02SE
    See the specks here:
    http://www.samsung.com/dk/consumer/computer-peripherals/notebook/notebook/NP535U4C-A02SE-spec
    Create a USB install disk that not freezes at ”starting windows” screen:
    First I followed this great guide (Thanks Daniel):
    http://
    hodgin.ca/2012/10/02/creating-a-uefibios-windows-7-usb-and-installing-to-gpt-partitions/
    STOP AFTER STEP 13!
    1. Open a command line in administrator mode
    2. run DISKPART
    3. type LIST DISK
    4. Look for the disk number that represents your USB drive
    5. type SELECT DISK # where # represents the number of your USB drive. Get this right or you will wipe a different drive out.
    6. type CLEAN
    7. type CREATE PARTITION PRIMARY
    8. type SELECT PARTITION 1
    9. type ACTIVE
    10. type FORMAT fs=fat32 quick
    11. type assign
    12. The drive should now be formatted and marked as active and fat32. Do not format the drive as NTFS or you will only be able to boot into the installer in BIOS mode.
    13. Now you will need to copy the contents of the windows 7 install dvd to the USB with a regular copy paste from windows explorer.
    Here comes a very weird hack... I do not know why it works, but I think it is all about flash drive data structure. I did these steps on a win 7 prof. computer.
    (Let’s assume it’s drive E:)
    Make a copy of your e:\efi\microsoft folder to e.g. your desktop.
    Delete the e:\efi folder
    Copy the \efi folder from a windows 8 installation disk (I used Windows 8 (x64) Professional) to the e:\efi folder. Sorry I cannot provide this for you.
    Here comes the weird part. Then delete e:\efi\microsoft you just copied from the win 8 installation disk.
    Copy the \microsoft folder form the desktop to e:\efi\microsoft
    Resume the guide from step 18.:
    http://
    hodgin.ca/2012/10/02/creating-a-uefibios-windows-7-usb-and-installing-to-gpt-partitions/
    18. Insert the USB in the machine and turn it on and boot into the UEFI/BIOS loader and check for boot options. On the ASUS Zenbook it detected two boot options on the USB drive. One was UEFI and one was regular BIOS. I made the
    UEFI option the first choice and restarted the machine.
    My bios setup was:
    Secure Boot = Disable
    OS Mode Selection = CSM and UEFI OS
    Boot Device Priority = I made the UEFI option the first choice and restarted the machine.
    The installation should start normal.
    E.g. See this guide:
    www.sevenforums.com/tutorials/186875-uefi-unified-extensible-firmware-interface-install-windows-7-a.html
    What I did was:
    Select custom installation (Advanced).
    Click Drive options (Advanced).
    Delete all partitions (this might not be needed). When I did not delete all partitions I was asked every time after the install, during start up by the windows boot manager to select ether win 8 or win 7.
    Click new (DO NOT make Changes in the size of the disk), apply, see NOTE!
    Edit the Primary partition as you want it e.g. divide it to more partitions.
    Select the one you will install windows on and do a normal install.
    I do not make changes in the Bios after install. The Boot priority is automatic set to “Windows boot manager”. If I change the boot mode back to OS Mode Selection = UEFI OS, the computer will freeze at the “starting windows” screen again.
    All this worked for me, good luck. There might be more to it, but this is a start.
    By the way, the start up time for a MBT install was 37 s. And for the GPT it was 49 s.
    Remember if we stand on each other’s shoulders we will reach higher
    J.
    NOTE: Here the installation program should create three partitions automatically!
    Partition 1 - System - The EFI System partition that contains the NTLDR, HAL, Boot.txt, and other files that are needed to boot the system, such as drivers.
    Partition 2 - MSR - The Microsoft Reserved (MSR) partition that reserves space on each disk drive for subsequent use by operating system software.
    Partition 3 - Primary - Where Windows is to be installed to.
    If this isn’t the cast you are not installing in UEIF mode. To check for this (thanks again Daniel):
    If you need to find out if you have booted into BIOS mode or UEFI mode when the installer starts you can press SHIFT+F10 when the welcome installer shows up to open a cmd prompt. from here you will likely be at X:\Sources. Type cd .. to
    go back a dir and move into \Windows\Panther\
    Then type notepad setupact.log
    Within this file do a ctrl+f and search for
        Callback_BootEnvironmentDetect: Detected boot environment:
    It should either say BIOS or UEFI.
    To check if your disk is in the GPT format.
    Open the command prompt.
    Type: DISKPART
    Type: List Disk
    See for the star (*) in the GPT column

  • HP m8430f stuck on "Starting Windows" after April 10, 2012 Microsoft Updates

    HP m8430f stuck on "Starting Windows" after April 10, 2012 Microsoft Updates.  Upgraded to Windows 7 X64 from Vista X64 almost two years ago.  Have never had any problems until morning of April 12th.  I will cut to the final resolution to help anyone else who is going through this or will in the future.  After trying to repair Win7, restoring back to factory recovery (got code purple), installing clean Vista 64 and trying upgrade to Windows 7 again, formatting drive using /p:2 option of writing 0's twice to whole drive and then doing a clean install of Win7 only to get to the same place of being stuck at "Starting Windows", I tried a trick I had read about.  Boot to safe mode, you will get an error that you can complete install from safe mode. Don't close window but hit Shift-F10 and a cmd prompt will open.  Type in compmgmtlauncher and choose Device Manager.  Disable the Visx PureTV-U 48B0 under Sound, Video and Game controllers.  Reboot computer and Win7 complete installation.  Since I was able to get into Safe mode back on April 12th, I should have tried disabling everything then, but since it was working without problems before the updates, I couldn't believe that it was any of the devices.  I have not been able to get around this issue with the tv-tuner, but I don't have a need for it right now for it.  I saw a tip to try moving it to another pci slot and I will try that if I ever have a need to open the computer.  Just wanted to document what to do to save others weeks of searching.  If this is a driver issue, I can't believe HP or Windows hasn't come up with a more current driver.  During all of the installs, I never get a yellow triangle for that device or any indication in Event log or anywhere that there was a problem with this device.

    I had a similar issue with mine not working properly running Windows 7 Ultimate.   Mine was working just fine for quite some time and then I moved my system into our TV room and hooked it up to the television, and used it there.   Everything worked fine, I then returned it to the normal location but did not plug the IR sensor back in.
    I had issues with it, I then plugged it back in and it seemed to be working fine, then started to freeze while we were working on it, it would do this all the time.  I was thinking I had virus, I tried restoring windows to a previous working state.  Upgrading my Virus software and everything.   This was all back in October 2011.  I finally just thought my system was going out after a number of years. 
    Then the other day for some reason I moved the IR sensor from one plug to the other.  It is currently plugged into the bottom right USB port next to the RJ45 port.   It seems to be working just fine now and I don't have the device you suggested disabled, though I will keep that in mind.
    Thanks for you post, Hope mine helps too.

  • Stuck at "Starting Windows" after Deployment

    Hello. I recently updated my MDT to 2013 as well as added the Windows assessment and deployment kit for Windows 8.1. Since then, I have one particular .wim image that I can't seem to deploy using MDT. It continuously gets stuck at "Starting Windows"
    after it's first reboot from the deployment window. I have enabled logging and see this error appear quite often, but I'm not sure if that helps. I can provide the logs if needed.
    Any help would be greatly appreciated!!
    <![LOG[Error executing web service http://(SERVERNAME):9800/MDTMonitorEvent/PostEvent?uniqueID=&computerName=LENOVOT530&messageID=41017&severity=1&stepName=&currentStep=0&totalSteps=0&id=B1CAF581-522F-11CB-863C-9D12A921BFEC,3C:97:0E:7F:F3:3C&message=LTI initiating task sequence-requested reboot.&dartIP=&dartPort=&dartTicket=&vmHost=&vmName=: The operation timed out"

    Turns out it was something in the BIOS causing the issue. This linked helped me out.
    http://social.technet.microsoft.com/Forums/windows/en-US/c0b9719c-657d-4366-b922-409561bb16c6/window-7-hang-up-at-starting-windows-screen-while-installing-with-uefi-mode?forum=w7itproinstall

  • Satellite C655-S5082 stuck at starting windows

    Satellite C655-S5082 stuck at starting windows. I started system restore back to out of box stated. Everything went smooth untill about the third resart an now it stuck at the starting windows screen. tried a repair from disk ith no luck there.

    Turns out it was something in the BIOS causing the issue. This linked helped me out.
    http://social.technet.microsoft.com/Forums/windows/en-US/c0b9719c-657d-4366-b922-409561bb16c6/window-7-hang-up-at-starting-windows-screen-while-installing-with-uefi-mode?forum=w7itproinstall

  • Lync 2013 Desktop does not start on WIndows 8.1

    My Office 365 version of Lync 2013 64bit crashes every time I start it.  There is no error message just the "Microsoft Lync has stopped working" message with Close option.  In further looking for a solution, I found the suggestion to
    uninstall the Intel Bluetooth drivers but my system uses Realtek Filter drivers.  I have looked  in the event logs and found:
    Log Name:      Application
    Source:        Windows Error Reporting
    Date:          2014-09-11 1:47:20 PM
    Event ID:      1001
    Task Category: None
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      --------Win8
    Description:
    Fault bucket 85949488684, type 4
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0
    Problem signature:
    P1: lync.exe
    P2: 15.0.4641.1000
    P3: 53c5ce3c
    P4: KERNELBASE.dll
    P5: 6.3.9600.17055
    P6: 532954fb
    P7: e06d7363
    P8: 0000000000005bf8
    P9:
    P10:
    Attached files:
    C:\Users\Yves\AppData\Local\Temp\WERCA6B.tmp.WERInternalMetadata.xml
    These files may be available here:
    C:\Users\Yves\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_lync.exe_1f7a49ef615ca788e016ddaf8db0d1fb92c4a8e9_00000000_256fdc4d
    Analysis symbol:
    Rechecking for solution: 0
    Report Id: aa908032-39db-11e4-8280-48d224dc5142
    Report Status: 0
    Hashed bucket: 61000269e077a9a343a6fe9bbb7efc54
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Windows Error Reporting" />
        <EventID Qualifiers="0">1001</EventID>
        <Level>4</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-09-11T17:47:20.000000000Z" />
        <EventRecordID>143379</EventRecordID>
        <Channel>Application</Channel>
        <Computer>Fedmet-YL-Win8</Computer>
        <Security />
      </System>
      <EventData>
        <Data>85949488684</Data>
        <Data>4</Data>
        <Data>APPCRASH</Data>
        <Data>Not available</Data>
        <Data>0</Data>
        <Data>lync.exe</Data>
        <Data>15.0.4641.1000</Data>
        <Data>53c5ce3c</Data>
        <Data>KERNELBASE.dll</Data>
        <Data>6.3.9600.17055</Data>
        <Data>532954fb</Data>
        <Data>e06d7363</Data>
        <Data>0000000000005bf8</Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
    C:\Users\Yves\AppData\Local\Temp\WERCA6B.tmp.WERInternalMetadata.xml</Data>
        <Data>C:\Users\Yves\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_lync.exe_1f7a49ef615ca788e016ddaf8db0d1fb92c4a8e9_00000000_256fdc4d</Data>
        <Data>
        </Data>
        <Data>0</Data>
        <Data>aa908032-39db-11e4-8280-48d224dc5142</Data>
        <Data>0</Data>
        <Data>61000269e077a9a343a6fe9bbb7efc54</Data>
      </EventData>
    </Event>
    A lot of sites suggest to uninstall Intel Bluetooth drive but I does not have Intel Bluetooth.

    Go to your computer manufacturer’s website and update all driver packages for your computer, especially:
    Audio drivers
    Bluetooth drivers
    System chipset drivers
    webcam drivers
    Important Note:
    If you use office 64 bit, Lync 2013 must be 64 bit also. {And vice versa, If you use office 32 bit, Lync 2013 must be 32 bit}
    Also check answer of Eric to fix this issue
    http://social.technet.microsoft.com/Forums/en-US/e8268935-e97c-4033-9a2e-02734b4390bf/lync-2013-client-on-windows-81-stuck-at-starting?forum=ocsclients
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
    Mai Ali | My blog: Technical | Twitter:
    Mai Ali

  • If you've changed your startup options on mac to start in windows, how do you fix and go back to mac on startup?

    if you've changed your startup options on mac to start in windows, how do you fix and go back to mac. I can't get my mac to switch back to mac, it is like stuck in widows mode, I have tried holding down the options key upon start up and that did not fix it either.
    Please help! Thank you so much!

    The Apple drivers you install in Windows also puts a Startup Drive icon in the Task Bar. Choose that to change the startup disk back OS X.

  • Java Server0 stuck in starting apps state

    Dear All,
    My J2EE server was up and running, since last 2 days the Java stack [ more importantly the Server0 process] is down (showing yellow in the MMC), the SDM is running, the JAVA dispatcher is running , but the Server0 process is stuck in starting apps phase. I checked the Oracle tablespaces and found that Oracle SAPSR3DB was only 1%, so we increased the same.
    When we restarted the ABAP+JAVA stack we again found that our Java Server0 process is yellow phase , our SDM is running, the JAVA dispatcher is running , but the Server0 process starts and then moves to starting framework phase and then gets stuck in the starting apps phase.
    My ABAP part is running fine.
    On Checking the developer trace for this server 0 process , it says that JLaunchISetState is changing the state from starting application [2] to starting applications [10] where is gets stuck.Have also gone through the latest log files in the J2ee/cluster/server0/log, but could not find any error .
    I have tried waiting for long durations, but this has not resolved the issue.The RAM size is 3.5 GB and virtual memory is 12 GB.doesnt reveal any error.Also tried to increase the instance heap size via the config tool [ current value is 1024 , tried changing the value to 2048 , restarted cluster , but same issue again , so reverted back to old value].The OS is windows 2003 server , DB-Oracle 10g.This is a NW2004s stack on which PI 7.0 has been activated.
    Have also checked and found all J2EE users i.e. j2ee_admin, J2ee_guest, sapjsf, and all PI related super users unlocked.
    Also all DB schema users were found to be unlocked. Also tried increasing the number of threads in the thread manager in config tool.
    Also tried increasing the enque/table_space value to 4 times of RAM, but no change in problem.
    Checked values of VM parameters, everything seems to be fine.
    Please find the Dev_server0 trace file below :-
    trc file: "E:\usr\sap\PI7\DVEBMGS00\work\dev_server0", trc level: 1, release: "700"
    node name   : ID9240450
    pid         : 5796
    system name : PI7
    system nr.  : 00
    started at  : Tue Dec 16 11:29:55 2008
    arguments       :
           arg[00] : E:\usr\sap\PI7\DVEBMGS00\exe\jlaunch.exe
           arg[01] : pf=E:\usr\sap\PI7\SYS\profile\PI7_DVEBMGS00_hcl3SAP
           arg[02] : -DSAPINFO=PI7_00_server
           arg[03] : pf=E:\usr\sap\PI7\SYS\profile\PI7_DVEBMGS00_hcl3SAP
           arg[04] : -DSAPSTART=1
           arg[05] : -DCONNECT_PORT=2168
           arg[06] : -DSAPSYSTEM=00
           arg[07] : -DSAPSYSTEMNAME=PI7
           arg[08] : -DSAPMYNAME=hcl3SAP_PI7_00
           arg[09] : -DSAPPROFILE=E:\usr\sap\PI7\SYS\profile\PI7_DVEBMGS00_hcl3SAP
           arg[10] : -DFRFC_FALLBACK=ON
           arg[11] : -DFRFC_FALLBACK_HOST=localhost
    [Thr 5792] Tue Dec 16 11:29:55 2008
    [Thr 5792] *** WARNING => INFO: Unknown property [instance.box.number=PI7DVEBMGS00hcl3sap] [jstartxx.c   841]
    [Thr 5792] *** WARNING => INFO: Unknown property [instance.en.host=hcl3SAP] [jstartxx.c   841]
    [Thr 5792] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c   841]
    [Thr 5792] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c   841]
    JStartupReadInstanceProperties: read instance properties [E:\usr\sap\PI7\DVEBMGS00\j2ee\cluster\instance.properties]
    -> ms host    : hcl3SAP
    -> ms port    : 3901
    -> OS libs    : E:\usr\sap\PI7\DVEBMGS00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : E:\usr\sap\PI7\DVEBMGS00\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : hcl3SAP
    -> ms port    : 3901
    -> os libs    : E:\usr\sap\PI7\DVEBMGS00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : E:\usr\sap\PI7\DVEBMGS00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID9240400  : E:\usr\sap\PI7\DVEBMGS00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID9240450  : E:\usr\sap\PI7\DVEBMGS00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID9240400            : E:\usr\sap\PI7\DVEBMGS00\j2ee\cluster\instance.properties
    -> [01] ID9240450            : E:\usr\sap\PI7\DVEBMGS00\j2ee\cluster\instance.properties
    [Thr 5792] Tue Dec 16 11:29:56 2008
    [Thr 5792] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 5792] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 5772] WaitSyncSemThread: Thread 5772 started as semaphore monitor thread.
    [Thr 5784] JLaunchRequestFunc: Thread 5784 started as listener thread for np messages.
    [Thr 5792] NiInit3: NI already initialized; param 'maxHandles' ignored (1;10002)
    [Thr 5792] CPIC (version=700.2006.09.13)
    [Thr 5792] [Node: server0] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_09
    [Thr 5792] JStartupICheckFrameworkPackage: can't find framework package E:\usr\sap\PI7\DVEBMGS00\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID9240450]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : C:\j2sdk1.4.2_09
    -> java parameters    : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
    -> java vm version    : 1.4.2_09-b05
    -> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : x86
    -> heap size          : 1024M
    -> init heap size     : 1024M
    -> root path          : E:\usr\sap\PI7\DVEBMGS00\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : E:\usr\sap\PI7\DVEBMGS00\j2ee\os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : E:\usr\sap\PI7\DVEBMGS00\exe\jstartup.jar;E:\usr\sap\PI7\DVEBMGS00\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50021
    -> shutdown timeout   : 120000
    [Thr 5792] JLaunchISetDebugMode: set debug mode [no]
    [Thr 5720] JLaunchIStartFunc: Thread 5720 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 262144 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djava.security.policy=./java.policy
    -> arg[  4]: -Djava.security.egd=file:/dev/urandom
    -> arg[  5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[  6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[  7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[  8]: -Djco.jarm=1
    -> arg[  9]: -XX:MaxPermSize=256M
    -> arg[ 10]: -XX:PermSize=256M
    -> arg[ 11]: -XX:NewSize=171M
    -> arg[ 12]: -XX:MaxNewSize=171M
    -> arg[ 13]: -XX:+DisableExplicitGC
    -> arg[ 14]: -verbose:gc
    -> arg[ 15]: -Xloggc:GC.log
    -> arg[ 16]: -XX:+PrintGCDetails
    -> arg[ 17]: -XX:+PrintGCTimeStamps
    -> arg[ 18]: -Djava.awt.headless=true
    -> arg[ 19]: -Dsun.io.useCanonCaches=false
    -> arg[ 20]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 21]: -XX:SurvivorRatio=2
    -> arg[ 22]: -XX:TargetSurvivorRatio=90
    -> arg[ 23]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
    -> arg[ 24]: -Dsys.global.dir=E:\usr\sap\PI7\SYS\global
    -> arg[ 25]: -Dapplication.home=E:\usr\sap\PI7\DVEBMGS00\exe
    -> arg[ 26]: -Djava.class.path=E:\usr\sap\PI7\DVEBMGS00\exe\jstartup.jar;E:\usr\sap\PI7\DVEBMGS00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 27]: -Djava.library.path=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin;C:\j2sdk1.4.2_09\bin;E:\usr\sap\PI7\DVEBMGS00\j2ee\os_libs;E:\oracle\PI7\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_09\bin;C:\j2sdk1.4.2_09\jre\bin;E:\usr\sap\PI7\SYS\exe\uc\NTI386
    -> arg[ 28]: -Dmemory.manager=1024M
    -> arg[ 29]: -Xmx1024M
    -> arg[ 30]: -Xms1024M
    -> arg[ 31]: -DLoadBalanceRestricted=no
    -> arg[ 32]: -Djstartup.mode=JCONTROL
    -> arg[ 33]: -Djstartup.ownProcessId=5796
    -> arg[ 34]: -Djstartup.ownHardwareId=G1631462527
    -> arg[ 35]: -Djstartup.whoami=server
    -> arg[ 36]: -Djstartup.debuggable=no
    -> arg[ 37]: -DSAPINFO=PI7_00_server
    -> arg[ 38]: -DSAPSTART=1
    -> arg[ 39]: -DCONNECT_PORT=2168
    -> arg[ 40]: -DSAPSYSTEM=00
    -> arg[ 41]: -DSAPSYSTEMNAME=PI7
    -> arg[ 42]: -DSAPMYNAME=hcl3SAP_PI7_00
    -> arg[ 43]: -DSAPPROFILE=E:\usr\sap\PI7\SYS\profile\PI7_DVEBMGS00_hcl3SAP
    -> arg[ 44]: -DFRFC_FALLBACK=ON
    -> arg[ 45]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 46]: -DSAPSTARTUP=1
    -> arg[ 47]: -DSAPSYSTEM=00
    -> arg[ 48]: -DSAPSYSTEMNAME=PI7
    -> arg[ 49]: -DSAPMYNAME=hcl3SAP_PI7_00
    -> arg[ 50]: -DSAPDBHOST=hcl3SAP
    -> arg[ 51]: -Dj2ee.dbhost=hcl3SAP
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    [Thr 5720] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 4072] Tue Dec 16 11:29:59 2008
    [Thr 4072] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 4072] Tue Dec 16 11:30:00 2008
    [Thr 4072] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 4072] JLaunchISetClusterId: set cluster id 9240450
    [Thr 4072] Tue Dec 16 11:30:01 2008
    [Thr 4072] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 4072] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 6392] Tue Dec 16 11:30:28 2008
    [Thr 6392] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
    [Thr 6392] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI
    [Thr 6392] Tue Dec 16 11:30:29 2008
    [Thr 6392] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.engine.Compress
    [Thr 6704] Tue Dec 16 11:30:36 2008
    [Thr 6704] JHVM_RegisterNatives: registering methods in com.sap.security.core.server.vsi.service.jni.VirusScanInterface
    [Thr 4072] Tue Dec 16 11:31:48 2008
    [Thr 4072] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
    Thanks in advance for your time and patience.
    Prashant
    Edited by: Prashant Vijayadas on Dec 16, 2008 5:14 PM

    Hi Jazz,
    i cannot seem to find any errors in the default trace files either [ located in usr/sap/<SID>/DVEBMGS/j2ee/cluster/server0/log ]
    Please find the default trace files below:
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[./log/defaultTrace.trc]/>
    <!PATTERN[defaultTrace.trc]/>
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    <!ENCODING[Cp1252]/>
    <!FILESET[4, 20, 10485760]/>
    <!PREVIOUSFILE[defaultTrace.3.trc]/>
    <!NEXTFILE[defaultTrace.5.trc]/>
    <!LOGHEADER[END]/>
    #1.5#0012793AE40C00440000000C0000121800045DD8487B974B#1229083417427#System.err##System.err#######SAPEngine_System_Thread[impl:5]_69##0#0#Error##Plain###     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)#
    #1.5#0012793AE40C00440000000D0000121800045DD8487D650D#1229083417552#System.err##System.err#######SAPEngine_System_Thread[impl:5]_69##0#0#Error##Plain###     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)#
    #1.5#0012793AE40C00440000000E0000121800045DD8487D65A5#1229083417552#System.err##System.err#######SAPEngine_System_Thread[impl:5]_69##0#0#Error##Plain###     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)#
    #1.5#0012793AE40C002F000000060000121800045DD848DD3380#1229083423878#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.init()#######SAPEngine_System_Thread[impl:5]_32##0#0#Error#1#/System/Server#Java###SNC properties not found ##
    #1.5#0012793AE40C0047000000000000121800045DD849291423#1229083428954#com.sap.aii.af.service.cpa.impl.cache.CacheManager##com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(boolean)#######SAPEngine_System_Thread[impl:5]_65##0#0#Error##Java###CPA Cache not updated with directory data, due to: #1#Couldn't open Directory URL (http://hcl3sap.hclt.corp.hcl.in:50000/dir/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=C&consumer=af.pi7.hcl3sap), due to: HTTP 503: Not Ready#
    #1.5#0012793AE40C0047000000010000121800045DD849298BB2#1229083428985#com.sap.aii.af.service.cpa.impl.cache.CacheManager##com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(boolean)#######SAPEngine_System_Thread[impl:5]_65##0#0#Error##Java###Confirmation handling failed, due to: #1#Couldn't send confirmation, due to: Couldn't access Confirmation URL, due to: HTTP 503: Not Ready#
    #1.5#0012793AE40C0049000000000000121800045DD8492F4B02#1229083429407#com.sap.aii.af.service.alerting.Alert##com.sap.aii.af.service.alerting.Alert.getMDTUrl()#######SAPEngine_System_Thread[impl:5]_8##0#0#Error##Plain###HTTP response code: 503 (Not Ready)#
    #1.5#0012793AE40C004E000000000000121800045DD8496DB509#1229083433562#com.sap.aii.adapter.jdbc.XI2JDBC##com.sap.aii.adapter.jdbc.XI2JDBC.init(Channel, AdminAdapter, boolean)#######SAPEngine_System_Thread[impl:5]_41##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC#Java###Configuration error in : #2#JDBC_Receiver_CC#<null>#
    #1.5#0012793AE40C002F000000090000121800045DD84973B644#1229083433968#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.init()#######SAPEngine_System_Thread[impl:5]_32##0#0#Error#1#/System/Server#Java###SNC properties not found ##
    #1.5#0012793AE40C0050000000020000121800045DD849746B3F#1229083433999#com.sap.engine.services.jndi##com.sap.engine.services.jndi#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_47##0#0#Warning#1#/System/Audit#Java###Exception #1#com.sap.engine.services.jndi.persistent.exceptions.NoPermissionException: Exception during getInitialContext operation. Wrong security principle/credentials. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]
         at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:70)
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:135)
         at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:65)
         at com.sap.engine.system.naming.provider.DefaultInitialContext.<init>(DefaultInitialContext.java:46)
         at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
         at javax.naming.InitialContext.init(InitialContext.java:219)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at com.sap.aii.af.service.jms.WorkerJMSSender.init(WorkerJMSSender.java:318)
         at com.sap.aii.af.service.jms.WorkerHandlerImpl.run(WorkerHandlerImpl.java:344)
         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:124)
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.
         at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:180)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:172)
         at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:60)
         ... 14 more
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Authentication did not succeed.
         at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:177)
         ... 17 more
    #1.5#0012793AE40C0050000000030000121800045DD849747B70#1229083434015#com.sap.aii.af.service.jms.WorkerJMSSender##com.sap.aii.af.service.jms.WorkerJMSSender.init(WorkerHandler moduleHandler, Object para)#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_47##0#0#Error##Java###Unable to create the QueueConnectionFactory due to #1#Error getting the server-side naming service functionality during getInitialContext operation.#
    #1.5#0012793AE40C0051000000000000121800045DD849761D0C#1229083434124#com.sap.aii.adapter.jdbc.JDBC2XI##com.sap.aii.adapter.jdbc.JDBC2XI.handleDBConnectException(Exception)#J2EE_GUEST#0#####JDBC2XI[:JDBC2JDBC_Sender_BS:JDBC_Sender_CC]_1##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC#Plain###Accessing database connection 'jdbc:odbc:Driver={Microsoft Access Driver (.mdb)};DBQ=C:
    XI
    Sender
    RamaSurya.mdb' failed: com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:odbc:Driver={Microsoft Access Driver (.mdb)};DBQ=C:
    XI
    Sender
    RamaSurya.mdb': SQLException: [Microsoft][ODBC Microsoft Access Driver]General error Unable to open registry key 'Temporary (volatile) Jet DSN for process 0x1218 Thread 0x70c DBC 0x779cd6c Jet'.#
    #1.5#0012793AE40C0050000000040000121800045DD8497B42D4#1229083434452#com.sap.aii.af.service.jms.WorkerJMSSender##com.sap.aii.af.service.jms.WorkerJMSSender.start()#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_47##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/JMS_ROOT#Java###Channel is errornous, hence it cannot be started. See error messages (' Error during channel initialization; exception trace: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Error getting the server-side naming service functionality during getInitialContext operation.
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:243)
         at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:65)
         at com.sap.engine.system.naming.provider.DefaultInitialContext.<init>(DefaultInitialContext.java:46)
         at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
         at javax.naming.InitialContext.init(InitialContext.java:219)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at com.sap.aii.af.service.jms.WorkerJMSSender.init(WorkerJMSSender.java:318)
         at com.sap.aii.af.service.jms.WorkerHandlerImpl.run(WorkerHandlerImpl.java:344)
         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:124)
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NoPermissionException: Exception during getInitialContext operation. Wrong security principle/credentials. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]
         at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:70)
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:135)
         ... 13 more
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.
         at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:180)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:172)
         at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:60)
         ... 14 more
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Authentication did not succeed.
         at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:177)
         ... 17 more
    ') before. Reconfigure it or restart the JMS service!#1#VASAVI_RCR_JMS_HR#
    #1.5#0012793AE40C004E000000020000121800045DD84981BA8C#1229083434874#com.sap.aii.adapter.jdbc.XI2JDBC##com.sap.aii.adapter.jdbc.XI2JDBC.handleDBConnectException(Exception, AlertContextInformation)#######SAPEngine_System_Thread[impl:5]_41##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC#Plain###Accessing database connection 'jdbc:oracle:thin:@10.117.34.111:1521:ORACLE' failed: com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:oracle:thin:@10.117.34.111:1521:ORACLE': SQLException: Io exception: Connection refused(DESCRIPTION=(TMP=)(VSNNUM=153092352)(ERR=12500)(ERROR_STACK=(ERROR=(CODE=12500)(EMFI=4))(ERROR=(CODE=12560)(EMFI=4))(ERROR=(CODE=530)(EMFI=4))(ERROR=(BUF='32-bit Windows Error: 2: No such file or directory'))))#
    #1.5#0012793AE40C0053000000000000121800045DD8498DB60C#1229083435670#com.sap.aii.af.rfc.core.RfcRuntimeManager##com.sap.aii.af.rfc.core.RfcRuntimeManager.channelAdded(Channel channel)#######SAPEngine_System_Thread[impl:5]_72##0#0#Error##Java###can not instantiate RfcPool object - ignoring this channel '''' due to: #2#CC_send_RFC#com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcServerPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed attempts#
    #1.5#0012793AE40C0054000000000000121800045DD8498F2B21#1229083435764#com.sap.aii.adapter.jdbc.JDBC2XI##com.sap.aii.adapter.jdbc.JDBC2XI.handleDBConnectException(Exception)#J2EE_GUEST#0#####JDBC2XI[:BS_MWSOA_SDR:VSD_CC_JDBC]_2##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC#Plain###Accessing database connection 'jdbc:oracle:thin:@10.117.34.111:1521:ORACLE' failed: com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:oracle:thin:@10.117.34.111:1521:ORACLE': SQLException: Io exception: Connection refused(DESCRIPTION=(TMP=)(VSNNUM=153092352)(ERR=12500)(ERROR_STACK=(ERROR=(CODE=12500)(EMFI=4))(ERROR=(CODE=12560)(EMFI=4))(ERROR=(CODE=530)(EMFI=4))(ERROR=(BUF='32-bit Windows Error: 2: No such file or directory'))))#
    #1.5#0012793AE40C0053000000010000121800045DD849987C48#1229083436373#com.sap.aii.af.rfc.core.RfcRuntimeManager##com.sap.aii.af.rfc.core.RfcRuntimeManager.channelAdded(Channel channel)#######SAPEngine_System_Thread[impl:5]_72##0#0#Error##Java###can not instantiate RfcPool object - ignoring this channel '''' due to: #2#CC_A_RFCSender#com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcServerPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed attempts#
    #1.5#0012793AE40C0055000000000000121800045DD8499BFF10#1229083436592#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDE]_11##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDE: No suitable sender agreement found#
    #1.5#0012793AE40C0056000000000000121800045DD849BF4E62#1229083438919#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDF]_41##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDF: No suitable sender agreement found#
    #1.5#0012793AE40C0057000000000000121800045DD849C87229#1229083439513#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDG]_53##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDG: No suitable sender agreement found#
    #1.5#0012793AE40C0058000000000000121800045DD849D0CAB8#1229083440060#com.sap.aii.adapter.file.XI2File##com.sap.aii.adapter.file.XI2File.init(Channel, AdminAdapter)#######SAPEngine_System_Thread[impl:5]_91##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Java###Configuration error in : #2#FileReceiver_FCC#<null>#
    #1.5#0012793AE40C0058000000020000121800045DD849E48706#1229083441356#com.sap.aii.adapter.file.XI2File##com.sap.aii.adapter.file.XI2File.init(Channel, AdminAdapter)#######SAPEngine_System_Thread[impl:5]_91##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Java###Configuration error in : #2#CC_Receiver1#<null>#
    #1.5#0012793AE40C0059000000000000121800045DD84A050EFF#1229083443480#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRDF:CC_BSRDF]_119##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDF: No suitable sender agreement found#
    #1.5#0012793AE40C002F0000000C0000121800045DD84A0DD554#1229083444058#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.init()#######SAPEngine_System_Thread[impl:5]_32##0#0#Error#1#/System/Server#Java###SNC properties not found ##
    #1.5#0012793AE40C0058000000040000121800045DD84A1C96B5#1229083445027#com.sap.aii.adapter.file.Conversion##com.sap.aii.adapter.file.Conversion.getTableParaWithErrorDescription(String)#######SAPEngine_System_Thread[impl:5]_91##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/Conversion#Java###Parameter : not set#1#student.fieldNames#
    #1.5#0012793AE40C0058000000060000121800045DD84A3FEB97#1229083447338#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.init(Channel, AdminAdapter, boolean)#######SAPEngine_System_Thread[impl:5]_91##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Java###Configuration error in : #2#stu_sender#<null>#
    #1.5#0012793AE40C0058000000080000121800045DD84A400FAA#1229083447354#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.start()#######SAPEngine_System_Thread[impl:5]_91##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###File adapter sender channel stu_sender not initalized - could not start#
    #1.5#0012793AE40C0054000000020000121800045DD84A48C532#1229083447916#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BS_TST:CC_F1_S]_185##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_F1_S: No suitable sender agreement found#
    #1.5#0012793AE40C005A000000000000121800045DD84A68B403#1229083450009#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRDF:CC_BSRDF]_257##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDF: No suitable sender agreement found#
    #1.5#0012793AE40C0059000000020000121800045DD84A68C418#1229083450009#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDG]_258##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDG: No suitable sender agreement found#
    #1.5#0012793AE40C005B000000000000121800045DD84A68F232#1229083450025#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDE]_259##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDE: No suitable sender agreement found#
    #1.5#0012793AE40C005C000000000000121800045DD84A68FDA1#1229083450025#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDF]_260##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDF: No suitable sender agreement found#
    #1.5#0012793AE40C005D000000000000121800045DD84A6BAA02#1229083450212#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRD]_263##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRD: No suitable sender agreement found#
    #1.5#0012793AE40C002F0000000F0000121800045DD84AA8C03D#1229083454211#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.init()#######SAPEngine_System_Thread[impl:5]_32##0#0#Error#1#/System/Server#Java###SNC properties not found ##
    #1.5#0012793AE40C005C000000020000121800045DD84B01421F#1229083460006#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRDF:CC_BSRDF]_434##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDF: No suitable sender agreement found#
    #1.5#0012793AE40C005E000000000000121800045DD84B01519A#1229083460006#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRD]_437##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRD: No suitable sender agreement found#
    #1.5#0012793AE40C005F000000000000121800045DD84B015B72#1229083460006#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDE]_439##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDE: No suitable sender agreement found#
    #1.5#0012793AE40C0059000000040000121800045DD84B015DEF#1229083460006#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDG]_436##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDG: No suitable sender agreement found#
    #1.5#0012793AE40C0060000000000000121800045DD84B01C588#1229083460037#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDF]_440##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDF: No suitable sender agreement found#
    #1.5#0012793AE40C0061000000000000121800045DD84B037ABA#1229083460146#com.sap.aii.adapter.jdbc.JDBC2XI##com.sap.aii.adapter.jdbc.JDBC2XI.handleDBConnectException(Exception)#J2EE_GUEST#0#####JDBC2XI[:JDBC2JDBC_Sender_BS:JDBC_Sender_CC]_438##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC#Plain###Accessing database connection 'jdbc:odbc:Driver={Microsoft Access Driver (.mdb)};DBQ=C:
    XI
    Sender
    RamaSurya.mdb' failed: com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:odbc:Driver={Microsoft Access Driver (.mdb)};DBQ=C:
    XI
    Sender
    RamaSurya.mdb': SQLException: [Microsoft][ODBC Microsoft Access Driver]General error Unable to open registry key 'Temporary (volatile) Jet DSN for process 0x1218 Thread 0x1988 DBC 0x78d1eac Jet'.#
    #1.5#0012793AE40C0062000000000000121800045DD84B282C7A#1229083462551#com.sap.aii.af.service.jms.WorkerJMSSender##com.sap.aii.af.service.jms.WorkerJMSSender.init(WorkerHandler moduleHandler, Object para)#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_50##0#0#Error##Java###Unable to create the QueueConnectionFactory due to #1#Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.41:7222#
    #1.5#0012793AE40C0062000000010000121800045DD84B283F6D#1229083462567#com.sap.aii.af.service.jms.WorkerJMSSender##com.sap.aii.af.service.jms.WorkerJMSSender.start()#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_50##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/JMS_ROOT#Java###Channel is errornous, hence it cannot be started. See error messages (' Error during channel initialization; exception trace: javax.naming.ServiceUnavailableException: Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.41:7222 [Root exception is javax.jms.JMSException: Failed to connect to the server at tcp://10.117.135.41:7222]
         at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:669)
         at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:489)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         ...') before. Reconfigure it or restart the JMS service!#1#CC_PO_RCR#
    #1.5#0012793AE40C0063000000000000121800045DD84B284C1A#1229083462567#com.sap.aii.af.service.jms.WorkerImpl##com.sap.aii.af.service.jms.WorkerImpl.init(WorkerHandler moduleHandler, Object para)#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_57##0#0#Error##Java###Unable to create the QueueConnectionFactory due to #1#Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.41:7222#
    #1.5#0012793AE40C0064000000000000121800045DD84B28531A#1229083462567#com.sap.aii.af.service.jms.WorkerImpl##com.sap.aii.af.service.jms.WorkerImpl.init(WorkerHandler moduleHandler, Object para)#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_56##0#0#Error##Java###Unable to create the QueueConnectionFactory due to #1#Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.41:7222#
    #1.5#0012793AE40C0065000000000000121800045DD84B289AAB#1229083462583#com.sap.aii.af.service.jms.WorkerImpl##com.sap.aii.af.service.jms.WorkerImpl.init(WorkerHandler moduleHandler, Object para)#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_53##0#0#Error##Java###Unable to create the QueueConnectionFactory due to #1#Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.41:7222#
    #1.5#0012793AE40C0066000000000000121800045DD84B2AB132#1229083462723#com.sap.aii.af.service.jms.WorkerJMSSender##com.sap.aii.af.service.jms.WorkerJMSSender.init(WorkerHandler moduleHandler, Object para)#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_49##0#0#Error##Java###Unable to create the QueueConnectionFactory due to #1#Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.66:7222#
    #1.5#0012793AE40C0064000000010000121800045DD84B397738#1229083463692#com.sap.aii.af.service.jms.WorkerImpl##com.sap.aii.af.service.jms.WorkerImpl.start()#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_56##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/JMS_ROOT#Java###Channel is errornous, hence it cannot be started. See error messages (' Error during channel initialization; exception trace: javax.naming.ServiceUnavailableException: Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.41:7222 [Root exception is javax.jms.JMSException: Failed to connect to the server at tcp://10.117.135.41:7222]
         at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:669)
         at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:489)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         ...') before. Reconfigure it or restart the JMS service!#1#CC_PIP_TO_B2MML#
    #1.5#0012793AE40C0066000000010000121800045DD84B39B5F3#1229083463707#com.sap.aii.af.service.jms.WorkerJMSSender##com.sap.aii.af.service.jms.WorkerJMSSender.start()#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_49##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/JMS_ROOT#Java###Channel is errornous, hence it cannot be started. See error messages (' Error during channel initialization; exception trace: javax.naming.ServiceUnavailableException: Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.66:7222 [Root exception is javax.jms.JMSException: Failed to connect to the server at tcp://10.117.135.66:7222]
         at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:669)
         at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:489)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         ...') before. Reconfigure it or restart the JMS service!#1#CC_B2MML_IB#
    #1.5#0012793AE40C0063000000010000121800045DD84B39C1BB#1229083463707#com.sap.aii.af.service.jms.WorkerImpl##com.sap.aii.af.service.jms.WorkerImpl.start()#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_57##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/JMS_ROOT#Java###Channel is errornous, hence it cannot be started. See error messages (' Error during channel initialization; exception trace: javax.naming.ServiceUnavailableException: Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.41:7222 [Root exception is javax.jms.JMSException: Failed to connect to the server at tcp://10.117.135.41:7222]
         at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:669)
         at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:489)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         ...') before. Reconfigure it or restart the JMS service!#1#CC_S_GR#
    #1.5#0012793AE40C0065000000010000121800045DD84B39C67B#1229083463707#com.sap.aii.af.service.jms.WorkerImpl##com.sap.aii.af.service.jms.WorkerImpl.start()#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_53##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/JMS_ROOT#Java###Channel is errornous, hence it cannot be started. See error messages (' Error during channel initialization; exception trace: javax.naming.ServiceUnavailableException: Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.41:7222 [Root exception is javax.jms.JMSException: Failed to connect to the server at tcp://10.117.135.41:7222]
         at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:669)
         at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:489)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         ...') before. Reconfigure it or restart the JMS service!#1#Sys_GoodsIssueFromStore_JMS_EMS#
    #1.5#0012793AE40C002F000000120000121800045DD84B420336#1229083464254#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.init()#######SAPEngine_System_Thread[impl:5]_32##0#0#Error#1#/System/Server#Java###SNC properties not found ##
    #1.5#0012793AE40C0067000000000000121800045DD84B4618D7#1229083464520#com.sap.aii.af.service.jms.WorkerImpl##com.sap.aii.af.service.jms.WorkerImpl.start()#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_58##0#0#Error##Java###Unable to create the Queue due to #1#Name not found: 'Inbound_APC_Queue_Order'#
    #1.5#0012793AE40C0068000000000000121800045DD84B483E2D#1229083464660#com.sap.aii.af.service.jms.WorkerImpl##com.sap.aii.af.service.jms.WorkerImpl.start()#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Java###Unable to create the Queue due to #1#Name not found: 'Inbound_APC_Queue_Order'#
    #1.5#0012793AE40C002F000000150000121800045DD84BDB73A2#1229083474297#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.init()#######SAPEngine_System_Thread[impl:5]_32##0#0#Error#1#/System/Server#Java###SNC properties not found ##
    #1.5#0012793AE40C006A000000000000121800045DD84C0FEB63#1229083477734#com.sap.aii.adapter.jdbc.JDBC2XI##com.sap.aii.adapter.jdbc.JDBC2XI.handleDBConnectException(Exception)#J2EE_GUEST#0#####JDBC2XI[:BS_F2FBPM_SENDER:CM_SENDER]_3##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC#Plain###Accessing database connection 'jdbc:oracle:thin:@10.117.34.178:1521:DEV' failed: com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:oracle:thin:@10.117.34.178:1521:DEV': SQLException: Io exception: The Network Adapter could not establish the connection#
    #1.5#0012793AE40C006B000000000000121800045DD851C45EB6#1229083573418#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff820003]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#44a92fa0c84511dd92ad0012793ae40c#File2XI[:BSystem_TestPractice_Sender:CC_A_flatefile]_13##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
    #1.5#0012793AE40C006B000000020000121800045DD851C46142#1229083573418#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#44a92fa0c84511dd92ad0012793ae40c#File2XI[:BSystem_TestPractice_Sender:CC_A_flatefile]_13##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_A_flatefile: Sending file failed with java.lang.NullPointerException - continue processing#
    #1.5#0012793AE40C006C000000000000121800045DD851DF9B17#1229083575199#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff820005]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#45bb3be0c84511dd976d0012793ae40c#File2XI[:BService_MDM_SENDER:Outbound_From_MDM2]_12##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
    #1.5#0012793AE40C006C000000020000121800045DD851DF9DBA#1229083575199#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFtpList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#45bb3be0c84511dd976d0012793ae40c#File2XI[:BService_MDM_SENDER:Outbound_From_MDM2]_12##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel Outbound_From_MDM2: Sending file failed with java.lang.NullPointerException - continue processing#
    #1.5#0012793AE40C006D000000000000121800045DD851F43711#1229083576557#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff820007]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#467eb2f0c84511ddce9a0012793ae40c#File2XI[:BS_Sat:MsgMerge_Sender1_CC]_48##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
    #1.5#0012793AE40C006D000000020000121800045DD851F439AA#1229083576557#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#467eb2f0c84511ddce9a0012793ae40c#File2XI[:BS_Sat:MsgMerge_Sender1_CC]_48##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel MsgMerge_Sender1_CC: Sending file failed with java.lang.NullPointerException - continue processing#
    #1.5#0012793AE40C006D000000040000121800045DD85210BEE6#1229083578416#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4759f7c0c84511dd8d7b0012793ae40c#File2XI[:BSRDF:CC_BSRDF]_545##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDF: No suitable sender agreement found#
    #1.5#0012793AE40C006C000000040000121800045DD852118EE5#1229083578479#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#46ff54a0c84511ddb71a0012793ae40c#File2XI[:BSRD:CC_BSRDG]_546##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDG: No suitable sender agreement found#
    #1.5#0012793AE40C006C000000060000121800045DD8522A479D#1229083580087#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#46ff54a0c84511ddb71a0012793ae40c#File2XI[:BSRD:CC_BSRDE]_547##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDE: No suitable sender agreement found#
    #1.5#0012793AE40C006D000000060000121800045DD8522AB3A6#1229083580119#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4759f7c0c84511dd8d7b0012793ae40c#File2XI[:BSRD:CC_BSRD]_548##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRD: No suitable sender agreement found#
    #1.5#0012793AE40C006C000000080000121800045DD852509FDA#1229083582602#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#46ff54a0c84511ddb71a0012793ae40c#File2XI[:BSRD:CC_BSRDF]_549##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDF: No suitable sender agreement found#
    #1.5#0012793AE40C006E000000000000121800045DD852544076#1229083582836#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff82000a]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4982cb30c84511ddbd890012793ae40c#File2XI[:BS_Sat1:MsgMerge_Sender2_CC]_69##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
    #1.5#0012793AE40C006E000000020000121800045DD85254AFC8#1229083582868#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4982cb30c84511ddbd890012793ae40c#File2XI[:BS_Sat1:MsgMerge_Sender2_CC]_69##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel MsgMerge_Sender2_CC: Sending file failed with java.lang.NullPointerException - continue processing#
    #1.5#0012793AE40C006F000000000000121800045DD852569148#1229083582993#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff82000b]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#499a98f0c84511ddb0c20012793ae40c#File2XI[:BS_PAUDV:CC_PAUDV_SEND]_134##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
    #1.5#0012793AE40C006F000000020000121800045DD852569409#1229083582993#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#499a98f0c84511ddb0c20012793ae40c#File2XI[:BS_PAUDV:CC_PAUDV_SEND]_134##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_PAUDV_SEND: Sending file failed with java.lang.NullPointerException - continue processing#
    #1.5#0012793AE40C006E000000040000121800045DD85256A507#1229083582993#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0####4b23f810c84511ddc7d30012793ae40c#File2XI[:BSRDE:CC_BSRDE]_558##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDE: No suitable sender agreement found#
    #1.5#0012793AE40C006F000000040000121800045DD85258BFEE#1229083583133#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0####4b3954d0c84511dd846c0012793ae40c#File2XI[:BSRDG:CC_BSRDG]_562##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDG: No suitable sender agreement found#
    #1.5#0012793AE40C0070000000000000121800045DD8527941A5#1229083585273#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff82000d]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4b370ae0c84511dd8e0c0012793ae40c#File2XI[:BSystem_TestPractice_Sender:CC_Sending_file]_183##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
    #1.5#0012793AE40C0070000000020000121800045DD8527943FF#1229083585273#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4b370ae0c84511dd8e0c0012793ae40c#File2XI[:BSystem_TestPractice_Sender:CC_Sending_file]_183##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_Sending_file: Sending file failed with java.lang.NullPointerException - continue processing#
    #1.5#0012793AE40C0071000000000000121800045DD852A635CB#1229083588210#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff82000f]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4c8e3670c84511dd94bf0012793ae40c#File2XI[:BS_PAUD:CC_POAUDSEND]_240##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
    #1.5#0012793AE40C0071000000020000121800045DD852A63A01#1229083588210#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4c8e3670c84511dd94bf0012793ae40c#File2XI[:BS_PAUD:CC_POAUDSEND]_240##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_POAUDSEND: Sending file failed with java.lang.NullPointerException - continue processing#
    #1.5#0012793AE40C0072000000000000121800045DD852AF7377#1229083588819#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff8200011]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4cad3020c84511ddb7490012793ae40c#File2XI[:BS_SEND2:CC_MERVSEND2]_250##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
    #1.5#0012793AE40C0072000000020000121800045DD852AF7668#1229083588819#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4cad3020c84511ddb7490012793ae40c#File2XI[:BS_SEND2:CC_MERVSEND2]_250##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_MERVSEND2: Sending file failed with java.lang.NullPointerException - continue processing#
    #1.5#0012793AE40C0073000000000000121800045DD852BBB4AD#1229083589615#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff8200013]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4cdf3ca0c84511dd8c190012793ae40c#File2XI[:BS_BLR:FileSender_BPM]_238##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
    #1.5#0012793AE40C0073000000020000121800045DD852BBB87F#1229083589615#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4cdf3ca0c84511dd8c190012793ae40c#File2XI[:BS_BLR:FileSender_BPM]_238##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel FileSender_BPM: Sending file failed with java.lang.NullPointerException - continue processing#
    #1.5#0012793AE40C0056000000020000121800045DD852BC3912#1229083589647#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff8200016]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4d1abf00c84511dda6510012793ae40c#File2XI[:BS_BLR:FWS_SEND_CC]_268##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
    #1.5#0012793AE40C0056000000040000121800045DD852BC3B81#1229083589662#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4d1abf00c84511dda6510012793ae40c#File2XI[:BS_BLR:FWS_SEND_CC]_268##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel FWS_SEND_CC: Sending file failed with java.lang.NullPointerException - continue processing#
    #1.5#0012793AE40C0074000000000000121800045DD852CD926F#1229083590787#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff8200017]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4e3d9420c84511ddc5950012793ae40c#File2XI[:BS_Sat:FileSender_FCC]_252##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
    #1.5#0012793AE40C0074000000020000121800045DD852CD94EB#1229083590787#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4e3d9420c84511ddc5950012793ae40c#File2XI[:BS_Sat:FileSender_FCC]_252##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel FileSender_FCC: Sending file failed with java.lang.NullPointerException - continue processing#
    #1.5#0012793AE40C006D000000080000121800045DD853948DA4#1229083603829#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.getFileList(File2XIConfiguration.FileSource[])#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4759f7c0c84511dd8d7b0012793ae40c#File2XI[:BS_DIPANKAR1_SENDER:Sender_CC]_553##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel Sender_CC: Directory
    192.168.91.1
    D:
    SAP_Data does not exist#
    #1.5#0012793AE40C0075000000010000121800045DD86BA73EED#1229084007463#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine#J2EE_GUEST#0##PI7#RIJUA                           #4446C8DDBF70F1DAB51A0012793AE40C#SAPEngine_Application_Thread[impl:3]_79##0#0#Error#1#/System/Server#Plain###bean LCRBEAN_GET_PROFILE_PARAMETER not found#
    #1.5#0012793AE40C0075000000030000121800045DD8861A181C#1229084450980#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine#J2EE_GUEST#0##PI7#PI7BASIS                        #4F47C8DD65E5F12CB51A0012793AE40C#SAPEngine_Application_Thread[impl:3]_79##0#0#Error#1#/System/Server#Plain###bean LCRBEAN_GET_PROFILE_PARAMETER not found#
    #1.5#0012793AE40C0076000000010000121800045DD88E669A80#1229084590160#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine#J2EE_GUEST#0##PI7#SAPSYS                          #9D47C8DD4EE4F161B51A0012793AE40C#SAPEngine_Application_Thread[impl:3]_95##0#0#Error#1#/System/Server#Plain###bean LCRBEAN_GET_PROFILE_PARAMETER not found#
    #1.5#0012793AE40C0076000000030000121800045DD899BD67E0#1229084780325#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine#J2EE_GUEST#0##PI7#RIJUA                           #1448C8DDD335F1E5B51A0012793AE40C#SAPEngine_Application_Thread[impl:3]_95##0#0#Error#1#/System/Server#Plain###bean LCRBEAN_GET_PROFILE_PARAMETER not found#
    #1.5#0012793AE40C0078000000010000121800045DD899EAE617#1229084783309#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine#J2EE_GUEST#0##HE6#SAPSYS                          #81C1A9AA09F24B0894CFA72F264F2842#SAPEngine_Application_Thread[impl:3]_24##0#0#Error#1#/System/Server#Plain###bean SLDJAVA_ACCESSOR_REQUEST not found#
    #1.5#0012793AE40C0079000000010000121800045DD899EB397B#1229084783325#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine#J2EE_GUEST#0##HE6#SAPSYS                          #81C1A9AA09F24B0894CFA72F264F2842#SAPEngine_Application_Thread[impl:3]_16##0#0#Error#1#/System/Server#Plain###bean SLDJAVA_ACCESSOR_REQUEST not found#
    #1.5#0012793AE40C007B000000010000121800045DD8F60F3B22#1229086329364#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: received EOF, connection closed!#
    #1.5#0012793AE40C007B000000030000121800045DD8F60F4058#1229086329364#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: receive failed (Connection closed -1)#
    #1.5#0012793AE40C007B000000050000121800045DD8F60F425A#1229086329364#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###ReadRunnable: receive failed (Encomi: receive failed (Connection closed -1) -1), flush pending responses#
    #1.5#0012793AE40C007C000000000000121800045DD8F6115F52#1229086329505#com.sap.engine.core.cluster.impl6.ms.MSRawConnection##com.sap.engine.core.cluster.impl6.ms.MSRawConnection.receiveRawMessage()######b0307110c84b11ddab1b0012793ae40c#SAP J2EE Engine|MS Socket Listener##0#0#Error##Plain###java.net.SocketException: Connection reset#
    #1.5#0012793AE40C007C000000010000121800045DD8F611603B#1229086329505#com.sap.engine.core.cluster.impl6.ms.MSRawConnection##com.sap.engine.core.cluster.impl6.ms.MSRawConnection.receiveRawMessage()######b0307110c84b11ddab1b0012793ae40c#SAP J2EE Engine|MS Socket Listener##0#0#Error##Plain###java.net.SocketException: Connection reset
         at java.net.SocketInputStream.read(SocketInputStream.java:168)
         at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
         at java.io.BufferedInputStream.read1(BufferedInputStream.java:222)
         at java.io.BufferedInputStream.read(BufferedInputStream.java:277)
         at com.sap.engine.core.cluster.impl6.ms.MSMessageHeader.read(MSMessageHeader.java:440)
         at com.sap.engine.core.cluster.impl6.ms.MSMessageObjectImpl.readHeader(MSMessageObjectImpl.java:142)
         at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.receiveRawMessage(MSRawConnection.java:1660)
         at com.sap.engine.core.cluster.impl6.ms.MSListener.run(MSListener.java:86)
         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#0012793AE40C007B000000070000121800045DD8F61E7D39#1229086330364#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000090000121800045DD8F61E7F00#1229086330364#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###ReadRunnable: failed to connect to server 1 times#
    #1.5#0012793AE40C007B0000000B0000121800045DD8F64AFC71#1229086333286#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B0000000D0000121800045DD8F6791AC5#1229086336302#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B0000000F0000121800045DD8F6A58D15#1229086339224#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000110000121800045DD8F6D20F7F#1229086342130#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000130000121800045DD8F6FE9326#1229086345052#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000150000121800045DD8F72CA0FC#1229086348067#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000170000121800045DD8F75795FA#1229086350880#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000190000121800045DD8F78418D5#1229086353802#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B0000001B0000121800045DD8F7B3C822#1229086356927#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B0000001D0000121800045DD8F7E02F82#1229086359833#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B0000001F0000121800045DD8F7E030C2#1229086359833#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###ReadRunnable: failed to connect to server 11 times#
    #1.5#0012793AE40C007B000000210000121800045DD8F80CB555#1229086362755#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000230000121800045DD8F83ABD55#1229086365770#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000250000121800045DD8F8674E72#1229086368692#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000270000121800045DD8F893C188#1229086371614#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000290000121800045DD8F8C1CD8A#1229086374630#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B0000002B0000121800045DD8F8EE5019#1229086377536#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B0000002D0000121800045DD8F91AD274#1229086380458#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B0000002F0000121800045DD8F947537E#1229086383379#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000310000121800045DD8F976E8A3#1229086386489#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000330000121800045DD8F9A36A4A#1229086389411#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000350000121800045DD8F9A36B62#1229086389411#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###ReadRunnable: failed to connect to server 21 times#
    #1.5#0012793AE40C007B000000370000121800045DD8F9D175D4#1229086392426#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000390000121800045DD8F9FDFF04#1229086395348#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B0000003B0000121800045DD8FA2A7A76#1229086398270#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007F000000010000121800045DD8FA49473F#1229086400285#com.sap.aii.utilxi.prop.impl.BasicPropertySource##com.sap.aii.utilxi.prop.impl.BasicPropertySource#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#158b1d00c84511dd9fed0012793ae40c#SAPEngine_Application_Thread[impl:3]_27##0#0#Error#1#/Applications/ExchangeInfrastructure#Plain###could not sync ExchangeProfile:
    Thrown:
    com.sap.rprof.dbprofiles.DBException: Connect to SAP gateway failed
    Connect_PM  TYPE=A ASHOST=HCL3SAP SYSNR=00 GWHOST=HCL3SAP GWSERV=sapgw00 PCS=1
    LOCATION    CPIC (TCP/IP) on local host with Unicode
    ERROR       partner '10.112.132.211:sapgw00' not reached
    TIME        Fri Dec 12 18:23:20 2008
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -10
    MODULE      nixxi.cpp
    LINE        2823
    DETAIL      NiPConnect2
    SYSTEM CALL connect
    ERRNO       10061
    ERRNO TEXT  WSAECONNREFUSED: Connection refused
    COUNTER     1
    Connect_PM  TYPE=A ASHOST=HCL3SAP SYSNR=00 GWHOST=HCL3SAP GWSERV=sapgw00 PCS=1
    LOCATION    CPIC (TCP/IP) on local host with Unicode
    ERROR       partner '10.112.132.211:sapgw00' not reached
    TIME        Fri Dec 12 18:23:20 2008
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -10
    MODULE      nixxi.cpp
    LINE        2823
    DETAIL      NiPConnect2
    SYSTEM CALL connect
    ERRNO       10061
    ERRNO TEXT  WSAECONNREFUSED: Connection refused
    COUNTER     1
         at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:457)
         at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:989)
         at com.sap.mw.jco.JCO$Client.connect(JCO.java:3193)
         at com.sap.rprof.dbprofiles.DBProfiles.getProfile(DBProfiles.java:101)
         at com.sap.rprof.dbprofiles.RemoteProfile.readRemoteProfileFromMedia(RemoteProfile.java:1286)
         at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfileFromFactory(RemoteProfile.java:193)
         at com.sap.aii.utilxi.prop.rprof.ExchangeProfilePropertySource.readProfile(ExchangeProfilePropertySource.java:177)
         at com.sap.aii.utilxi.prop.rprof.ExchangeProfilePropertySource.sync(ExchangeProfilePropertySource.java:165)
         at com.sap.aii.utilxi.misc.api.AIIProperties.sync(AIIProperties.java:580)
         at com.sap.aii.af.service.sld.SLDAccess.syncExchangeProfile(SLDAccess.java:43)
         at com.sap.aii.adapter.xi.ms.SLDReader.fire(SLDReader.java:52)
         at com.sap.aii.adapter.xi.ms.SLDReader.run(SLDReader.java:167)
         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)
    #1.5#0012793AE40C007B0000003D0000121800045DD8FA56FC49#1229086401176#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B0000003F0000121800045DD8FA83A493#1229086404114#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000410000121800045DD8FAB189C5#1229086407113#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000430000121800045DD8FADF9505#1229086410129#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engin

  • WebLogic Server: 10.3.5.0 - Managed stuck in STARTING

    Hi all. I have a managed stuck in STARTING for like 2 hours, the logs are these:
    ####<Sep 25, 2013 1:40:42 PM CEST> <Info> <JMS> <XXXXXXXXXXXXX> <ofi-spss-01> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6737003733c3b0fc:-2e9de822:14154e52035:-7ffd-0000000000000002> <1380109242585> <BEA-040321> <JMSServer "JMSServer-SPSS-1" is resuming.>
    ####<Sep 25, 2013 1:44:56 PM CEST> <Info> <Messaging> <XXXXXXXXXXXXX> <ofi-spss-01> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6737003733c3b0fc:-2e9de822:14154e52035:-7ffd-0000000000000002> <1380109496786> <BEA-282003> <The messaging kernel JMSServer-SPSS-1 will use up to 536,870,912 bytes of memory before paging begins>
    ####<Sep 25, 2013 1:44:56 PM CEST> <Info> <Messaging> <XXXXXXXXXXXXX> <ofi-spss-01> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6737003733c3b0fc:-2e9de822:14154e52035:-7ffd-0000000000000002> <1380109496795> <BEA-282001> <The messaging kernel JMSServer-SPSS-1 is beginning recovery of its persistent state>
    It's creating a log ot .TMP files under the managed tmp. There is a way to speed up or elude this "recover"? Please note that I'm quite noob with Weblogic.
    Thanks!

    Hi,
    Add -Dweblogic.StdoutDebugEnabled flag while starting the managed server and then post the verbose error message in your next post
    For setting the flag follow the below steps
    If your using Linux box and not using node manager to start the managed server,add the below line startManagedWebLogic.sh file
    JAVA_OPTIONS="-Dweblogic.StdoutDebugEnabled=true ${JAVA_OPTIONS}"
    echo "JAVA_OPTIONS=${JAVA_OPTIONS}"
    If your using Windows box and not using node manager to start the managed server,add the below line startManagedWebLogic.cmd file
    set JAVA_OPTIONS=-Dweblogic.StdoutDebugEnabled=true %JAVA_OPTIONS%
    echo JAVA_OPTIONS=%JAVA_OPTIONS%
    If you are starting the Managed server through the node manager then use these flags From Admin console : servers >>>. MS1 >>>> server start >>>> Arguments :-Dweblogic.StdoutDebugEnabled=true
    Regards,
    Fabian

  • Workflow stuck in starting state after applying SharePoint 2010 CU December 2012

    I have custom visual studio workflow which are associated with Custom content type. workflow gets triggered automatically when a file is uploaded to SharePoint. Everything was working fine till when i apply the following CU
    http://blogs.msdn.com/b/joerg_sinemus/archive/2012/12/27/sharepoint-2010-and-december-2012-cu.aspx
    After applying this my workflow get stuck in "Starting" state.
    No error were logged in 14 hive logs.
    Thanks in Advance!

    It took me a while but I came up with a work around.  There is a PowerShell script below that can be used to trigger the workflow.  Hopefully this will hold all of us over until the official fix arrives.
    First remove the auto start on change or new from the affected workflow
    Edit the script below to match your environment
    Add the script to Windows task scheduler with the PowerShell.exe in the command line
    This assumes PowerShell.exe is in the path
    Then add the full path and script name in the add arguements text box
    Script:
    #The purpose of this script is to start the SPD workflow with the windows task scheduler for a trigger
    #This should avoid the check in-out issue caused by the December 2012 SP CU patch
    #This needs to be run on an account with membership in the farm administration group for SharePoint and Shell in SQL
    #You can use a find and replace to replace the server and other names with your actual names
    #There are no status messages being used since this will be a scheduled task in the Windows task scheduler
    #Add SharePoint modules and create variable space
    add-pssnapin microsoft.sharepoint.powershell
    start-spassignment -global
    #Open the web site, list and the workflow
    $site=get-spsite %site url%"
    $web=get-spweb %Web url%
    #Open the %affected% library or list and workflow association
    $%affected%=$web.getlist("%affected%")
    $manager=$site.workflowmanager
    $culture=[system.globalization.cultureinfo]::currentculture
    $wfname="%affected workflow name"
    $association=$%affected%.workflowassociations.getassociationbyname($wfname,$culture)
    $data=$association.associationdata
    $wfrunoption=[microsoft.sharepoint.workflow.spworkflowrunoptions]::synchronous
    #Start workflow
    foreach ($item in $%affected%.items) {
    $site.workflowmanager.startworkflow($item,$association,$data,$wfrunoption)
    stop-spassignment -global

  • Azure Pack Windows Service Bus 1.1 wont start on Windows 8.1

    Hi I am installing Azure Pack Windows Service Bus 1.1 on my Windows 8.1 (I have tried with 4 more computers) and everyone keep getting the same error.
    After the configuration when the Service Bus Gateway tries to start up it gets stuck in starting mode and after a while it is turned off then try to start again.
    After some fail searching I can see that it is the <component name="MessagingRuntimeProvider" type="Microsoft.Cloud.ServiceBus.Messaging.Runtime.MessagingRuntimeProviderFactory, Microsoft.Cloud.ServiceBus.Messaging" /> component
    that make it get stuck.
    I have no idea why though, any ideas?
    This is the error I get in the event log:
    Faulting application name: Microsoft.ServiceBus.Gateway.exe, version: 2.0.30904.0, time stamp: 0x5227aa54
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0x80131623
    Fault offset: 0x00007ffb3a8258c8
    Faulting process id: 0xe20
    Faulting application start time: 0x01d07cf56f493327
    Faulting application path: C:\Program Files\Service Bus\1.1\Microsoft.ServiceBus.Gateway.exe
    Faulting module path: unknown
    Report Id: e317b8e7-e8e8-11e4-8261-600308a8ce71
    Faulting package full name: 
    Faulting package-relative application ID: 

    Not many responses...

  • Managed server is stuck in STARTING

    Hi All,
    I have managed severs on weblogic consol.
    These servers are linked to the windows services on my prodcution server.
    to start and stop the managed servers we used to simply restart the respective services on the production server.
    Now the situation is - two managed servers are stuck in STARTING state though i restarted my windiws services several tims?
    Please advice ASAP as its a production enviroment issue.. Thanks
    Mahendra

    same thing in our case but little different.
    i have a domain with four different clusters where two instances per cluster and those instances reside on two separate machines. All these instances are under NM control with -Xnohup switch on the serverstart tab.
    the problem i have is, when we have a weekly reboot on the two windows servers, one particular cluster instances always in 'STARTING' state. As you can see below the .out log will have the following content and nothing else. EVen for a day or two the server sits on 'STARTING' state with no additional logging in .out file.
    At this stage it gets ugly to bring the instances back to normal. We can't kill the instances so we had to use process explorer to kill it. As nodemanager restarts the instance immediately after killed the isntances we had to stop NM.
    again start NM and start repeating the steps untill the instances back up to normal. This is not good.
    not sure what else we can do. any kind of help is appreciated..thanks
    <Oct 19, 2012 11:01:41 AM> <Info> <NodeManager> <Starting WebLogic server with command line: D:\bea\jrockit-jdk1.5.0_24-R28.1.0-4.0.1\bin\java -Dweblogic.Name=System_Managed01 -Dbea.home=D:\bea -Djava.security.policy=D:\bea\weblogic92\server\lib\weblogic.policy -Dweblogic.management.server=http://rchz3105.mckesson.com:7510 -Djava.library.path=D:\bea\WEBLOG~1\server\bin;.;C:\WINDOWS\system32;C:\WINDOWS;D:\bea\WEBLOG~1\server\native\win\x64;D:\bea\WEBLOG~1\server\bin;D:\bea\jrockit-jdk1.5.0_24-R28.1.0-4.0.1\jre\bin;D:\bea\jrockit-jdk1.5.0_24-R28.1.0-4.0.1\bin;D:\bea\WEBLOG~1\server\native\win\x64\oci920_8;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files (x86)\ZANTAZ\EAS Client\; -Djava.class.path=D:\bea\patch_weblogic923\profiles\default\sys_manifest_classpath\weblogic_patch.jar;D:\bea\weblogic92\domains\SupplyManager\lib\xercesImpl.jar;D:\bea\weblogic92\domains\SupplyManager\lib\yuicompressor-2.4.2.jar;D:\bea\jrockit-jdk1.5.0_24-R28.1.0-4.0.1\lib\tools.jar;D:\bea\weblogic92\domains\SupplyManager\lib\ojdbc14_10.2.0.4.jar;D:\bea\weblogic92\server\lib\weblogic.jar;D:\bea\weblogic92\domains\SupplyManager\lib\customlogger2.jar;D:\Program Files\wily\WebAppSupport.jar -Dweblogic.system.BootIdentityFile=D:\bea\weblogic92\domains\SupplyManager\servers\System_Managed01\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xgc:gencon -Xms1024m -Xmx1024m -XXcompressedRefs:enable=false -XX:+FlightRecorder -XX:FlightRecorderOptions=defaultrecording=true,disk=true,repository=D:/bea/weblogic92/domains/SupplyManager/jfr,maxage=5m,maxchunksize=10m -XX:StartFlightRecording=filename=system.jfr -XlargePages -XX:+HeapDumpOnCtrlBreak -XX:+HeapDumpOnOutOfMemoryError -Xnohup -Xverbose:gc,gcpause,codegen,opt,codegc -XverboseLog:D:\wls_logs\servers\System\gc.txt -XverboseTimeStamp -Dweblogic.TracingEnabled=true -javaagent:"D:\Program Files\wily\Agent.jar" -Dcom.wily.introscope.agentProfile="D:\Program Files\wily\IntroscopeAgent.profile" -Dcom.wily.introscope.agent.agentName="system-managed01" -XX:+UnlockDiagnosticVMOptions -XX:MaxClassBlockMemory=100M weblogic.Server >
    <Oct 19, 2012 11:01:41 AM> <Info> <NodeManager> <Working directory is "D:\bea\weblogic92\domains\SupplyManager">
    <Oct 19, 2012 11:01:41 AM> <Info> <NodeManager> <Server output log file is "D:\bea\weblogic92\domains\SupplyManager\servers\System_Managed01\logs\System_Managed01.out">

  • ReportApplicationServer (RAS) stuck at starting on BO XI 3.1 SP2

    Greetings,
    We have been facing a problem with the RAS service. The status of the server is stuck on starting and doesn't go to a started state. All other servers start normally
    Our Environment:
    OS: Windows Server 2008
    BO: BOXI 3.1 SP2 Clustered (2 servers)
    CMS Database: Oracle 10G
    Web Tier Components: WebLogic 10.3
    All other BO servers start normally. The problem appears on only one of the clustered servers. The other member of the cluster has not issues.
    We enabled tracing and this is the error part:
    2010/04/06 07:32:56.782|==| | | 9248|9940| |||||||||||||||(.\oscafactory.cpp:748) successful after bind factory
    2010/04/06 07:32:56.782|==| | | 9248|9940| |||||||||||||||(.\rasdtsfactory.cpp:262) CRASDTSFactory::CreateServices() returns successfully
    2010/04/06 07:32:56.782|==| | | 9248|9940| |||||||||||||||OSCASimpleFactory::isDisabled() 1
    2010/04/06 07:32:56.782|==| | | 9248|9940| |||||||||||||||
    TraceLog 2010  4  6 10:32:56.782 9248 9940 (*:0) (.\dts\dts.cpp:2683): CDTSApp::InitInstance(): m_bsCMSMachineName is [ECCBOP201.aramco.com:6400]
    2010/04/06 07:32:56.782|==| | | 9248|9940| |||||||||||||||
    TraceLog 2010  4  6 10:32:56.782 9248 9940 (*:0) (.\dts\dts.cpp:1235): CreateAgent: creating agent=1
    2010/04/06 07:32:56.782|==| | | 9248|9940| |||||||||||||||
    TraceLog 2010  4  6 10:32:56.782 9248 9940 (*:0) (.\dts\dts.cpp:2747): CDTSApp::InitInstance() returns 1
    2010/04/06 07:33:51.715|==| | | 9248|9928| |||||||||||||||CNSClientManager::CheckObjects() : search fails(37) - Transport user error: object with the specified name not found.
    2010/04/06 07:33:51.715|==| | | 9248|9928| |||||||||||||||(.\nsclient.cpp:2151) Failed to resolve object.  Reregister all...
    2010/04/06 07:33:51.825|==| | | 9248|9928| |||||||||||||||(.\nsclient.cpp:2155) succeed.
    2010/04/06 07:33:51.825|==| | | 9248|3324| |||||||||||||||OSCASimpleFactory::isDisabled() 1
    2010/04/06 07:33:51.825|==| | | 9248|3324| |||||||||||||||(.\oscadtsfactory.cpp:231) OSCADTSFactory_impl::newService() throwing because server is disabled: serviceName[Auditing], descriptor[]
    2010/04/06 07:33:53.825|==| | | 9248|8772| |||||||||||||||OSCASimpleFactory::isDisabled() 1
    2010/04/06 07:33:53.825|==| | | 9248|8772| |||||||||||||||(.\oscadtsfactory.cpp:231) OSCADTSFactory_impl::newService() throwing because server is disabled: serviceName[Auditing], descriptor[]
    Notes
    The appliaction crystalras.exe is allowed through the firewall.
    Any ideas?
    Thanks

    We have resolved the problem (minutes after posting it!)
    There are two NIC cards on the sever and apparently that caused the issue.
    Resolution:
    1. Log on to CmcApp
    2. Go to Servers
    3. Go to the properties of the ReportApplicationServer
    4. Under Common Settings:Host Identifiers:IP Addres: Specify the IP of of the primary NIC card of the BO Server.
    5. Save and close
    6. Restart the ReportApplicationServer
    Regards,
    Hassan

  • Virtualized servers get stuck at "Shutting down Windows Modules Installer service ..."

    Hi,
    I have a Windows 2008 R2 (no service pack) server that has been virtualized last summer and since then:
    - Windows Update does not download any updates (it says Cancelled for every update in the Update History)
    - When I reboot the vm, it gets stuck on "Shutting down Windows Modules Installer service ..." and I have to cold-Reset the vm to get it working again.
    I tried running Windows Update Standalone Installer (Windows6.1-KB947821-v20-x64.msu) on the machine, but that gets stuck on "searching for updates"...
    I tried stopping the Windows Update service but that doesn't work either, it says that the service is not responding...
    I'm not sure what to try next, I'd appreciate any pointers.
    Thanks a lot,
    Guillaume

    Hi,     
    Pls try to do the following to reset the whole
    SoftwareDistribution folder:
    1. Stop the windows Updates service. To do this, follow these ste
    a. Click "Start", click"Run", type "services.msc" (without the quotation marks), and
    then click "OK".
    b. Right-click the "windows Updates" service.
    c. Click "Stop". The service will take a moment to stop.
    2.rename this folder(renamed to oldsoftwaredistruibution)
    3. Start the windosw Updates service. To do this, follow these steps
    a. Click "Start", click "Run", type "services.msc" (without the quotation marks), and then click "OK".
    b. Right-click the "Automatic Updates" service, and then click "Start".
    The service will take a moment to start and the folder will be recreated when you try to visit windows update site. You can then delete the folder.
    After all, try to see whether your AU is functioning.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Maybe you are looking for

  • ITunes 7.1 won't start, invalid Win32 application error message comes up

    I repeatedly tried to download iTunes 7.1 for my new iPod nano on my Windows XP, when the download completes and I try to run the program an error message comes up stating that iTunesupdate.exe is not a valid Win32 application...I have tried erasing

  • What is the purpose of GL account in the account assignment tab of PO scree

    hi, in the purchase order screen, in the account assignment tab, there is a field labelled as GL account. May i know what is the purpose of this gl account because as far as i am concerned we need to specify the vendor gl account (in the vendor maste

  • Can't open nef files

    Hi, I am pretty new. On a trial version of Elements 7. When I try to open raw files from my Nikon ( NEF ), I get an error: "Could not complete your request because the file-format module cannot parse the file" I selected the type ( NEF ) in the open

  • Trying to download Fifa 13 via iTunes, but i get some error.

    Trying to download Fifa 13 via iTunes, get error when i have downloaded over 1gb, when trying to resume, it starts from scratch, and it happens several times. Somebody know what to do? It says it is some error with my connection, but my connection is

  • G/L account  is not defined in chart of accounts

    Hello Experts, Can someone solve my problem. I have created an expense account in my Chart of Account (FSP0) and the same COA is assigned to my Co.Cd in OBY6. When I tried to post to this G/L account ( FB60 - Vendor Invoice posting ),  I got the foll