Job error: Sync jdbc/SAP/BC_ADM
Hi all,
2 days ago i trigger an analysis risk and it had an error. I saw the log and it said:
"Warnning: Synchronisation reader could not access data source jdbc/SAP/BC_ADM"
And then the job stopped. Does anyone know why did it occurred?
We have SAP GRC 5.3.
Thank you in advanced!!!
Hi
Some times JAVA errors are very tough to understand by Security consultant.
it is good if you restart J2ee server then many of the errors are get off.
Regards
Hari
Similar Messages
-
SAP ME 15 Installation error in CTC SAP ME Configuration
Hi,
We are doing an SAP ME 15 installation and are getting an error during CTC
for "SAP ME Configuration for installation" during step 6 of 7 "Create or update Global site".
All the JDBC Datasources for VMJDBC are green and working.
From the default trace log I can see this:
#2.0 #2014 10 07 12:36:47:020#+0200#Error#com.sap.tc.lm.ctc.cul.serviceimpl.process.InvokeServiceControllerDefault#
#BC-INS-CTC#tc~lm~ctc~cul~core_sda#C000AC117450002A00000013000002F4#7447350000000004#sap.com/tc~lm~itsam~ui~mainframe~wd#com.sap.tc.lm.ctc.cul.serviceimpl.process.InvokeServiceControllerDefault#Administrator#1##693380984E0C11E49BBF00000071A336#290bfa2c4e0811e4c25d0050569c1b6e#290bfa2c4e0811e4c25d0050569c1b6e#0#Thread[Thread-49,5,Dedicated_Application_Thread]#Plain##
Service execution error; invocation target error when calling method createAndUpdateGlobalSite in class com.sap.me.ctc.services.idat.GlobalSiteConfiguration of component sap.com/xapps~me~ctc~ear (error message = com.sap.me.frame.domain.BusinessRuntimeException: java.lang.NullPointerException: while trying to invoke the method java.util.List.clear() of a null object loaded from field com.sap.sql.jdbc.vendor.VendorPooledConnection.openStatements of an object loaded from local variable 'this')
[EXCEPTION]
com.sap.tc.lm.ctc.cul.api.CULServiceException: Service execution error; invocation target error when calling method createAndUpdateGlobalSite in class com.sap.me.ctc.services.idat.GlobalSiteConfiguration of component sap.com/xapps~me~ctc~ear (error message = com.sap.me.frame.domain.BusinessRuntimeException: java.lang.NullPointerException: while trying to invoke the method java.util.List.clear() of a null object loaded from field com.sap.sql.jdbc.vendor.VendorPooledConnection.openStatements of an object loaded from local variable 'this')
at com.sap.tc.lm.ctc.cul.broker.BrokerServiceExecuter.executeService(BrokerServiceExecuter.java:61)
at com.sap.tc.lm.ctc.cul.serviceimpl.executor.CULServiceExecutor.executeService(CULServiceExecutor.java:36)
at com.sap.tc.lm.ctc.cul.serviceimpl.process.InvokeServiceControllerDefault.execute(InvokeServiceControllerDefault.java:133)
at com.sap.tc.lm.ctc.metamodel.process.controller.ProcessControllerImpl.remoteOrLocalExecution(ProcessControllerImpl.java:741)
at com.sap.tc.lm.ctc.metamodel.process.controller.ProcessControllerImpl.execute(ProcessControllerImpl.java:286)
at com.sap.tc.lm.ctc.metamodel.process.controller.ProcessExecuter.run(ProcessExecuter.java:156)
at java.lang.Thread.run(Thread.java:763)
Caused by: com.sap.tc.lm.ctc.provider.javaServiceProvider.exceptions.CPIServiceExecutionException: Service execution error; invocation target error when calling method createAndUpdateGlobalSite in class com.sap.me.ctc.services.idat.GlobalSiteConfiguration of component sap.com/xapps~me~ctc~ear (error message = com.sap.me.frame.domain.BusinessRuntimeException: java.lang.NullPointerException: while trying to invoke the method java.util.List.clear() of a null object loaded from field com.sap.sql.jdbc.vendor.VendorPooledConnection.openStatements of an object loaded from local variable 'this')
at com.sap.tc.lm.ctc.provider.javaServiceProvider.JavaMethodExecuter.invoke(JavaMethodExecuter.java:291)
at com.sap.tc.lm.ctc.provider.javaServiceProvider.JavaServiceExecuter.executeService(JavaServiceExecuter.java:86)
at com.sap.tc.lm.ctc.cul.broker.BrokerServiceExecuter.executeService(BrokerServiceExecuter.java:59)
... 6 more
Caused by: java.lang.reflect.InvocationTargetException
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:597)
at com.sap.tc.lm.ctc.provider.javaServiceProvider.JavaMethodExecuter.invoke(JavaMethodExecuter.java:259)
... 8 more
Caused by: com.visiprise.frame.service.ext.ExtensionExecutionException: com.sap.me.frame.domain.BusinessRuntimeException: java.lang.NullPointerException: while trying to invoke the method java.util.List.clear() of a null object loaded from field com.sap.sql.jdbc.vendor.VendorPooledConnection.openStatements of an object loaded from local variable 'this'
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.handleExtensionException(GenericServiceExecutionProcess.java:174)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.executeExtension(GenericServiceExecutionProcess.java:158)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.executeExtensions(GenericServiceExecutionProcess.java:125)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.execute(GenericServiceExecutionProcess.java:97)
at com.visiprise.frame.service.ext.TransactionDecoratorSupport.execute(TransactionDecoratorSupport.java:86)
at com.sap.me.frame.service.BaseTransactionExecutionProcess.execute(BaseTransactionExecutionProcess.java:95)
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:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:172)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:99)
at com.sun.proxy.$Proxy916.execute(Unknown Source)
at com.visiprise.frame.service.ext.ServiceExecutionInterceptor.intercept(ServiceExecutionInterceptor.java:44)
at com.sap.me.frame.service.BusinessServiceExecutionInterceptor.intercept(BusinessServiceExecutionInterceptor.java:57)
at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
at com.visiprise.frame.proxy.GenericSOProxy.invoke(GenericSOProxy.java:81)
at com.sun.proxy.$Proxy1546.loadInitialData(Unknown Source)
at com.sap.me.plant.impl.SiteConfigurationService.createGlobalSite(SiteConfigurationService.java:397)
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:597)
at com.visiprise.frame.proxy.DefaultInterceptor.intercept(DefaultInterceptor.java:31)
at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
at com.visiprise.frame.proxy.ProxyContext.process(ProxyContext.java:67)
at com.visiprise.frame.service.ext.MethodInvocationActivity.execute(MethodInvocationActivity.java:34)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.executeActivity(GenericServiceExecutionProcess.java:202)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.executeService(GenericServiceExecutionProcess.java:136)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.execute(GenericServiceExecutionProcess.java:94)
at com.visiprise.frame.service.ext.TransactionDecoratorSupport.execute(TransactionDecoratorSupport.java:86)
at com.sap.me.frame.service.BaseTransactionExecutionProcess.execute(BaseTransactionExecutionProcess.java:95)
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:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:172)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:99)
at com.sun.proxy.$Proxy916.execute(Unknown Source)
at com.visiprise.frame.service.ext.ServiceExecutionInterceptor.intercept(ServiceExecutionInterceptor.java:44)
at com.sap.me.frame.service.BusinessServiceExecutionInterceptor.intercept(BusinessServiceExecutionInterceptor.java:57)
at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
at com.visiprise.frame.proxy.GenericSOProxy.invoke(GenericSOProxy.java:81)
at com.sun.proxy.$Proxy1546.createGlobalSite(Unknown Source)
at com.sap.me.ctc.services.idat.GlobalSiteConfiguration.createAndUpdateGlobalSite(GlobalSiteConfiguration.java:191)
... 13 more
Caused by: com.sap.me.frame.domain.BusinessRuntimeException: java.lang.NullPointerException: while trying to invoke the method java.util.List.clear() of a null object loaded from field com.sap.sql.jdbc.vendor.VendorPooledConnection.openStatements of an object loaded from local variable 'this'
at com.sap.me.common.impl.DynamicInvocationService.invoke(DynamicInvocationService.java:76)
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:597)
at com.visiprise.frame.proxy.DefaultInterceptor.intercept(DefaultInterceptor.java:31)
at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
at com.visiprise.frame.proxy.ProxyContext.process(ProxyContext.java:67)
at com.visiprise.frame.service.ext.MethodInvocationActivity.execute(MethodInvocationActivity.java:34)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.executeActivity(GenericServiceExecutionProcess.java:202)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.executeService(GenericServiceExecutionProcess.java:136)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.execute(GenericServiceExecutionProcess.java:94)
at com.visiprise.frame.service.ext.TransactionDecoratorSupport.execute(TransactionDecoratorSupport.java:86)
at com.sap.me.frame.service.BaseTransactionExecutionProcess.execute(BaseTransactionExecutionProcess.java:95)
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:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:172)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:99)
at com.sun.proxy.$Proxy916.execute(Unknown Source)
at com.visiprise.frame.service.ext.ServiceExecutionInterceptor.intercept(ServiceExecutionInterceptor.java:44)
at com.sap.me.frame.service.BusinessServiceExecutionInterceptor.intercept(BusinessServiceExecutionInterceptor.java:57)
at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
at com.visiprise.frame.proxy.GenericSOProxy.invoke(GenericSOProxy.java:81)
at com.sun.proxy.$Proxy1578.invoke(Unknown Source)
at com.sap.me.common.impl.XmlInvocationService.invokeConfigLoad(XmlInvocationService.java:695)
at com.sap.me.common.impl.XmlInvocationService.loadApplicationConfiguration(XmlInvocationService.java:174)
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:597)
at com.visiprise.frame.proxy.DefaultInterceptor.intercept(DefaultInterceptor.java:31)
at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
at com.visiprise.frame.proxy.ProxyContext.process(ProxyContext.java:67)
at com.visiprise.frame.service.ext.MethodInvocationActivity.execute(MethodInvocationActivity.java:34)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.executeActivity(GenericServiceExecutionProcess.java:202)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.executeService(GenericServiceExecutionProcess.java:136)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.execute(GenericServiceExecutionProcess.java:94)
at com.visiprise.frame.service.ext.TransactionDecoratorSupport.execute(TransactionDecoratorSupport.java:86)
at com.sap.me.frame.service.BaseTransactionExecutionProcess.execute(BaseTransactionExecutionProcess.java:95)
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:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:172)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:99)
at com.sun.proxy.$Proxy916.execute(Unknown Source)
at com.visiprise.frame.service.ext.ServiceExecutionInterceptor.intercept(ServiceExecutionInterceptor.java:44)
at com.sap.me.frame.service.BusinessServiceExecutionInterceptor.intercept(BusinessServiceExecutionInterceptor.java:57)
at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
at com.visiprise.frame.proxy.GenericSOProxy.invoke(GenericSOProxy.java:81)
at com.sun.proxy.$Proxy1535.loadApplicationConfiguration(Unknown Source)
at com.sap.me.plant.impl.ConfigDataLoader.execute(ConfigDataLoader.java:103)
at com.sap.me.plant.impl.ConfigDataLoader.execute(ConfigDataLoader.java:77)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.executeActivity(GenericServiceExecutionProcess.java:202)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.executeExtension(GenericServiceExecutionProcess.java:153)
... 94 more
Caused by: java.lang.NullPointerException: while trying to invoke the method java.util.List.clear() of a null object loaded from field com.sap.sql.jdbc.vendor.VendorPooledConnection.openStatements of an object loaded from local variable 'this'
at com.sap.sql.jdbc.vendor.VendorPooledConnection.invalidate(VendorPooledConnection.java:352)
at com.sap.sql.jdbc.vendor.VendorPooledConnection.destroyConnection(VendorPooledConnection.java:317)
at com.sap.sql.connect.datasource.DBDataSourceImpl.closePooledConnection(DBDataSourceImpl.java:737)
at com.sap.sql.connect.datasource.DBDataSourceImpl.destroy(DBDataSourceImpl.java:1043)
at com.sap.sql.connect.datasource.DBDataSourceImpl.destroy(DBDataSourceImpl.java:45)
at com.sap.sql.connect.pool.CreatedObjectsPool.destroy(CreatedObjectsPool.java:140)
at com.sap.sql.connect.pool.Pool.release(Pool.java:558)
at com.sap.sql.connect.datasource.DBDataSourceImpl.releasePooledConnection(DBDataSourceImpl.java:914)
at com.sap.sql.connect.datasource.PooledConnectionHandle.close(PooledConnectionHandle.java:59)
at com.sap.engine.services.dbpool.spi.XAManagedConnectionImpl.destroy(XAManagedConnectionImpl.java:70)
at com.sap.engine.services.connector.jca.ConnectionHashSet.destroy(ConnectionHashSet.java:450)
at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:359)
at com.sap.engine.services.connector.jca.ShareableConnectionManager.allocateConnection(ShareableConnectionManager.java:54)
at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:52)
at com.sap.me.frame.AbstractDataSource.getDBConnection(AbstractDataSource.java:413)
at com.sap.me.frame.AbstractDataSource.executeQuery(AbstractDataSource.java:142)
at com.sap.me.frame.BaseDataSource.executeQuery(BaseDataSource.java:197)
at com.sap.me.frame.BaseDataSource.recordExists(BaseDataSource.java:830)
at com.sap.me.frame.AuditLogHandler.createAL(AuditLogHandler.java:129)
at com.sap.me.frame.AuditLogHandler.performAuditLogWork(AuditLogHandler.java:953)
at com.sap.me.frame.dao.AuditLogListener.performAuditLog(AuditLogListener.java:62)
at com.sap.me.frame.dao.AuditLogListener.afterCreate(AuditLogListener.java:29)
at com.sap.me.frame.dao.CompositeLifeCycleListener.afterCreate(CompositeLifeCycleListener.java:83)
at com.sap.me.frame.dao.ProductionDataAccessService.create(ProductionDataAccessService.java:193)
at com.sap.me.frame.dao.DomainDataAccessService.create(DomainDataAccessService.java:65)
at com.sap.me.frame.dao.DomainDataAccessService.create(DomainDataAccessService.java:30)
at com.sap.me.frame.domain.DefaultDomainService.create(DefaultDomainService.java:96)
at com.sap.me.activity.impl.ExtensionConfigurationService.createExtensionPoint(ExtensionConfigurationService.java:243)
at com.sap.me.activity.impl.ExtensionConfigurationService.createExtensionLocal(ExtensionConfigurationService.java:962)
at com.sap.me.activity.impl.ExtensionConfigurationService.createExtensionByCreateExtensionRequest(ExtensionConfigurationService.java:230)
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:597)
at com.visiprise.frame.proxy.DefaultInterceptor.intercept(DefaultInterceptor.java:31)
at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
at com.visiprise.frame.proxy.ProxyContext.process(ProxyContext.java:67)
at com.visiprise.frame.service.ext.MethodInvocationActivity.execute(MethodInvocationActivity.java:34)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.executeActivity(GenericServiceExecutionProcess.java:202)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.executeService(GenericServiceExecutionProcess.java:136)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.execute(GenericServiceExecutionProcess.java:94)
at com.visiprise.frame.service.ext.TransactionDecoratorSupport.execute(TransactionDecoratorSupport.java:86)
at com.sap.me.frame.service.BaseTransactionExecutionProcess.execute(BaseTransactionExecutionProcess.java:95)
at sun.reflect.GeneratedMethodAccessor454.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:172)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:99)
at com.sun.proxy.$Proxy916.execute(Unknown Source)
at com.visiprise.frame.service.ext.ServiceExecutionInterceptor.intercept(ServiceExecutionInterceptor.java:44)
at com.sap.me.frame.service.BusinessServiceExecutionInterceptor.intercept(BusinessServiceExecutionInterceptor.java:57)
at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
at com.visiprise.frame.proxy.GenericSOProxy.invoke(GenericSOProxy.java:81)
at com.sun.proxy.$Proxy1581.createExtensionByCreateExtensionRequest(Unknown Source)
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:597)
at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:57)
at sun.reflect.GeneratedMethodAccessor47.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:260)
at java.beans.Statement.invokeInternal(Statement.java:239)
at java.beans.Statement.access$000(Statement.java:39)
at java.beans.Statement$2.run(Statement.java:140)
at java.security.AccessController.doPrivileged(Native Method)
at java.beans.Statement.invoke(Statement.java:137)
at java.beans.Expression.getValue(Expression.java:98)
at com.sap.me.common.impl.DynamicInvocationService.invoke(DynamicInvocationService.java:64)
... 188 more
Best regards,
JohanHi Chandrababu,
Unfortunately I don't know any more than this. I have only done one SAP ME 15 installation so far
and this was the solution to our error situation.
If you don't get it working then you should log a support ticket to SAP.
Best regards,
Johan -
Sending job error message to admin by email
Hi everyone...
Anyone knows how to send job error message to admin by email? For example, if crawler failed, an email is sent to admin with the error message. I'm thinking of building windows service which run at the background and knows when a job fail and send the error message through email to admin.
Is there a better way?
Cheers,
Jefi Santosohi,
>>>Can this be achieved through BPM?
yes you can put your transformation step
and send step in a block and specify an exception
branch and catch all exceptions that will
occur during transformations and the send step
then you can send info from the exception branch to
any other system
you won't be able to catch the error's name
but you will be able to notify any thinrd party
about the error
more on error catching:
http://help.sap.com/saphelp_nw04/helpdata/en/33/4a773f12f14a18e10000000a114084/content.htm
Regards,
michal -
Error while installing SAP NetWeaver Composition Environment 7.1 SR3
I got the following error while installing SAP NetWeaver Composition Environment 7.1 SR3 Evalution SDN Version - Java EE only
on my Windows XP, 1 GB RAM, 1.6 GHZ processor speed
An error occurred while processing service SAP NetWeaver CE Developer Edition > SAP NetWeaver CE Development System( Last error reported by the step :Java EE Engine configuration error. DIAGNOSIS: See output of logfile configtool.0.trc: ' INFO: Loading tool launcher... INFO: [OS: Windows XP] [VM vendor: SAP AG] [VM version: 5.1.000] [VM type: SAP Java Server VM] INFO: Main class to start: "com.sap.engine.configtool.batch.BatchInstall" INFO: Loading 51 JAR files: [D:\usr\sap\CE1\SYS\global\security\lib\tools\iaik_jce.jar, D:\usr\sap\CE1\SYS\global\security\lib\tools\iaik_jsse.jar, D:\usr\sap\CE1\SYS\global\security\lib\tools\iaik_smime.jar, D:\usr\sap\CE1\SYS\global\security\lib\tools\iaik_ssl.jar, D:\usr\sap\CE1\SYS\global\security\lib\tools\w3c_http.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\jaas.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\jdbc.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\jload.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\jperflib.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\jsizecheck.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\jstartup.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\jstartupapi.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\jstartupimpl.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comsl.ut.infoprovider_lib.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comsl.ut.manager.offline.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comslctcimport.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcantlrruntime.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcblconfigimpl.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcbldeploycontrolleroffline_phase_asm.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcbliqlibimpl.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcbljdsrjdsr.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcbljkernel_dummyframe_dummy.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcbljkernel_dummykernel_dummy.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcbljkernel_utilimpl.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcbljrfcimpl.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcbloffline_launcherimpl.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcblopensqlimplStandalone.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcblslutilityimpl.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcdddbcatalogimplCatalog.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcdddbdictionarydatabaseimplDictionaryDatabase.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcexceptionimpl.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtci18ncpjarIMPL.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcjebootstrapimpl.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcjecfscontainerstandalone_impl.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcjeclientlibimpl.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcjeconfigtool.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcjeextramile.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcjeofflineconfigurationimpl.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcjeofflinelicense.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcjeoffline_deployimpl.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcjewebcontainerimpl.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcloggingjavaimpl.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcsapxmltoolkitsapxmltoolkit.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcsdtcvlimpl.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcsecdestinationslibimpl.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcsecinstallertoolsimpl.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcseclikeylikey_assembly.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\sap.comtcsecsecstorefsjavacore.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\servlet.jar, C:\Program Files\sapinst_instdir\CE71_DEV_ADA\INSTALL\install\lib\tcje~cl_deploy.jar, D:\sapdb\programs\runtime\jar\sapdbc.jar] INFO: Start PerfTimes : loadNativeLayer: loading jperflib failed. no jperflib in java.library.path '.). You may now
choose Retry to repeat the current step.
choose View Log to get more information about the error.
stop the task and continue with it later.
Log files are written to C:\Program Files/sapinst_instdir/CE71_DEV_ADA/INSTALL.
Plz help me..itz urgent,
Cheers,
Aravind.Hi Eric,
The trace file says,
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.7.1006]/>
<!NAME[configtool.trc]/>
<!PATTERN[configtool.trc]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[UTF8]/>
<!FILESET[0, 5, 1000000]/>
<!PREVIOUSFILE[configtool.4.trc]/>
<!NEXTFILE[configtool.1.trc]/>
<!LOGHEADER[END]/>
#1.5 #02004C4F4F50000000000001005E8D7DFFFFFFFFFFFFFFFF#1202100775046#configtool##configtool#######Thread[main,5,main]##0#0#Fatal#1#/configtool#Java###Can't connect to DB.
[EXCEPTION]
#1#com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:409)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:153)
at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:48)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:176)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:263)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:57)
at com.sap.engine.configtool.batch.BatchInstall.executeTasks(BatchInstall.java:192)
at com.sap.engine.configtool.batch.BatchInstall.main(BatchInstall.java:238)
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.offline.OfflineToolStart.main(OfflineToolStart.java:161)
Caused by: com.sap.dbtech.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Cannot connect to jdbc:sapdb://computer/CE1 [Restart required].
at com.sap.dbtech.jdbc.DriverSapDB.connect(DriverSapDB.java:216)
at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendorConnection(DriverPooledConnectionFactory.java:50)
at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledConnection(DriverPooledConnectionFactory.java:37)
at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnection(DBDataSourceImpl.java:677)
at com.sap.sql.connect.datasource.DBDataSourceImpl.newPooledConnection(DBDataSourceImpl.java:626)
at com.sap.sql.connect.datasource.DBDataSourceImpl.getPooledConnection(DBDataSourceImpl.java:165)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:211)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:353)
... 12 more
#1.5 #02004C4F4F5000000000000101904E0DFFFFFFFFFFFFFFFF#1202101914781#configtool##configtool#######Thread[main,5,main]##0#0#Fatal#1#/configtool#Java###Can't connect to DB.
[EXCEPTION]
#1#com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:409)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:153)
at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:48)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:176)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:263)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:57)
at com.sap.engine.configtool.batch.BatchInstall.executeTasks(BatchInstall.java:192)
at com.sap.engine.configtool.batch.BatchInstall.main(BatchInstall.java:238)
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.offline.OfflineToolStart.main(OfflineToolStart.java:161)
Caused by: com.sap.dbtech.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Cannot connect to jdbc:sapdb://computer/CE1 [Restart required].
at com.sap.dbtech.jdbc.DriverSapDB.connect(DriverSapDB.java:216)
at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendorConnection(DriverPooledConnectionFactory.java:50)
at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledConnection(DriverPooledConnectionFactory.java:37)
at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnection(DBDataSourceImpl.java:677)
at com.sap.sql.connect.datasource.DBDataSourceImpl.newPooledConnection(DBDataSourceImpl.java:626)
at com.sap.sql.connect.datasource.DBDataSourceImpl.getPooledConnection(DBDataSourceImpl.java:165)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:211)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:353)
... 12 more
#1.5 #02004C4F4F50000000000001014B84C7FFFFFFFFFFFFFFFF#1202102025296#configtool##configtool#######Thread[main,5,main]##0#0#Fatal#1#/configtool#Java###Can't connect to DB.
[EXCEPTION]
#1#com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:409)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:153)
at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:48)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:176)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:263)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:57)
at com.sap.engine.configtool.batch.BatchInstall.executeTasks(BatchInstall.java:192)
at com.sap.engine.configtool.batch.BatchInstall.main(BatchInstall.java:238)
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.offline.OfflineToolStart.main(OfflineToolStart.java:161)
Caused by: com.sap.dbtech.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Cannot connect to jdbc:sapdb://computer/CE1 [Restart required].
at com.sap.dbtech.jdbc.DriverSapDB.connect(DriverSapDB.java:216)
at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendorConnection(DriverPooledConnectionFactory.java:50)
at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledConnection(DriverPooledConnectionFactory.java:37)
at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnection(DBDataSourceImpl.java:677)
at com.sap.sql.connect.datasource.DBDataSourceImpl.newPooledConnection(DBDataSourceImpl.java:626)
at com.sap.sql.connect.datasource.DBDataSourceImpl.getPooledConnection(DBDataSourceImpl.java:165)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:211)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:353)
... 12 more
#1.5 #02004C4F4F5000000000000100E0C7C3FFFFFFFFFFFFFFFF#1202099599843#configtool##configtool#######Thread[main,5,main]##0#0#Fatal#1#/configtool#Java###Can't connect to DB.
[EXCEPTION]
#1#com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:409)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:153)
at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:48)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:176)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:263)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:57)
at com.sap.engine.configtool.batch.BatchInstall.executeTasks(BatchInstall.java:192)
at com.sap.engine.configtool.batch.BatchInstall.main(BatchInstall.java:238)
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.offline.OfflineToolStart.main(OfflineToolStart.java:161)
Caused by: com.sap.dbtech.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Cannot connect to jdbc:sapdb://computer/CE1 [Restart required].
at com.sap.dbtech.jdbc.DriverSapDB.connect(DriverSapDB.java:216)
at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendorConnection(DriverPooledConnectionFactory.java:50)
at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledConnection(DriverPooledConnectionFactory.java:37)
at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnection(DBDataSourceImpl.java:677)
at com.sap.sql.connect.datasource.DBDataSourceImpl.newPooledConnection(DBDataSourceImpl.java:626)
at com.sap.sql.connect.datasource.DBDataSourceImpl.getPooledConnection(DBDataSourceImpl.java:165)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:211)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:353)
... 12 more
#1.5 #02004C4F4F5000000000000100C22A3BFFFFFFFFFFFFFFFF#1202101476187#configtool##configtool#######Thread[main,5,main]##0#0#Fatal#1#/configtool#Java###Can't connect to DB.
[EXCEPTION]
#1#com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:409)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:153)
at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:48)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:176)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:263)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:57)
at com.sap.engine.configtool.batch.BatchInstall.executeTasks(BatchInstall.java:192)
at com.sap.engine.configtool.batch.BatchInstall.main(BatchInstall.java:238)
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.offline.OfflineToolStart.main(OfflineToolStart.java:161)
Caused by: com.sap.dbtech.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Cannot connect to jdbc:sapdb://computer/CE1 [Restart required].
at com.sap.dbtech.jdbc.DriverSapDB.connect(DriverSapDB.java:216)
at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendorConnection(DriverPooledConnectionFactory.java:50)
at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledConnection(DriverPooledConnectionFactory.java:37)
at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnection(DBDataSourceImpl.java:677)
at com.sap.sql.connect.datasource.DBDataSourceImpl.newPooledConnection(DBDataSourceImpl.java:626)
at com.sap.sql.connect.datasource.DBDataSourceImpl.getPooledConnection(DBDataSourceImpl.java:165)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:211)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:353)
... 12 more
#1.5 #02004C4F4F50000000000001014B84C7FFFFFFFFFFFFFFFF#1202107230359#configtool##configtool#######Thread[main,5,main]##0#0#Fatal#1#/configtool#Java###Can't connect to DB.
[EXCEPTION]
#1#com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:409)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:153)
at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:48)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:176)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:263)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:57)
at com.sap.engine.configtool.batch.BatchInstall.executeTasks(BatchInstall.java:192)
at com.sap.engine.configtool.batch.BatchInstall.main(BatchInstall.java:238)
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.offline.OfflineToolStart.main(OfflineToolStart.java:161)
Caused by: com.sap.dbtech.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Cannot connect to jdbc:sapdb://computer/CE1 [Restart required].
at com.sap.dbtech.jdbc.DriverSapDB.connect(DriverSapDB.java:216)
at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendorConnection(DriverPooledConnectionFactory.java:50)
at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledConnection(DriverPooledConnectionFactory.java:37)
at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnection(DBDataSourceImpl.java:677)
at com.sap.sql.connect.datasource.DBDataSourceImpl.newPooledConnection(DBDataSourceImpl.java:626)
at com.sap.sql.connect.datasource.DBDataSourceImpl.getPooledConnection(DBDataSourceImpl.java:165)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:211)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:353)
... 12 more
Can you please advice me how to get rid of this problem?
Is there any prob with MAC address resolution or loop back adapter? if yes, how to get rid of that?
Cheers,
Aravind -
I am getting this error while installing SAP on oracle 9
can anyone help me in solving this issue.
Files\sapinst_instdir\ECC50\SYSTEM\ABAP\ORA\NUC\DB/SAPAPPL0.cmd -l C:\Program Files\sapinst_instdir\ECC50\SYSTEM\ABAP\ORA\NUC\DB/SAPAPPL0.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
ORA-1578 occured when executing SQL
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
(DB) ERROR: DDL statement failed
(DROP INDEX "SMIMPHIO~LID")
DbSlExecute: rc = 103
(SQL error 1418)
error message returned by DbSl:
ORA-01418: specified index does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
DbSl Trace: ORA-1578 occured when executing SQL statement (parse error offset = 32)
(DB) ERROR: DDL statement failed
(CREATE INDEX "SMIMPHIO~LID" ON "SMIMPHIO" ( "LOIO_ID" ) TABLESPACE PSAPC12 STORAGE (INITIAL 1379150 NEXT 0000000640K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
DbSlExecute: rc = 99
(SQL error 1578)
error message returned by DbSl:
ORA-01578: ORACLE data block corrupted (file # 21, block # 253803)
ORA-01110: data file 21: 'C:\ORACLE\C12\SAPDATA1\C12_19\C12.DATA19'
(DB) INFO: disconnected from DB
C:\usr\sap\C12\SYS\exe\run/R3load.exe: job finished with 1 error(s)
C:\usr\sap\C12\SYS\exe\run/R3load.exe: END OF LOG: 20070712094205After reinstalling this is error, can anyone throw some light and steps
C:\usr\sap\C12\SYS\exe\run/R3load.exe: START OF LOG: 20070712150850
C:\usr\sap\C12\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#6 $ SAP
C:\usr\sap\C12\SYS\exe\run/R3load.exe: version R6.40/V1.4
C:\usr\sap\C12\SYS\exe\run/R3load.exe -ctf I D:/ECC5/ECC5-1/EXP1/DATA/SAP0000.STR C:\Program Files\sapinst_instdir\ECC50\SYSTEM\ABAP\ORA\NUC\DB/DDLORA.TPL C:\Program Files\sapinst_instdir\ECC50\SYSTEM\ABAP\ORA\NUC\DB/SAP0000.TSK ORA -l C:\Program Files\sapinst_instdir\ECC50\SYSTEM\ABAP\ORA\NUC\DB/SAP0000.log -o D
C:\usr\sap\C12\SYS\exe\run/R3load.exe: job completed
C:\usr\sap\C12\SYS\exe\run/R3load.exe: END OF LOG: 20070712150850
C:\usr\sap\C12\SYS\exe\run/R3load.exe: START OF LOG: 20070712151337
C:\usr\sap\C12\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#6 $ SAP
C:\usr\sap\C12\SYS\exe\run/R3load.exe: version R6.40/V1.4
C:\usr\sap\C12\SYS\exe\run/R3load.exe -dbcodepage 1100 -i C:\Program Files\sapinst_instdir\ECC50\SYSTEM\ABAP\ORA\NUC\DB/SAP0000.cmd -l C:\Program Files\sapinst_instdir\ECC50\SYSTEM\ABAP\ORA\NUC\DB/SAP0000.log -stop_on_error
DbSl Trace: OCI-call 'OCISessionBegin' failed: rc = 1034
DbSl Trace: CONNECT failed with sql error '1034'
DbSl Trace: OCI-call 'OCISessionBegin' failed: rc = 1034
DbSl Trace: CONNECT failed with sql error '1034'
(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCISessionBegin' failed: rc = 1034
DbSl Trace: CONNECT failed with sql error '1034'
DbSl Trace: OCI-call 'OCISessionBegin' failed: rc = 1034
DbSl Trace: CONNECT failed with sql error '1034'
(DB) ERROR: DbSlErrorMsg rc = 99
C:\usr\sap\C12\SYS\exe\run/R3load.exe: job finished with 1 error(s)
C:\usr\sap\C12\SYS\exe\run/R3load.exe: END OF LOG: 20070712151338 -
Error in JDBC receiver Communication Channel
Hi,
I am facing a problem at receiver communication channel of JDBC adapter. I am gettting the error as,
"com.sap.aii.af.ra.ms.api.RecoverableException: Channel has reached maximum concurrency(5,000 concurrent Messages) and no free resourse found within 5,000 milliseconds; Increase the maximum Concurrency Level."
I am having the configuration on 4 different nodes. but suddenly only 1 out of 4 is working fine but remaining 3 are throwing this exception. It says to increase Maximum Concurrency level but i want to send only one message through one channel.
Is there a way to rectify this error. I am in deep trouble.
can anyone help me out in solving this issue, Its very greatfull if you do the needy.
Thanks,
Soorya,Hello Aarthi,
I have gone through the link which you have provided for me in this regard. But i am not clear why those values,
AFW.Call.maxConsumers 10
AFW.Recv.maxConsumers 5
AFW.Rqst.maxConsumers 10
AFW.Send.maxConsumers 5
JDBC_http://sap.com/xi/XI/System.Call.maxConsumers 20
JDBC_http://sap.com/xi/XI/System.Recv.maxConsumers 10
JDBC_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
JDBC_http://sap.com/xi/XI/System.Send.maxConsumers 10
These are concerned to MS only but not at JDBC adpater.
We have to look at JDBC prospective but not at the MS prospective.
So can you please look into the issue as JDBC adapter perspective.
Its like this that, there are 5000 messages are waiting for the free resource with in the next 5secs and as it is reached maximum concurrency of 1.
So my question here is,
Is there only one option to increase this value to 2 or more?
Or else do we have any other option to overcome this problem.
Please reply to this ASAP.
Thanks,
Soorya. -
Error while installing SAP IDES ECC6.0 on windows server 2003.
Hi gurus,
I am getting error in installing SAP IDES ECC 6.0. In import ABAP step i am not able to execute all 19 services only 1 services is getting fail that is related to sapview.So,can anyone suggest me that how to solve this error and complete installation.
Thanks in Advace,
nainesh patadia.C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20100726222931
C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20100726223305
C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jul 17 2007 01:28:45
C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe -i SAPVIEW.cmd -dbcodepage 4103 -l SAPVIEW.log -loadprocedure fast
(DB) ERROR: db_connect rc = 256
(DB) ERROR: DbSlErrorMsg rc = 99
C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20100726223306
C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20100726223709
C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jul 17 2007 01:28:45
C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe -i SAPVIEW.cmd -dbcodepage 4103 -l SAPVIEW.log -loadprocedure fast
(DB) ERROR: db_connect rc = 256
(DB) ERROR: DbSlErrorMsg rc = 99
C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20100726223710
C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20100811085903
C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jul 17 2007 01:28:45
C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe -i SAPVIEW.cmd -dbcodepage 4103 -l SAPVIEW.log -loadprocedure fast
(DB) ERROR: db_connect rc = 256
(DB) ERROR: DbSlErrorMsg rc = 99
C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20100811085911 -
Connection error in JDBC Adapter
Hi All,
I am using PI 7.1 and created a JDBC Receiver Comm. Channel.
When I try to create an External Definition in ESR using the mentioned JDBC Channel, I get the following error:
Serialized cause: com.sap.aii.mapping.lookup.LookupException: Connection to system RUNTIME using application RUNTIME lost. Detailed information: Error accessing "http://pidev.ndpl.com:50000/run/system/int?container=web" with user "PIREPUSER". Response code is 500, response message is "Internal Server Error"
+ at com.sap.aii.ibrep.server.lookup.LookupServiceProvider$RemoteClientDelegator.call(LookupServiceProvider.java:122)+
Please help!!!!
regards,
PiyushHi Raj,
I am not using any look up function.
My only intention is to test the jdbc connection.
I am usinng "SQL Server JDBC Driver 2.0" with PI 7.1 and MS SQL Server 2000.
I also deployed the test appliction for jdbc test as per the note 1085539. It also gives the following error:
Exception Occurred : The TCP/IP connection to the host 192.168.164.129, port 445 has failed. Error: "connect timed out. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port.".
Exception Stack Trace : com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host 192.168.164.129, port 445 has failed. Error: "connect timed out. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port.".
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:170)
regards,
Piyush
Edited by: Piyush Mathur SAP on Nov 7, 2009 6:21 AM -
"Error establishing socket" error on JDBC Receiver Channel.
Dear All,
Scenario: Soap to JDBC.
I m getting error on JDBC Receiver Channel. messages are processed succesfully on ABAP Stack and receiver channel is on below error:
ERROR : Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error when attempting to get processing resources: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: DriverManagerException: Cannot establish connection to URL 'jdbc:microsoft:sqlserver://156.5.202.194:3312;DatabaseName=ODW': SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
Note: i already tested another interface with this same IP and it was fine with different port.
jdbc:microsoft:sqlserver://IP:PORT;DatabaseName=Name
Regards,
Manikandanand it was fine with different port
socket exception is (always) related to port....did you check with the network team about this new Port? -
IDOC to JDBC :Error using JDBC
Hi Frnds,
My scenario is Idoc to JDBC scenario, I am getting the follwoing error while trying to process an idoc. Please help me in hadling this error.
Error Message:
JDBC message processing failed; reason Error when attempting to get processing resources: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: DriverManagerException: Cannot establish connection to URL 'jdbc:microsoft:sqlserver://180.1.32.194:1433;DatabaseName=CZZ03;': SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
Regards,
ShivHello Shiva,
Are you installed JDBC Drivers?
Go through this links,
/people/varadharajan.krishnasamy/blog/2007/02/27/configuring-jdbc-connector-service-to-perform-database-lookups
http://searchsap.techtarget.com/tip/0,289483,sid21_gci1246926,00.html
To install JDBC driver follow the how to guide.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how%20to%20install%20and%20configure%20external%20drivers%20for%20jdbc%20and%20jms%20adapters.pdf
Configuration of JDBC Adapter for SQL Server
JDBC Driver = com.microsoft.jdbc.sqlserver.SQLServerDriver
Connection = jdbc:microsoft:sqlserver://hostname:<port>;DatabaseName=<DBName>
UserID and Password.
If the connection is not working find the correct port number.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40b92770-db81-2a10-8e91-f747188d8033
JDBC- X I - R/3 Scenario
/people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
Please check the driver path as mentioned below.
JDBC Driver : sun.jdbc.odbc.JdbcOdbcDriver
Connection:jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=//location of DB table.mdb;
No JDBC driver required.
Receiver JDBC scenario MS access - /people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
follow this thread
Re: Problem when connecting to MS Access through JDBC Adapter.
SAP Note 850116 has details
Thanks,
Satya Kumar
Reward if it is usefulll -
New e-Sourcing 5.0 Install - Error checking JDBC Driver version
Hi All,
I am currently attempting to install an e-Sourcing 5.0 Patch Level E instance on a Windows system using Oracle 10.2.0.3 and WebLogic 8.1 SP4. e-Sourcing's installation and configuration complete without issue. The schema in the database is loaded with the e-Sourcing tables and data.
However, when attempting to deploy the ear file via WebLogic, I receive the following JDBC error:
Error checking JDBC Driver version. Detail: Error: found unsupported JDBC Driver name: Oracle JDBC driver version: 10.1.0.2.0.
The JDBC driver in use is from my Oracle install ..\oracle\product\10.2.0\db_1\jdbc\lib\ojdbc14.jar
I've also tried classes12.jar for versions 9.2.0.8, 10.1.0.2, and 10.2.0.1 but always receive the same error (...driver version: 10.1.0.2.0...) message regardless of the version of driver I am using.
Error Log:
*** Starting Frictionless SRM (5.0.00 E build 08-Apr-2008.16:46) 2009-10-14 20:33:40.656 local3 DEBUG class=ConfigDatabase;server=CAGTAW804886;method=loadFromServletContext();thread=ExecuteThread: '4' for queue: 'weblogic.kernel.System' Cached weblogic.httpd.servlet.reloadCheckSecs=-1 from servlet context
2009-10-14 20:33:40.681 INFO local3 ExecuteThread: '4' for queue: 'weblogic.kernel.System' Disabling logging blackbox support
Unable to start server: unable to connect to the database: oracle [localhost:1521:orcl (SAP/SAP)]:0 reason: Error checking JDBC Driver version. Detail: Error: found unsupported JDBC Driver name: Oracle JDBC driver version: 10.1.0.2.0. Exiting.
Given that the database is loaded with the tables and data I know my instance can connect to the DB. Does anyone know why the deployment would complain that the JDBC driver is incorrect? Is there a way to disable the check and complete the server startup? Is there only a single specific driver that is acceptable for this e-Sourcing version?
Thanks,
Greg
Edited by: Greg Stewart on Oct 15, 2009 3:20 PMThe issue is still occurring.
The Supported Platform documentation indicates that the Oracle JDBC thin driver 10.2.0.1.0 is the supported driver. I have tried both the Classes12.jar and ojdbc14.jar for this version of driver.
What is odd about this error is that it always displays the same message and version #, no matter what version of driver I use.
"found unsupported JDBC Driver name: Oracle JDBC driver version: 10.1.0.2.0" (I execute setup and configuration each time I use a different driver to ensure the ear file is updated)
I have also tried using a different Driver Class path. The installation guides for 5.0 and 5.1 indicate Driver Class as oracle.jdbc.driver.OracleDriver. I have also tried oracle.jdbc.OracleDriver for a few of the versions with no success. I still receive the same error at the same point.
If anyone has run into a similar situation any suggestions or tips to resolving the issue would be appreciated.
Thanks,
Greg -
Hi Gurus,
I have a program with rounddown quantities in deliveries notes. This program is run in background with all other programs. When we checked the batch job error log, we found out that when it gets to this Rounddown program, there are some SAP generated errors messages (examples are listed below).
This issue is there is no way to know exactly which deliveries the error is generated from and if the program actually rounddown the quantities of all the deliveries passed to it and so on, because this error messages are not specific enough (like we can see below).
This program passed this new rounddown quantity number from the internal table using a BAPI.
Is there a way to change this SAP generated error messages to be specific enough like stating which actual delivery number is been affected or even stop at the error and send an email to the user to change the delivery or something in that manner, OR is there a way we can replace this SAP generated error messages with our own messages and send email out to the user.
Error Messages:-
01/16/2008 01:40:40 Step 005 started (program ZSDSO_DELIVERY_QTY_ROUNDDOWN, variant , user ID AUTOSYSUSER
01/16/2008 01:51:35 Item 000020 belongs to delivery group 001
01/16/2008 01:52:13 Item 000020 belongs to delivery group 001
01/16/2008 01:52:15 Item 000030 belongs to delivery group 001
01/16/2008 01:52:19 Item 000020 belongs to delivery group 001
01/16/2008 01:52:29 Dynamic credit check has been exceeded 23,984.52 USD
01/16/2008 01:52:30 Item 000020 (change quantity manually to 400 PC because of complex struct
01/16/2008 01:52:30 Item 000030 (change quantity manually to 400 PC because of complex struct
01/16/2008 01:52:30 Quantity correlation for dependent items has been carried out
01/16/2008 01:52:30 Item 000020 belongs to delivery group 008
01/16/2008 01:52:30 Item 000030 belongs to delivery group 008
01/16/2008 01:52:31 Dynamic credit check has been exceeded 23,984.52 USD
01/16/2008 01:52:32 Delivery quantity must be entered for the item
01/16/2008 01:52:34 Dynamic credit check has been exceeded 23,984.52 USD
01/16/2008 01:53:05 Item 000020 belongs to delivery group 001
01/16/2008 01:54:40 Dynamic credit check has been exceeded 15,501.88 USD
01/16/2008 01:55:53 Item 000020 belongs to delivery group 001
Thanks.
Points will be awarded.This is the Subrouting Form code.
FORM call_bapi_delivery_change TABLES p_i_lips LIKE i_lips.
DATA: w_header_data TYPE bapiobdlvhdrchg,
w_header_control TYPE bapiobdlvhdrctrlchg,
w_delivery TYPE bapiobdlvhdrchg-deliv_numb.
DATA: i_item_data TYPE STANDARD TABLE OF bapiobdlvitemchg,
w_item_data TYPE bapiobdlvitemchg,
i_item_control TYPE STANDARD TABLE OF bapiobdlvitemctrlchg,
w_item_control TYPE bapiobdlvitemctrlchg,
i_return TYPE STANDARD TABLE OF bapiret2,
w_return TYPE bapiret2.
LOOP AT p_i_lips INTO w_lips.
w_item_data-deliv_numb = w_lips-vbeln.
w_item_data-deliv_item = w_lips-posnr.
w_item_data-material = w_lips-matnr.
w_item_data-batch = w_lips-charg.
w_item_data-dlv_qty = w_lips-lfimg.
w_item_data-dlv_qty_imunit = w_lips-lfimg.
w_item_data-fact_unit_nom = 1.
w_item_data-fact_unit_denom = 1.
APPEND w_item_data TO i_item_data.
CLEAR w_item_control.
w_item_control-deliv_numb = w_lips-vbeln.
w_item_control-deliv_item = w_lips-posnr.
IF w_lips-delete NE 'X'.
w_item_control-chg_delqty = 'X'.
ELSEIF w_lips-delete EQ 'X'.
w_item_control-del_item = 'X'.
ENDIF.
APPEND w_item_control TO i_item_control.
ENDLOOP.
w_header_data-deliv_numb = w_lips-vbeln.
w_header_control-deliv_numb = w_lips-vbeln.
w_delivery = w_lips-vbeln.
CALL FUNCTION 'BAPI_OUTB_DELIVERY_CHANGE'
EXPORTING
header_data = w_header_data
header_control = w_header_control
delivery = w_delivery
TECHN_CONTROL =*
TABLES
HEADER_PARTNER =*
HEADER_PARTNER_ADDR =*
HEADER_DEADLINES =*
item_data = i_item_data
item_control = i_item_control
ITEM_SERIAL_NO =*
SUPPLIER_CONS_DATA =*
EXTENSION1 =*
EXTENSION2 =*
return = i_return
TOKENREFERENCE =*
IF sy-subrc EQ 0.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
wait = 'X'.
w_zbdcopendn-otce706 = 'X'.
MODIFY i_zbdcopendn FROM w_zbdcopendn TRANSPORTING otce706
WHERE delivery EQ w_deliveries-vbeln.
ELSE.
CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
DELETE i_zbdcopendn WHERE delivery EQ w_deliveries-vbeln.
DELETE i_deliveries WHERE vbeln EQ w_lips-vbeln.*
w_bad_delv-vbeln = w_deliveries-vbeln.
APPEND w_bad_delv TO i_bad_delv.
ENDIF.
ENDFORM. " call_bapi_delivery_change
Thanks again. -
Hi,
we have installed Data Services Release XI 3.2 SP3 on Linux machine SUSE Linux Enterprise 10 version 64 bit, with
Tomcat 5.5 and Java JRE 5.0.
When we try to execute a simple job that should create a single flat file we receive this error from Job Error Log:
(12.2) 03-07-11 10:36:54 (E) (16840:1206227584) *RUN-050406*: |Session Job_Srv_test|Data flow DF_Load_File
Data flow <DF_Load_File> received a bad system message. Message text from the child process is
<huFFA1, ==========================================================
Please collect the following and send to Customer Support:
1. Log files(error_*, monitor_*, trace_*) associated with this failed job.
2. Exported Atl file of this failed job.
3. DDL statements of tables referenced in this failed job.
4. Data to populate the tables referenced in the failed job. If not possible, get the last few rows (or sample of them) when
the job failed.
5. Core dump, if any, generated from this failed job.
==========================================================
>. The process executing data flow <DF_Load_File> has died abnormally. For NT, check errorlog.txt. For HPUX, check
stack_trace.txt. Also, notify Technical Support.
(12.2) 03-07-11 10:36:54 (E) (16840:1206227584) *RUN-050409*: |Session Job_Srv_test
The job process could not communicate with the data flow <DF_Load_File> process. For details, see previously logged error
<50406>.
(12.2) 03-07-11 10:36:54 (E) (16840:1206227584) *RUN-050406*: |Session Job_Srv_test|Data flow DF_Load_File
Data flow <DF_Load_File> received a bad system message. Message text from the child process is
<huFFA1, ==========================================================
Please collect the following and send to Customer Support:
1. Log files(error_*, monitor_*, trace_*) associated with this failed job.
2. Exported Atl file of this failed job.
3. DDL statements of tables referenced in this failed job.
4. Data to populate the tables referenced in the failed job. If not possible, get the last few rows (or sample of them) when
the job failed.
5. Core dump, if any, generated from this failed job.
==========================================================
>. The process executing data flow <DF_Load_File> has died abnormally. For NT, check errorlog.txt. For HPUX, check
stack_trace.txt. Also, notify Technical Support.
We try to restart Job Server, again and again, but nothing change.
The validate of the data flow and of all the objects in the project return with no error.
From Designer we can see Job Server running successfully but we can't login in Profiler Server although is running, we have configured a Profiler Repo and an User Admin Repo in the Management Console, can't understand why the login is not successful, but i think that is not important to our problem.
We try to create another simple Job but the result it's the same..
Anyone have any ideas of the type of problem?
Thanks.Hi:
Please check if the SAP note below helps you in solving this issue.
1299106 - "Error: Data flow received a bad system message - in job containing Table Comparison object"
Regards,
Francisco Milán. -
Dear All,
WE are getting followin error while scheduling job in db13 tcode.
Function DB6_PLAN_ADD_BATCH failed with return code = Job error
ECC 6.0
Oracle 10gYou indicated that your database is Oracle 10G. This forum is for SAP on DB2 LUW as the database server. Please post your question on the appropriate forum.
Regards,
Adam Wilson
SAP Development Support
IBM Toronto Lab. -
Cleanup of DB13 Plannings + Job error
Hi all,
when i have gone through ST04, JOBS->DBA LOG, i am getting the following job error
16.01.2008 14:00:46 16.01.2008 14:00:46 00:00:00 Collection of DB Performance History OK
16.01.2008 14:00:44 16.01.2008 14:00:46 00:00:02 Cleanup of DB13 Plannings Job error
16.01.2008 13:00:44 16.01.2008 13:00:45 00:00:01 Collection of DB/DBM Config. History OK
16.01.2008 12:00:45 16.01.2008 12:00:45 00:00:00 Collection of DB Performance History OK
16.01.2008 12:00:43 16.01.2008 12:00:45 00:00:02 Cleanup of DB13 Plannings Job error
Actually what is this error ? Why it is caused? what is the solution
regards
padmaThe following note should be helpful ~
[Note 576752 - DB6: Error in job for clear DB13 scheduling|https://service.sap.com/sap/support/notes/576752]
Maybe you are looking for
-
My battery appears to have died and my 80G classic ipod is no longer recognized in itunes, have tried the 5 steps on internet support page and still nothing....is it dead?
-
I was using my laptop and I then **bleep** the screen without turning the screen off to take my dogs for a walk for around 20 minutes. I returned from the walk and went to my laptop ur when I tried to turn it on the screen did not appear. The on butt
-
Report on wake-on-lan enable/disable
Hi, I'm needing to find a way to report on whether or not workstations have Wake-on-Lan enabled. Any ideas? Kind regards, Laura
-
I have mistakenly flashed an older version of firmware onto my device, and now I don't know how to make it accept the correct version of firmware. --- What brought me to this situation ----------------- 1. My N900 had be randomly shutting itself off
-
Opening similiar files in different windows problems
When i opening an existing file in a new window or "desktop" (the ones you see when you press F3), i want them to open in the desktop window that i have selected. For example if i open for file in desktop one in will open there. Now if i wanted to op