OIM11gr2 Error while performing Recon with status field

Hi,
We are performing recon from flatfile(Target recon).We have username and status in the feed.First time if we perform recon user is getting linked.Second time if we change the status of user and run the recon it says not linked to user and we get follwing error in log.
[ERROR] [] [oracle.iam.reconciliation.impl] [tid: [ACTIVE].ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: oiminternal] [ecid: a099d121d15cdd7f:-1ab7d2e8:13b493f3844:-8000-0000000000000004,0] [APP: oim#11.1.2.0.0] Generic Information: {0}[[
oracle.iam.platform.utils.SuperRuntimeException: oracle.iam.platform.tx.OIMTransactionException: java.sql.SQLException: ORA-19202: Error occurred in XML processing
ORA-00972: identifier is too long
ORA-06512: at "SYS.DBMS_XMLGEN", line 7
ORA-06512: at "SYS.DBMS_XMLGEN", line 147
ORA-06512: at "DEV_OIM.OIM_SP_RECONBLKACCOUNTCHGLOG", line 294
ORA-06512: at "DEV_OIM.XL_SP_RECONBLKCHILDMTHACNTCRUD", line 3380
ORA-06512: at "DEV_OIM.XL_SP_RECONBLKACNTRQDCMTCHCRUD", line 91
ORA-06512: at line 1
at oracle.iam.reconciliation.dao.DBCall.execute(DBCall.java:24)
at oracle.iam.reconciliation.dao.ReconActionDao.processSPCall(ReconActionDao.java:1467)
at oracle.iam.reconciliation.dao.ReconActionDao.executeBulkAccountMatchCRUD(ReconActionDao.java:886)
at oracle.iam.reconciliation.impl.AccountHandler.executeBulkCUD(AccountHandler.java:76)
at oracle.iam.reconciliation.impl.BaseEntityTypeHandler.process(BaseEntityTypeHandler.java:57)
at oracle.iam.reconciliation.impl.ActionEngine.processBatch(ActionEngine.java:118)
at oracle.iam.reconciliation.impl.ActionEngine.execute(ActionEngine.java:91)
at oracle.iam.reconciliation.impl.ActionTask.execute(ActionTask.java:73)
at oracle.iam.platform.async.impl.TaskExecutor.executeUnmanagedTask(TaskExecutor.java:99)
at oracle.iam.platform.async.impl.TaskExecutor.execute(TaskExecutor.java:69)
at oracle.iam.platform.async.messaging.MessageReceiver.onMessage(MessageReceiver.java:68)
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.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy1583.onMessage(Unknown Source)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:574)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:477)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:380)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4659)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4345)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3822)
at weblogic.jms.client.JMSSession.access$000(JMSSession.java:115)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: oracle.iam.platform.tx.OIMTransactionException: java.sql.SQLException: ORA-19202: Error occurred in XML processing
ORA-00972: identifier is too long
ORA-06512: at "SYS.DBMS_XMLGEN", line 7
ORA-06512: at "SYS.DBMS_XMLGEN", line 147
ORA-06512: at "DEV_OIM.OIM_SP_RECONBLKACCOUNTCHGLOG", line 294
ORA-06512: at "DEV_OIM.XL_SP_RECONBLKCHILDMTHACNTCRUD", line 3380
ORA-06512: at "DEV_OIM.XL_SP_RECONBLKACNTRQDCMTCHCRUD", line 91
ORA-06512: at line 1
at oracle.iam.platform.tx.OIMTransactionManager.execute(OIMTransactionManager.java:28)
at oracle.iam.reconciliation.dao.ReconActionDao$1ReconDBCall.command(ReconActionDao.java:1423)
at oracle.iam.reconciliation.dao.ReconActionDao$1ReconDBCall.command(ReconActionDao.java:1419)
at oracle.iam.reconciliation.dao.DBCall.execute(DBCall.java:17)
... 33 more
Caused by: java.sql.SQLException: ORA-19202: Error occurred in XML processing
ORA-00972: identifier is too long
ORA-06512: at "SYS.DBMS_XMLGEN", line 7
ORA-06512: at "SYS.DBMS_XMLGEN", line 147
ORA-06512: at "DEV_OIM.OIM_SP_RECONBLKACCOUNTCHGLOG", line 294
ORA-06512: at "DEV_OIM.XL_SP_RECONBLKCHILDMTHACNTCRUD", line 3380
ORA-06512: at "DEV_OIM.XL_SP_RECONBLKACNTRQDCMTCHCRUD", line 91
ORA-06512: at line 1
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:931)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:481)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:548)
at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:213)
at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:1111)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1488)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3769)
at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3954)
at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:9353)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1539)
at weblogic.jdbc.wrapper.PreparedStatement.execute(PreparedStatement.java:99)
at oracle.iam.reconciliation.dao.ReconActionDao$1ReconDBCall$1.process(ReconActionDao.java:1440)
at oracle.iam.reconciliation.dao.ReconActionDao$1ReconDBCall$1.process(ReconActionDao.java:1423)
at oracle.iam.platform.tx.OIMTransactionCallback.doInTransaction(OIMTransactionCallback.java:13)
at oracle.iam.platform.tx.OIMTransactionCallback.doInTransaction(OIMTransactionCallback.java:6)
at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:128)
at oracle.iam.platform.tx.OIMTransactionManager.execute(OIMTransactionManager.java:22)
at oracle.iam.reconciliation.dao.ReconActionDao$1ReconDBCall.command(ReconActionDao.java:1423)
at oracle.iam.reconciliation.dao.ReconActionDao$1ReconDBCall.command(ReconActionDao.java:1419)
at oracle.iam.reconciliation.dao.DBCall.execute(DBCall.java:17)
at oracle.iam.reconciliation.dao.ReconActionDao.processSPCall(ReconActionDao.java:1467)
at oracle.iam.reconciliation.dao.ReconActionDao.executeBulkAccountMatchCRUD(ReconActionDao.java:886)
at oracle.iam.reconciliation.impl.AccountHandler.executeBulkCUD(AccountHandler.java:76)
at oracle.iam.reconciliation.impl.BaseEntityTypeHandler.process(BaseEntityTypeHandler.java:57)
at oracle.iam.reconciliation.impl.ActionEngine.processBatch(ActionEngine.java:118)
at oracle.iam.reconciliation.impl.ActionEngine.execute(ActionEngine.java:91)
at oracle.iam.reconciliation.impl.ActionTask.execute(ActionTask.java:72)
at oracle.iam.platform.async.impl.TaskExecutor.executeUnmanagedTask(TaskExecutor.java:99)
at oracle.iam.platform.async.impl.TaskExecutor.execute(TaskExecutor.java:69)
at oracle.iam.platform.async.messaging.MessageReceiver.onMessage(MessageReceiver.java:68)
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.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy1583.onMessage(Unknown Source)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:574)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:477)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:379)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4659)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4345)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3821)

