Error in tutorial: Could not create XML document carrying AQ Headers

Hi,
We try to run the AQOutboundCorrelation tutorial. After running the enqueue_reply.sql script the message was placed from the request to the reply queue and read by the AQ inbound adapter.
Nothing happened in the flow. The following error occured in the domain log:
Could not create XML document carrying AQ Headers
Please help!!
See log messages below
<2007-01-18 13:58:59,187> <DEBUG> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_addPrimitive: field = PAYLOAD, value = Hallo
<2007-01-18 13:58:59,187> <DEBUG> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_addPrimitive: field = RESULT, value = request received
<2007-01-18 13:58:59,187> <DEBUG> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_getAsXML message:<<<<<<<
<?xml version = '1.0' standalone = 'yes'?>
<CORRELATIONREPLY_TYPE xmlns="http://xmlns.oracle.com/xdb/ANDRE">
<PAYLOAD xmlns="">Hallo</PAYLOAD>
<RESULT xmlns="">request received</RESULT>
</CORRELATIONREPLY_TYPE>
>>>>>>>>
<2007-01-18 13:58:59,187> <DEBUG> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_readMessage: aqHeader = oracle.xml.parser.v2.XMLDocument@eabad
<2007-01-18 13:58:59,187> <DEBUG> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_readMessage:Header<<<<<<<
<?xml version = '1.0' standalone = 'yes'?>
<Header xmlns="http://xmlns.oracle.com/pcbpel/adapter/aq/inbound/">
<MessageId>CA714367FA1B4BB3B2AC0211C9ECF2DB</MessageId>
<Priority>1</Priority>
<Correlation>209EE57CB6AC4B2FA2034C6FA58AD24B</Correlation>
<Attempts>0</Attempts>
<EnqueueTime>2007-01-18T13:58:59.000+01:00</EnqueueTime>
<OrigMessageId></OrigMessageId>
</Header>
>>>>>>>>
<2007-01-18 13:58:59,187> <ERROR> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_ReadMessage: Could not create XML document carrying AQ Headers: [Ljava.lang.StackTraceElement;@12916fe
<2007-01-18 13:58:59,187> <ERROR> <default.collaxa.cube.activation> <AQ Adapter::Inbound>
java.lang.NullPointerException
     at java.lang.String.<init>(String.java:479)
     at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:573)
     at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.run(AQActivationSpecDequeuer.java:183)
     at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
     at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:272)
     at java.lang.Thread.run(Thread.java:595)
Message was edited by:
rverbeea1

Sorry for not mentioning the product versions:
The bpel process was build and deployed with Jdeveloper Studio edition version 10.1.3.1.0.3984 on a Bpel server/Application Server with version 10.1.3.1 (NT).

Similar Messages

AQ Adapter error: Could not create XML document carrying AQ Headers

I'm having problem with the AQ adapter (ADT) sample that comes with the SOA 10g install.
I am running 10.1.3.4 on XP, using Oracle XE.
I can use the sample sql script to enque and deque. However, when I deploy the sample ADT (BPEL project), I see errors in the opmn log. The BPEL instance is not even created.
I see another post with similar question, Re: Debugging BPEL when using Oracle AQ but no answer.
Any help is greatly appreciated. Thx!
----------------- err log --------------
<2009-07-15 00:04:31,656> <INFO> <collaxa> <ServerManager::loadProcesses> Done loading processes for all domains
<2009-07-15 00:04:32,031> <INFO> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_ctor: Initialized MessageReader for queue CUSTOMER_IN_QUEUE, consumer = null)
<2009-07-15 00:12:15,984> <ERROR> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_ReadMessage: Could not create XML document carrying AQ Headers: [Ljava.lang.StackTraceElement;@e7af3a
<2009-07-15 00:12:15,984> <ERROR> <default.collaxa.cube.activation> <AQ Adapter::Inbound>
java.lang.Exception: java.lang.NullPointerException
     at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:750)
     at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.run(AQActivationSpecDequeuer.java:261)
     at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
     at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:280)
     at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
     at oracle.oc4j.sql.proxy.StatementBCELProxy.oc4j_releaseToCache(StatementBCELProxy.java:67)
     at oracle.oc4j.sql.proxy.StatementBCELProxy.oc4j_releaseTarget(StatementBCELProxy.java:79)
     at oracle.oc4j.sql.proxy.SQLBCELProxy.oc4j_close(SQLBCELProxy.java:95)
     at oracle.oc4j.sql.proxy.StatementBCELProxy.close(StatementBCELProxy.java:92)
     at oracle.AQ.AQOracleQueue.destroyStmt(AQOracleQueue.java:3099)
     at oracle.AQ.AQOracleQueue.dequeue(AQOracleQueue.java:1793)
     at oracle.AQ.AQOracleQueue.dequeue(AQOracleQueue.java:1307)
     at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:485)
     ... 4 more
