Central Instance Java Server0/Server1 not starting

We recently installed a new dialog instance for our CUA system (abap and java stacks). Now, whenever the Java stack fully initializes itself on the Dialong Instance first, the Server0 and Server1 on the Central Instance Java stack will not complete their startups. Both Server0 and Server1 get stuck on the "Starting Apps" status. Anybody see this before? Any suggestions on how to fix/reconfigure the java so that this does not happen?
Currently, our work around is to always let the Central Instance finish its startup and then start the Dialong Instance. However, if the CI Java crashes and restarts on its own, it will not be able to complete its startup until we shut down the DI instance.
Thanks.

andreas,
Here is a partial std_server0.out file. It seems that the dumping/memory/locking problem starts immediately after the Framework has started:
ServiceManager started for 354203 ms.
Framework started for 422687 ms.
SAP J2EE Engine Version 7.00 PatchLevel 109886.44 is running!
PatchLevel 109886.44 November 17, 2007 10:27 GMT
Full thread dump Java HotSpot(TM) 64-Bit Server VM (1.4.2_13-b06 mixed mode):
"DSR_Write_Rate_Monitor: DOWNEAVM249.dow_DGD_407398750" prio=5 tid=0x000000001a6b9860 nid=0x4864 runnable [0x0000000000000000..0x0000000000000000]
"Thread-33" prio=5 tid=0x000000001a6b95d0 nid=0x4230 runnable [0x0000000000000000..0x0000000000000000]
"Thread-32" daemon prio=10 tid=0x000000001a6b90b0 nid=0x5044 in Object.wait() [0x000000001de1f000..0x000000001de1fb80]
 at java.lang.Object.wait(Native Method)
 - waiting on <0x000000008eff2080> (a java.util.TaskQueue)
 at java.util.TimerThread.mainLoop(Timer.java:429)
 - locked <0x000000008eff2080> (a java.util.TaskQueue)
 at java.util.TimerThread.run(Timer.java:382)
"SAPEngine_CCMSCommandConsumer_0" prio=10 tid=0x000000001ac73d80 nid=0x1b1c in Object.wait() [0x000000001dc1f000..0x000000001dc1fb80]
 at java.lang.Object.wait(Native Method)
 - waiting on <0x000000008eff0108> (a java.lang.Object)
 at java.lang.Object.wait(Object.java:429)
 at com.sap.engine.lib.util.concurrent.LinkedQueue.take(LinkedQueue.java:104)
 - locked <0x000000008eff0108> (a java.lang.Object)
 at com.sapmarkets.bam.jmxadapter.CCMSCommandConsumer.run(CCMSCommandConsumer.java:38)
 at java.lang.Thread.run(Thread.java:534)
"Thread-29" prio=10 tid=0x000000001ac73860 nid=0x2a64 in Object.wait() [0x000000001da1f000..0x000000001da1fb80]
 at java.lang.Object.wait(Native Method)
 - waiting on <0x000000008eff01d0> (a com.sap.jmx.provider.ProviderConnectionTimer)
 at com.sap.jmx.provider.ProviderConnectionTimer.run(ProviderConnectionTimer.java:31)
 - locked <0x000000008eff01d0> (a com.sap.jmx.provider.ProviderConnectionTimer)
 at java.lang.Thread.run(Thread.java:534)
"Thread-28" prio=10 tid=0x0000000008d2dad0 nid=0x4bf4 in Object.wait() [0x000000001d81f000..0x000000001d81fb80]
 at java.lang.Object.wait(Native Method)
 - waiting on <0x000000008eff0268> (a com.sap.jmx.provider.LazyMBeanLoader)
 at java.lang.Object.wait(Object.java:429)
 at com.sap.jmx.provider.LazyMBeanLoader.run(LazyMBeanLoader.java:133)
 - locked <0x000000008eff0268> (a com.sap.jmx.provider.LazyMBeanLoader)
 at java.lang.Thread.run(Thread.java:534)
"SAPEngine_Application_Thread[impl:3]_1" prio=5 tid=0x00000000012e4920 nid=0x38b0 in Object.wait() [0x0000000007daf000..0x0000000007dafb80]
 at java.lang.Object.wait(Native Method)
 - waiting on <0x000000008fb8f078> (a com.sap.engine.lib.util.WaitQueue)
 at java.lang.Object.wait(Object.java:429)
 at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
 - locked <0x000000008fb8f078> (a com.sap.engine.lib.util.WaitQueue)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:149)
"SAPEngine_Application_Thread[impl:3]_0" prio=5 tid=0x00000000012e4690 nid=0xc20 in Object.wait() [0x00000000079af000..0x00000000079afb80]
 at java.lang.Object.wait(Native Method)
 - waiting on <0x000000008fb8f078> (a com.sap.engine.lib.util.WaitQueue)
 at java.lang.Object.wait(Object.java:429)
 at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
 - locked <0x000000008fb8f078> (a com.sap.engine.lib.util.WaitQueue)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:149)
"Thread-1" prio=5 tid=0x00000000012e4170 nid=0x3a68 in Object.wait() [0x0000000007baf000..0x0000000007bafb80]
 at java.lang.Object.wait(Native Method)
 - waiting on <0x000000008fbbf530> (a com.sap.engine.core.Framework)
 at java.lang.Object.wait(Object.java:429)
 at com.sap.engine.core.Framework.start(Framework.java:207)
 - locked <0x000000008fbbf530> (a com.sap.engine.core.Framework)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at com.sap.engine.boot.FrameThread.run(FrameThread.java:61)
 at java.lang.Thread.run(Thread.java:534)
"Signal Dispatcher" daemon prio=10 tid=0x00000000012e34a0 nid=0x2334 waiting on condition [0x0000000000000000..0x0000000000000000]
"Finalizer" daemon prio=9 tid=0x00000000012e3210 nid=0x23c8 in Object.wait() [0x0000000006baf000..0x0000000006bafb80]
 at java.lang.Object.wait(Native Method)
 - waiting on <0x00000000909192e0> (a java.lang.ref.ReferenceQueue$Lock)
 at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111)
 - locked <0x00000000909192e0> (a java.lang.ref.ReferenceQueue$Lock)
 at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)
 at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
"Reference Handler" daemon prio=10 tid=0x00000000012e2f80 nid=0x1438 in Object.wait() [0x00000000069af000..0x00000000069afb80]
 at java.lang.Object.wait(Native Method)
 - waiting on <0x000000008f9a61d0> (a java.lang.ref.Reference$Lock)
 at java.lang.Object.wait(Object.java:429)
 at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:115)
 - locked <0x000000008f9a61d0> (a java.lang.ref.Reference$Lock)