Similar Messages

Error while performing SSO with java application

hi ALL ,
I got rhe following error when i call a java application in portal using ticket logon sso
Exception report
message Internal Server Error
description The server encountered an internal error (Internal Server Error) that prevented it from fulfilling this request.
exception
com.sap.test.TicketVerifierException: Request does not contain cookies
     at com.sap.test.TicketVerifierServlet.getSSOCookie(TicketVerifierServlet.java:149)
     at com.sap.test.TicketVerifierServlet.getUserFromRequest(TicketVerifierServlet.java:94)
     at com.sap.test.TicketVerifierServlet.doPost(TicketVerifierServlet.java:80)
     at com.sap.test.TicketVerifierServlet.doGet(TicketVerifierServlet.java:68)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
     at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
     at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1027)
     at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125)
     at java.lang.Thread.run(Thread.java:484)

Hi Sarang,
It seems you are following the two basic pre-req.
It may be now possible that your browser might be not allowing cookies. Which browser are u using? Version etc?
Right now u can try two things:
1) When you have logged into portal, type the following command in the adress bar "javascript:alert(document.cookie)". This will give u a popup displaying the cookies formed when logged into portal
2) Use some software like HTTPWatch or ieHeaders and find out the details. It will give you all the cookie details etc.
You should be able to see the JSESSIONID, MYSAPSSO2 cookies...Let me know the result of above..
Regards
Gaurav

ABAP run time error while perform LT06 or create TO with respect to posting

Hi SAP WM Gurus,
System is giving ABAP run time error while perform LT06 or create TO with respect to posting change notice, below are runtime analysis details.
>> Short dump has not been completely stored. It is too big.
>       P_MENGA = P_MENGE.
007940       P_UMREZ = 1.
007950       P_UMREN = 1.
Can you give any idea on this issue.
Thanks and Regards,
SHARAN.

