SPID stuck in KILLED/ROLLBACK state

Hi All,
SQL Server 2008R2 (10.50.4279) I've noticed a process that hungs, the wait type was "PREEMPTIVE_OS_PIPEOS" and the process itself was a SQL Server Agent job.
First thing is that in Job Activity monitor I could not see any job running.
I've tried to kill the spid from Activity monitor but now the SPID is stuck in "KILLED/ROLLBACK" state, and the wait is always "PREEMPTIVE_OS_PIPEOS".
I've checked that the job executes a stored procedure that invokes sp_send_dbmail with an attachment, I've tried to restart the SQL Server Agent, but the spid is always there.
How can I kill the process?

I can't reboot a production server so easily, come on!
Then you will have to live with it. The wait type PREEMPTIVE_OS_PIPEOPS means that the process is performing an OS call to something related to PIPEOPS. SQL Server employs cooperative multi-tasking. That is, processes yields everyone once in a while to let
other other processes run. And that's when they check if they have been killed. But if the process is running an OS call, they are outside the realm of SQL Server and will never see the kill flag.
What you can try is to see if there is some other activity on the machine that appears to be related to this job. For instance, the process may be running xp_cmdshell and be stuck there.
Erland Sommarskog, SQL Server MVP, [email protected]

Similar Messages

  • Session went Killed / Rollback state in sql server

    Hi ,
    I have sql server 2008 on my infra.
    There one backup job was running more than a day, so i killed the session and it went to killed/rollback state.
    And it was consuming more resources in terms of CPU and Disk I/O. I have restarted the sql server service to free the resources.
    I just want to know,
    Is there any way to clear the session without restarting the sql services ?
    Or Is there any way to free the resources on the server or terminate the session ?
    Regards,
    Vinodh Selvaraj

    Is there any way to clear the session without restarting the sql services ?
    Or Is there any way to free the resources on the server or terminate the session ?
    Before killing(although that was not a good option) did you noted what was the wait type from sys.dm_exec_requests. Wait type would have told you why and on what resource it was waiting.
    A rollback for backup should be easy a rollback for query is more complex and yes rollback can take more time and resource than a original query to run if you killed it in between you have no option but to wait.
    Before killing you should have run
    Kill SPID with statusonly to know tentative time required to rollback. Start backup again and see the waitype and revert
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • Agent stuck in the login state ..

    Hi,
    one of agent is stuck in the login state . We are using the UCCE setup version-8.5. when i was trying to kill this agent session through PG CMD line (using procmon -->>>resetas Agent ID ) its showing "Agent already logged out or pending log out. AgentID=41332752" , but after doing this that agent not able to login on any Ext. error "showing this agent is alrady loged on".   Any one kindly help me to come out from this issue. We are using CTI toll kit for agent login.

    Hi,
    If you get this message error "showing this agent is alrady loged on" only for one Extension.
    Then you can deassociate and associate the device in th PG user for that phone.
    I hope the issue you are talkin about the AgentID not able to login to any of the extension.
    Then check in the t_Agent_Real_Time table for this agent's current state and the extension.
    Login using the agentID in that extension and logout.
    Regards,
    Senthil

  • 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

  • Updates getting stuck in V2 processed state

    Hi,
    In our ERP production system EP0, update entries are getting stuck
    in 'V2 Processed' state.
    Details of the same show that the collective run state is in initial
    state for functional module 'MCEX_UPDATE_03'.
    Please find the attached screenshot of details.
    These updates are gettin stuck for specific transactions like MIGO.
    We have already tried running the report RSM13005 but it has not helped.
    Please look into it urgently as the system is a production system.
    Thanks in advance.
    Regards,
    Suresh
    Edited by: suresh k on Sep 26, 2008 2:38 PM

    Hi
    As you checked in transaction SM13 they are stucked in Initial state. There was various states associated with the update like INIT and ERR.
    What is INIT status:
    Update records which have not yet been processed have the status INIT or AUTO. INIT refers to a complete update record (header, function module call of update and data elements are present), which has not yet been processed however.
    What to do: SM13 -> Update records -> Update -> All records/Single
    you can set the update administration so that all records with the status 'INIT' or AUTO' (all update records which have not yet been updated) are processed (as far as possible).
    Warnings: please check with the user who posted the updates in the first place - make sure that they have not already reposted the update manually. If you are in doubt, please re-enter the data manually rather than using this update function.
    Hope this helps!!
    Kind Regards
    Esha
    Edited by: Esha Rajpal on Sep 30, 2008 5:06 AM

  • How to create rollback statements automatically

    Hi People
    I need to write a script which can generate the ROLLBACK statements for the IMPLEMENTATIONS(Create table, view, index, package, trigger etc Insert table, update table, delete table, Grant etc - which means that implementation could be anything) .
    Is there is anyway that I can create or generate corresponding ROLLBACK statements for each statement that i exceute on my database?
    Basically there could be a list of operations that I will do and later on I would like to bring the database back to where it was prior to the implementation.

    Welcome to the forum!
    Whenever you post provide your 4 digit Oracle version (result of SELECT * FROM V$VERSION).
    >
    Is there is anyway that I can create or generate corresponding ROLLBACK statements for each statement that i exceute on my database?
    Basically there could be a list of operations that I will do and later on I would like to bring the database back to where it was prior to the implementation.
    >
    You could use Oracle's FLASHBACK DATABASE funtionality. See Using Flashback Database and Restore Points in the backup and recovery doc
    http://docs.oracle.com/cd/E11882_01/backup.112/e10642/flashdb.htm
    Chapter 16 of that doc shows how to do it - Performing Flashback and Database Point-In-Time Recovery
    http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmflash.htm

  • PEAP clients stuck in the 8021X_REQD state

    Hi,
    I've got complaining for lots of PEAP clients not connecting to wireless network. Everything was working fine before. I logged into WLC and found out these clients are associated but stuck in the 8021X_REQD state. I checked our Radius server and couldn't find the failed log. The below message shows the debug for a client 00:0b:6b:24:66:55 and the attachment is the client info shown on the WLC. Please help. Thanks.
    (vau-cr-wlc4402-1) >debug client 00:0b:6b:24:66:55
    (vau-cr-wlc4402-1) >Mon Aug  8 15:40:53 2011: 00:0b:6b:24:66:55 802.1x 'timeoutEvt' Timer expired for station 00:0b:6b:24:66:55
    Mon Aug  8 15:40:53 2011: 00:0b:6b:24:66:55 Retransmit 1 of EAP-Request (length 127) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:23 2011: 00:0b:6b:24:66:55 Association received from mobile on AP 00:1c:57:8b:34:e0
    Mon Aug  8 15:41:23 2011: 00:0b:6b:24:66:55 STA - rates (8): 130 132 139 150 140 18 152 36 176 72 96 108 0 0 0 0
    Mon Aug  8 15:41:23 2011: 00:0b:6b:24:66:55 STA - rates (12): 130 132 139 150 140 18 152 36 176 72 96 108 0 0 0 0
    Mon Aug  8 15:41:23 2011: 00:0b:6b:24:66:55 Processing RSN IE type 48, length 20 for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:23 2011: 00:0b:6b:24:66:55 Received RSN IE with 0 PMKIDs from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:23 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Initializing policy
    Mon Aug  8 15:41:23 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Change state to AUTHCHECK (2) last state 8021X_REQD (3)
    Mon Aug  8 15:41:23 2011: 00:0b:6b:24:66:55 10.115.148.80 AUTHCHECK (2) Change state to 8021X_REQD (3) last state 8021X_REQD (3)
    Mon Aug  8 15:41:23 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Plumbed mobile LWAPP rule on AP 00:1c:57:8b:34:e0
    Mon Aug  8 15:41:23 2011: 00:0b:6b:24:66:55 apfPemAddUser2 (apf_policy.c:209) Changing state for mobile 00:0b:6b:24:66:55 on AP 00:1c:57:8b:34:e0 from Associated to Associated
    Mon Aug  8 15:41:23 2011: 00:0b:6b:24:66:55 Stopping deletion of Mobile Station: (callerId: 48)
    Mon Aug  8 15:41:23 2011: 00:0b:6b:24:66:55 Sending Assoc Response to station on BSSID 00:1c:57:8b:34:e0 (status 0)
    Mon Aug  8 15:41:23 2011: 00:0b:6b:24:66:55 apfProcessAssocReq (apf_80211.c:3838) Changing state for mobile 00:0b:6b:24:66:55 on AP 00:1c:57:8b:34:e0 from Associated to Associated
    Mon Aug  8 15:41:23 2011: 00:0b:6b:24:66:55 dot1x - moving mobile 00:0b:6b:24:66:55 into Connecting state
    Mon Aug  8 15:41:23 2011: 00:0b:6b:24:66:55 Sending EAP-Request/Identity to mobile 00:0b:6b:24:66:55 (EAP Id 1)
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL START from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 dot1x - moving mobile 00:0b:6b:24:66:55 into Connecting state
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP-Request/Identity to mobile 00:0b:6b:24:66:55 (EAP Id 2)
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Received Identity Response (count=2) from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 EAP State update from Connecting to Authenticating for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 dot1x - moving mobile 00:0b:6b:24:66:55 into Authenticating state
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=204) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 WARNING: updated EAP-Identifer 2 ===> 204 for STA 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 204)
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 204, EAP Type 25)
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=205) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 205)
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 205, EAP Type 25)
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=206) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 206)
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 206, EAP Type 25)
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=207) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 207)
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 207, EAP Type 25)
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=208) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 208)
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 208, EAP Type 25)
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=209) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 209)
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 209, EAP Type 25)
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=210) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 210)
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 210, EAP Type 25)
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=211) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 211)
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 211, EAP Type 25)
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=212) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 212)
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 212, EAP Type 25)
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=213) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 213)
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 213, EAP Type 25)
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=214) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 214)
    Mon Aug  8 15:42:04 2011: 00:0b:6b:24:66:55 802.1x 'timeoutEvt' Timer expired for station 00:0b:6b:24:66:55
    Mon Aug  8 15:42:04 2011: 00:0b:6b:24:66:55 Retransmit 1 of EAP-Request (length 127) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Association received from mobile on AP 00:1c:57:8b:0d:40
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 STA - rates (8): 130 132 139 150 140 18 152 36 176 72 96 108 0 0 0 0
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 STA - rates (12): 130 132 139 150 140 18 152 36 176 72 96 108 0 0 0 0
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Processing RSN IE type 48, length 20 for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Received RSN IE with 0 PMKIDs from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Deleted mobile LWAPP rule on AP [00:1c:57:8b:34:e0]
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Updated location for station old AP 00:00:00:00:00:00-0, new AP 00:1c:57:8b:0d:40-0
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Initializing policy
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Change state to AUTHCHECK (2) last state 8021X_REQD (3)
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 10.115.148.80 AUTHCHECK (2) Change state to 8021X_REQD (3) last state 8021X_REQD (3)
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Plumbed mobile LWAPP rule on AP 00:1c:57:8b:0d:40
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 apfPemAddUser2 (apf_policy.c:209) Changing state for mobile 00:0b:6b:24:66:55 on AP 00:1c:57:8b:0d:40 from Associated to Associated
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Stopping deletion of Mobile Station: (callerId: 48)
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Sending Assoc Response to station on BSSID 00:1c:57:8b:0d:40 (status 0)
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 apfProcessAssocReq (apf_80211.c:3838) Changing state for mobile 00:0b:6b:24:66:55 on AP 00:1c:57:8b:0d:40 from Associated to Associated
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 dot1x - moving mobile 00:0b:6b:24:66:55 into Connecting state
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP-Request/Identity to mobile 00:0b:6b:24:66:55 (EAP Id 1)
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Received Identity Response (count=1) from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 EAP State update from Connecting to Authenticating for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 dot1x - moving mobile 00:0b:6b:24:66:55 into Authenticating state
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=153) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 WARNING: updated EAP-Identifer 1 ===> 153 for STA 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 153)
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 153, EAP Type 25)
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=154) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 154)
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response packet with mismatching id (currentid=154, eapid=153) from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 154, EAP Type 25)
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=155) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 155)
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 155, EAP Type 25)
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=156) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 156)
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 156, EAP Type 25)
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=157) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 157)
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 157, EAP Type 25)
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=158) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 158)
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 158, EAP Type 25)
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=159) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 159)
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 159, EAP Type 25)
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=160) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 160)
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 160, EAP Type 25)
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=161) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 161)
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 161, EAP Type 25)
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=162) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 162)
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 162, EAP Type 25)
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=163) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 163)
    Mon Aug  8 15:43:03 2011: 00:0b:6b:24:66:55 802.1x 'timeoutEvt' Timer expired for station 00:0b:6b:24:66:55
    Mon Aug  8 15:43:03 2011: 00:0b:6b:24:66:55 Retransmit 1 of EAP-Request (length 127) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:33 2011: 00:0b:6b:24:66:55 802.1x 'timeoutEvt' Timer expired for station 00:0b:6b:24:66:55
    Mon Aug  8 15:43:33 2011: 00:0b:6b:24:66:55 Retransmit 2 of EAP-Request (length 127) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Association received from mobile on AP 00:1c:57:8b:0d:40
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 STA - rates (8): 130 132 139 150 140 18 152 36 176 72 96 108 0 0 0 0
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 STA - rates (12): 130 132 139 150 140 18 152 36 176 72 96 108 0 0 0 0
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Processing RSN IE type 48, length 20 for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Received RSN IE with 0 PMKIDs from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Initializing policy
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Change state to AUTHCHECK (2) last state 8021X_REQD (3)
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 10.115.148.80 AUTHCHECK (2) Change state to 8021X_REQD (3) last state 8021X_REQD (3)
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Plumbed mobile LWAPP rule on AP 00:1c:57:8b:0d:40
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 apfPemAddUser2 (apf_policy.c:209) Changing state for mobile 00:0b:6b:24:66:55 on AP 00:1c:57:8b:0d:40 from Associated to Associated
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Stopping deletion of Mobile Station: (callerId: 48)
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Sending Assoc Response to station on BSSID 00:1c:57:8b:0d:40 (status 0)
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 apfProcessAssocReq (apf_80211.c:3838) Changing state for mobile 00:0b:6b:24:66:55 on AP 00:1c:57:8b:0d:40 from Associated to Associated
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 dot1x - moving mobile 00:0b:6b:24:66:55 into Connecting state
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP-Request/Identity to mobile 00:0b:6b:24:66:55 (EAP Id 1)
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Received Identity Response (count=1) from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 EAP State update from Connecting to Authenticating for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 dot1x - moving mobile 00:0b:6b:24:66:55 into Authenticating state
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=174) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 WARNING: updated EAP-Identifer 1 ===> 174 for STA 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 174)
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 174, EAP Type 25)
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=175) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 175)
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 175, EAP Type 25)
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=176) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 176)
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 176, EAP Type 25)
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=177) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 177)
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 177, EAP Type 25)
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=178) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 178)
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 178, EAP Type 25)
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=179) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 179)
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 179, EAP Type 25)
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=180) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 180)
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 180, EAP Type 25)
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=181) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 181)
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 181, EAP Type 25)
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=182) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 182)
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 182, EAP Type 25)
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=183) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 183)
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 183, EAP Type 25)
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=184) for mobile 00:0b:6b:24:66:55
    Mon Aug  8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 184)
    Mon Aug  8 15:44:07 2011: 00:0b:6b:24:66:55 802.1x 'timeoutEvt' Timer expired for station 00:0b:6b:24:66:55
    Mon Aug  8 15:44:07 2011: 00:0b:6b:24:66:55 Retransmit 1 of EAP-Request (length 127) for mobile 00:0b:6b:24:66:55
    (vau-cr-wlc4402-1) >debug disable-all

    Hi,
    Check the username/password database on the AD if ur using one or check if the AD is integrated correctly with the IAS or  the ACS.
    Issue either on the IAS or ACS (RADIUS server) , the WLC is waiting for the response from the RADIUS.
    Regards
    Surendra

  • Messages gets stuck up in active state

    Hi ,
    In our production environment, we are facing strange issues for the past 1 week.
    Issue 1:
    Messages gets stuck up in active state. In our message tracking mechanism ,the status is successfully sent to destination party. The message should not hold up in active state in first place?
    If we restart the Host instance, it is creating duplicate and processing it which is creating misssing ICR issue.
    Per day message flow-200 messages
    Please suggest ?
    Kind Regards,
    Giri.a
    girishkumar.a

    Hi Girish, 
    I believe OFTP adapter is not native adapter(in box) for BizTalk Server.
    So, is there any logging mechanism in OFTP adapter?
    Also, can we connect to the FTP server using some other tool like Filezilla etc. If other 3rd party products are also not able to connect to this server then we can say that its not a BizTalk issue.
    Thanks,
    Prashant
    Please mark this post accordingly if it answers your query or is helpful.

  • Oracle 9i - Is there any way to trace the amount of rollback statements ?

    Hi,
    we're running Oracle 9.2.0.5.0 and we would need to monitor the amount of rollback statements executed on a specific table.
    Turning on traces for "set events '10046 trace name context forever, level 1'" would be too much invasive given the current load of the system so that was wondering if there was any quicker way to do that.
    Thanks in advance!
    Mike

    Did not want to raise another issue :)
    We have a few huge tables which we need to monitor in terms of activities so that we're using triggers to update some oracle sequences keeping track of the action performed on them.
    basically the trigger only increase the sequence value.
    CREATE OR REPLACE TRIGGER xxx_Summary_Trigger
    AFTER INSERT OR UPDATE or delete ON xxx
    FOR EACH ROW
    declare dummy number(10);
    BEGIN
         IF :New.xxx_Status = 'used' THEN
              SELECT used_plus.nextval into dummy from dual;
         ELSIF :New.Card_Status = 'activated' THEN
              SELECT activated_plus.nextval into dummy from dual;
         END IF;
         IF :Old.xxx_Status = 'used' THEN
              SELECT used_minus.nextval into dummy from dual;
         ELSIF :Old.xxx_Status = 'activated' THEN
              SELECT activated_minus.nextval into dummy from dual;
         END IF;
    END;
    So that each time the xxx_Status is updated we have an updated sequence (nocache) which allows us to get the overall distribution without a long scan on the table (hosting more than 200M records).
    I know triggers are not the best way to approach, not to mention they fire before a commit, so that in case of a rollback the resulting sequence would be showing a wrong value.
    But this was only a quick and dirt approach, which works fine for the time being. I just wanted to confirm the inconsistencies we are encountering are due to some rollbacks which mislead the trigger, that's why I was interested in getting a stat on the rollback statement execution.
    We get discrepancies every now and then, so that leaving traces on for a long time may be disruptive.
    Thanks!
    Mike

  • Sync Process stuck on the Process State

    This morning i check the Sync status like every morning and find out this issue:
    Sync failed with the exception "Error in RelationalProviderProxy.ExecuteAndRetryServiceOperation, Method: Void <BeginSession>b__0(), CurrentTimeout: 60 Exception
    Details: System.ServiceModel.Security.MessageSecurityExceptionThe security timestamp is invalid because its creation time ('2014-10-27T20:43:13.669Z') is in the future. Current time is '2014-10-27T20:38:13.124Z' and allowed clock skew is '00:05:00'.Server
    stack trace:    at System.ServiceModel.Security.SecurityTimestamp.ValidateFreshness(TimeSpan timeToLive, TimeSpan allowedClockSkew)   at System.ServiceModel.Security.SecurityTimestamp.ValidateRangeAndFreshness(TimeSpan timeToLive, TimeSpan allowedClockSkew)
      at System.ServiceModel.Security.ReceiveSecurityHeader.ReadTimestamp(XmlDictionaryReader reader)   at System.ServiceModel.Security.ReceiveSecurityHeader.ExecuteFullPass(XmlDictionaryReader reader)   at System.ServiceModel.Security.StrictModeSecurityHeaderElementInferenceEngine.ExecuteProcessingPasses(ReceiveSecurityHeader
    securityHeader, XmlDictionaryReader reader)   at System.ServiceModel.Security.ReceiveSecurityHeader.Process(TimeSpan timeout, ChannelBinding channelBinding, ExtendedProtectionPolicy extendedProtectionPolicy)   at System.ServiceModel.Security.TransportSecurityProtocol.VerifyIncomingMessageCore(Message&
    message, TimeSpan timeout)   at System.ServiceModel.Security.TransportSecurityProtocol.VerifyIncomingMessage(Message& message, TimeSpan timeout)   at System.ServiceModel.Security.SecurityProtocol.VerifyIncomingMessage(Message& message, TimeSpan
    timeout, SecurityProtocolCorrelationState[] correlationStates)   at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.ProcessReply(Message reply, SecurityProtocolCorrelationState correlationState, TimeSpan timeout)   at
    System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout)   at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)   at System.ServiceModel.Channels.ServiceChannel.Call(String
    action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage
    message)Exception rethrown at [0]:    at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)  
    at Microsoft.SqlAzureDataSync.ClientServerCommon.ISyncServiceContract.BeginSession(String scopeName, SyncTaskRequestInfo syncInfo, DssConflictResolutionPolicy conflictPolicy, String objectSchema)   at Microsoft.SqlAzureDataSync.AgentHostLib.RelationalProviderProxy.<BeginSession>b__0()
      at Microsoft.SqlAzureDataSync.AgentHostLib.SyncServiceProxy`1.ExecuteAndRetryServiceOperation(Action operation)Inner exception: The security timestamp is invalid because its creation time ('2014-10-27T20:43:13.669Z') is in the future. Current time is
    '2014-10-27T20:38:13.124Z' and allowed clock skew is '00:05:00'."    For more information, provide tracing ID ‘01b12bfd-1467-4fb2-ad8e-551a85fdd1da’ to customer support.
    And after that the Sync got stuck in the processing state, i try to stop it and resend it again but is still trying to stop it. I already fix the time settings in the server and restart the service of sync and nothing. Here are the info related to the Sync
    Group. 
    STATUS
    Processing
    LAST SYNC
    10/27/2014 4:24:00 PM
    SYNC GROUP ID
    045ac6f9-d27a-47ba-8194-7aadf8fc90de_East US
    LOCATION
    East US
    SUBSCRIPTION NAME
    Pay-As-You-Go
    SUBSCRIPTION ID
    399ba2d3-f357-4c7b-a52e-972bcb3cc2d7
    CONFLICT RESOLUTION
    Client Wins

    Hi,
    Thanks for you posting the subscription ID and Sync Group ID. The Microsoft support engineer will help to solve the problem from backend. Sometime delay might be expected. Your patience is greatly appreciated. Thank you for your understanding and support.
    Regards,
    Mekh.

  • TS1702 My kindle app for iPad is stuck in the installing state what do I do to fix it?

    My kindle app for iPad is stuck in the installing state what do I do to fix it?

    Try a reset. Hold the Sleep and Home button down for about 10 seconds until you see the Apple logo. Ignore the red slider.

  • My sync group is stuck in the processing state

    The database sync that we have configured has been working for months and suddenly stopped successfully running 1/19/2015 2:19 PM Pacific Time. We have the sync configured to automatically execute every 5 mins and I even tried to run it manually. The job
    stays perpetually in a "Processing" state with no additional info (e.g. error, warning, etc).
    Can anyone provide assistance? (e.g. reset the sync status, provide detailed logging as to the cause of the issues) What is the proper course of action? (e.g. reconfigure the sync service, etc) Please advise.
    Here are the technical details of the instance:
    STATUS
    Processing
    LAST SYNC
    1/19/2015 2:19:25 PM
    SYNC GROUP ID
    e5c228ff-a8e8-4b99-85f8-504709e22908_West US
    SUBSCRIPTION ID
    4caa7e07-76e5-424d-8b4b-6f26cce36026
    CONFLICT RESOLUTION
    Hub Wins

    Hi,
    Thanks for posting here.
    Any of the following can result in a sync group being stuck in the processing state.
    a)The client agent is offline.
    Be sure that the client agent is online then try again.
    b)The client agent is uninstalled or missing. 
    Please check the above and try to sync again.
    In the mean time we would check from our back-end. It may take more time than expected. 
    Girish Prajwal

  • Why are messages not dequeuing and stuck in the ready state?

    Messages are successfully enqueueing but not dequeuing and are stuck in ready state (STATE = 0).  The ENQ_TIME is 5 hours ahead of system time.  In one environment, AQ is working (10g 10.2.0.4.0).  In the other environment, it is not working (11g 11.2.0.3.0).
    I just did the following:
    1. Purged queue table
    2. Stopped queues
    3. Dropped queues
    4. Dropped queue table
    5. Created queue table
    6. Created queues
    7. Started queues
    I tested once and a record was inserted in the queue table:
    MSGID      <msgid>
    CORRID     
    PRIORITY      1
    STATE      0
    DELAY     
    EXPIRATION     
    TIME_MANAGER_INFO     
    LOCAL_ORDER_NO      0
    CHAIN_NO      0
    CSCN      0
    DSCN      0
    ENQ_TIME      12/23/2014 4:33:43.338902 PM
    ENQ_UID      <enq_uid>
    ENQ_TID      <enq_tid>
    DEQ_TIME     
    DEQ_UID     
    DEQ_TID     
    RETRY_COUNT      0
    EXCEPTION_QSCHEMA     
    EXCEPTION_QUEUE     
    STEP_NO      0
    RECIPIENT_KEY      0
    DEQUEUE_MSGID     
    SENDER_NAME     
    SENDER_ADDRESS     
    SENDER_PROTOCOL     
    USER_DATA      <user_data>
    USER_PROP     
    Notice the RETRY_COUNT is 0.  The ENQ_TIME is 5 hours ahead.  In the procedures to enqueue and dequeue, there are no errors.
    Following is the plsql to enqueue:
    CREATE OR REPLACE PACKAGE BODY
    pkg_2
    AS
        FUNCTION queue_create_thing ( <parameters> )
            RETURN NUMBER
        IS
            enqueue_options     dbms_aq.enqueue_options_t;
            message_properties  dbms_aq.message_properties_t;
            message_handle      RAW(16);
            v_message           msg_type;
            v_thing_id          things.id%TYPE;
        BEGIN
            v_message := msg_type( <parameters> );
            dbms_aq.enqueue(queue_name => '<queue name>',
                            enqueue_options => enqueue_options,
                            message_properties => message_properties,
                            payload => v_message,
                            msgid => message_handle);
            RETURN v_thing_id;
        EXCEPTION
            WHEN OTHERS
            THEN
               errpkg.record_and_stop (SQLCODE);
        END queue_create_thing;
        PROCEDURE queue_delete_thing( <parameters> )
        IS
            enqueue_options     dbms_aq.enqueue_options_t;
            message_properties  dbms_aq.message_properties_t;
            message_handle      RAW(16);
            v_message           msg_type;
        BEGIN
            v_message := msg_type( <parameters> );
            dbms_aq.enqueue(queue_name => '<queue name>',
                            enqueue_options => enqueue_options,
                            message_properties => message_properties,
                            payload => v_message,
                            msgid => message_handle);
        END;
    END pkg_2;
    Following is the code to dequeue:
    CREATE OR REPLACE PACKAGE BODY
    pkg_1
    AS 
        PROCEDURE create_thing ( context IN RAW,
                                    reginfo IN sys.aq$_reg_info,
                                    descr IN sys.aq$_descriptor,
                                    payload IN RAW,
                                    payloadl IN NUMBER )
        IS 
            dequeue_options dbms_aq.dequeue_options_t;
            message_properties dbms_aq.message_properties_t;
            message_handle RAW(16);
            message msg_type;
        BEGIN
            dequeue_options.msgid := descr.msg_id;
            dequeue_options.consumer_name := descr.consumer_name;
            DBMS_AQ.DEQUEUE(queue_name => descr.queue_name,
                            dequeue_options => dequeue_options,
                            message_properties => message_properties,
                            payload => message,
                            msgid => message_handle);
            pkg_2.create_thing( p_thing_id => message.thing_id );
            UPDATE table t
               SET creation_complete = 1
             WHERE id = message.thing_id;
            COMMIT;
        EXCEPTION
            WHEN OTHERS
            THEN
                ROLLBACK;
                plog.error(SQLERRM);
                plog.full_call_stack;
        END create_thing;
        PROCEDURE delete_thing ( context IN RAW,
                                    reginfo IN sys.aq$_reg_info,
                                    descr IN sys.aq$_descriptor,
                                    payload IN RAW,
                                    payloadl IN NUMBER )
        IS 
            dequeue_options dbms_aq.dequeue_options_t;
            message_properties dbms_aq.message_properties_t;
            message_handle RAW(16);
            message msg_type;
        BEGIN
            dequeue_options.msgid := descr.msg_id;
            dequeue_options.consumer_name := descr.consumer_name;
            DBMS_AQ.DEQUEUE(queue_name => descr.queue_name,
                            dequeue_options => dequeue_options,
                            message_properties => message_properties,
                            payload => message,
                            msgid => message_handle);
            pkg_2.delete_thing( p_thing_id => message.thing_id );
            COMMIT;
        EXCEPTION
            WHEN OTHERS
            THEN
                ROLLBACK;
                plog.error(SQLERRM);
                plog.full_call_stack;
        END delete_thing;   
    END pkg_1;

    Following is the code to create the queue:
    BEGIN
      SYS.DBMS_AQADM.STOP_QUEUE ( QUEUE_NAME => '<queue name>');
      SYS.DBMS_AQADM.DROP_QUEUE ( QUEUE_NAME => '<queue name>');
    END;
    BEGIN
      SYS.DBMS_AQADM.CREATE_QUEUE
        QUEUE_NAME          =>   '<queue name>'
       ,QUEUE_TABLE         =>   '<queue table>'
       ,QUEUE_TYPE          =>   SYS.DBMS_AQADM.NORMAL_QUEUE
       ,MAX_RETRIES         =>   5
       ,RETRY_DELAY         =>   0
       ,RETENTION_TIME      =>   0
       ,COMMENT             =>   'Queue for processing creation of things'
    END;
    BEGIN
      SYS.DBMS_AQADM.START_QUEUE
        QUEUE_NAME => '<queue name>'
       ,ENQUEUE => TRUE
       ,DEQUEUE => TRUE
    END;

  • 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

  • FXS Port stucks in Off-Hook state on NM-HDA

    Hi,
    i have some trouble with an FXS Port on an NM-HDA which stucks in the Off-Hook state, after some time of normal operation. The Voice-Port is in Off-Hook state regardless of if there is an Enddevice attached or not. Even an reload of the router does not help.
    The voice port is configured for loop-start. The NM-HDA is housed in an Cisco 3725 running IOS Vers. 12.3(14)T2 with H.323 signalling.
    Is there anybody who has seen this before? Could this be caused by an IOS-Bug or is it more likley that the NM-HDA is faulty?
    Regards
    Robert

    Here's the bug ID: CSCse15025
    Doubt the NM is faulty - we had the same issue in a 2821 and migrated to 12.4(4)T4 to correct it. No hardware replacement required. All has worked fine since then.
    HTH
    Tom

Maybe you are looking for

  • Log and capture with Sony A1U camera, Sony HD700 HDV deck

    Hello, I am still having problems capturing HDV from a Sony GV HD700. It sees the deck, can capture some, but then crashes. Anybody have experience with certain decks and cameras not able to capture with Final cut 7? I am stumped. Settings are HDV...

  • BPC 7.5NW Drill-through to FIM

    Hi all, I upload data to BPC 7.5 NW SP06 through FIM. I tried to set up the Drill-through functionality of BPC so as to see the analysis of the trial balance uploaded in FIM, but with no success. The How-to-paper for drill-through functionality for N

  • 64 bit Java 1.5 on  Windows Server 2003 64bit?

    I have search the Sun website, Google etc but I am unable to find a definitive statement as to whether Java 1.5.0 has support for 64 bit processing when run on on Windows Server 2003 64bit? There appears to be separate 64 bit versions available for d

  • Function modules for selection ID of Demand planning

    Hello All, I need a function module which can return product / location combinations associated with a selection ID. OR, a function module which can return me 1) Planning book 2) data view and 3) Version associated with a selection ID. For the second

  • How to export a Flex3 project in AS3?

    Hi, I have read somewhere that I can export any flex project in AS3 to edit some default values of different components. Does anybody knows how to export it? Thanks She