"main" prio=5 tid=0x00000000012e2cf0 nid=0x3cb8 in Object.wait() [0x000000000222f000..0x000000000222fc68]
 at java.lang.Object.wait(Native Method)
 - waiting on <0x000000008fbbf3e0> (a com.sap.engine.boot.StartFrame)
 at java.lang.Object.wait(Object.java:429)
 at com.sap.engine.boot.StartFrame.work(StartFrame.java:121)
 - locked <0x000000008fbbf3e0> (a com.sap.engine.boot.StartFrame)
 at com.sap.engine.boot.Start.main(Start.java:34)
"VM Thread" prio=5 tid=0x000000000137a4a0 nid=0x3cac runnable
"VM Periodic Task Thread" prio=10 tid=0x000000000137a6a0 nid=0xccc waiting on condition
"Suspend Checker Thread" prio=10 tid=0x000000000137a5a0 nid=0x67c runnable
Service tc.monitoring.logviewer started. (89484 ms).
>
Login :### Excluding compile: com.sap.engine.services.webservices.jaxrpc.encoding.TypeMappingImpl::initializeRelations
Excluding compile: com.sap.engine.services.webservices.jaxrpc.encoding.GeneratedComplexType::_loadInto
Thanks, Bruce

Similar Messages

Java server0 its not starting with error -11113

Dear Experts team,
When We are starting SAP Solution Manager 7.10, Its ABAP Instance is running file ,
But Java Instance not running , In this Java Process table , SDM and dispatcher is working file (green)
But in server0 its not starting and -11113 (core service or addition service start fails)
When check Developer Trace of dev_server0 , it show last few lines as given below,
Thr 5464] JLaunchIExitJava: exit hook is called (rc = -11113)
[Thr 5464] **********************************************************************
[Thr 5464] *** ERROR => The Java VM terminated with a non-zero exit code.
[Thr 5464] *** Please see SAP Note 943602 , section 'J2EE Engine exit codes'
[Thr 5464] *** for additional information and trouble shooting.
[Thr 5464] **********************************************************************
[Thr 5464] JLaunchCloseProgram: good bye (exitcode = -11113)
Please suggest ...
Thanks
Regards
Sunil k

Hi,
Hope you are doing good.
Please check the latest STD_SERVER0 and the default traces and attach the contents here. This should have the error details. Exit code 11113 means that some essential service fails to start so the server/dispatcher process fails.
Thank you!
Kind Regards,
Hemanth
SAP AGS

Java Process server0 is not Starting (exitcode -11113)

Hi,
Need your help. My Java AS is not starting after I encounter error during JSPAM component upgrade error. I tried to deploy updates on SAP J2EE ENGINE 7.00 then I got exitcode = -11113
Below is my tail logs i got from dev_server0 file. Appreciate your help.
[Thr 9764] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 1028] Thu May 08 18:02:20 2014
[Thr 1028] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 1028] Thu May 08 18:02:23 2014
[Thr 1028] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 1028] Thu May 08 18:02:24 2014
[Thr 1028] JLaunchISetClusterId: set cluster id 24050450
[Thr 1028] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 1028] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 9712] Thu May 08 18:03:15 2014
[Thr 9712] JLaunchIExitJava: exit hook is called (rc = -11113)
[Thr 9712] **********************************************************************
*** ERROR => The Java VM terminated with a non-zero exit code.
*** Please see SAP Note 943602 , section 'J2EE Engine exit codes'
*** for additional information and trouble shooting.
[Thr 9712] JLaunchCloseProgram: good bye (exitcode = -11113)
Cheers!
Henry

Hello Henry,
The exitcode -11113 is just a generic message to tell us that a core service has failed to start. In this case, it is the UME service due to the error java.lang.NoClassDefFoundError: com/sap/security/core/util/config/IUMConfiguration
This is caused by an inconsistency inside NW Java stack. With any NoClassDefFound errors, We need you to patch some sca files as there is missing references or corrupted classes on the filesystem. As you say that this error occurred during an upgrade then I assume you are missing dependencies
The affected sda files belong to UME:
com.sap.security.core.offline.sda (extract from SAPJEECOR**_*.SCA)
com.sap.security.api.offline.sda (extract from SAPJEECOR**_*.SCA)
com.sap.security.core.ume.service.sda (extract from SAPJEE**_*.SCA)
What you need to do is to download the latest patches for the above components and apply them in your system with SUM/SDM. As there are certain dependencies with core Java components, Along with patching SAPJEECOR and SAPJEE, you should also patche SAPJTECHS and SAPJTECHF.
Regards,
David

SRM AS JAVA not starting(JControl.EXE and Server0 are not starting )

Hi All,
We have SAP SRM 7.0 AS ABAP and AS JAVA with SAP PI and MDM installed on Windows Server 2008 R2.
When we are trying to start SRM as JAVA from SAPMMC is not starting.
The JControl.EXE and Server0 are not starting.
For your convenience I am pasting error part of trace files
Our dev_jcontrol log file text is as follows:
[Thr 7112] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
[Thr 7112] [Node: bootstrap] java home is set by profile parameter
[Thr 7112]      Java Home: C:\j2sdk1.4.2_19-x64
[Thr 7112] JStartupICheckFrameworkPackage: can't find framework package E:\usr\sap\SRJ\JC22\exe\jvmx.jar
[Thr 7112] JControlICheckProcessList: process server0 started (PID:4688)
[Thr 7112] Thu Dec 15 16:43:42 2011
[Thr 7112] JControlICheckProcessList: process server0 (pid:4688) died (RUN-FLAG)
[Thr 7112] JControlIResetProcess: reset process server0
[Thr 7112] JControlIResetProcess: [server0] not running -> increase error count (4)
[Thr 7112] JControlICheckProcessList: running flight recorder:
[Thr 7112]      C:\j2sdk1.4.2_19-x64\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID228052750 1323947582 -bz E:\usr\sap\SRJ\SYS\global
[Thr 5568] Thu Dec 15 17:23:18 2011
[Thr 5568] JControlSigInt: signal = 2
[Thr 5568] JControlIStopInstance: shutting down (command: 0)
[Thr 5568] JControlIProcessSoftKill: soft kill of process dispatcher (pid:7648)
[Thr 5568] ERROR => invalid connect to named pipe (rc = 232) [jstartnt.c   268]
[Thr 5568] ERROR => Can't send soft kill (rc=-1) [jcntrxxi.c   1743]
[Thr 5568] JControlIProcessSoftKill: soft kill of process SDM (pid:7664)
[Thr 5568] ERROR => invalid connect to named pipe (rc = 232) [jstartnt.c   268]
[Thr 5568] ERROR => Can't send soft kill (rc=-1) [jcntrxxi.c   1743]
Our dev_bootstrap log is:
[Thr 7712] CCMS: AlMsUpload called by wp 1004.
[Thr 7712] CCMS: AlMsUpload successful for E:\usr\sap\SRJ\JC22\log\ALMTTREE.DAT (302 MTEs).
[Thr 7712] CCMS: CCMS Monitoring Initialization finished, rc=0.
[Thr 7712] [Node: bootstrap] java home is set by profile parameter
[Thr 7712]      Java Home: C:\j2sdk1.4.2_19-x64
[Thr 7712] JStartupICheckFrameworkPackage: can't find framework package E:\usr\sap\SRJ\JC22\exe\jvmx.jar
In dev_server0 the log is as follows:
ERROR => The Java VM terminated with a non-zero exit code.
What should be the issue I am not getting. Please help me to solve this.
Thanks & Regards,
Ishan