<2009-07-15 00:12:16,203> <FATAL> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Uncaught exception oracle.as.j2ee.transaction.tpc.ProtocolErrorWithNotification in JCA-work-instance:AQ Adapter-0 - cause: Branch [oracle.oc4j.sql.xa.EmulatedXAResource@14d9865, Xid( Global Id 34.5f.1e.a8.ff.ff.ff.ff.cd.b9.38.7d.22.01.00.00.7a.02.00.00.00.00.00.00, Format Id 1330790740, Branch Id 7c.e5.55.76.00.00.00.00.00.00.00.00.00.00.00.01), oracle.oc4j.sql.xa.EmulatedXAResource@14d9865, state={PREPARED}, exception error code=] in transaction Global Transaction Xid( Global Id 34.5f.1e.a8.ff.ff.ff.ff.cd.b9.38.7d.22.01.00.00.7a.02.00.00.00.00.00.00, Format Id 1330790740), type=orabpel, state=COMMITTING, time in completion or recovering=0)
....

thanks for the reply. I did look into that post, and couldn't found where to set that option either.
However, my PC was rebooted a few times today (I didn't change anything with BPEL), and I just re-ran the test now, that problem disappeared! It is working fine now.

Could not create XML document carrying AQ Headers

Hi gurus,
I’m trying to run the "Simple_XMLType_Payload" sample, and I have successfully deploy it on Oracle BPEL v10.1.3.1.0 , and after en-queue into the XMLType_Payload_In queue the recorded has been de-queued successfully, however there no instance for the BPEL has been created on the BPEL Console moreover there is no recorded inserted in XMLType_Payload_Out queue.
After investigating the OC4j_SOA log file, I found the following error
11/03/29 16:32:45 Confluent Monitor component started
11/03/29 16:32:45 Oracle Containers for J2EE 10g (10.1.3.1.0) initialized
11/03/29 16:52:28 java.lang.ClassCastException: oracle.xdb.XMLType
11/03/29 16:52:28      at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:448)
11/03/29 16:52:28      at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.run(AQActivationSpecDequeuer.java:189)
11/03/29 16:52:28      at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
11/03/29 16:52:28      at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:272)
11/03/29 16:52:28      at java.lang.Thread.run(Thread.java:595)
<2011-03-29 16:52:28,082> <ERROR> <defualt.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_ReadMessage: Could not create XML document carrying AQ Headers: [Ljava.lang.StackTraceElement;@748771
<2011-03-29 16:52:28,089> <ERROR> <defualt.collaxa.cube.activation> <AQ Adapter::Inbound>
java.lang.ClassCastException: oracle.xdb.XMLType
     at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:448)
     at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.run(AQActivationSpecDequeuer.java:189)
     at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
     at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:272)
     at java.lang.Thread.run(Thread.java:595)

But I have tried it on another server that also has 10.1.3.1 version but the OS version is HP-UX B.11.23 U ia64 , and it woks fine, however I’m still has the same issue on the original server that has OS version HP-UX B.11.31 U ia64 ?
Edited by: user11096490 on Apr 4, 2011 11:06 AM

Could not create discount document

Hello!
We are having the following error either on automatic (F110) or manual payments (F-53) when generating a discount documents:
Manual Payments error:
Could not create discount document
Message no. 8A605
Automatic Payments error:
FF848: Entry of tax for C1 000 is not possible because of tax base 0
I think that the error is generated because the tax base amount is not being completed automatically.
I have already checked discount documents customizing and I´ve founded everything ok.
Also Tax Category field for the discount GL account is completed.
Any help would be appreciated.
Regards.

