UPSA status stuck in "Starting" state - how to Stop

my UPSA   sttus is starting state, i tried to stop but i am not able to perform this task.
may i know why this is happening. i am in   domain network and AD is configured in my dev.env and  this  box  is a VM with sp 2013, sp d   etc are installed on   win srvr 2012 os

Hi,
The User Profile Synchronization service runs under the farm account. The farm account requires specific permissions to configure profile synchronization, The Farm account must be a member of the Administrators group on the synchronization server. You can
remove this permission after you have configured the User Profile Synchronization service.
The Farm account must be able to log on locally to the synchronization server
The synchronization account for a connection to Active Directory Domain Services (AD DS) must have the following permissions:
It must have Replicate Directory Changes permission on the domain with which you'll synchronize. 
Here are the complete steps
To grant Replicate Directory Changes permission on a domain
On the domain controller, click Start, click Administrative Tools, and then click Active Directory Users and Computers.
In Active Directory Users and Computers, right-click the domain, and then click Delegate Control.
On the first page of the Delegation of Control Wizard, click Next.
On the Users or Groups page, click Add.
Type the name of the synchronization account, and then click OK.
Click Next.
On the Tasks to Delegate page, select Create a custom task to delegate, and then click Next.
On the Active Directory Object Type page, select This folder, existing objects in this folder, and creation of new objects in this folder, and then click Next.
On the Permissions page, in the Permissions box, select Replicating Directory Changes (select Replicate Directory Changes on
Windows Server 2003), and then click Next.
Click Finish.
http://technet.microsoft.com/en-us/library/hh296982.aspx
Please don't forget to mark it answered, if your problem resolved or helpful.