Hi All,
I removed last changes i did. n restarted it.
Thanks,
Ishan

Dispacher and server0 is not started during NW2004s installation

Hi,
Dispacher and server0 is not started during NW2004s installation. SAPInst is stopped on the step of the 'Start java instance'. SDM is 'running' but dispacher and server0 is 'Starting framwork'. So I configured the some parameters via configtool but I can't solve this probelm. I found the some error logs as the followings.
(22503) Starting local Command:
Command: en.sapMPP_SCS33 pf=/usr/sap/MPP/SYS/profile/MPP_SCS33_spdeai01
listen failed on port/service sapdp33
initialize_global: another instance of the enque server seems to be running. EXIT
***LOG Q01=> MsSInit, MSStart (Msg Server 1 22502) [msxxserv_mt. 1818]
[Thr 1] SigISetDefaultAction : default handling for signal 18
[Thr 1] load acl file = /usr/sap/MPP/SYS/global/ms_acl_info
[Thr 1] MsGetOwnIpAddr: my host addresses are :
[Thr 1] 1 : [10.223.50.15] spdeai01 (HOSTNAME)
[Thr 1] 2 : [127.0.0.1] localhost (LOCALHOST)
[Thr 1] 3 : [10.223.50.215] 10.223.50.215 (NILIST)
[Thr 1] 4 : [10.223.50.115] 10.223.50.115 (NILIST)
[Thr 1] MsHttpInit: full qualified hostname = spdeai01
[Thr 1] HTTP logging is switch off
[Thr 1] set HTTP state to LISTEN
[Thr 1] ms/icf_info_server : deleted
[Thr 1] *** I listen to internal port 3933 (3933) ***
[Thr 1] *** HTTP port 8133 state LISTEN ***
[Thr 1] CUSTOMER KEY: >Q0820898445<
[Thr 1] Wed Oct 24 18:28:11 2007
[Thr 1] MsJ2EE_AddLoggedInNode: add node [305110500] into logged in list
[Thr 1] Wed Oct 24 18:28:21 2007
[Thr 1] MsJ2EE_AddLoggedInNode: add node [305110550] into logged in list
Our JDK version is '1.4.2_11' and We are installing on the HA environment.
How can I solve this problem? or What should I check about it?
Best Regards,
David.

Check if the Database serivice is up and running. If this is not so.. you might have to start all over again..!!
VJ

JAVA servers are not starting