Hi Nirav, thank for your answer.
I have already check that field that you mentioned.
It is exactly the way you told me.
Do you have in mind anything else?
Regards.

An error has occurred: Could not find the document.

I get the "An error has occurred: Could not find the document." error when trying to open a URL using OpenDocument. The URL is as follows:
http://:<myserver>8080/BOE/OpenDocument/opendoc/openDocument.jsp?iDocID=AZjCUhaL3c9Is.YxtGMc7K4&sIDType=CUID
I am certain the value of iDocID is correct, and I am also certain that I can get an OpenDocument to work on the server. In fact, I tried the same URL using a different iDocID for a Webi report in a different folder, and it works. For some reason, it appears as though the report in this folder won't open though.
Any thoughts on this would be greatly appreciated. I've been working on this for a couple of days an am completely stumped. Also, I'm relatively new to Business Objects. Is there a log file that I can view that might give me more details regarding the error?
Thanks in advance for your help!

May be that the user who is accessing the report does not have sufficient rights to view it.
Check whether you are able to view the document as an administrator.
Regards,
Niraj

Error : Item Category could not created.

Hello SAP Masters,
While creating a "sales process" in SAP CRM I've got the following error
"Item Category could not created"
Now let me tel you what exactly I've done, I have defined a "Sales Process" Type transaction called "Ysal" and by copying the slandered Item Category "Tan" I've created "ZTAN" , and for the Item category group and the Item Category Usage I've created "ZItem Group" and "ZItem usage".
Now in the Item Category determination I've filled up
Transaction Type = Ysal
Item Cat. Group = ZItem Group
Item Cat Usage = Zitem Usage
Main Item Cat. = Ztan
and under Item Category determination
Item Category = ZTAN
after this I've created A product Master and a ,material where I've assigned Item Category Group, and the product master.
Now Please explain why I've got this error, as I've maintained the determination properly so in my view during transaction creation Item Category should be determined automatically.
One more thing I am confused about "Higher Level Item Category" and "Lower Level Item Category" please explain.
Thanks and Regards
Rahul

Hi,
Thanks for your reply, as per your guidance left the "Item Category" field blank, and also the "Main Item Category" as blank and selected my "ZTAN" in Item category.
After that It worked, and the Item Category perfectly determined.
But there is error for "ATP" not checked. Can you please explain. Also please explain what is "Main Item Category".
As you have said the higher level category is for main product, and lower level category is for dependent product like free product, then if there is scenario where no free product , in that case what should be done?
Thanks and Regards
Rahul
Edited by: Rahul07 on Jan 21, 2011 7:22 PM

Java system error: Server repository could not create function template