This part is just the place in the program where the error occured, but why the error occured is mentioned earlier in the dump.
Maybe you have a too big number in the field and hence a field overflow, maybe you have a character instead of a number in the field.
Read the dump from the beginning. if you dont know how to read a dump,then try to get help from any local Abaper.

System is giving ABAP run time error while perform LT06 or create TO with r

Hi SAP WM Gurus,
System is giving ABAP run time error while perform LT06 or create TO with respect to posting change notice, below are runtime analysis details.
Short dump has not been completely stored. It is too big.
P_MENGA = P_MENGE.
007940 P_UMREZ = 1.
007950 P_UMREN = 1.
Can you give any idea on this issue.
Thanks and Regards,
SHARAN.

Hi,
Go to Tcode ST22 and mentione the dump code there and check.
Also take help[ of Abapers to fix it.
Thanks
Utsav

Error while performing Oracle 11g upgrade

Hi,
I am facing error while performing an Oracle upgrade from 10.2.0.4 to 11.2.0.2.
DBUA was disconnected with error Ora 1092 Oracle instance terminated.
When tried to run manual upgrade it is showing the below error,
SQL> @catupgrd.sql
DOC>#######################################################################
DOC>#######################################################################
DOC>
DOC> The first time this script is run, there should be no error messages
DOC> generated; all normal upgrade error messages are suppressed.
DOC>
DOC> If this script is being re-run after correcting some problem, then
DOC> expect the following error which is not automatically suppressed:
DOC>
DOC> ORA-00001: unique constraint (<constraint_name>) violated
DOC> possibly in conjunction with
DOC> ORA-06512: at "<procedure/function name>", line NN
DOC>
DOC> These errors will automatically be suppressed by the Database Upgrade
DOC> Assistant (DBUA) when it re-runs an upgrade.
DOC>
DOC>#######################################################################
DOC>#######################################################################
DOC>#
DOC>######################################################################
DOC>######################################################################
DOC> The following statement will cause an "ORA-01722: invalid number"
DOC> error if the user running this script is not SYS. Disconnect
DOC> and reconnect with AS SYSDBA.
DOC>######################################################################
DOC>######################################################################
DOC>#
no rows selected
DOC>######################################################################
DOC>######################################################################
DOC> The following statement will cause an "ORA-01722: invalid number"
DOC> error if the database server version is not correct for this script.
DOC> Perform "ALTER SYSTEM CHECKPOINT" prior to "SHUTDOWN ABORT", and use
DOC> a different script or a different server.
DOC>######################################################################
DOC>######################################################################
DOC>#
SELECT TO_NUMBER('MUST_BE_11_2') FROM v$instance
ERROR at line 1:
ORA-01722: invalid number
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Please help ASAP as this is a production system.
Thanks,
Prabhakar
Edited by: prabhakaryc on Jun 19, 2011 2:47 PM

prabhakaryc wrote:
Hi Orkun Gedik,
>
> Thank you for your quick reply.
>
> Yes i am running this on windows and i have set with correct ORACLE_HOME (11202 directory)
>
> Do you think any other reason ?
>
> I have seen this error log inside of catupgrd.sql and it seems to be very known error but i am not finding the solution anywhere ?
>
> Your quick reply helps me a lot.
>
> Thanks,
> Prabhakar
Hi Prabhakar,
>> DBUA was disconnected with error Ora 1092 Oracle instance terminated.
But, as far as I understand that you didn't completed DB upgrade succesfully. Under this circumstance, you shouldn't change ORACLE_HOME variable to 11.2.0.2. I suggest you that complete Oracle upgrade (restart DBUA) and do not execute upgrade procedures, manually.
Best regards,
Orkun Gedik

VSTS loadtest error while running Loadtest with Runsettings as No of test iterations , ERROR is : could not read result repository: unknown transaction id in results:

Subject: VSTS loadtest error while running Loadtest with Runsettings as No of test iterations , ERROR is : could not read result repository: unknown transaction
id in results:
Hello All,
I am facing the following error while running a loadtest (when i choose the scenario to be executed for No of test iterations). But the same loadtest with the Run duration for X minutes is running fine without any issues.
Any suggestions on the issue i am facing
error is :
could not read result repository: unknown transaction id in results:
or
could not read result repository: unknown request id in results:
Thanks
Satish

Hi Kotapati,
>>Subject: VSTS loadtest error while running Loadtest with Runsettings as No of test iterations , ERROR is : could not read result repository: unknown transaction
id in results:
According to your description, you mean that when you run your load test using the Test Iterations way and then get the error message, am I right?
If yes, please you try to close the VS, and then open this VS again. Then clean your load test project/solution and then re-build it, run your load test again check this issue again.
In addition, I suggest you could try to create a new load test and then run it using Test Iterations way check if you get the issue for the specified load test or all load tests.
If possible, I suggest you could share me simple load test for us so that we will further help you.
You could upload your load test to OneDrive and then copy link here.
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Error while Test Connection with Connector

hi all:
     there is an error while Test Connection with Connector , I also test it through sys administration->sys configuration->
suport -> sap transaction, I got all errors, I put these two errors as folows, could you please tell me how to sovle it
***************ERROR 1 while *error while Test Connection with Connector ******************************************************
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this
system object
Results
Retrieval of default alias successful
Connection failed. Make sure that Single Sign-On is configured correctly
************error sys administration->sys configuration-> suport -> sap transaction        ********************** 1.5 #0025B3E02892006100000A0800001798000487530FB0122E#1274690722265#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt
.runtime#guodongdong#47472##n/a##690347f0670e11df98cc0025b3e02892#SAPEngine_Application_Thread[impl:3]
9##0#0#Error##Java###04:4524/05/10_0077_6087550
[EXCEPTION]
#1#com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Application URL
&\#39;:///sap(ZT1KVXBWektldldTeV9QQXBXRjNaWTRBLS1OZmRvZzBRWWY2QmN0WThNUmgqdUlRLS0=)/bc/gui/sap/its/webgui&\#39; is not valid!
Please check the protocol and host entries for system &\#39;sapdev&\#39;.
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass
(AbstractIntegratorComponent.java:123)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:523)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:412)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process
(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     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:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Hi,
As per this part of the trace:
Exception in SAP Application Integrator occured: Application URL &\#39;:///sap(ZT1KVXBWektldldTeV9QQXBXRjNaWTRBLS1OZmRvZzBRWWY2QmN0WThNUmgqdUlRLS0=)/bc/gui/sap/its/webgui&\#39; is not valid! Please check the protocol and host entries for system &\#39;sapdev&\#39;. at ...
You can clearly see that the system object 'sapdev' is not configured correctly/at all - you are trying to launch transaction iView
(WEBGUI) and in order to do so you should configure the 'internet transaction server' category of the system object
with the hostname of the ITS server.
Generally the template is
<System.Access.ITS.protocol>://<System.Access.ITS.hostname>/sap<ESID>/bc/gui/sap/its/webgui?\....
So that's why you got
Please check the protocol and host entries for system ..

Error while performing Risk Analysis at user level for a cross system user

Dear All,
I am getting the below error, while performing the risk analysis at user level for a cross system (Oracle) user.
The error is as follows:
"ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.connector.exceptions.BaseResourceException: Cannot get connection for 120 seconds. Possible reasons: 1) Connections are cached within SystemThread(can be any server service or any code invoked within SystemThread in the SAP J2EE Engine), 2) The pool size of adapter "SAPJ2EDB" is not enough according to the current load of the system or 3) The specified time to wait for connection is not enough according to the pool size and current load of the system. In case 1) the solution is to check for cached connections using the Connector Service list-conns command, in case 2) to increase the size of the pool and in case 3) to increase the time to wait for connection property. In case of application thread, there is an automatic mechanism which detects unclosed connections and unfinished transactions.RC:1
Can anyone please help.
Regards,
Gurugobinda

Hi..
Check the note # SAP Note 1121978
SAP Note 1121978 - Recommended settings to improve peformance risk analysis.
Check for the following...
CONFIGTOOL>SERVER>MANAGERS>THREADMANAGER
ChangeThreadCountStep =50
InitialThreadCount= 100
MaxThreadCount =200
MinThreadCount =50
Regards
Gangadhar

DPM encountered an error while performing an operation for \\?\Volume{fc1f0549-9865-4349-b4df-8596a19ad7fe}\FolderPath\Work\ on FileServer (ID 2033 Details: The system cannot find the path specified (0x80070003))

DPM encountered an error while performing an operation for \\?\Volume{fc1f0549-9865-4349-b4df-8596a19ad7fe}\FolderPath\Work\ on FileServer (ID 2033 Details: The system cannot find the path specified (0x80070003))
Can I know what this mean? It completely fail all entire job.
Backup was on half way go, it already took about 3TB data and it fail.

Hi Oneoa,
Please verify the antivirus exeptions. Look at this two links for more information:
http://technet.microsoft.com/en-us/library/ff399439.aspx
http://support.microsoft.com/kb/928840
I hope this solves your problem, please post your progress so I may assist you further.
Best Regards
Robert Hedblom
MVP DPM
Check out my DPM blog @ http://robertanddpm.blogspot.com

"Error during application input" while processing IDOC with status 51

Hi ,
I tried to post an error IDOC with status "51" of message type FIDCC2 using program RBDINPUT, it just creates a message "Error during application input" . It is not calling the application dialog . Does anyone have answer for this?
Thanks,
Hemant.

HI,
Kindly check the RFC entries in t-code SM58.
If any entries are their please release them manually selecting each one and press "F6".
Regards,
Anil.

IOS 8 - MDM error while removing profile with provided identifier

I've implemented a custom solution for an MDM vendor, It works well but lately with an Iphone 6 device with IOS 8.1.3 installed, I got this error (MDM ErrorCode: 12013) while performing a "RemoveProfile" command. Here is command provided:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<plist version="1.0">
    <dict>
        <key>Command</key>
        <dict>
            <key>Identifier</key>
            <string>com.nttdata.dymora.policy.restrictions.80EA49BF-9506-450E-8D99-6A9DA6ED 6999</string>
            <key>RequestType</key>
            <string>RemoveProfile</string>
        </dict>
        <key>CommandUUID</key>
        <string>dd71d6d0-5e04-4baf-9408-841e01227bfb</string>
    </dict>
</plist>
and here is device response:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
        <key>CommandUUID</key>
        <string>dd71d6d0-5e04-4baf-9408-841e01227bfb</string>
        <key>ErrorChain</key>
        <array>
                <dict>
                        <key>ErrorCode</key>
                        <integer>12013</integer>
                        <key>ErrorDomain</key>
                        <string>MCMDMErrorDomain</string>
                        <key>LocalizedDescription</key>
                        <string>Il profilo “com.nttdata.dymora.policy.restrictions.80EA49BF-9506-450E-8D99-6A9DA6ED6999<E2 ><80>? non è gestito da MDM.</string>
                        <key>USEnglishDescription</key>
                        <string>The profile “com.nttdata.dymora.policy.restrictions.80EA49BF-9506-450E-8D99-6A9DA6ED6999<E2 ><80>? is not managed by MDM.</string>
                </dict>
        </array>
        <key>Status</key>
        <string>Error</string>
        <key>UDID</key>
        <string>bc880d07f41f5ef84a06253ee89a4bdd2b584b84</string>
</dict>
</plist>
I don't understand the reason why this command return such error, it has always worked properly!?!? Is there anyone with same error?
Thanks!
Paolo

I've implemented a custom solution for an MDM vendor, It works well but lately with an Iphone 6 device with IOS 8.1.3 installed, I got this error (MDM ErrorCode: 12013) while performing a "RemoveProfile" command. Here is command provided:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<plist version="1.0">
    <dict>
        <key>Command</key>
        <dict>
            <key>Identifier</key>
            <string>com.nttdata.dymora.policy.restrictions.80EA49BF-9506-450E-8D99-6A9DA6ED 6999</string>
            <key>RequestType</key>
            <string>RemoveProfile</string>
        </dict>
        <key>CommandUUID</key>
        <string>dd71d6d0-5e04-4baf-9408-841e01227bfb</string>
    </dict>
</plist>
and here is device response:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
        <key>CommandUUID</key>
        <string>dd71d6d0-5e04-4baf-9408-841e01227bfb</string>
        <key>ErrorChain</key>
        <array>
                <dict>
                        <key>ErrorCode</key>
                        <integer>12013</integer>
                        <key>ErrorDomain</key>
                        <string>MCMDMErrorDomain</string>
                        <key>LocalizedDescription</key>
                        <string>Il profilo “com.nttdata.dymora.policy.restrictions.80EA49BF-9506-450E-8D99-6A9DA6ED6999<E2 ><80>? non è gestito da MDM.</string>
                        <key>USEnglishDescription</key>
                        <string>The profile “com.nttdata.dymora.policy.restrictions.80EA49BF-9506-450E-8D99-6A9DA6ED6999<E2 ><80>? is not managed by MDM.</string>
                </dict>
        </array>
        <key>Status</key>
        <string>Error</string>
        <key>UDID</key>
        <string>bc880d07f41f5ef84a06253ee89a4bdd2b584b84</string>
</dict>
</plist>
I don't understand the reason why this command return such error, it has always worked properly!?!? Is there anyone with same error?
Thanks!
Paolo

System Refresh SAPINST.exe error ExeProcs was executed with status Error

Hi Everyone,
                     As part of system refresh, our QA ECC is restored with Production Data backup. In this process, sapinst.exe is executed to perform homogeneous system copy steps. This process is being terminated with error at the step *"Create SAP stored procedures"*.
The error being displayed is as follows:
An error occurred while processing option SAP Toools for MS SQL Server > Database Copy Completion( Last error reported by the step: Errors when executing sql command: [Microsoft][ODBC SQL Server Driver][SQL Server]The specified @job_name ('SAP CCMS_qpe_QPE_Update_Tabstats') does not exist.
SOLUTION: If this message is displayed as a warning, you can ignore it. If this is an error, contact SAP support.
). You can now:
Choose Retry to repeat the current step.
Choose View Log to get more information about the error.
Stop the option and continue with it later.
Log files are written to C:\Program Files/sapinst_instdir/MSS/CPY.
sapinst.log file contains following information:
INFO 2010-11-06 17:40:30
Copied file 'C:/Program Files/sapinst_instdir/ERP/LM/COPY/MSS/SYSTEM/DISTRIBUTED/AS-ABAP/DB/inifile.xml' to 'C:/Program Files/sapinst_instdir/ERP/LM/COPY/MSS/SYSTEM/DISTRIBUTED/AS-ABAP/DB/inifile.4.xml'.
INFO 2010-11-06 17:40:30
Copied file 'C:/Program Files/sapinst_instdir/ERP/LM/COPY/MSS/SYSTEM/DISTRIBUTED/AS-ABAP/DB/inifile.xml' to 'C:/Program Files/sapinst_instdir/ERP/LM/COPY/MSS/SYSTEM/DISTRIBUTED/AS-ABAP/DB/inifile.5.xml'.
INFO 2010-11-06 17:40:31
Execute step
Component W2K_ServicePack_Check|ind|ind|ind|ind
Preprocess of component |NW_ABAP_DB|ind|ind|ind|ind|0|0|NW_First_Steps|ind|ind|ind|ind|0|0|W2K_ServicePack_Check|ind|ind|ind|ind|2|0.
INFO 2010-11-06 17:40:41
Copied file 'C:/Program Files/sapinst_instdir/ERP/LM/COPY/MSS/SYSTEM/DISTRIBUTED/AS-ABAP/DB/keydb.xml' to 'C:/Program Files/sapinst_instdir/ERP/LM/COPY/MSS/SYSTEM/DISTRIBUTED/AS-ABAP/DB/keydb.3.xml'.
INFO 2010-11-06 17:40:41
Execute step ExeProcs of component |NW_ABAP_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|8|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSysCopy|ind|ind|ind|ind|10|0|MssProcs|ind|ind|ind|ind|4|0.
ERROR 2010-11-06 17:40:58
FCO-00011 The step ExeProcs with step key |NW_ABAP_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|8|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSysCopy|ind|ind|ind|ind|10|0|MssProcs|ind|ind|ind|ind|4|0|ExeProcs was executed with status ERROR .
Our Environment details:
SAP Version : ECC6
OS                 : Microsoft windows server 2003
DB                 : Microsoft SQL Server         2005.
Can some please guide me in debugging this issue. Your help is highly appreciated.
Thanks a lot in advance.
Kind Regards,
Bharani.

Hi Satya,
             Thank you for the reply. QA in our landsacpe was in use since 2008. Serveral times system refresh is carried out on our QA with production data but never came accross this issue.
             Usually if the SAPINST.exe run is successfull, temperory licence will be installed and we will be allowed to login into the sytem with our user names normally and carry out post installation steps.
             As the SAPISNT.exe is being terminated, temperory license is not being installed and we got to work around by including parameter to allow default sap* userid and password to login and install license and carry on with the post installation steps. To be frank this issue is not really a show stopper, but there seems to be an issue that is to be resolved.
Thank you,
Kind Regards,
Bharani.

Re: Error while Deploying OEDQ with a deployement plan on weblogic

Hi All,
I am getting this Exception while deployment and look like this is same type of exception
weblogic.application.ModuleException: Unmarshaller failed
[fa:deploy] <fusion_domain>: <fusion_domain>: Exception while performing deployJ2EE for application AdvancedPlanningApp : java.lang.Exception: Deployment FAILED:weblogic.application.ModuleException: [HTTP:101064][WebAppModule(AdvancedPlanningApp:advancedPlanning)] Error parsing descriptor in Web appplication "/scratch/software/mw_local/FMWTOOLS_11.1.1.7.0_GENERIC_130327.1838_PATCHES4FA_11.1.1.7.0_PLATFORMS_JDK64/bitukuma/mw_home_standalone/user_projects/domains/fusion_domain/servers/AdminServer/upload/AdvancedPlanningApp/app/AdvancedPlanningApp/EarScmAps.war"
[fa:deploy] weblogic.application.ModuleException: Unmarshaller failed
[fa:deploy]     at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1345)
[fa:deploy]     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:375)
[fa:deploy]     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180)
[fa:deploy]     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
[fa:deploy]     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
[fa:deploy]     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
[fa:deploy]     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
[fa:deploy]     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
[fa:deploy]     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
[fa:deploy]     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
[fa:deploy]     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
[fa:deploy]     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59)
[fa:deploy]     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
[fa:deploy]     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
[fa:deploy]     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:209)
[fa:deploy]     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
[fa:deploy]     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
[fa:deploy]     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749)
[fa:deploy]     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
[fa:deploy]     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
[fa:deploy]     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160)
[fa:deploy]     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
[fa:deploy]     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
[fa:deploy]     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:47)
[fa:deploy]     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
[fa:deploy]     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
[fa:deploy]     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
[fa:deploy] Caused by: weblogic.descriptor.BeanAlreadyExistsException: Bean already exists: "weblogic.j2ee.descriptor.FilterBeanImpl@82a9ceb4(/Filters[ADFLibraryFilter])"
[fa:deploy]     at weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceManager.java:231)
[fa:deploy]     at weblogic.j2ee.descriptor.WebAppBeanImpl.setFilters(WebAppBeanImpl.java:715)
[fa:deploy]     at sun.reflect.GeneratedMethodAccessor249.invoke(Unknown Source)
[fa:deploy]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[fa:deploy]     at java.lang.reflect.Method.invoke(Method.java:597)
[fa:deploy]     at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:48)
[fa:deploy]     at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.setValue(RuntimeBindingType.java:539)
[fa:deploy]     at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType$QNameRuntimeProperty.fillCollection(AttributeRuntimeBindingType.java:382)
[fa:deploy]     at com.bea.staxb.runtime.internal.MultiIntermediary.getFinalValue(MultiIntermediary.java:52)
[fa:deploy]     at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType.getFinalObjectFromIntermediary(AttributeRuntimeBindingType.java:140)
[fa:deploy]     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:200)
[fa:deploy]     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:169)
[fa:deploy]     at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
[fa:deploy]     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150)
[fa:deploy]     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
[fa:deploy]     at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
[fa:deploy]     at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
[fa:deploy]     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
[fa:deploy]     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
[fa:deploy]     at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
[fa:deploy]     at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1331)
Please help me to resolve this error.
Thanks