Hi SAP Gurus,
some days back i did system refresh from prod. now ABAP is running but only java servers are not starting. other nodes dispatcher & SDM running. please suggest.
here is dev_server1 file
=============================================
-> arg[ 36]: -Djstartup.whoami=server
-> arg[ 37]: -Djstartup.debuggable=no
-> arg[ 38]: -DSAPINFO=BQN_51_server
-> arg[ 39]: -DSAPSTART=1
-> arg[ 40]: -DCONNECT_PORT=64990
-> arg[ 41]: -DSAPSYSTEM=51
-> arg[ 42]: -DSAPSYSTEMNAME=BQN
-> arg[ 43]: -DSAPMYNAME=cpcsapv1_BQN_51
-> arg[ 44]: -DSAPPROFILE=/usr/sap/BQN/SYS/profile/BQN_DVEBMGS51_cpcsapv1
-> arg[ 45]: -DFRFC_FALLBACK=ON
-> arg[ 46]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 47]: -DSAPSTARTUP=1
-> arg[ 48]: -DSAPSYSTEM=51
-> arg[ 49]: -DSAPSYSTEMNAME=BQN
-> arg[ 50]: -DSAPMYNAME=cpcsapv1_BQN_51
-> arg[ 51]: -DSAPDBHOST=cpcsapv1
-> arg[ 52]: -Dj2ee.dbhost=cpcsapv1
[Thr 4] Fri Feb 3 14:28:34 2012
[Thr 4] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server1]
[Thr 27] Fri Feb 3 14:28:36 2012
[Thr 27] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 27] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 27] JLaunchISetClusterId: set cluster id 515639851
[Thr 27] Fri Feb 3 14:28:44 2012
[Thr 27] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 27] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
Fri Feb 3 14:29:13 2012
40.606: [GC 40.606: [ParNew: 87040K->5145K(130560K), 0.0272228 secs] 87040K->5145K(1005056K), 0.0273939 secs]
Fri Feb 3 14:30:59 2012
147.504: [GC 147.505: [ParNew: 92185K->4232K(130560K), 0.0099921 secs] 92185K->4232K(1005056K), 0.0101364 secs]
Fri Feb 3 14:31:32 2012
180.020: [GC 180.020: [ParNew: 91272K->11482K(130560K), 0.0398227 secs] 91272K->11482K(1005056K), 0.0400287 secs]
Fri Feb 3 14:31:35 2012
182.991: [GC 182.992: [ParNew: 98522K->16449K(130560K), 0.0520708 secs] 98522K->16449K(1005056K), 0.0522291 secs]
Fri Feb 3 14:31:37 2012
184.671: [GC 184.671: [ParNew: 103489K->16840K(130560K), 0.0362919 secs] 103489K->16840K(1005056K), 0.0364886 secs]
Fri Feb 3 14:31:38 2012
185.955: [GC 185.955: [ParNew: 103880K->17465K(130560K), 0.1179448 secs] 103880K->17465K(1005056K), 0.1181308 secs]
Fri Feb 3 14:31:39 2012
187.030: [GC 187.030: [ParNew: 104505K->19470K(130560K), 0.0490249 secs] 104505K->19470K(1005056K), 0.0492104 secs]
Fri Feb 3 14:31:40 2012
187.892: [GC 187.892: [ParNew: 106510K->20973K(130560K), 0.0462993 secs] 106510K->20973K(1005056K), 0.0464782 secs]
Fri Feb 3 14:31:41 2012
188.624: [GC 188.625: [ParNew: 108013K->22480K(130560K), 0.0549972 secs] 108013K->22480K(1005056K), 0.0551496 secs]
Fri Feb 3 14:31:42 2012
189.855: [GC 189.856: [ParNew: 109520K->26140K(130560K), 0.0483116 secs] 109520K->26140K(1005056K), 0.0485971 secs]
[Thr 139] Fri Feb 3 14:31:47 2012
[Thr 139] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
[Thr 139] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI
[Thr 139] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.engine.Compress
Fri Feb 3 14:31:48 2012
196.478: [GC 196.479: [ParNew
Fri Feb 3 14:31:49 2012
: 113180K->34002K(130560K), 0.0845910 secs] 113180K->34002K(1005056K), 0.0848079 secs]
Fri Feb 3 14:32:14 2012
221.647: [GC 221.647: [ParNew: 121042K->43127K(130560K), 0.0901828 secs] 121042K->43127K(1005056K), 0.0904040 secs]
Fri Feb 3 14:32:15 2012
223.343: [GC 223.343: [ParNew: 130143K->37620K(130560K), 0.0733509 secs] 130143K->46470K(1005056K), 0.0735802 secs]
Fri Feb 3 14:32:16 2012
224.069: [GC 224.069: [ParNew: 124591K->40179K(130560K), 0.0747273 secs] 133442K->49029K(1005056K), 0.0749214 secs]
Fri Feb 3 14:32:17 2012
224.682: [GC 224.683: [ParNew: 127211K->40700K(130560K), 0.0815027 secs] 136062K->52675K(1005056K), 0.0816996 secs]
225.187: [GC 225.187: [ParNew: 127724K->40534K(130560K), 0.0587785 secs] 139699K->54340K(1005056K), 0.0589684 secs]
[Thr 130] Fri Feb 3 14:35:11 2012
[Thr 130] JHVM_RegisterNatives: registering methods in com.sap.security.core.server.vsi.service.jni.VirusScanInterface
[Thr 149] Fri Feb 3 14:35:12 2012
[Thr 149] ***LOG S98=> STISearchConv, no conv (14387978) [r3cpic_mt.c 6137]
[Thr 149]
[Thr 149] * LOCATION    CPIC (TCP/IP) on local host with Unicode
[Thr 149] * ERROR       no conversation found with id 14387978
[Thr 149] *
TIME        Fri Feb 3 14:35:12 2012
[Thr 149] * RELEASE     701
[Thr 149] * COMPONENT   CPIC (TCP/IP) with Unicode
[Thr 149] * VERSION     3
[Thr 149] * RC          473
[Thr 149] * MODULE      r3cpic_mt.c
[Thr 149] * LINE        6138
[Thr 149] * COUNTER     1
[Thr 149] *
[Thr 149] *****************************************************************************
[Thr 149]
**[Thr 149] * LOCATION    CPIC (TCP/IP) on local host with Unicode**
**[Thr 149] * ERROR       illegal parameter value ( function=SAPCMTIMEOUT2 /**_
***              parameter=conversationID / value=14387978 )**_
**[Thr 149] ***
*** TIME        Fri Feb 3 14:35:12 2012**
**[Thr 149] * RELEASE     701**
**[Thr 149] * COMPONENT   CPIC (TCP/IP) with Unicode**
**[Thr 149] * VERSION     3**
**[Thr 149] * RC          769**
**[Thr 149] * MODULE      r3cpicmt.c**_
**[Thr 149] * LINE        7354**
**[Thr 149] * COUNTER     2**
**[Thr 149] ***
**[Thr 149] *******************************************************************************
[Thr 27] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
399.717: [GC 399.717: [ParNew: 127574K->43520K(130560K), 0.0996730 secs] 141380K->60028K(1005056K), 0.0999462 secs]
Fri Feb 3 14:35:15 2012
402.992: [GC 402.993: [ParNew: 130425K->39664K(130560K), 0.0697386 secs] 146933K->65055K(1005056K), 0.0699946 secs]
Fri Feb 3 14:35:18 2012
406.083: [GC 406.083: [ParNew: 126695K->36855K(130560K), 0.0698643 secs] 152086K->67926K(1005056K), 0.0701081 secs]
Fri Feb 3 14:35:19 2012
407.337: [GC 407.338: [ParNew: 123895K->36788K(130560K), 0.0644911 secs] 154966K->67859K(1005056K), 0.0646924 secs]
Fri Feb 3 14:35:20 2012
Excluding compile: com.sap.engine.services.webservices.jaxrpc.encoding.TypeMappingImpl::initializeRelations
Fri Feb 3 14:35:21 2012
409.075: [GC 409.075: [ParNew: 123700K->38997K(130560K), 0.0669356 secs] 154771K->70069K(1005056K), 0.0671589 secs]
Fri Feb 3 14:35:24 2012
411.813: [GC 411.814: [ParNew: 126037K->41099K(130560K), 0.0865503 secs] 157109K->72170K(1005056K), 0.0867652 secs]
==============================================================

Hi,
From the logs, looks like the Java is not able to connect to the ABAP via the RFC.
ERROR no conversation found with id 14387978
Check the SAPJSF user which is required for communication between ABAP and Java stacks. Check for roles and if it is locked. Also you could try a server restart, which may reset the conversation IDs.
Regards,
Srikishan

Dispatcher process on ABAP + JAVA system does not start.

Hi all,
Dispatcher process on ABAP + JAVA system does not start.
Can someone help me to solve this issue in a ABAP+JAVA stack system?
service p4 ================= ERROR =================
Core service p4 failed. J2EE Engine cannot be started.
com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='Can't assign requested addres
s (errno:227)
com.sap.engine.services.rmi_p4.dispatcher.TransportMonitor constructor : can't open server socket.', Arguments: []--> : Can't find resource for bundle java
.util.PropertyResourceBundle, key Can't assign requested address (errno:227)
com.sap.engine.services.rmi_p4.dispatcher.TransportMonitor constructor : can't open server socket.
 at com.sap.engine.services.rmi_p4.dispatcher.TransportMonitor.<init>(TransportMonitor.java:211)
 at com.sap.engine.services.rmi_p4.dispatcher.P4ServiceFrame.start(P4ServiceFrame.java:93)
 at com.sap.engine.core.service630.container.ServiceRunner.startCommunicationServiceFrame(ServiceRunner.java:228)
 at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:158)
 at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
 at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)
 at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)
com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='Can't assign requested addres
s (errno:227)
com.sap.engine.services.rmi_p4.dispatcher.TransportMonitor constructor : can't open server socket.', Arguments: []--> : Can't find resource for bundle java
.util.PropertyResourceBundle, key Can't assign requested address (errno:227)
com.sap.engine.services.rmi_p4.dispatcher.TransportMonitor constructor : can't open server socket.
 at com.sap.engine.services.rmi_p4.dispatcher.TransportMonitor.<init>(TransportMonitor.java:211)
 at com.sap.engine.services.rmi_p4.dispatcher.P4ServiceFrame.start(P4ServiceFrame.java:93)
 at com.sap.engine.core.service630.container.ServiceRunner.startCommunicationServiceFrame(ServiceRunner.java:228)
 at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:158)
 at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
 at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)
 at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)
[Framework -> criticalShutdown] Core service p4 failed. J2EE Engine cannot be started.
Nov 9, 2011 6:41:09 AM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:6]_26] Fatal: Critical shutdown was invoked. Reason is: Core
service p4 failed. J2EE Engine cannot be started.
Please let me know if you need any further information in this regard.
with regards,
Raja

Hi,
Core service p4 failed. J2EE Engine cannot be started.
com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='Can't assign requested addres
Please reboot the server to free up occupied ports. Later start the sap system.
Regards,
Deepak kori

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

Server0 will not start. client 100 does not exist.

On my NetWeaver 7.0 system with Solution Mgr 7.0 (build from IDES 600 image) on a HPUX 11.23 IA & Oracle with Java 1.4.2.15 installed, I'm going thru the basic setup steps for configuring MOPZ and get to the step
Following IMG basic install steps (basic settings->SAP Solution Manager System->System Landscape(SLD)->Specify service for comm. w/ SLD in Visual Admin), unable to connect to J2EE engine via Visual Admin.
The dev_server0 log:
[Thr 6] JLaunchIExitJava: exit hook is called (rc = -11113)
[Thr 6] **********************************************************************
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 943602 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.
Std_server0.out log:
===========================================================
Apr 27, 2009 8:14:20 AM ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_73] Fatal:
service com.sap.security.core.ume.service ================= ERROR =================
Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed"
. Technical details: Client 100 is not available in this system
I ran JCmon to restart the instance.
cd /usr/sap/SMA/ DVEBMGS00/j2ee/os_lib
jcmon pf= /usr/sap/SMA/SYS/profile/SMA_DVEBMGS00_pax3
20: local Admin.
Restarted instance, but same error, client 100 is not available in this system.
std_server0.out details
===============================================================
Apr 30, 2009 4:24:50 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_97] Fatal: Initialization of ABAP data
source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: "Client 100 is not available in this system". This message
is critical if it appears during the startup of the AS Java.
Apr 30, 2009 4:24:50 PM ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_97] Fatal:
service com.sap.security.core.ume.service ================= ERROR =================
Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Cli
ent 100 is not available in this system
 at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
 at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
 at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
 at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
 at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
 at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
 at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:107)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Client 100 is not available in this system
 at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
 at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:445)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
 at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
 at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
 ... 6 more
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Cli
ent 100 is not available in this system
 at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
 at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
 at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
 at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
 at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
 at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
 at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:107)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Client 100 is not available in this system
 at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
 at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:445)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
 at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
 at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
 ... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Apr 30, 2009 4:24:50 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_97] Fatal: Critical shutdown was invoke
d. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
============================================================
Solution maybe obvious, create a client 100. But server0 was running fine on this node when I first installed Solution Mgr, and it is running fine on my ERP / BI system that II built from the same IDES media, ofwhich it does not have a client 100 and Java WebAS is running fine. Also, able to connect to portal via http://host:50000/irj. Only difference is I have java 1.4.2.20 installed on the BI system.
So is there some other reason why server0 will not come up?

Using the search tool for property name containing "client", the only client defs in the configtool are ume.r3.connection.001-004.client under
cluster-data->Global server configuration->services->com.sap.security.core.ume.service. Values are blank. This is the same on my failing system SMA (SolMgr) and working system BIF(BI system).
The ume.r3.connection.master.client has custom value of 100. I set it to one and restarted the cluster.
The WebAS is up and running again. Don't know what could of changed it to 100.
Thanks for all your help.
-Don.

SAP PI 7.11 JAVA Stack do not start - Loading [PoolManager]...

Hello,
 
our Java Stack of our SAP PI 7.11 do not start. In the SAP MMC we get following error:
 
-1501 (Some managers fails to start)
 
I loooked into the std_server0 log and find this error: 
Loading [PoolManager]... [31] ms 
ERROR: Server process failed to start due to: 
java.lang.NoClassDefFoundError: com/sap/jvm/monitor/thread/ThreadWatcher$Callback 
 at java.lang.Class.getDeclaredConstructors0(Native Method) 
 at java.lang.Class.privateGetDeclaredConstructors(Class.java:2357) 
 at java.lang.Class.getConstructor0(Class.java:2671) 
 at java.lang.Class.newInstance0(Class.java:321) 
 at java.lang.Class.newInstance(Class.java:303) 
 at com.sap.engine.core.Framework.loadSingleManager(Framework.java:601) 
 at com.sap.engine.core.Framework.loadManagers(Framework.java:394) 
 at com.sap.engine.core.Framework.start(Framework.java:329) 
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
 at java.lang.reflect.Method.invoke(Method.java:585) 
 at com.sap.engine.boot.FrameThread.startFramework(FrameThread.java:155) 
 at com.sap.engine.boot.FrameThread.run(FrameThread.java:179) 
 at com.sap.engine.boot.StartFrame.work(StartFrame.java:93) 
 at com.sap.engine.boot.Start.main(Start.java:35) 
Caused by: java.lang.ClassNotFoundException: com.sap.jvm.monitor.thread.ThreadWatcher$Callback 
Now I post you the all of the Log-File: 
 
stdout/stderr redirection 
 
node name : server0 
host name : iilsrv02 
system name : IPE 
system nr. : 00 
started at : Mon Jan 09 13:57:24 2012 
JVMX version - Nov 5 2007 23:34:18 - 01_REL - optU - windows amd64 - bas2:88748 (mixed mode, sharing) 
(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) 
(CompilerOracle exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects) 
The active factory is : com.sap.engine.boot.loader.StandardClassLoaderFactory 
WARNING: The hash of package index [E:\usr\sap\IPE\DVEBMGS00\j2ee\cluster\bin\index.list] is corrupted 
Reading kernel properties from kernelProperties.bin file... 
 Checked the data for 47 ms 
 Read the objects for 234 ms 
 Substituted the values for 31 ms 
Finished reading kernel objects for 265 ms 
Startup mode [NORMAL] and action [NONE] read 
AS Java version [7.11.3710.93986.20100429121726] is starting server process [ID2867950] on host [iilsrv02]... 
Loading [LogManager]... [157] ms 
Loading [PoolManager]... [31] ms 
ERROR: Server process failed to start due to: 
java.lang.NoClassDefFoundError: com/sap/jvm/monitor/thread/ThreadWatcher$Callback 
 at java.lang.Class.getDeclaredConstructors0(Native Method) 
 at java.lang.Class.privateGetDeclaredConstructors(Class.java:2357) 
 at java.lang.Class.getConstructor0(Class.java:2671) 
 at java.lang.Class.newInstance0(Class.java:321) 
 at java.lang.Class.newInstance(Class.java:303) 
 at com.sap.engine.core.Framework.loadSingleManager(Framework.java:601) 
 at com.sap.engine.core.Framework.loadManagers(Framework.java:394) 
 at com.sap.engine.core.Framework.start(Framework.java:329) 
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
 at java.lang.reflect.Method.invoke(Method.java:585) 
 at com.sap.engine.boot.FrameThread.startFramework(FrameThread.java:155) 
 at com.sap.engine.boot.FrameThread.run(FrameThread.java:179) 
 at com.sap.engine.boot.StartFrame.work(StartFrame.java:93) 
 at com.sap.engine.boot.Start.main(Start.java:35) 
Caused by: java.lang.ClassNotFoundException: com.sap.jvm.monitor.thread.ThreadWatcher$Callback 
Loader Info -
 
ClassLoader name: [system:Kernel] 
Living status: alive 
Direct parent loaders: 
 [library:core_lib] 
Resources: 
 E:\usr\sap\IPE\DVEBMGS00\j2ee\cluster\bin\kernel\jenqulib.jar
 E:\usr\sap\IPE\DVEBMGS00\j2ee\cluster\bin\kernel\sap.comtcantlr~runtime.jar
 E:\usr\sap\IPE\DVEBMGS00\j2ee\cluster\bin\kernel\sap.comtcblcachemgmtapi_for_assembly.jar
 E:\usr\sap\IPE\DVEBMGS00\j2ee\cluster\bin\kernel\sap.comtcblcachemgmtimpl.jar
 E:\usr\sap\IPE\DVEBMGS00\j2ee\cluster\bin\kernel\sap.comtcblcache_pluginslib.jar
 E:\usr\sap\IPE\DVEBMGS00\j2ee\cluster\bin\kernel\sap.comtcblframekrn.jar
 E:\usr\sap\IPE\DVEBMGS00\j2ee\cluster\bin\kernel\sap.comtcbljkernel_cacheimpl.jar
 E:\usr\sap\IPE\DVEBMGS00\j2ee\cluster\bin\kernel\sap.comtcbljkernel_classloadkrn.jar
 E:\usr\sap\IPE\DVEBMGS00\j2ee\cluster\bin\kernel\sap.comtcbljkernel_clusterkrn.jar
 E:\usr\sap\IPE\DVEBMGS00\j2ee\cluster\bin\kernel\sap.comtcbljkernel_configurationkrn.jar
 E:\usr\sap\IPE\DVEBMGS00\j2ee\cluster\bin\kernel\sap.comtcbljkernel_databasekrn.jar
 E:\usr\sap\IPE\DVEBMGS00\j2ee\cluster\bin\kernel\sap.comtcbljkernel_licensingkrn.jar
 E:\usr\sap\IPE\DVEBMGS00\j2ee\cluster\bin\kernel\sap.comtcbljkernel_lockingkrn.jar
 E:\usr\sap\IPE\DVEBMGS00\j2ee\cluster\bin\kernel\sap.comtcbljkernel_logkrn.jar
 E:\usr\sap\IPE\DVEBMGS00\j2ee\cluster\bin\kernel\sap.comtcbljkernel_poolkrn.jar
 E:\usr\sap\IPE\DVEBMGS00\j2ee\cluster\bin\kernel\sap.comtcbljkernel_servicekrn.jar
 E:\usr\sap\IPE\DVEBMGS00\j2ee\cluster\bin\kernel\sap.comtcbljkernel_threadkrn.jar
 E:\usr\sap\IPE\DVEBMGS00\j2ee\cluster\bin\kernel\sap.comtcblopensqlkernelimplOpenSQLKrn.jar
 E:\usr\sap\IPE\DVEBMGS00\j2ee\cluster\bin\kernel\sap.comtcjeoffline_deployimpl.jar
 E:\usr\sap\IPE\DVEBMGS00\j2ee\cluster\bin\kernel\sap.comtcjesessionmgmtimpl.jar
 E:\usr\sap\IPE\DVEBMGS00\j2ee\cluster\bin\kernel\sap.comtcseclikeylikey_assembly.jar 
 
 at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:274) 
 at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:243) 
 at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:353) 
 ... 16 more 
Have someone an idee where to find the error and how we could resolve it? 
Thanks and regards 
Martin

Hi,
You are right, JSPM will not start with server0 down. And server0 will not come up with SAP JVM not updated.
Perhaps you could try a manual update of the SAP JVM as mentioned in the thread:
SAP EHP1 FOR SAP NW CE 7.1 - java doesn't start after updating jvm
Hope it helps.
Regards,
Srikishan

Dialog Instance installation - Error u0093Service Not Started u0093

Hi All,
We are facing some issues while installing Dialog Instance on Windows 2003 server. Please help me on this...
Below are the Central Instance Details:
     SAP Component Version: SAP NetWeaver 2004s
     Basis Release: 700
     Kernel Release : 700
     Patch Level : 111
     Operating System: AIX 5.2
     Database : Oracle 10.2.0
     Central Instance host: centralhost
     SID : CID
Dialog Instance Details:
     SAP Component Version: SAP NetWeaver 2004s
     Operating System: Windows 2003 Server(SP2 32 Bit)
     Dialog Instance host: dialoghost
     Instance No: 02
In Step 8 of installation, we are getting error Service Not Started
sapinst.log file content :-
INFO 2008-02-18 03:46:44
Creating SAP start service of instance CID/D02...
INFO 2008-02-18 03:46:45
Creating file C:\Program Files\sapinst_instdir\NW04S\LM\AS\ORA\DI\sapstartsrv.exe.log.
INFO 2008-02-18 03:46:45
Output of D:\usr\sap\CID\D02\exe\sapstartsrv.exe -r -q -p
centralhost\sapmnt\CID\SYS\profile\START_D02_DIALOGHOST -s CID -n 02 -U DIALOGHOST\SAPServiceCID -P XXXXXX -e DIALOGHOST\cidadm is written to the logfile sapstartsrv.exe.log.
WARNING 2008-02-18 03:46:51
Execution of the command "D:\usr\sap\CID\D02\exe\sapstartsrv.exe -r -q -p
centralhost\sapmnt\CID\SYS\profile\START_D02_DIALOGHOST -s CID -n 02 -U DIALOGHOST\SAPServiceCID -P XXXXXX -e DIALOGHOST\cidadm" finished with return code -1. Output:
Service not started.
ERROR 2008-02-18 03:46:52
MOS-01011 'D:/usr/sap/CID/D02/exe/sapstartsrv.exe' returned with '-1'.
ERROR 2008-02-18 03:46:52
MOS-01011 'D:/usr/sap/CID/D02/exe/sapstartsrv.exe' returned with '-1'.
ERROR 2008-02-18 03:46:52
FCO-00011 The step createService with step key |NW_DI|ind|ind|ind|ind|0|0|NW_DI_Instance|ind|ind|ind|ind|10|0|NW_Instance|ind|ind|ind|ind|1|0|createService was executed with status ERROR .
Service User SAPSERVICECID is aligned to administrator group.
And when we tried to start the windows service (SAPCID_02) we got below message
"The SAPCID_02 service on Local computer Started and then stopped. Some Services stop automatoically,if they have no work to do, for example , the performane logs and Alert service"
Please help me on this..
Thanks..
Preethish

Hi Haynes,
From windows machine we can access the Dilaog instance profile.
Path to executable in SAPCID_02 service is "D:\usr\sap\CID\D02\exe\sapstartsrv.exe" pf="
centalhost\sapmnt\CID\SYS\profile\START_D02_DIALOGHOST"
On Cental Instance( AIX machine) :-
CI profiles are in " /sapmnt/CID/profile " path
and DI profiles are in " /sapmnt/CID/SYS/profile " path
centralhost:cidadm 2> cd /sapmnt/CID/profile
centralhost:cidadm 3> ls -l
total 64
-rw-rr   1 CIDadm   sapsys         4958 Feb 12 20:40 CID_DVEBMGS00_CENTRALHOST
-rw-rr   1 CIDadm   sapsys         2272 Feb 12 18:39 DEFAULT.PFL
-rw-rr   1 CIDadm   sapsys         3826 Nov 20 02:25 START_DVEBMGS00_CENTRALHOST
drwxr-xr-x   2 CIDadm   sapsys          256 Nov 02 02:23 oracle
centralhost:cidadm 4> cd /sapmnt/CID/SYS/profile
centralhost:cidadm 5> ls -l
total 40
-rwxrr   1 CIDadm   sapsys          303 Feb 17 19:40 CID_D02_DIALOGHOST
-rwxrr   1 CIDadm   sapsys         2307 Feb 14 09:43 DEFAULT.PFL
-rwxrr   1 CIDadm   sapsys         1013 Feb 17 19:40 START_D02_DIALOGHOST
drwxr-xr-x   2 CIDadm   sapsys          256 Feb 14 14:06 oracle
centralhost:CIDadm 6>

Server0 do not start during NW2004s installation

Hello friends,
I am doing a installation of NW2004s Dual Stack system with AS abap, AS Java, EP, EP core & BI JAVA.
During phase, install software units, server0 is not coming up. I check in VM, com.sap.portal.fpn.accessservice & sap.com/irj are in status STARTING.
please let me know if you can suggest something.
best regards
ashish

Hi Ashish,
Paste the logs for dev_server0 ,dev_dispatcher and std_server0.
With Regards
Ashutosh Chaturvedi

Server0 does not start

Hi,
I´ve an ABAP + JAVa system and I did a homogeneous copy and now the J22 engine does not start and is strange because nothing is written into the /usr/sap/SID/DV*/j2ee/cluster/server0/log.
Can someone help me as soon as possible?
Thnaks a a lot and best regards

Hi,
I follow the guide :
System copy for SAP systems based on SAP NW 7.0 including enhancement package1 ABAP Java.
The problem is that only 2 Jlaunch are running and just one Jcontrol, also the folder /usr/sap/AB2/DV*/j2ee/cluster/server0/log
is missing .
DB:oracle 10.2.0.4
OS: hp-ux
Any suggestion about what is happening?
thnaks thanks thanks a lot

Java Stack is not started in SAP netweaver ABAP+JAVA Stack

Dear All,
Win2003 64 bit , ECC6.0 , Oracle 10.2.0.2.
Its a newly installed SAP Netweaver Dual Stack (PI) , Yesterday i have done Client copy from 001 to 999 (SAP_UCUS).
Client copy also successfully completed .
login/system_client=999 ,i have activated in Default profile and i have restarted the Server.
Now i dont have issue with ABAP stack ,its working fine, but java stack is not working running.
std_output0.out log:
Service com.sap.aii.adapter.mail.svc started. (812 ms).
Service com.adobe~XMLFormService started. (2937 ms).
Service com.sap.aii.af.ispeak.svc started. (390 ms).
ServiceManager started for 73719 ms.
Framework started for 85781 ms.
SAP J2EE Engine Version 7.00 PatchLevel is running!
PatchLevel September 11, 2006 16:35 GMT
>
Login :### Excluding compile: com.sap.engine.services.webservices.jaxrpc.encoding.TypeMappingImpl::initializeRelations
Excluding compile: com.sap.engine.services.webservices.jaxrpc.encoding.GeneratedComplexType::_loadInto
Excluding compile: com.sap.engine.services.webservices.jaxrpc.encoding.InstanceBuilder::readSequence
Excluding compile: com.sap.engine.services.webservices.jaxrpc.encoding.InstanceBuilder::readElement
SAP J2EE Engine Version 7.00 PatchLevel is shutting down! PatchLevel September 11, 2006 16:35 GMT
=================
C:\Documents and Settings\ixdadm>jcmon pf=D:\usr\sap\IXD\SYS\profile\IXD_DVEBMGS
00_SAPXIDEV
[Thr 4576] MtxInit: -2 0 0
============================================================
JControl Monitor Program - Main Menu
============================================================
0 : exit
10 : Cluster Administration Menu
20 : Local Administration Menu
30 : Shared Memory Menu (Solid Rock, experimental)
command => 20
Can't open shared memory administration (rc = -107)
============================================================
Kindly suggest .
Edited by: satheesh0812 on Dec 30, 2010 12:00 PM

Hi,
Please provide the full log entries of server0_out.log.
You can access UME service properties in config tool by following this path..
Global server configuration -> services -> com.sap.security.core.ume.service
There you can set the following settings for new client 900 (it u want to change it)
ume.r3.connection.master.client
ume.r3.connection.master.user
ume.r3.connection.master.passwd
Refer this [useful link|http://help.sap.com/saphelp_nw04s/helpdata/en/45/1bbdccc7850064e10000000a1553f7/frameset.htm] to get more detailed information. Refer [Config Tool actviities|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0a3d713-5ab6-2c10-ddb1-e7487bc33384?quicklink=index&overridelayout=true] link To get more information.
Also, Make sure that the Users J2EE_GUEST, J2EE_ADMIN, SAPJSF ABAP Users exist in the ABAP client (i.e. client number as mentioned in ume.r3.connection.master.client ) and they are not locked. All the required roles need to be assigned properly.
Regards,
Bhavik G. Shroff
Edited by: Bhavik G. Shroff on Dec 31, 2010 2:58 PM

Java Server can not start while applying the Patches !!!

Hi Gurus,
Under NW04s, While updating Patch Level from 9 to 13 after fresh Installation of EP 7.0 with BI JAVA under RH Linux / Oracle.At first the patch application process went ok till the first 4 component. Afert that, the error occurred that " J2EE Engine is running in safe mode. Pl. restart the Java Engine and
then Restart the JSPM." When I restarted the J2EE engine and then JSPM, I have the following 2 error
messages in
A std_server0.out File :
#1 Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: No such file or directory jar:file:/etc/alternatives/ibmjava/142/jre/lib/ext/ibmjceprovider.jar
#2
The error occurred while trying to load "com.sap.security.core.server.ume.service.UMEServiceFileIO".
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:401)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:243)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Framework -> criticalShutdown Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Jan 19, 2008 2:50:14 AM com.sap.engine.core.Framework [SAPEngine_System_Threadimpl:5]_53 Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
</verbosegc>
<<<
B. The file dev_server0 has the following warning msg :
Thr 182896194496 Sat Jan 19 02:49:16 2008
Thr 182896194496 *** WARNING => INFO: Unknown property http://instance.box.number=EP1JC00v38cab1 http://jstartxx_mt. 841
Thr 182896194496 *** WARNING => INFO: Unknown property http://instance.en.host=v38cab1 http://jstartxx_mt. 841
Thr 182896194496 *** WARNING => INFO: Unknown property http://instance.en.port=3201 http://jstartxx_mt. 841
Thr 182896194496 *** WARNING => INFO: Unknown property http://instance.system.id=0 http://jstartxx_mt. 841
JStartupReadInstanceProperties: read instance properties [/usr/sap/EP1/JC00/j2ee/cluster/instance.properties]
-> ms host : v38cab1
-> ms port : 3901
-> OS libs : /usr/sap/EP1/JC00/j2ee/os_libs
-> Admin URL :
-> run mode : safe
-> run action : UPGRADE
-> enabled : yes
<<<
C The dev_jcontrol file has error msg that server0 not running ...which is apparent from the above message.
I have checked my J2SDK Version i.e. ibmjava 142 and also, JAVA_HOME and PATH Variable and it appears that ther's nothing wrong in it as mentioned :
JAVA_HOME=/etc/alternatives/ibmjava/142
PATH=/etc/alternatives/ibmjava/142/bin:/etc/alternatives/bin/bin:/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin
I have checked the compatibility of the HW and J2SDK version as per note 861215 and it is ok as per the note
-It seems that due to error A #1 : Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: ..the J2EE Engine runs in safe mode for a while and then it goes down.
So, any idea that how to solve this issue ? I read somewhere that ibmjava 142 is THE correct one and the other versions are having sever issue with the UNIX / Linux ..is this true ?
Pl. help as we are facing this problem since last 24 hours and it is very critical.
Any / All Help is most welcome and would be rewarded with appropriate point without failure.
Many Thanks in Advance,
Regards,
ISHAN

