Reports REST server not working in Azure Application Service

[Grant]

Hi all - we have a website which uses Telerik Reporting, setup as a REST webservice - we have a backend api which makes calls to the Telerik service.

We have 3 separate environments - DEV, STAGING and PROD, of which only PROD is giving us problems.

Thought it might be a firewall issue, but now thinking something is interfering with the REST service - after tracing a few calls, the client id is created and given back, but often when we send it to get a report, we get an error that the client is is "not found" and "expired".

I've also seen it get PAST this part, go ahead and generate the report, then give back the ID, but when we make the call to fetch the report document, we get a "gone" error.

It seems like a session is started when the client 1st gets the client ID, but does not stay alive, or is being killed, before we can do anything.,

I HAVE ALREADY SET ClientSessionTimeout - tried setting it to 16 minutes, but the call to api/Reports/clients/sessionTimeout ALWAYS return 960 - ???

I'm thinking it's maybe some Azure Application Service setting, but I'm not the one who would check, I'm just a programmer, hoping to have some ideas to pass along to the Azure team here.

Thanks!

[Grant]

FYI, turns our our PROD environment was setup with a service application that's a shared service app, we moved it to a dedicated svc. app, and the Telerik issues stopped.

In case this helps anyone else.

[Todor]

Hello Grant,

Thank you for sharing the details of your scenario and the fix you found for the problem. I hope the information will help other Telerik Reporting users.

it is not clear why the Reporting REST Service works fine as a dedicated service app and not as a shared service app. We would be glad to investigate further if you can send more details, for example, Trace Listener logs from the two services for comparisons.

Regards,
Todor
Progress Telerik