Error while publishing BI 7.0 report in SAP EP..

Hi,
I want to publish BI 7.0 report in sap ep. I have done SSO configured between SAP EP and SAP BI.
When I go to content admin and crerate iview for BI i followed this step:
iview template>BEx Web Application iView (SAP Netwever 7.0 Format)> there I have given iview/ID name say ( Test_BI )--->System (in this only 1 option is coming that is only SAP_LocalSystem option is coming, what ever system objects i created in system admin nothing is coming here, so i choose this ooption only and in option BEx Web Application Query string i put this: TEMPLATE=Z_0MATERIAL_TEST where Z_0MATERIAL_TEST is the quesry string --> next and finish)
after doing this when i go to the iview and do preview i am getting error:
Portal Runtime Error
An exception occurred while processing your request
Exception id: 10:12_10/09/10_0022_1240150
Than i opened that iview in the content admin and in the iview object property i changed that system property from SAP_LocalSystem to SAP_BI (SAP_BI is the system object i created fro BI and portal SSO) and again tested but even now also same error .
Please let me know why i m not able to publish that BI report in my portal.

yes mayank, i am getting same error even after trying 3-4 times with 7.0 iview.
I have given query=<query string> in 7.0 iview but no success
here are the logs: Log No. 1
Full Message Text
Exception ID:02:43_22/09/10_0017_1240150
[EXCEPTION]
com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/new_development/iView/aa
Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
User : AA_EP
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
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:524)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
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(AccessController.java:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<System.scheme>://<System.servername>:<System.serverport><BWLauncherComponent[PORTAL_URL]>;jsessionid=<Request.JSessionID>?sap-bw-iViewID=<FPN.PCDHomeLocation[url_ENCODE]>&sap-ext-sid=<ESID[url_ENCODE]>&sap-pp-producerid=<producerID>&sap-pp-consumerBaseURL=<Request.BaseURL[url_ENCODE]>&theme=<LAF.Theme[url_ENCODE]>&sap-lafversions=<LAF.AllVersions[url_ENCODE]>&<BusinessParameters>'; the problem occured at position 138. Cannot process expression <FPN.PCDHomeLocation>
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.doPreview(AbstractPortalComponent.java:240)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:168)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
... 29 more
================================================
Log No. 2
Full Message Text
Content pass of Application Integrator failed.
Component Name:       com.sap.portal.appintegrator.sap.BWReport,
Context Name (iView): pcd:portal_content/new_development/iView/aa,
Top Layer:            BWReport/TopLayer,
Producer ID (FPN):    null,
System Alias:         SAP_BI,
[EXCEPTION]
com.sapportals.portal.appintegrator.ApplicationIntegratorException: Unable to parse template '<System.scheme>://<System.servername>:<System.serverport><BWLauncherComponent[PORTAL_URL]>;jsessionid=<Request.JSessionID>?sap-bw-iViewID=<FPN.PCDHomeLocation[url_ENCODE]>&sap-ext-sid=<ESID[url_ENCODE]>&sap-pp-producerid=<producerID>&sap-pp-consumerBaseURL=<Request.BaseURL[url_ENCODE]>&theme=<LAF.Theme[url_ENCODE]>&sap-lafversions=<LAF.AllVersions[url_ENCODE]>&<BusinessParameters>'; the problem occured at position 138. Cannot process expression <FPN.PCDHomeLocation>
at com.sapportals.portal.appintegrator.layer.AbstractIntegrationLayer.processTemplate(AbstractIntegrationLayer.java:455)
at com.sapportals.portal.appintegrator.layer.URLTemplateProcessLayer.processLayer(URLTemplateProcessLayer.java:33)
at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:159)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:68)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:54)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:396)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
at com.sapportals.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:799)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:652)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
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(AccessController.java:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sapportals.portal.appintegrator.template_processor.TemplateParserException: Unable to parse template '<System.scheme>://<System.servername>:<System.serverport><BWLauncherComponent[PORTAL_URL]>;jsessionid=<Request.JSessionID>?sap-bw-iViewID=<FPN.PCDHomeLocation[url_ENCODE]>&sap-ext-sid=<ESID[url_ENCODE]>&sap-pp-producerid=<producerID>&sap-pp-consumerBaseURL=<Request.BaseURL[url_ENCODE]>&theme=<LAF.Theme[url_ENCODE]>&sap-lafversions=<LAF.AllVersions[url_ENCODE]>&<BusinessParameters>'; the problem occured at position 138. Cannot process expression <FPN.PCDHomeLocation>
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.processWholeTagExpression(TemplateProcessor.java:167)
at com.sapportals.portal.appintegrator.template_processor.compiler.TemplateCompiler.processWholeTagExpression(TemplateCompiler.java:54)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseSimpleExpression(TemplateParser.java:234)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpression(TemplateParser.java:188)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpressionEx(TemplateParser.java:210)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpression(TemplateParser.java:193)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseTagExpression(TemplateParser.java:170)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseTemplateExpressionPart(TemplateParser.java:97)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parse(TemplateParser.java:89)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parse(TemplateParser.java:83)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.processImpl(TemplateProcessor.java:407)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.process(TemplateProcessor.java:374)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.process(TemplateProcessor.java:386)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessorService.processTemplate(TemplateProcessorService.java:54)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessorService.processTemplate(TemplateProcessorService.java:107)
at com.sapportals.portal.appintegrator.layer.AbstractIntegrationLayer.processTemplate(AbstractIntegrationLayer.java:441)
... 30 more
Caused by: java.lang.ClassCastException: com.sap.portal.pcm.system.System incompatible with com.sap.portal.pcm.remoteportal.producer.IProducerInformation
at com.sap.portal.fpn.runtime.services.AppIntegratorInformationService.getProducerByAlias(AppIntegratorInformationService.java:120)
at com.sap.portal.fpn.runtime.services.AppIntegratorInformationService.buildFPNLocatorForShortcut(AppIntegratorInformationService.java:136)
at com.sap.portal.fpn.runtime.services.AppIntegratorInformationService.transformURL(AppIntegratorInformationService.java:200)
at com.sapportals.portal.appintegrator.template_processor.context.FPNWrapper.getTerminal(FPNWrapper.java:69)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.processWholeTagExpression(TemplateProcessor.java:152)
... 45 more
Edited by: Rahul Pradhan on Sep 22, 2010 11:54 AM

Similar Messages

Error while trying to open crystal report with SAP B1 8.8

Hello Experts
    I found one problem when I open my Crystal Report from SAP B1 8.8 then it gives me error like
   "Failed to retrieve data from database. Details : [Database Vendor Code : 156]"
   This report perfectly work while open in crystal report outside from SAP.
Waiting for your replies...
Hepil Doshi

Dear Experts,
I face the exactly same problem, please forgive if i am not suppose to ask the same question in other people thread.
I am using SAP 8.8, PL09, SQL Server 2005, the Crystal Report is working perfectly after import into SAP B1.
However, when i do the same configuration in my customer server, the error message prompt:
Failed to retrieve data from the database.
Detail: [Database Vendor Code: 156]
Failed to retrieve data from the database.
Error in File Temp {8090e857-e2a3-4fa9-80dc-9e776e5991b8}{0912E6A5-88EF-406C-BD89-0155AE10F045}.rpt:
Failed to retrieve data from the database.
Detail: [Database Vendor Code: 156]
The server is using SAP 8.8, PL09, with SQL Server 2008.
Could it be some setting require for SQL Server 2008?
Please advice.
Thanks.
Regards,
Lay Chin

Failed to commit objects to server. Error while publishing reports from BW

Hi,
I am getting below error while publishing reports from BW to BO.
"0000000001 Unable to commit the changes to Enterprise. Reason: Failed to commit objects to server : #Duplicate object name in the same folder."
Anyone having any solution for this. Thanks in advance.

Hi Amit
It would be great if you could add a little info about how you solved this issue. Others might run into similar situations - I just did:-(
Thank you:-)

Error While Executing the Asset history report S_ALR_87011990

Hi,
I am getting the below error while executing the Asset History Report - S_ALR_87011990
No data was selected
Message no. AB064
Kindly advice me

Hi,
Thi may be a authorisation issue. I doubt that it will get recorded in su53 for report executing. Check with basis guy for respective asset class authorization.

Getting multiple error while refreshing or scheduling WebI report

Hi BO Admin Experts ,
Feacing multiple errors while refreshing or scheduling webi reports in BI4.0 CMC ,
Please find the below errors :
1)report schedule status failed
2)Parameters : xxxcorp-franklinee; ATOu supply unv
Error Message : An internal error occured while calling 'ProcessDPcmndsEx' API (Error:ERR_WIS_30270)
3 ) Format : WebI
Parameters : 10000000000159270
Error Message :CORBA error while communicating with the SL service
Could you please help me on the abive 3 issues for the WebI schedule reports
Cheers ,
Pradeep Gorpadu