Hi, Our BI person is trying to publish/broadcast a query to the PRODCTION portal, she gets the below error message. I am
attaching the defaulttracelog file
"Java system error: Server repository could not create function template for RSRD_X_PRODUCE_PROXY caused by: com.sap.mw.jco.JCO$Exception: (103)"
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[./log/defaultTrace.trc]/>
<!PATTERN[defaultTrace.trc]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[UTF8]/>
<!FILESET[8, 20, 10485760]/>
<!PREVIOUSFILE[defaultTrace.7.trc]/>
<!NEXTFILE[defaultTrace.9.trc]/>
<!LOGHEADER[END]/>
#1.5 #002264F9350800600000022F000019C000048E9B91EF3AB3#1282698726384#com.sap.security.core.persistence#sap.com/irj#com.sap.security.core.persistence#J2EE_GUEST#0##n/a##4dba6f30af8111df934c002264f93508#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Security/Usermanagement#Java#An exception was thrown in the UME/ABAP user management connector that was caused by unavailability of the RFC communication with the backend system: "". ##An exception was thrown in the UME/ABAP user management connector that was caused by unavailability of the RFC communication with the backend system: "". #1#Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=localhost SYSNR=00 GWHOST=localhost GWSERV=sapgw00 PCS=1
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       partner '127.0.0.1:sapgw00' not reached
TIME        Tue Aug 24 21:12:06 201
RELEASE     700
COMPONENT   NI (network interface)
VERSION     38
RC          -10
MODULE      nixxi.cpp
LINE        2823
DETAIL      NiPConnect2
SYSTEM CALL connect
ERRNO       10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUNTER     56
#1.5 #002264F93508006000000230000019C000048E9B91EF47C8#1282698726384#com.sap.engine.services.monitor.mbeans.Monitor#sap.com/irj#com.sap.engine.services.monitor.mbeans.Monitor#J2EE_GUEST#0##n/a##4dba6f30af8111df934c002264f93508#SAPEngine_Application_Thread[impl:3]_35##0#0#Error##Plain###Caller J2EE_GUEST not authorized, user J2EE_GUEST is not available from user management, reason: com.sap.security.api.NoSuchUserException:USER_AUTH_FAILED: User account for logonid "J2EE_GUEST" not found!#
#1.5 #002264F93508006000000231000019C000048E9B91EF4CD5#1282698726384#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##4dba6f30af8111df934c002264f93508#SAPEngine_Application_Thread[impl:3]_35##0#0#Error##Plain###com.sap.engine.services.jmx.exception.JmxSecurityException: Caller J2EE_GUEST not authorized, user J2EE_GUEST is not available from user management, reason: com.sap.security.api.NoSuchUserException:USER_AUTH_FAILED: User account for logonid "J2EE_GUEST" not found!
     at com.sap.engine.services.jmx.auth.UmeAuthorization.checkMBeanPermission(UmeAuthorization.java:63)
     at com.sap.engine.services.jmx.JmxServerFrame.checkMBeanPermission(JmxServerFrame.java:98)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.unregisterMBean(MBeanServerSecurityWrapper.java:395)
     at com.sap.engine.services.jmx.ClusterInterceptor.unregisterMBean(ClusterInterceptor.java:1327)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.unregisterMBean(MBeanServerInterceptorChain.java:258)
     at com.sap.engine.services.monitor.mbeans.Monitor.unregister(Monitor.java:106)
     at com.sap.engine.library.monitor.impl0.AbstractMonitorNode.remove(AbstractMonitorNode.java:154)
     at com.sap.engine.library.monitor.impl0.MonitorObjectFactory.uninstallMonitorNode(MonitorObjectFactory.java:483)
     at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:595)
     at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
     at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
     at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
     at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
     at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
     at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
     at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:568)
     at com.sap.engine.services.monitor.server.ApplicationLifeCycleImpl.applicationStopped(ApplicationLifeCycleImpl.java:52)
     at com.sap.engine.services.monitor.deployment.MonitorDeploymentContainer.commitStop(MonitorDeploymentContainer.java:630)
     at com.sap.engine.services.deploy.server.application.StopTransaction.commonCommitFinished(StopTransaction.java:244)
     at com.sap.engine.services.deploy.server.application.StopTransaction.commitCommon(StopTransaction.java:290)
     at com.sap.engine.services.deploy.server.application.StopTransaction.commitLocal(StopTransaction.java:278)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:374)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.stopApplicationLocalAndWait(DeployServiceImpl.java:4569)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.stopApplicationLocalAndWait(DeployCommunicatorImpl.java:628)
     at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime$2.run(SAPJ2EEPortalRuntime.java:602)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.lang.ClassLoader$NativeLibrary.load(Native Method)
     at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1586)
     at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1482)
     at java.lang.Runtime.load0(Runtime.java:737)
     at java.lang.System.load(System.java:811)
     at com.sapportals.wcm.service.fsmount.FSMountService.loadDLL(FSMountService.java:736)
     at com.sapportals.wcm.service.fsmount.FSMountService.<clinit>(FSMountService.java:796)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:219)
     at com.sapportals.wcm.repository.runtime.CmConfigurationProvider.convertGS(CmConfigurationProvider.java:637)
     at com.sapportals.wcm.repository.runtime.CmConfigurationProvider.convertServiceConfig(CmConfigurationProvider.java:601)
     at com.sapportals.wcm.repository.runtime.CmConfigurationProvider.readConfiguration(CmConfigurationProvider.java:205)
     at com.sapportals.wcm.crt.CrtSystemImpl.createComponentManager(CrtSystemImpl.java:108)
     at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:202)
     at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:164)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:974)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:192)
     at com.sapportals.wcm.portal.service.KMServiceImpl.afterInit(KMServiceImpl.java:249)
     at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstanceStep2(PortalServiceItem.java:877)
     at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:1118)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1707)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1662)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplications(PortalAppBroker.java:1592)
     at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:422)
     at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
     at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:161)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:361)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:42)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:114)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:394)
     at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:139)
     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
     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)