Hi Gurus,
Under NW04s, While updating Patch Level from 9 to 13 after fresh Installation of EP 7.0 with BI JAVA under RH Linux / Oracle.At first the patch application process went ok till the first 4 component. Afert that, the error occurred that " J2EE Engine is running in safe mode. Pl. restart the Java Engine and
then Restart the JSPM." When I restarted the J2EE engine and then JSPM, I have the following 2 error
messages in
A std_server0.out File :
#1 Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: No such file or directory jar:file:/etc/alternatives/ibmjava/142/jre/lib/ext/ibmjceprovider.jar
#2
The error occurred while trying to load "com.sap.security.core.server.ume.service.UMEServiceFileIO".
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:401)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:243)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Framework -> criticalShutdown Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Jan 19, 2008 2:50:14 AM com.sap.engine.core.Framework [SAPEngine_System_Threadimpl:5]_53 Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
</verbosegc>
<<<
B. The file dev_server0 has the following warning msg :
Thr 182896194496 Sat Jan 19 02:49:16 2008
Thr 182896194496 *** WARNING => INFO: Unknown property http://instance.box.number=EP1JC00v38cab1 http://jstartxx_mt. 841
Thr 182896194496 *** WARNING => INFO: Unknown property http://instance.en.host=v38cab1 http://jstartxx_mt. 841
Thr 182896194496 *** WARNING => INFO: Unknown property http://instance.en.port=3201 http://jstartxx_mt. 841
Thr 182896194496 *** WARNING => INFO: Unknown property http://instance.system.id=0 http://jstartxx_mt. 841
JStartupReadInstanceProperties: read instance properties [/usr/sap/EP1/JC00/j2ee/cluster/instance.properties]
-> ms host : v38cab1
-> ms port : 3901
-> OS libs : /usr/sap/EP1/JC00/j2ee/os_libs
-> Admin URL :
-> run mode : safe
-> run action : UPGRADE
-> enabled : yes
<<<
C The dev_jcontrol file has error msg that server0 not running ...which is apparent from the above message.
I have checked my J2SDK Version i.e. ibmjava 142 and also, JAVA_HOME and PATH Variable and it appears that ther's nothing wrong in it as mentioned :
JAVA_HOME=/etc/alternatives/ibmjava/142
PATH=/etc/alternatives/ibmjava/142/bin:/etc/alternatives/bin/bin:/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin
I have checked the compatibility of the HW and J2SDK version as per note 861215 and it is ok as per the note
-It seems that due to error A #1 : Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: ..the J2EE Engine runs in safe mode for a while and then it goes down.
So, any idea that how to solve this issue ? I read somewhere that ibmjava 142 is THE correct one and the other versions are having sever issue with the UNIX / Linux ..is this true ?
Pl. help as we are facing this problem since last 24 hours and it is very critical.
Any / All Help is most welcome and would be rewarded with appropriate point without failure.
Many Thanks in Advance,
Regards,
ISHAN

Central Instance Java Server0/Server1 not starting

Similar Messages

Maybe you are looking for