Hi,
While refreshing the WEBI Reports would recommend you check the WEBI PROCESSING Server's last changed date from CMC--> Servers.
Check when you are refreshing the reports, do you see the time stamp changed of WEBI PROCESSING servers?
Do you keep getting this error messages for all WEBI reports? Can you re-produce this with simple e-fashion reports as well?
After that go to the node where WEBI PROCESSING servers installed and check on the event viewer details if you see any relevant error messages.
Regards,
Upendra

Getting error while publishing workflow using SP designer for SharePoint 2013

Hi,
I am try to setup Workflow manager for our sharepoint applications.
WF manager set ran without any issue.
I registered the SPWorkflow service which succeeded as well. The Workflow service application shows "Workflow is connected"
I am creating a workflow using sharepoint designer using my credential (not Service account). I am able to save it but while publishing, its prompting with an error.
The error says "Errors were found while compiling the workflow.The workflow files were saved but cannot run." Clicking advanced button show
"Microsoft.SharePoint.SPException: We're sorry, we weren't able to complete the operation, please try again in a few minutes. If you see this message repeatedly, contact your administrator.
at Microsoft.SharePoint.SPScaleOutDatabaseMap.CreateSqlSession(ISPScaleOutDatabaseMapProvider mapProvider, Byte[] compositeKey, Guid forceRefreshVersion, Guid& version)
at Microsoft.SharePoint.SPScaleOutDatabaseCommandExecutor.Execute(ExecuteDelegate operation, ISPScaleOutDatabaseMapProvider mapProvide"
Any help would be highly appreciated
Thanks,

Hi,
According to your post, my understanding is that you got error while publishing workflow using SharePoint designer for SharePoint 2013.
Please check whether the Central Admin > Manage Service Application-> “App Management Service” is started.
Please check whether the “Configure service application associations”, ”App Management Service” is already associated.
Then please check whether the “Manage Services on server” and the “App Management Service” is started.
In addition, please try to re-register Workflow Service.
If the issues still exists, please follow the steps in the
Steps to Verify that Server Is Correctly Set Up. After you verified that the server is correctly set up, follow the steps in the
Steps to Troubleshoot Workflow Management Service and
Troubleshooting the Service Bus for Windows Server then retry your action related to publishing workflows
More information:
http://wp.ahcheng.com/2013/03/23/error-were-found-when-compiling-the-workflow-the-workflow-files-were-saved-but-cannot-be-run/
http://sp2013.pro/2013/04/solution-errors-were-found-when-compiling-the-workflow-the-workflow-files-were-saved-but-cannot-be-run-cannot-set-unknown-member/
Best Regards,
Linda Li
Linda Li
TechNet Community Support

File to RFC - error while processing message to remote system:com.sap.aii.

Hi
i m working on File to RFC scenario. the records are getting displayed in sender CC and receiver CC. But in receiver CC i m also getting the following error:
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling ZRFC in remote system (RfcClient[CC_RIS_STC_PIMASTER_RECEIVER]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Screen output without connection to user.
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling ZRFC in remote system (RfcClient[CC_RIS_STC_PIMASTER_RECEIVER]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Screen output without connection to user.
It was working fine few hours earlier but showing this error now. i was giving a SUBMIT program , but stopped that now.
But still facing the same problem. and in SXMB_MONI its showing recorded for Outbound processing.
could anyone help.

Hi
I am Facing Following Error When I am trying to call SAP Screen through JCO.jar
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Screen output without connection to user
Please Guide Whethere it is possible to call SAP screen Through JCO.jar ot NOT
Please HELP if it is possible to Call SAP screen through JCO.jar with step and Code
Thanks
Vivek

I have error while testing the system created from a sap business objects template in SAP portal

I have error while testing the system created from a sap business objects template in SAP portal. Error text:
com.sapportals.connector.connection.ConnectionFailedException: Connection Failed: A nested exception occurred. Could not initialize physical connection. Connection Failed: A nested exception occurred. Could not initialize physical connection. Connection Failed: A nested exception occurred. Could not create JCO connection. 'mshost' missing
I configure integration SAP portal and SAP BW system. All system requirements are complied.
Environment
SAP Business Objects 4.0
SAP BW 7.31
1.     I configure SSSO between SAP BW and SAP Business Objects Enterprise 4.0
2.     Next I setting integration SAP PORTAL with SAP BW system
3.     I download certificate from portal. Select Certificates and key (http://sapserver:port/nwa) – See scren_
4.     In next window selected Ticketkeystore and Saplogonticketpair-cert( near part window form)
5. Select Export entry button and binary format file certificate for download. Press download.
6.     Save certificate file in local PC folder
In next step need export certificate file to SAP system. Sequence of step:
1.       Run STRUSTSS02 transaction .
2.       Chose certificate ->import.
3.       Select downloaded certificate file
4.       Select Add to certificate list button and Add to ACL button
5.       Inter System ID and Client(000)
6.       In next I download iview sap business objects template into sap portal: System administration->transport->Import. And select and download sap business Objects iview template in .epa format into sap portal.
7.       Result – downloaded iview.
8.       In next step I create system from template. System administration->system landscape.
9. In next step I input parameters for my system in Connector category, Sap business objects and user management categories: See screen _2
10.   When I created the system and test the connection error occurred: See screen_3
This issue is important enough. I would be grateful for opinions and ideas. Thanks in advance.

Did you find a solution?

Error while Activating / running Bex queries/reports

Hello
I have following ERRORs while activating / running BEx reports/queries.
1. While Activating BEx reports, I keel getting following ERRORS
Object directory entry R3TR ELEM E341OIR6G715GUMGN0MRXP3MA does not exist
Error when activating element BX7FOOKQB4588RROCBTC2YVZN
BEx transport request 'BIDK901352' is not available or not suitable
2. While running the BEx report/query in Bex Analyzer, I'm getting ERROR in entering the parameters, its NOT allowing / giving me option to select the parameters, for example for 0COSTCENTER, it is NOT displaying list costcenters to select before I can RUN that particular report.
3. How can I trouble shoot ERRORs related to BEx and Portal connectivity.
4. How would I setup the Variants for a Bex query/report ? Are these Variants for per user basis / per report basis. Can I have each variant for particular users OR all users must select their own variant each time when they RUN the report ?
Thanks, Sorry I have asked multiple questions, in jst one thread.
BI

Goto SE03 -->Search for Objects in Requests/Tasks option , select the object type and execute it will give all the transports it has collected before ..
Also you can use transport connection in RSA1 and select the query and find out all the objects in query locked by what request etc ..
Thanks,
Ravi

Error while generating PDF BI 7 Report Designer

Hi,
I am getting this error Error while generating PDF when i tried print version on report designer,
I tried to find information on this error but there was no information regarding this , so posted here.
Please let me know if you have any suggestions.
Thanks,
Kumar

We have restated the java server and now the issue solved.
Kumar

Error while publishing thru Service registry

Hi friends
While publishing service thru service registry, I am getting this error message.
Any Solution?
Thanks
-Mitesh
com.sap.esi.uddi.sr.api.exceptions.SRExceptionerror code: null detail message: com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.ValidationException: Cannot load WSDL due to "Invalid Response Code: (401) Unauthorized. The requested URL was:"http://host:8000/sap/bc/srt/xip/sap/ECC_SALESORDERCRTRC1?sap-client=001&wsdl=1.1"". Check that the specified WSDL URL "http://host:8000/sap/bc/srt/xip/sap/ECC_SALESORDERCRTRC1?sap-client=001&wsdl=1.1" points to WS-I Basic Profile 1.1 compliant WSDL Definitions file->com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.ValidationException: Cannot load WSDL due to "Invalid Response Code: (401) Unauthorized. The requested URL was:"http://host:8000/sap/bc/srt/xip/sap/ECC_SALESORDERCRTRC1?sap-client=001&wsdl=1.1"". Check that the specified WSDL URL "http://host:8000/sap/bc/srt/xip/sap/ECC_SALESORDERCRTRC1?sap-client=001&wsdl=1.1" points to WS-I Basic Profile 1.1 compliant WSDL Definitions file->com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.ValidationMessage: Cannot load WSDL due to "Invalid Response Code: (401) Unauthorized. The requested URL was:"http://host:8000/sap/bc/srt/xip/sap/ECC_SALESORDERCRTRC1?sap-client=001&wsdl=1.1"". Check that the specified WSDL URL "http://host:8000/sap/bc/srt/xip/sap/ECC_SALESORDERCRTRC1?sap-client=001&wsdl=1.1" points to WS-I Basic Profile 1.1 compliant WSDL Definitions file

Hello Mitesh
Would this forum question be interesting for you?
[ESR post-installation tasks are missing|ESR post-installation tasks are missing]
regards
Rathish

Error while running batch in Hyperion Reports

Has anybody run accross this error while trying to run a batch in Hyperion Reports:
Unexpected Error creating query to datasource in createCubeViews:
The book the batch is running is big...

Have you ever successfully scheduled a batch? Make sure the scheduled batch name does not contain an ampersand "&" symbol or an apostrophe/single tick symbol. Those cause batches to error out for us.
-Karen

Error while publishing a service with WSPUBLISH: Error publishing Endpoint

Hallo,
I've a problem while publishing a service which a had created via proxy. I configured the service and one endpoint (binding) in SOAMANAGER. When I publish the service in WSPUBLISH I get the error:
'Error publishing Endpoint for SD : <Proxy>, Service : <Service>, EP : <Endpoint>.
with details:
'10160A save request exceeded the quantity limits for a given structure type .#Number of BusinessEntities exceeds your limit of 1 (2)'
In the Service Registry I can find the service but without endpoints.
Does anybody know what happend ?
We use a SAP NetWeaver 7.10 with SP05 (SAPKB71005) but the same error happens if I publish a service from a CRM 5.0 with SP15 (SAPKB70015) to the Service Registry of the 7.10
Christoph

This is my steps to publish ES to SR:
1. Create RFC destination in SM59
2. Create ES Parameter in WSPARAM
3. Create logical port for SR in LPCONFIG
4. Release Web Service for SOA Runtime in WSCONFIG
5. Publish ES in WSPUBLISH.
When i was using SOAMANAGER to manually create the endpoint, the endpoint in the SR doesnt works though.
eg, Business Administration -> WS Administration -> Search for CRM_BPBASICDATABYIDQR -> Apply selection -> Configuration -> Create Service -> enter new service name and new binding name -> user id/password for HTTP Authentication -> save.
It works after i released it in WSCONFIG (ya, i know it's old way) and re-publish.
-julius

Error while opening hierarchy Location Analysis Report in Bex

Hi All,
I encounter an error while generating a Bex report Location Analysis report which contains hierarchy for functional location.The infoobject is 0FUNCT_LOC.
There is a global hierarchy created for this infoobject and within this global hierarchy there are many hierarchies which come from differernt source system around 5 source systems.
The error i get is "Warning error when writing in the internal buffer."
Warning presentation hierarchy ZGBL_HIER acts as a dynamic filter".
ZGBL_HIER is the global hierarchy created.And i have provided this name in the query.
Please can someone help me with this issue.

Hi,
May be it worked in your case How the job names going to affect the execution of the job. The issue is purely because of RFC timeout (As per the logs). I recommend to change the parameter in the configuration tab as recommended by Sunny in the previous thread.
Regards,
Raghu

Error while publishing the JCA Adapter.

Hi,
I created a DBAdapter through JDeveloper and created the .bz file from the .JCA file using OSB eclipse console. I have provided datasource and deployment configurations on the weblogic server. While publishing (run on server) the .bz file I am getting the follolwing error.
===============================================================
<Mar 17, 2011 8:06:12 PM IST> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=ConnectorApplicationOverviewPage&ConnectorApplicationOverviewPortlethandle=com.bea.console.handles.AppDeploymentHandle%28%22com.bea%3AName%3DDbAdapter%2CType%3DAppDeployment%22%29.>
<Mar 17, 2011 8:06:12 PM IST> <Warning> <WebLogicDescriptorWL> <BEA-2156000> <"config-root" D:\Oracle\Middleware\Oracle_OSB1\soa\connectors\plan was not found>
<Mar 17, 2011 8:07:21 PM IST> <Error> <JCATransport> <BEA-381979> <An error occured while validating JCA transport endpoint, exception: javax.resource.ResourceException: Cannot locate Java class oracle.tip.adapter.db.DBWriteInteractionSpec
javax.resource.ResourceException: Cannot locate Java class oracle.tip.adapter.db.DBWriteInteractionSpec
at oracle.tip.adapter.sa.impl.fw.validation.WSDLDeploymentValidation.validateWsdlJcaBindingOperation(WSDLDeploymentValidation.java:338)
at oracle.tip.adapter.sa.impl.meta.JCABindingEndpointMetadataHelper.validateJCAOperationSpecProperties(JCABindingEndpointMetadataHelper.java:262)
at oracle.tip.adapter.sa.impl.meta.JCABindingEndpointMetadata.validateJCAInteractionSpecProperties(JCABindingEndpointMetadata.java:348)
at oracle.tip.adapter.sa.impl.JCABindingEndpointContextImpl.validateJCAInteractionSpecProperties(JCABindingEndpointContextImpl.java:151)
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.validateJCAInteractionSpecProperties(JCABindingReferenceImpl.java:154)
Truncated. see log file for complete stacktrace
>
===========================================================================
The datasource >OutBound connection properties
dataSourceName java.lang.String
defaultNChar java.lang.Boolean false
platformClassName java.lang.String org.eclipse.persistence.platform.database.Oracle10Platform
sequencePreallocationSize java.lang.Integer 50
usesBatchWriting java.lang.Boolean true
usesNativeSequencing java.lang.Boolean true
usesSkipLocking java.lang.Boolean true
xADataSourceName java.lang.String jdbc/JDBCEmp
If I restart the server I am getting a different error
<Mar 17, 2011 8:00:53 PM IST> <Warning> <Coherence> <BEA-000000> <Oracle Coherence 3.5.3/465p2 (member=n/a): Local address "127.0.0.1" is a loopback address; this cluster node will not connect to nodes located on different machines> <Mar 17, 2011 8:01:00 PM IST> <Warning> <WliSbTransports> <BEA-381917> <MQ Transport could not be registered due to : Missing MQ Library> <Mar 17, 2011 8:01:01 PM IST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'DbAdapter' due to error weblogic.application.ModuleException: A <jndi-name> is specified for the resource adapter bean in weblogic-ra.xml, however no <resourceadapter-class> element is specified in ra.xml.weblogic.application.ModuleException: A <jndi-name> is specified for the resource adapter bean in weblogic-ra.xml, however no <resourceadapter-class> element is specified in ra.xml at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.java:229) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:507) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149) Truncated. see log file for complete stacktrace> <Mar 17, 2011 8:01:01 PM IST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'OracleAppsAdapter' due to error weblogic.application.ModuleException: java.lang.NoClassDefFoundError: oracle/tip/adapter/db/DBManagedConnection.weblogic.application.ModuleException: java.lang.NoClassDefFoundError: oracle/tip/adapter/db/DBManagedConnection at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.java:239) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:507) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149) Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: oracle.tip.adapter.db.DBManagedConnection at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:253) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:177) Truncated. see log file for complete stacktrace> [ERROR] AdapterManager - ServletContainerAdapter manager not initialized correctly.
Oracle Service Bus Debugger listening on port 7453.
<Mar 17, 2011 8:01:14 PM IST> <Notice> <LoggingService> <BEA-320400> <The log file D:\Oracle\Middleware\user_projects\domains\base_domain\servers\AdminServer\logs\base_domain.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.> <Mar 17, 2011 8:01:14 PM IST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to D:\Oracle\Middleware\user_projects\domains\base_domain\servers\AdminServer\logs\base_domain.log00013. Log messages will continue to be logged in D:\Oracle\Middleware\user_projects\domains\base_domain\servers\AdminServer\logs\base_domain.log.> <Mar 17, 2011 8:01:14 PM IST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.> <Mar 17, 2011 8:01:14 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN> <Mar 17, 2011 8:01:14 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING> <Mar 17, 2011 8:01:14 PM IST> <Warning> <Server> <BEA-002611> <Hostname "PC102536.cts.com", maps to multiple IP addresses: 10.226.187.76, fe80:0:0:0:197b:851d:ec88:5730%11> <Mar 17, 2011 8:01:14 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.226.187.76:7001 for protocols iiop, t3, ldap, snmp, http.> <Mar 17, 2011 8:01:14 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on fe80:0:0:0:197b:851d:ec88:5730:7001 for protocols iiop, t3, ldap, snmp, http.> <Mar 17, 2011 8:01:14 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[4]" is now listening on 0:0:0:0:0:0:0:1:7001 for protocols iiop, t3, ldap, snmp, http.> <Mar 17, 2011 8:01:14 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.> <Mar 17, 2011 8:01:14 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on fe80:0:0:0:0:5efe:ae2:bb4c:7001 for protocols iiop, t3, ldap, snmp, http.> <Mar 17, 2011 8:01:14 PM IST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "AdminServer" for domain "base_domain" running in Development Mode> <Mar 17, 2011 8:01:15 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING> <Mar 17, 2011 8:01:15 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode> <Mar 17, 2011 8:01:23 PM IST> <Error> <JCATransport> <BEA-381979> <An error occured while validating JCA transport endpoint, exception: javax.resource.ResourceException: Cannot locate Java class oracle.tip.adapter.db.DBWriteInteractionSpecjavax.resource.ResourceException: Cannot locate Java class oracle.tip.adapter.db.DBWriteInteractionSpec at oracle.tip.adapter.sa.impl.fw.validation.WSDLDeploymentValidation.validateWsdlJcaBindingOperation(WSDLDeploymentValidation.java:338) at oracle.tip.adapter.sa.impl.meta.JCABindingEndpointMetadataHelper.validateJCAOperationSpecProperties(JCABindingEndpointMetadataHelper.java:262) at oracle.tip.adapter.sa.impl.meta.JCABindingEndpointMetadata.validateJCAInteractionSpecProperties(JCABindingEndpointMetadata.java:348) at oracle.tip.adapter.sa.impl.JCABindingEndpointContextImpl.validateJCAInteractionSpecProperties(JCABindingEndpointContextImpl.java:151) at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.validateJCAInteractionSpecProperties(JCABindingReferenceImpl.java:154) Truncated. see log file for complete stacktrace
=======================================
Please help me on this..
Thanks
PM