#1.5 #002264F93508005C0000042300002CF00004939AAEE9AEB7#1288192475655#com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager#sap.com/irj#com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager#J2EE_GUEST#0##n/a##c7d00e00e1dc11dfa36d002264f93508#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain###setting initial ACL on /reporting_backend/reports/System Administration/CM Store/cm.crawlcontent - com.sap.security.api.NoSuchRoleException: Role with uniqueName system_admin_role not found!
     at com.sap.security.core.imp.RoleFactory.getRoleByUniqueName(RoleFactory.java:1783)
     at com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager.getRoles(RPRepositoryManager.java:1474)
     at com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager.syncReportResources(RPRepositoryManager.java:1334)
     at com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager.initBackend(RPRepositoryManager.java:489)
     at com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager.getResource(RPRepositoryManager.java:581)
     at com.sapportals.wcm.repository.RMAdapter.getResource(RMAdapter.java:228)
     at com.sapportals.wcm.repository.runtime.CmAdapter.findResource(CmAdapter.java:1349)
     at com.sapportals.wcm.repository.runtime.CmAdapter.findManagerAndResource(CmAdapter.java:1322)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:979)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:192)
     at com.sapportals.wcm.service.reporting.ReportingService.localConfigure(ReportingService.java:294)
     at com.sapportals.wcm.service.reporting.ReportingService.startUpImpl(ReportingService.java:74)
     at com.sapportals.wcm.service.AbstractService.start(AbstractService.java:167)
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:247)
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:109)
     at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:322)
     at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:403)
     at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)
     at com.sapportals.wcm.crt.CrtSystemImpl.lookupComponentByUri(CrtSystemImpl.java:131)
     at com.sapportals.wcm.crt.CrtComponentManager.startUp(CrtComponentManager.java:278)
     at com.sapportals.wcm.crt.CrtSystemImpl.startUpComponentManager(CrtSystemImpl.java:166)
     at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:227)
     at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:164)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:974)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:192)
     at com.sapportals.wcm.portal.service.KMServiceImpl.afterInit(KMServiceImpl.java:249)
     at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstanceStep2(PortalServiceItem.java:877)
     at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:1118)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1707)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1662)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplications(PortalAppBroker.java:1592)
     at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:422)
     at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
     at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:161)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:361)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:42)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:114)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:394)

Go to visual admin -> server -> services -> JCO RFC provider.
Check the RFC that connects to the BI Abap.
Its reporting the J2EE_GUEST user in the SAP with the system nr 00.
Is this BI java portal?
Is the java portal a addon to Abap or having seperate SID?
Check the connection definitions are correct and the gateway is running.

"An error has occurred: Could not find the document." on opening the BO report

Hi ,
On publishing the BO report in Portal, we get the blank screen with warning message as below screenshot and facing the ""An error has occurred: Could not find the document."" error message when accessing the BO report using open document URL directly in browser instead of portal.
Link: http://<host>:8080/OpenDocument/opendoc/openDocument.jsp?sIDType=CUID&iDocID=ASClVc_yw55L
We already have many BO reports successfully running in the production environment.
But for this new report we are getting this error. The difference found in this report is from Infoviewapp the login page appears as below in to which the developer logs in.
But for the reports coming with error the login page authentication value is changed to "Enterprise". So the system related fields disappear after that and looks like below
Please let us know the root-cause of this error message. Is this something to do with user authorization in BO system at report level or some config changes related to SAP/Enterprise authentication.
Multiple posts in SDN related to this error message points to check for user authorizations in BO system. Please provide details on this if this is the case.
Regards,
Bhaskar

