The Report Session Manager is responsible for running asynchronous reports.
The Report Session Manager:
Starts reports.
Monitors the status of running reports through to their completion.
Keeps record of reports awaiting recovery.
Stores the parameters needed by reports.
Stops and terminates reports.
Handles WakeUp calls.
In the event of a report failure, the Report Session Manager restarts the report automatically. If there is a problem with the restart, it is attempted three times before aborting. If a report uses CriticalPoint logic, the Report Session Manager can restart it from the last good Critical Point.
Limitations with Running Reports
The limitations with running reports are as follows:
Report Session Manager has a limit on how many reports can be actively running for a single system. This limit is 189 reports (actively running) for each Windows Runtime system.
There is an overall maximum limit of about 110 reports that can be initiated in one session of Report Session Manager due to a Windows operating system limit called “desktop heap Size”. This limit is controlled by a registry setting that can be increased to allocate more heap memory to spawn more processes in a given session. This can be achieved by configuring the value of the non-interactive session in the registry, under the key,
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ SessionManager\SubSystems\Windows
This value is represented by the third value in the “SharedSection” parameter, for example, SharedSection=1024,20480,768. This value can be increased significantly, for example, SharedSection=1024,20480,8192.