Your error does not appear to be to do with EDQ at all. I do not recognise the name of the war file giving you the error. Which version of EDQ are you deploying?
Please do not use the public forum if you need support with an internal deployment of a pre-release version.

JCAActivationAgent::load - Error while performing endpoint activation:java.

Hi,
I am getting following error while deploying a BPEL process. This is very surprising because the process used to run fine until yesterday. Also for some time I was getting a funny error - the JDev was not able to "read" a wsdl file on local machine. I restarted the server, machine many times but it did not help. I do not have any proxies set and the file resides on my local harddrive.
<2006-04-11 11:30:20,090> <ERROR> <default.collaxa.cube.activation> <AdapterFramework::Inbound> JCAActivationAgent::load - Er
ror while performing endpoint activation:java.lang.NullPointerException
<2006-04-11 11:30:20,090> <ERROR> <default.collaxa.cube.activation> <AdapterFramework::Inbound>
java.lang.NullPointerException
at oracle.tip.adapter.fw.agent.jca.JCAActivationAgent.load(JCAActivationAgent.java:208)
at com.collaxa.cube.engine.core.BaseCubeProcess.loadActivationAgents(BaseCubeProcess.java:931)
at com.collaxa.cube.engine.core.BaseCubeProcess.load(BaseCubeProcess.java:302)
at com.collaxa.cube.engine.deployment.CubeProcessFactory.create(CubeProcessFactory.java:66)
at com.collaxa.cube.engine.deployment.CubeProcessLoader.create(CubeProcessLoader.java:391)
at com.collaxa.cube.engine.deployment.CubeProcessLoader.load(CubeProcessLoader.java:302)
at com.collaxa.cube.engine.deployment.CubeProcessHolder.loadAndBind(CubeProcessHolder.java:881)
at com.collaxa.cube.engine.deployment.CubeProcessHolder.getProcess(CubeProcessHolder.java:789)
at com.collaxa.cube.engine.deployment.CubeProcessHolder.loadAll(CubeProcessHolder.java:361)
at com.collaxa.cube.engine.CubeEngine.loadAllProcesses(CubeEngine.java:960)
at com.collaxa.cube.admin.ServerManager.loadProcesses(ServerManager.java:284)
at com.collaxa.cube.admin.ServerManager.loadProcesses(ServerManager.java:250)
at com.collaxa.cube.ejb.impl.ServerBean.loadProcesses(ServerBean.java:219)
at IServerBean_StatelessSessionBeanWrapper14.loadProcesses(IServerBean_StatelessSessionBeanWrapper14.java:2399)
at com.collaxa.cube.admin.agents.ProcessLoaderAgent$ProcessJob.execute(ProcessLoaderAgent.java:395)
at org.quartz.core.JobRunShell.run(JobRunShell.java:141)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:281)
<2006-04-11 11:30:20,152> <ERROR> <default.collaxa.cube.engine.deployment> <CubeProcessLoader::create>
<2006-04-11 11:30:20,152> <ERROR> <default.collaxa.cube.engine.deployment> Process "CallHomeBPEL" (revision "1.0") load FAILE
D!!
<2006-04-11 11:30:20,230> <ERROR> <default.collaxa.cube.engine.deployment> <CubeProcessHolder::loadAll> Error while loading p
rocess 'CallHomeBPEL', rev '1.0': Error while loading process.
The process domain encountered the following errors while loading the process "CallHomeBPEL" (revision "1.0"): null.
If you have installed a patch to the server, please check that the bpelcClasspath domain property includes the patch classes.
Please help.