Hi ,
The dropdown is now made visible to the users in the opendocument property as per the suggestion in the below links. The user can choose the authentication type and login into reports after that.
http://scn.sap.com/thread/3525264
http://scn.sap.com/thread/1417858
My question now is after changing the visibility of the authentication true, the SSO doesn't work as before. Is there any way to make the SSO available with this setup ?
Regards,
Bhaskar

I installed the CC trial with an error window saying: Could not create the file '/Users/dranim/Library/Preferences/Adobe/After Effects/13.2/dummy'. That was the first window. Heres the second: After Effects can't continue: unexpected failure during app

I installed the CC trial with an error window saying: Could not create the file '/Users/dranim/Library/Preferences/Adobe/After Effects/13.2/dummy'. That was the first window. Heres the second: After Effects can’t continue: unexpected failure during application startup I paid for the month subscription of 29.99. It claims it is downloading again?! Am I missing something here? Why is this process so complicated? I need to get this resolved asap and start working.

I originally had Adobe Photoshop Extended, then upgraded to the Production Suite. I ran the Adobe Cleaner, and that uninstalled most Adobe products, including my existing Adobe install, and then I re-installed everything with the same error code. Since CS4 came with CS5, I've installed AE CS4, but would really like to upgrade because I'm new to Creative Suite, and not sure how CS4 integrates with CS5...CS4 After Effects installed perfectly. I do have a 64 bit system, and installing to an OCZ Vertex 2....every other suite installs perfectly, except AE. And I think that is the coolest program in the Suite. I thank you all so much for taking the time to help, I really want to get AECS5 running...I did try to install after doing the recommended items Adobe suggests for Exit Codes 6 and 7, including turning off many startups...
I'm baffled....
Ben

WL 6.1 to 8.1 XSL Error SAX Exception, Could not parse xsl document

1)I have an application which is deployed and running successfully on WL6.1. The application uses lot of xsl style sheets. Parsers used were from xalan.jar and xerces.jar
2)Now, I am migrating it to WL8.1, the application is deployed on 8.1 but when I open the login(first page) it gives the following error:
====================
ABCD.xsl; Line 0; Column 0
XSL Error: Could not parse C:/src/xslsheets/ABC4.xsl document!
XSL Error: SAX Exception
====================
3)As the previous versions of WebLogic Server included the unmodified versions of the Xerces parser and Xalan transformer from www.apache.org in the WL_HOME\server\ext\xmlx.zip file. The ZIP file no longer includes these classes and interfaces in 8.1.
4)I understand it is the the Parser Exception and wud like to know the best possible way to solve this.
Thanks
Val

1)I have an application which is deployed and running successfully on WL6.1. The application uses lot of xsl style sheets. Parsers used were from xalan.jar and xerces.jar
2)Now, I am migrating it to WL8.1, the application is deployed on 8.1 but when I open the login(first page) it gives the following error:
====================
ABCD.xsl; Line 0; Column 0
XSL Error: Could not parse C:/src/xslsheets/ABC4.xsl document!
XSL Error: SAX Exception
====================
3)As the previous versions of WebLogic Server included the unmodified versions of the Xerces parser and Xalan transformer from www.apache.org in the WL_HOME\server\ext\xmlx.zip file. The ZIP file no longer includes these classes and interfaces in 8.1.
4)I understand it is the the Parser Exception and wud like to know the best possible way to solve this.
Thanks
Val

Install error on Mac "could not create ~/library/application support/adobe/coresync"

Any reason why this would be happening and what I should do?

I'm getting this same error after trying to install on my mac pro.
I see that the cloud installer was able to create the ~/Library/Application Support/Adobe folder and a bunch of folders in side that, but it complains
about not being able to create the CoreSync folder.
I ran into this, then uninstalled everything, and nuked the ~/Library/Application Support/Adobe folder completely and started over.
The installed created the Adobe folder and "AAMUpdaterInventory", "AdobeApplicationManager", "Extension Manager CC", OOBE, SLCache, SLStore, Vulcan
folders just fine. but it can't create the CoreSync folder in the same location.
I'm stuck.