Similar Messages

  • 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

  • Workflows stuck in "Starting" state.

    Workflows have been running fine for awhile.  All workflows are currently stuck in a "Starting" state.  Was finally able to capture this in ULS
    03/20/2014 11:58:23.46  w3wp.exe (0x15AC)                        0x2A98 SharePoint Foundation        
     Workflow Infrastructure        72fv Unexpected AutoStart Workflow: System.ArgumentException: Value does not fall within the expected range.     at Microsoft.SharePoint.Workflow.SPWorkflowActivationProperties..ctor(SPWorkflow
    workflow, String initiationData, Object context)     at Microsoft.SharePoint.Workflow.SPWorkflowManager.StartWorkflowElev(Object context, SPWorkflowAssociation association, DateTime elevationTimeUtc, SPWorkflowEvent startEvent, SPWorkflowRunOptions
    runOptions)     at Microsoft.SharePoint.Workflow.SPWorkflowAutostartEventReceiver.<>c__DisplayClass1.<AutoStartWorkflow>b__0(SPSite superUserSite, SPWeb superUserWeb) 
    Any ideas?
    TIA

    Hi Milo,
    Please check whether you have installed any CUs for SharePoint 2010.
    Please install June 2013 CU or higher for SharePoint 2010, compare the result.
    Here are some similar posts for you to take a look at:
    http://blogs.msdn.com/b/chaun/archive/2013/05/16/if-your-sp2010-workflows-are-stuck-in-the-starting-state.aspx
    http://social.technet.microsoft.com/Forums/sharepoint/en-US/5a6e6e83-b59f-4099-a86f-a07723ff2b98/workflow-stuck-in-starting-state-after-applying-sharepoint-2010-cu-december-2012?forum=sharepointadminprevious
    I hope this helps.
    Thanks,
    Wendy
    Wendy Li
    TechNet Community Support

  • OIM server not running, stuck in starting state

    I have started OIM server through cmd , but its not going to running state, and its stuck to starting only.
    Kindly suggest
    KK

    is there any error?
    try once by deleting temp files in oim_server.
    _saurabh                                                                                                                                                                                   

  • How to restart the stuck BPM ( started state)

    Hi XI experts,
    We need to restart the stuck BPM in XI. Please advise how to do this..
    Thanks in advance.

    Hi Mohan,
    You can directly restart the process by this transaction
    SWF_XI_SWPR
    Check the url
    http://help.sap.com/saphelp_nwpi71/helpdata/EN/44/692b2cb6a93673e10000000a114a6b/content.htm
    if you dont click continue immediately, just execute the transaction and see the BPM. there is a option of Restart workflow
    Regards
    Suraj

  • Timer event doesn't listen to my if else statements how do stop it?

    So I'm building a random generator of just a vector that i imported into flash and everything works just fine, almost. I added a timer to the creation of the vector. I also have some if else statements that are going to govern User Input. I realized that if the UI was initially outside of the parameters i've set it runs fine but once the once the function with the timer starts it never stops regardless of whether or not the UI is in the parameters I set. How do I stop the function when the UI is not what i want it to be?
    Heres my code:
    //initial universal variable declaration
    var kface:Kobbyface;
    var UI:Number;
    var kfacex:Number;
    var kfacey:Number;
    var UIold:Number = 0;
    var timer:Timer = new Timer(200);
    //background rectangle
    graphics.beginFill(0xFFFF00, 1);
    graphics.drawRect(0,65, stage.stageWidth, stage.stageHeight);
    graphics.endFill();
    trace (inputnumber);
    //eventlistener for click
    gobutton.addEventListener(MouseEvent.CLICK, create);
    function create(me:MouseEvent):void {
    UI = Number(inputnumber.text);
    if (isNaN(UI)) {
    errormessages.text = "Kobby only responds to numbers"
    else if (UI > 500) {
    errormessages.text = "You're not ready for that many Kobbys"
    else if (UI < 15) {
    errormessages.text = "Come on you can handle more than that"
    else{
    createfaces();
    //for loop///
    function createfaces ():void {
    ////////timer for face animation///////
    timer.addEventListener(TimerEvent.TIMER, animate);
    timer.start();
    function animate(evt:TimerEvent):void {
    /////keep track of old number/////
    if (UIold != 0) {
    for (var i: int = 1; i<UIold + 1; i++) {
    stage.removeChildAt(1);
        /////assign old number to new number////
    UIold = UI;
    for ( var i:int = 1; i<UI + 1; i++ ) {
    trace( i );
    ////assign values to coordinate varialbes/////
    var kfacex:Number = Math.random() * stage.stageWidth;
    var kfacey:Number = Math.random() * stage.stageHeight + 65;
    //creation of faces///
    kface = new Kobbyface();
    stage.addChild(kface);
    kface.x = kfacex;
    kface.y = kfacey;

    you can apply the stop() method to your timer:
    timer.stop();

  • IMovie 10 starts with computer start-up - how to stop this?

    Ever since the new version of iMovie was released with OS X Mavericks, it starts up every time I boot up my computer. How can I stop this from happening? I couldn't find a setting within the program that controls this.

    When you next  'Shut down' make sure the check box is empty in box that asks if you want to shut down. This will stop any open programmes from opening up during start up.

  • ITunes always starts automatically, how to stop it?

    iTunes for some reason has started to automatically run every time I restart or turn on the iMac.
    I can't find any menus to allow me to change this in iTunes preferences. Is there another area I need to look in?

    I too was having a similar problem recently. My 1 1/2 old kid likes to play with the mouse and keyboard when no one is looking and I bet she did this accidently.LOL.
    Thanks for the info. I didn't know what was going on but I now know.

  • 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">

  • Workflows remain in starting state

    There is a production sharepoint site and qa sharepoint site. The workflows were made and tested in the qa site. I then made templates of all the list associated and added them to the production sharepoint site. After that I recreated all the workflows because
    they were list workflows, and set them to go off when an item is created. However when ever an item is created all the workflows remain in a starting state and no amount of time changes it, for I still have a workflow starting from 2 days ago. What do I do
    to resolve this problem? As well this will all made using SPD 2010 and sharepoint 2010

    Hi,
    see whether these links helps you -
    http://blogs.msdn.com/b/chaun/archive/2013/05/16/if-your-sp2010-workflows-are-stuck-in-the-starting-state.aspx
    http://social.technet.microsoft.com/Forums/sharepoint/en-US/5a6e6e83-b59f-4099-a86f-a07723ff2b98/workflow-stuck-in-starting-state-after-applying-sharepoint-2010-cu-december-2012?forum=sharepointadminprevious
    Hope this helps!
    Ram - SharePoint Architect
    Blog - SharePointDeveloper.in
    Please vote or mark your question answered, if my reply helps you

  • How to stop Dragon Gaming Center's auto-start?

    Dragon Gaming Center is a good monitor, but i only want to start it before gaming. i cant find anything about Dragon Gaming Center in msconfig.exe and services.msc, but it already can auto-start. How to stop it?

    Nevermind, found it and fixed it.
    After some googling around further   I found this page which said it was started by a scheduled task. ( second result was shouldiremoveit site, but I can't post external links here )
    So I went to taskscheduler and found it through the active task list at the bottom. (make sure you run it as administrator if you want to change it)
    It is called "MSI_Dragon Gaming Center" and engages at logon. So I thought, "Well, why not simply disable it". Well, as it happens, the taskscheduler gets a fit and looses it's marbles (seriously! scheduled task lists seem to get flushed) when you try to disable it (right click on it for context menu) because somehow it was assigned by MSI to be done by an incorrect user, named "User" or "Users". I can't remember exactly anymore. The former does not exist by default so some MSI dev might have forgotten to replace  a systemvariable reference. The latter is a user-group, not a user! It may have caused the fault because I have a dutch language pack, and that group is named differently on my system. It's aka "Built-In\Users" in english. Anyway, correcting this was the fix that allows it to be disabled/edited.
    So, I opened the properties of the task (again right click for context menu) and changed the executing user to my personal useraccount. When that succeeded I was able to disable the task succesfully, and it didn't start at  login anymore.

  • How to stop FF checking compatibility of add-ons every time it starts.

    Since upgrading to 4.0.1, FF checks compatibility of add-ons every time it starts. How to stop this?

    Did you delete prefs.js in the [http://kb.mozillazine.org/Profile_folder_-_Firefox Firefox Profile Folder]?
    * Help > Troubleshooting Information > Profile Directory: Open Containing Folder
    This can also be a problem with the file(s) that store the extensions registry.
    Delete the files extensions.* (extensions.sqlite, extensions.rdf, extensions.cache, extensions.ini) and compatibility.ini in the Firefox [[Profiles|profile folder]] to reset the extensions registry. New files will be created when required.
    See "Corrupt extension files": http://kb.mozillazine.org/Unable_to_install_themes_or_extensions
    If you see disabled, not compatible, extensions in "Tools > Add-ons > Extensions" then click the "Find Updates" button (Firefox 4: click the Tools button at the left side of the Search Bar) to do a compatibility check.

  • Stuck in a starting state

    Hi,
    I'm using WebLogic 9.2.2. I have a single server in my cluster. The server is perpetually stuck in a "STARTING" state (http://screencast.com/t/GMDTihmVYD). I'm not sure how it got there, but when I visit the Shutdown -> Force Shutdown Now option, although I'm told the request was sent to the server, the server remains in this ambiguous "STARTING" state.
    How do I break out of this state and restart my server?
    Thanks, - Dave

    On your advice, logged in as etsbea, I ran the command, filtered with java and got:
    etsbea 9948 49.1 2.9562912464808 ? O Oct 13 58:22 /export/third-party/etsbea/product/wls_9.2.2/jdk1.5.0_12/jre/bin/java -Dweblogic.Name=btsgui-ms-1 -Djava.security.policy=/export/third-party/etsbea/product/wls_9.2.2/weblogic92/server/lib/weblogic.policy -Dweblogic.management.server=http://rhonti:17001 -Djava.library.path=/export/third-party/etsbea/product/wls_9.2.2/jdk1.5.0_12/jre/lib/sparc/client:/export/third-party/etsbea/product/wls_9.2.2/jdk1.5.0_12/jre/lib/sparc:/export/third-party/etsbea/product/wls_9.2.2/jdk1.5.0_12/jre/../lib/sparc:/export/third-party/etsbea/product/wls_9.2.2/patch_weblogic922/profiles/default/native:/export/third-party/etsbea/oracle/product/10.2.0/lib:/export/third-party/etsbea/home/etsbea/netegrity/sdk/bin:/opt/GCC3.3.2/lib/:/opt/GCC3.3.2/lib/sparcv9/:/usr/lib/:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/server/native/solaris/sparc:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/server/native/solaris/sparc/oci920_8:/export/third-party/etsbea/product/netegrity_6.0.2/sdk/bin:/usr/lib -Djava.class.path=/export/third-party/etsbea/application_conf/wls_9.2.2/btsgui_conf:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/server/lib/weblogic.jar:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/platform/lib/p13n/p13n-schemas.jar:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/platform/lib/p13n/p13n_common.jar:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/platform/lib/p13n/p13n_system.jar:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/platform/lib/wlp/netuix_common.jar:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/platform/lib/wlp/netuix_schemas.jar:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/platform/lib/wlp/netuix_system.jar:.:/export/third-party/etsbea/product/wls_9.2.2/jdk1.5.0_12/lib/tools.jar -Dweblogic.system.BootIdentityFile=/export/third-party/etsbea/product/wls_9.2.2/user_projects/domains/nps_pt_92/servers/btsgui-ms-1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xms256m -Xmx256m -XX:NewSize=64m -XX:MaxNewSize=64m -XX:SurvivorRatio=4 -Dweblogic.wsee.useRequestHost=true weblogic.Server
    etsbea 9171 1.3 4.0821424652216 ? S Oct 13 46:17 /export/third-party/etsbea/product/wls_9.2.2/jdk1.5.0_12/bin/java -server -Xms256m -Xmx512m -XX:MaxPermSize=128m -da -Dplatform.home=/export/third-party/etsbea/product/wls_9.2.2/weblogic92 -Dwls.home=/export/third-party/etsbea/product/wls_9.2.2/weblogic92/server -Dwli.home=/export/third-party/etsbea/product/wls_9.2.2/weblogic92/integration -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/export/third-party/etsbea/product/wls_9.2.2/patch_weblogic922/profiles/default/sysext_manifest_classpath -D_Offline_FileDataArchive=true -Dweblogic.Name=npsadmin -Djava.security.policy=/export/third-party/etsbea/product/wls_9.2.2/weblogic92/server/lib/weblogic.policy weblogic.Server
    etsbea 18855 0.3 2.5579448398064 ? S Oct 14 7:00 /export/third-party/etsbea/product/wls_9.2.2/jdk1.5.0_12/jre/bin/java -Dweblogic.Name=npsgui-ms-1 -Djava.security.policy=/export/third-party/etsbea/product/wls_9.2.2/weblogic92/server/lib/weblogic.policy -Dweblogic.management.server=http://rhonti:17001 -Djava.library.path=/export/third-party/etsbea/product/wls_9.2.2/jdk1.5.0_12/jre/lib/sparc/client:/export/third-party/etsbea/product/wls_9.2.2/jdk1.5.0_12/jre/lib/sparc:/export/third-party/etsbea/product/wls_9.2.2/jdk1.5.0_12/jre/../lib/sparc:/export/third-party/etsbea/product/wls_9.2.2/patch_weblogic922/profiles/default/native:/export/third-party/etsbea/oracle/product/10.2.0/lib:/export/third-party/etsbea/home/etsbea/netegrity/sdk/bin:/opt/GCC3.3.2/lib/:/opt/GCC3.3.2/lib/sparcv9/:/usr/lib/:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/server/native/solaris/sparc:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/server/native/solaris/sparc/oci920_8:/export/third-party/etsbea/product/netegrity_6.0.2/sdk/bin:/usr/lib -Djava.class.path=/export/third-party/etsbea/application_conf/wls_9.2.2/nps_gui_conf:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/server/lib/weblogic.jar:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/platform/lib/p13n/p13n-schemas.jar:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/platform/lib/p13n/p13n_common.jar:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/platform/lib/p13n/p13n_system.jar:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/platform/lib/wlp/netuix_common.jar:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/platform/lib/wlp/netuix_schemas.jar:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/platform/lib/wlp/netuix_system.jar:.:/export/third-party/etsbea/product/wls_9.2.2/jdk1.5.0_12/lib/tools.jar -Dweblogic.system.BootIdentityFile=/export/third-party/etsbea/product/wls_9.2.2/user_projects/domains/nps_pt_92/servers/npsgui-ms-1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xms256m -Xmx256m -XX:NewSize=128m -XX:MaxNewSize=128m -XX:SurvivorRatio=4 -Dweblogic.wsee.useRequestHost=true -XX:+HeapDumpOnOutOfMemoryError -D_Offline_FileDataArchive=true -Dweblogic.connector.ConnectionPoolProfilingEnabled=false -Dcom.bea.wlw.netui.disableInstrumentation=true weblogic.Server
    etsbea 9474 0.3 0.622793689408 ? S Oct 13 8:51 /export/third-party/etsbea/product/wls_9.2.2/jdk1.5.0_12/bin/java -client -Xms32m -Xmx200m -XX:MaxPermSize=128m -Xverify:none -Djava.security.policy=/export/third-party/etsbea/product/wls_9.2.2/weblogic92/server/lib/weblogic.policy -Dweblogic.nodemanager.javaHome=/export/third-party/etsbea/product/wls_9.2.2/jdk1.5.0_12 -DListenPort=11555 weblogic.NodeManager -v
    etsbea 16582 0.2 2.5641048413024 ? S Oct 14 6:04 /export/third-party/etsbea/product/wls_9.2.2/jdk1.5.0_12/jre/bin/java -Dweblogic.Name=nps-prov-ws-ms-1 -Djava.security.policy=/export/third-party/etsbea/product/wls_9.2.2/weblogic92/server/lib/weblogic.policy -Dweblogic.management.server=http://rhonti:17001 -Djava.library.path=/export/third-party/etsbea/product/wls_9.2.2/jdk1.5.0_12/jre/lib/sparc/client:/export/third-party/etsbea/product/wls_9.2.2/jdk1.5.0_12/jre/lib/sparc:/export/third-party/etsbea/product/wls_9.2.2/jdk1.5.0_12/jre/../lib/sparc:/export/third-party/etsbea/product/wls_9.2.2/patch_weblogic922/profiles/default/native:/export/third-party/etsbea/oracle/product/10.2.0/lib:/export/third-party/etsbea/home/etsbea/netegrity/sdk/bin:/opt/GCC3.3.2/lib/:/opt/GCC3.3.2/lib/sparcv9/:/usr/lib/:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/server/native/solaris/sparc:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/server/native/solaris/sparc/oci920_8:/export/third-party/etsbea/product/netegrity_6.0.2/sdk/bin:/usr/lib -Djava.class.path=/export/third-party/etsbea/application_conf/wls_9.2.2/nps_provisioning_ws_conf:/export/third-party/etsbea/product/wls_9.2.2/patch_weblogic922/patch_jars/CR359539_920MP2.jar:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/server/lib/weblogic.jar:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/platform/lib/p13n/p13n-schemas.jar:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/platform/lib/p13n/p13n_common.jar:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/platform/lib/p13n/p13n_system.jar:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/platform/lib/wlp/netuix_common.jar:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/platform/lib/wlp/netuix_schemas.jar:/export/third-party/etsbea/product/wls_9.2.2/weblogic92/platform/lib/wlp/netuix_system.jar:.:/export/third-party/etsbea/product/wls_9.2.2/jdk1.5.0_12/lib/tools.jar -Dweblogic.system.BootIdentityFile=/export/third-party/etsbea/product/wls_9.2.2/user_projects/domains/nps_pt_92/servers/nps-prov-ws-ms-1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xms256m -Xmx256m -XX:NewSize=128m -XX:MaxNewSize=128m -XX:SurvivorRatio=2 -XX:MaxPermSize=128m -XX:PermSize=128m -verbose:gc -XX:+PrintGCTimeStamps -XX:+PrintGCDetails -XX:+PrintHeapAtGC -XX:+HeapDumpOnOutOfMemoryError -D_Offline_FileDataArchive=true -Dweblogic.connector.ConnectionPoolProfilingEnabled=false -Dcom.bea.wlw.netui.disableInstrumentation=true -Dweblogic.wsee.useRequestHost=true -Dweblogic.wsee.security.clock.skew=28800000 -Dweblogic.wsee.security.delay.max=28800000 weblogic.Server
    etsbea 9255 0.1 0.414619251752 ? S Oct 13 1:18 /export/third-party/etsbea/bea/jdk142_05/bin/java -client -Xms32m -Xmx200m -Xverify:none -Djava.security.policy=/export/third-party/etsbea/bea/weblogic81/server/lib/weblogic.policy -Dweblogic.nodemanager.javaHome=/export/third-party/etsbea/bea/jdk142_05 weblogic.NodeManager
    etsbea 9540 0.1 0.422755263480 ? S Oct 13 1:06 /export/third-party/etsbea/product/wls_9.2.2/jdk1.5.0_12/bin/java -client -Xms32m -Xmx200m -XX:MaxPermSize=128m -Xverify:none -Djava.security.policy=/export/third-party/etsbea/product/wls_9.2.2/weblogic92/server/lib/weblogic.policy -Dweblogic.nodemanager.javaHome=/export/third-party/etsbea/product/wls_9.2.2/jdk1.5.0_12 -DListenPort=5566 weblogic.NodeManager -v
    etsbea 26464 0.0 0.0 1280 1032 pts/2 S 12:40:21 0:00 grep java
    etsbea 18608 0.0 0.1227296 9480 ? S Oct 14 0:00 /export/third-party/etsbea/product/wls_9.2.2/jdk1.5.0_12/bin/java -client -Xms32m -Xmx200m -XX:MaxPermSize=128m -Xverify:none -Djava.security.policy=/export/third-party/etsbea/product/wls_9.2.2/weblogic92/server/lib/weblogic.policy -Dweblogic.nodemanager.javaHome=/export/third-party/etsbea/product/wls_9.2.2/jdk1.5.0_12 -DListenPort=11555 weblogic.NodeManager -v
    etsbea 25011 0.0 0.1227296 9648 ? S 09:04:31 0:00 /export/third-party/etsbea/product/wls_9.2.2/jdk1.5.0_12/bin/java -client -Xms32m -Xmx200m -XX:MaxPermSize=128m -Xverify:none -Djava.security.policy=/export/third-party/etsbea/product/wls_9.2.2/weblogic92/server/lib/weblogic.policy -Dweblogic.nodemanager.javaHome=/export/third-party/etsbea/product/wls_9.2.2/jdk1.5.0_12 -DListenPort=11555 weblogic.NodeManager -v
    Hard for me to figure out what is going on with the above. I definitely appreciate any further info, - Dave

  • CMS server stuck at "Starting" status

    CMS server stuck at "Starting" status. I cannot stop it and cannot restart it. I even rebooted the NT box several times and it didn't help. Any suggestions? I am running BO XI R2 on Windows NT box.
    The message from Events Viewer is: CMS is unstable and will shut down immediately. Reason: Database access error. Reason ORA-24369: required callbacks not registered for one or more  bind handles
    Edited by: Michael Burgoyne on Jun 4, 2009 5:50 PM

    Here is the meaning of the error :
    ORA-24369:
    required callbacks not registered for one or more bind handles
    Cause:      No callbacks have been registered for one or more of the bind handles which are part of the
    RETURNING clause.
    Action:      The bind handles which are to receive data in a DML statememt with a RETURNING clause must have their mode set as DATA_AT_EXEC and callback functions must be registered for these bind handles using OCIBindDynamic.
    It sounds to me that when DB was moved from one server to another CMS DB was either corrupted or not migrated properly or new DB has different settings compared to original.
    This is definately on the DB side.
    How exactly this move was accomplished ?
    How was R2 system repointed to new DB location ?
    Do you still have original "pre-move" CMS DB ?

  • 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

Maybe you are looking for

  • Downloaded new OS and having trouble with wifi, bluetooth Facebook and Skype performanc​e

    Dowloaded 10.2.1.537 When I first loaded this it had a lot of trouble finding my Wifi again and would disengage.  Problem went away after a few hours but it recurred this am.  Also affected Facebook. Skype is loading more slowly and jumps to a black

  • Preview in browser - Firefox / File not found

    Specs: OS X 10.4.7 Dreamweaver 8.0.2 Firefox 1.5.0.1 I (and my whole office) am having a major problem. We all work directly from files on our osx server. When working in Dreamweaver and trying to "Preview in browser" with Firefox 1.5 we get a "File

  • Migration from Jdeveloper 11g r1 to 11g r2 problem

    Hi all I have a project initially created in Jdeveloper 11g r1 after migrating it to Jdeveloper 11g r2 i tried to replace lookup ejb invocation to dependency injection. So i used @EJB annotation in my managed bean. I'm shure there could be no mistake

  • How to get the connection string at runtime

    Hi, I'm using Forms6i. I'm using EXEC_SQL to execute a dynamic sql in my form. I need connection string for that . But i cannot give it hardcodingly. Is there any form's properties to get the database connection string, to which the form is connected

  • How to Enable Signal Quality (%)

    Good Day, Checked the manuals and forum to no avail. My Cisco 1200 AP is displaying Signal Strength (dBm) but not Signal Quality (%). Is there something I need to do to enable this, or is it client specific? Thanks for the help!