Hi all,
Thanks for your help I found my DBAdapter was not running on the server. I redeployed and the issue was resolved.
I tried testing the insert operation from the sbconsole I got the following error. Even from the OSB eclipse console I am facing same issue. I have pasted the error below. If any one can help me on this, will be a great help to me.
The invocation resulted in an error: <jca-transport-application-error xmlns="http://www.bea.com/wli/sb/transports/jca" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<jca-transport-error-message>Invoke JCA outbound service failed with application error</jca-transport-error-message>
<jca-runtime-fault-detail>
<eis-error-code xsi:nil="true"/>
<eis-error-message>Duplicate Property Values Exception.
The properties [xADataSourceName] and [dataSourceName (both in connector properties)] can not both be [JDBCEmployee].
Sometimes it may not make sense for two or more related properties to have the same value.
Make sure the property is valid in the interaction (activation) spec by editing its definition in the wsdl. Refer to the Configuring the Database Adapter Guide.</eis-error-message>
<exception>com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/EmployeeDetails/Resources/JCA%20Adapter/Database/EmpDetails/EMP_DETAILS/employeeService [ employeeService_ptt::insert(CtsEmpCollection) ] - WSIF JCA Execute of operation 'insert' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by javax.resource.spi.InvalidPropertyException: Duplicate Property Values Exception.
The properties [xADataSourceName] and [dataSourceName (both in connector properties)] can not both be [JDBCEmployee].
Sometimes it may not make sense for two or more related properties to have the same value.
Make sure the property is valid in the interaction (activation) spec by editing its definition in the wsdl. Refer to the Configuring the Database Adapter Guide.
; nested exception is:
BINDING.JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by javax.resource.spi.InvalidPropertyException: Duplicate Property Values Exception.
The properties [xADataSourceName] and [dataSourceName (both in connector properties)] can not both be [JDBCEmployee].
Sometimes it may not make sense for two or more related properties to have the same value.
Make sure the property is valid in the interaction (activation) spec by editing its definition in the wsdl. Refer to the Configuring the Database Adapter Guide.
You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server. This exception is considered not retriable, likely due to a modelling mistake.
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invokeOneWay(JCATransportOutboundOperationBindingServiceImpl.java:114)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendOneWay(JCATransportEndpoint.java:191)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:168)
at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:571)
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.wli.sb.transports.Util$1.invoke(Util.java:83)
at $Proxy125.sendMessageAsync(Unknown Source)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:148)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:603)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:538)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:558)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:426)
at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:377)
at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:76)
at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:134)
at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:132)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
at com.bea.wli.sb.test.service.ServiceMessageSender.send(ServiceMessageSender.java:137)
at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.java:454)
at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:172)
at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:167)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestService_sqr59p_EOImpl.java:353)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:345)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_1033_WLStub.invoke(Unknown Source)
at com.bea.alsb.console.test.TestServiceClient.invoke(TestServiceClient.java:174)
at com.bea.alsb.console.test.actions.DefaultRequestAction.invoke(DefaultRequestAction.java:117)
at com.bea.alsb.console.test.actions.DefaultRequestAction.execute(DefaultRequestAction.java:70)
at com.bea.alsb.console.test.actions.ServiceRequestAction.execute(ServiceRequestAction.java:143)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:97)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2044)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:91)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2116)
at com.bea.alsb.console.common.base.SBConsoleRequestProcessor.processActionPerform(SBConsoleRequestProcessor.java:91)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:556)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:853)
at com.bea.alsb.console.common.base.SBConsoleRequestProcessor.process(SBConsoleRequestProcessor.java:191)
at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:631)
at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:158)
at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:256)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServlet.java:133)
at com.bea.alsb.console.common.base.SBConsoleActionServlet.doGet(SBConsoleActionServlet.java:49)
at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1199)
at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1129)
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:687)
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:142)
at com.bea.portlet.adapter.scopedcontent.StrutsStubImpl.processAction(StrutsStubImpl.java:76)
at com.bea.portlet.adapter.NetuiActionHandler.raiseScopedAction(NetuiActionHandler.java:111)
at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:181)
at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:167)
at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:225)
at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:180)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:324)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:130)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:184)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:159)
at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388)
at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:199)
at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:130)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/EmployeeDetails/Resources/JCA%20Adapter/Database/EmpDetails/EMP_DETAILS/employeeService [ employeeService_ptt::insert(CtsEmpCollection) ] - WSIF JCA Execute of operation 'insert' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by javax.resource.spi.InvalidPropertyException: Duplicate Property Values Exception.
The properties [xADataSourceName] and [dataSourceName (both in connector properties)] can not both be [JDBCEmployee].
Sometimes it may not make sense for two or more related properties to have the same value.
Make sure the property is valid in the interaction (activation) spec by editing its definition in the wsdl. Refer to the Configuring the Database Adapter Guide.
; nested exception is:
BINDING.JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by javax.resource.spi.InvalidPropertyException: Duplicate Property Values Exception.
The properties [xADataSourceName] and [dataSourceName (both in connector properties)] can not both be [JDBCEmployee].
Sometimes it may not make sense for two or more related properties to have the same value.
Make sure the property is valid in the interaction (activation) spec by editing its definition in the wsdl. Refer to the Configuring the Database Adapter Guide.
You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server. This exception is considered not retriable, likely due to a modelling mistake.
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.post(JCABindingReferenceImpl.java:201)
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invokeOneWay(JCATransportOutboundOperationBindingServiceImpl.java:109)
... 117 more
Caused by: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/EmployeeDetails/Resources/JCA%20Adapter/Database/EmpDetails/EMP_DETAILS/employeeService [ employeeService_ptt::insert(CtsEmpCollection) ] - WSIF JCA Execute of operation 'insert' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by javax.resource.spi.InvalidPropertyException: Duplicate Property Values Exception.
The properties [xADataSourceName] and [dataSourceName (both in connector properties)] can not both be [JDBCEmployee].
Sometimes it may not make sense for two or more related properties to have the same value.
Make sure the property is valid in the interaction (activation) spec by editing its definition in the wsdl. Refer to the Configuring the Database Adapter Guide.
; nested exception is:
BINDING.JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by javax.resource.spi.InvalidPropertyException: Duplicate Property Values Exception.
The properties [xADataSourceName] and [dataSourceName (both in connector properties)] can not both be [JDBCEmployee].
Sometimes it may not make sense for two or more related properties to have the same value.
Make sure the property is valid in the interaction (activation) spec by editing its definition in the wsdl. Refer to the Configuring the Database Adapter Guide.
You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server. This exception is considered not retriable, likely due to a modelling mistake.
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:667)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeOperation(WSIFOperation_JCA.java:357)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:316)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation(WSIFOperation_JCA.java:295)
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.invokeWsifProvider(JCABindingReferenceImpl.java:354)
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.post(JCABindingReferenceImpl.java:199)
... 118 more
Caused by: BINDING.JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by javax.resource.spi.InvalidPropertyException: Duplicate Property Values Exception.
The properties [xADataSourceName] and [dataSourceName (both in connector properties)] can not both be [JDBCEmployee].
Sometimes it may not make sense for two or more related properties to have the same value.
Make sure the property is valid in the interaction (activation) spec by editing its definition in the wsdl. Refer to the Configuring the Database Adapter Guide.
You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server. This exception is considered not retriable, likely due to a modelling mistake.
at oracle.tip.adapter.db.exceptions.DBResourceException.createNonRetriableException(DBResourceException.java:653)
at oracle.tip.adapter.db.exceptions.DBResourceException.createEISException(DBResourceException.java:619)
at oracle.tip.adapter.db.exceptions.DBResourceException.couldNotCreateTopLinkSessionException(DBResourceException.java:291)
at oracle.tip.adapter.db.DBManagedConnectionFactory.acquireSession(DBManagedConnectionFactory.java:883)
at oracle.tip.adapter.db.transaction.DBTransaction.getSession(DBTransaction.java:375)
at oracle.tip.adapter.db.DBConnection.getSession(DBConnection.java:258)
at oracle.tip.adapter.db.DBInteraction.executeOutboundWrite(DBInteraction.java:721)
at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:241)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:534)
... 123 more
Caused by: javax.resource.spi.InvalidPropertyException: Duplicate Property Values Exception.
The properties [xADataSourceName] and [dataSourceName (both in connector properties)] can not both be [JDBCEmployee].
Sometimes it may not make sense for two or more related properties to have the same value.
Make sure the property is valid in the interaction (activation) spec by editing its definition in the wsdl. Refer to the Configuring the Database Adapter Guide.
at oracle.tip.adapter.db.exceptions.DBResourceException.duplicatePropertyValuesException(DBResourceException.java:324)
at oracle.tip.adapter.db.DBManagedConnectionFactory.createServerSession(DBManagedConnectionFactory.java:1170)
at oracle.tip.adapter.db.DBManagedConnectionFactory.acquireSession(DBManagedConnectionFactory.java:615)
... 128 more</exception>
</jca-runtime-fault-detail>
</jca-transport-application-error>.
Thanks once again
PM

Error while publishing BI 7.0 report in SAP EP..

Similar Messages

Maybe you are looking for