EHSM - Create Vendor - error: 'Could not find a document for the given key'

Dear all,
In the Chemical Approval Process I have attached a SDS document to the Approval Request. You can assign a Vendor to the SDS. As there are no (EHSM) Vendors currently available in the system I would like to create a new (EHSM) Vendor by clicking on 'Create Vendor'.
This will lead me to the following Webdynpro Application: Edit Vendor (EHFND_UI_VENDOR_OVP).
Only one field is shown in the Webdynpro named: 'Name of the Vendor'. After typing a name e.g. 'test', the following error message appears; 'Could not find a document for the given key'. See also attached document. This issue looks like a missing number range, however I could not find a EHSM number range for Vendors.
How to solve this issue?
More information:
Software Component: SAP EHS Management (EHSM) Support Package: 3
Process: Chemical Approval
Webdynpro application: EHFND_UI_VENDOR_OVP
Thank you.
Kind regards,
Roy

Hi
babooraj
This might be a problem with Windows Power Shell.
The solution is to copy the folder: "PSWorkflow" from "C:\Windows\System32\WindowsPowerShell\v1.0\Modules\"
to "C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Modules"
Than everything works fine.
Ps.: @Microsoft, please fix this problem in future versions.
Thomas van Veen

SAP MMC error - MMC Could not create the snap in

I installed 3 new instances on a new server, and i get the following errors.
MMC Could not create the snap-in
MMC could not create the snap-in, the snap-in might not have been installed correctly.
Name SAP System Manager
CLSID: {633547ee-A302-11D1-Ae59-080009b07dbb}
Any Ideals.

Hi,
I got the exactly the same error. I installed GUI 7.10, and I installed the latest MMC but during installation of MMC was prompted that current version is allready newer.
Do you got some more specific answer on how did you solve this issue?
Thanks!
Best regards,
Jacco Raymakers.

Acrobat Standard (9.4.6) - Issue: "Acrobat could not create a new PDF form"

I have Adobe Acrobat Standard (version 9.4.6). I am trying to create a form but when I start the form wizard, locate the document to convert and click next, I get an error message "Acrobat could not create a new PDF form." What's wrong? (I've used this feature before in Adobe Pro so I am familiar with the process but I am using Standard now). It's not letting me upload my document (an MS Word 2003 document). Please, someone, anyone, help! I think I got a bad batch of software here. Any suggestions? If it's hopeless, who do I call for a replacement if that's the case? Is this software under warranty?

Hello Michael,
Thank you for your email. The file I am trying to convert to PDF and create a form with is a MS Office Word 2003 file. It isn't any specific file; the issue happens every time. I type my text in the Word doc and then proceed to open Adobe Acrobat Standard and use the wizard to create a form from an existing file. I tried to repairing the software but it does not help. Any other suggestions? Is this version of software defective? I really need this feature. I look forward to your reply. Thanks.
Angela

Could not create JCOClientConnection for logical System: MUSA_MODEL_DATA

Hi,
I am facing a big problem...I have created WebDynpro Application & when I am running that application from WebDynpro, it's showing the page but giving me the error message as:-
Could not create JCOClientConnection for logical System: MUSA_MODEL_DATA - Model: class com.bcone.bcool.musa.model.MUSABAPI. Please assure that you have configured the RFC connections and/or logical system name properly for this model!
What do I do? what connections I have to check?
pls help.

Hey if you are connecting to SAP system making use of adaptive RFC model you hav to create logical systems(JCOs).So while creating the model you have to specify 2 logical system names(one for model data or on for the meta data).If you have not created the JCOs or if the JCOs are not active then you are going to get this type of error.To activate those JCOs ask your administrator to activate the JCO for metadata of your application.If you are having proper credentials then log on to portal
System administration>webdynpro>expand the local directory>select your project>click on maintain JCOs and activate the JCO for the metadata.
Or else change the logical system in your application.

Error in tutorial: Could not create XML document carrying AQ Headers

Similar Messages

Maybe you are looking for