Finally , I was able to redeploy the process. After comparing new files with old files I observed an activationAgents entry in bpel.xml, which was not present previously.
<activationAgents>
<activationAgent className="oracle.tip.adapter.fw.agent.jca.JCAActivationAgent" partnerLink="CallHomeFileUtility">
<property name="portType">Read_ptt</property>
</activationAgent>
</activationAgents>
when I removed this from bpel.xml the process deployed successfully. Not sure when the <activationAgents> is added to bpel.xml
Thanks for your inputs.

Error while creating delivery with reference to STO

Hi,
I am getting the following error while creating the delivery with reference to STO
Document is incomplete: You cannot save the delivery
Diagnosis:
When the system checked whether saving delivery was
permitted, it determined that the requirements stored in
Define Incompletion Procedures for this document do not
allow this subsequent function.
I have checked the following already:
1. Maintained shipping data for both the supplying and receiving plants.
2. Shipping tab exists in the PO
3. Shipping point determination is checked.
4. Customer masters created for both supplying plants and receiving plant for the sales area created for STO
5. Material master is available in both receiving and supplying plants.
It is working fine in one client. and giving a problem only in the other.not able to figure out where the error is. appreciate your suggestions
regards
joe

Hi Joseph,
First go to transaction "VUA4" and see what is the incompletion procedure asigned to your delivery type. Then go to
"OVA2" and see what are the fileds maintained in incompletion procedure of the delivery type and the status groups assigned to them. Now you go to "OVA0(ZERO) and see whether the status group allows to save the delivery. If it doesn't you can untick that check box. But if this is a live system , i doubt if you would be bale to do that. Any way one of the possible causes is storgae location missing. Kindly pelase let me know If you need any more infromation on this.
Regards,
Ram Pedarla

OIM11gr2 Error while performing Recon with status field

Similar Messages

Maybe you are looking for