Not able to invoke BPM oData (taskdata.svc) service

[Former Member]

Hello,

I am trying to access input/output data of a task using BPM oData service (taskdata.svc), but i am getting  "500 Internal Server Error" while accessing the same using below URL:

http://host:port/bpmodata/taskdata.svc/fc57eb8862f611e39b0800000058dd6a/InputData(‘fc57eb8862f611e39...

Error: An error occurred. 500 Internal Server Error. Log ID: C000AC112A030BF00000000000006F3B

Note - I am using PO SP09 and the potential owner of the task is already having "BPEM End User" and "UnifiedInboxUserRole" roles assigned to it.

In addition to that, i am able to retrieve metadata of a task using below URL (tasks.svc service), so i am wondering why the URL having taskdata.svc is not working?

http://host:port/bpmodata/tasks.svc/TaskCollection(‘fc57eb8862f611e39b0800000058dd6a’)?$format=json

Thanks

Amit Srivastava

[Former Member · Accepted solution]

Hello,

The most annoying part is i can't able to find any logs (NWA -> Troubleshooting -> logs and traces-> Log viewer) pertaining to the log id?

(Hope i am not seeing at wrong place)

Thanks

Amit Srivastava

[Former Member · Accepted solution]

Hello,

I again tried accessing the above URL and just after that i checked NWA logs and this is what i can find ("Logon policies are disabled" highlighted below):

LOGIN.OK
User: ASRIVASTAVA
Authentication Stack: sap.com/tc~bpem~odata~ear*bpmodata
Authentication Stack Properties:
        policy_domain = /bpmodata
        auth_method = form
        realm_name = BPMODataServlet

Login Module                                                               Flag        Initialize  Login      Commit     Abort      Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT  ok          false      false                
2. com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule    SUFFICIENT  ok          exception  false                 Received no SAP Authentication Assertion Ticket.
3. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          true       true                 
4. com.sap.security.core.server.jaas.CreateTicketLoginModule               OPTIONAL    ok          true       true                 
Central Checks                                                                                                true                 
Logon policies are disabled

Thanks

Amit Srivastava

[AndreH · Accepted solution]

Hello Amit,

the log entry is written in the developer traces (also known as default trace). You can open it as described in http://help.sap.com/saphelp_nw73ehp1/helpdata/en/47/b069c101391599e10000000a42189c/content.htm

Best Regards,

Andre

[Former Member · Accepted solution]

Hello,

Default traces from NWA are as below:

Request URI: http://host:port/bpmodata/taskdata.svc/fc57eb8862f611e39b0800000058dd6a/$metadata.

HTTP Headers:
cookie: JSESSIONID=RWnpjAfmzVZspJlyQ2-1g1xN-2flQgFr3VgA_SAPfx07pACV9dlXZ_T76TxgS1z9; saplb_*=(J2EE5823820)5823851; JSESSIONMARKID=c2953QJuSHW1COhhMZ-bvEA7F48W7nL3VGl2vdWAA; MYSAPSSO2=AjExMDAgABJwb3J0YWw6QVNSSVZBU1RBVkGIAAdkZWZhdWx0AQALQVNSSVZBU1RBVkECAAMwMDADAANEUEkEAAwyMDEzMTIxMjA1MjcFAAQAAAAICgALQVNSSVZBU1RBVkH%2FAQUwggEBBgkqhkiG9w0BBwKggfMwgfACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHATGB0DCBzQIBATAiMB0xDDAKBgNVBAMTA0RQSTENMAsGA1UECxMESjJFRQIBADAJBgUrDgMCGgUAoF0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMxMjEyMDUyNzAzWjAjBgkqhkiG9w0BCQQxFgQUojDeKg7GfHM9wl2oy2A0Ko110gowCQYHKoZIzjgEAwQvMC0CFQCRd8Ae6K!awb0onG!4JsJuxpcWmgIULr3qfKRx8UbyEUicYXedx89byOM%3D
connection: keep-alive
accept-language: en-US,en;q=0.5
user-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:25.0) Gecko/20100101 Firefox/25.0
accept-encoding: gzip, deflate
Content-Type: null
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8

[EXCEPTION]
com.sap.core.odata.api.exception.ODataException: java.lang.IllegalArgumentException: Nested properties are not supported. Property name: Context
at com.sap.bpm.odata.BPMODataServiceFactory.createService(BPMODataServiceFactory.java:31)
at com.sap.core.odata.core.ODataRequestHandler.handle(ODataRequestHandler.java:61)
at com.sap.core.odata.core.rest.ODataSubLocator.handle(ODataSubLocator.java:121)
at com.sap.core.odata.core.rest.ODataSubLocator.handleGet(ODataSubLocator.java:35)
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 org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:198)
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:261)
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:94)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:158)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:243)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:168)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:219)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)
at com.sap.bpm.odata.security.CsrfFilter.doFilter(CsrfFilter.java:60)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:432)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: java.lang.IllegalArgumentException: Nested properties are not supported. Property name: Context
at com.sap.bpm.odata.convert.impl.SdoToEdmDataConverter.validateProperty(SdoToEdmDataConverter.java:121)
at com.sap.bpm.odata.convert.impl.SdoToEdmDataConverter.convertToEdm(SdoToEdmDataConverter.java:109)
at com.sap.bpm.odata.convert.impl.SdoToEdmDataConverter.convert(SdoToEdmDataConverter.java:49)
at com.sap.bpm.odata.convert.impl.SdoToEdmDataConverter.convert(SdoToEdmDataConverter.java:30)
at com.sap.bpm.odata.EdmFactory.createEntityTypeForTaskData(EdmFactory.java:155)
at com.sap.bpm.odata.TaskDataEdmProvider.initEdmCaches(TaskDataEdmProvider.java:58)
at com.sap.bpm.odata.TaskDataEdmProvider.<init>(TaskDataEdmProvider.java:51)
at com.sap.bpm.odata.BPMODataServiceFactory.createService(BPMODataServiceFactory.java:28)
... 66 more

Thanks

Amit Srivastava

[AndreH · Accepted solution]

Hello Amit,

As described in the section Restrictions of the blog entry , with SP09 we do not support complex data types. This has changed with SP10. You could either use the described workaround or upgrade to SP10.

Best Regards,

Andre

[Former Member · Accepted solution]

Hello Andre,

It worked after correcting data type structure.

Thanks!!

Thanks

Amit Srivastava

[Former Member · Accepted solution]

Hello Andre,

I am facing strange exception while completing custom UI5 task. Raised a separate thread for the same. It would be highly appreciable if you suggest some pointers...

Error Traces from NWA - The Data Services Request version '3.0' is not supported for the request payload.

Thanks

Amit Srivastava

[AndreH]

Hello Amit,

In case of any error, the OData Service creates a log entry and provides more details about the error in this log entry. The corresponding ID of the log entry is given in the error response of the OData Service. In your case, it is Log ID: C000AC112A030BF00000000000006F3B. Have you already looked into the created log entry? What is described there?

It is only guessing, but maybe there is a spelling mistake in the entities you would like to expand. Keep in mind, that the $expand operation in case-sensitive.

Best Regards,

Andre

[Former Member]

Hi Amit,

Please go to the log viewer and search for the LOG ID mentioned. Post it back to the thread so we can see what the actual error is.

regards, Nick