For reports that take a very long time to generate, it can be difficult to get it to complete successfully even if timeout values are adjusted appropriately (see https://blogs.msdn.microsoft.com/dynamicsaxbi/2013/02/14/how-to-addressing-ssrs-session-timeouts). If the report is printed to file and it takes hours to generate, it is possible that it will never complete. The problem is within the "Render" web service call to SQL Reporting Services.
A new registry value has been introduced in this hotfix. Inside of registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Dynamics\6.0\Reporting, add a String Value with name "RenderFileUsingWebRequest" and value set to "true". This needs to be done on any machine from where you want to render long-running reports - typically a Batch AOS server.
When the new registry value is present and set to true, the reporting framework will use a different call to render the report - instead of using the "Render" SOAP web service method, a regular HTTP GET request with an infinite timeout will be used.
Article ID: 4035606 - Last Review: 2017, ജൂലൈ 13 - Revision: 1