Can large reports reboot / restart the server. Any how Reports created by Report builder 3.0 + SSAS can responsible restart the Server?
Because it happen When I Execute my report having ~15 column.
Or it is problem with server. CPU and Memory utilization is normal.
Thanks in advance.
- Edited by Mahesh Kumar Sharma Friday, July 04, 2014 3:28 PM
To be honest, You will have better luck diagnosing what is causing the reboots by looking at the system logs of the server.
There are a large number things that could cause the server to reboot (pick a bsod). Correlating the reboots to the report running narrows it down a little, but there's still far to much in play to take a guess
Could you please provide below information:
1. Are you executing the report from repor builder directly or it is deployed report and you are running the report from report manager.
2. Have you experinced anytime, "Not Responding message" for report in the Task bar.
3. Check the ExecutionLogStorage table and let us know what is max time report takes to execute if any successful executuion is there.
4. Implement a file share subscription to the same machine and see whether system getting restarted or not. You can use below link for file share subscription:
5. What is the RAM size of the machine
6. Report Server DB hosted in the same box or different
7. Auto File Growth for Report Server DB in database property
8. Change the dataset query and run the report for top 50/100 records and see whether you are getting any restart issue.
9. Run these reports in multiple machine(s) and check that whether all machine(s) are getting restarted.
Based on above information, we will try to get the root cause of the system restart.
Hi Mahesh Kumar Sharma,
According to your description, your report server always restart unexpectedly when execute large reports. Right?
In this scenario, you can check the Reporting Services log file to see the detail error message. Go to C:\Program Files\Microsoft SQL Server\MSRS10_50.SSRSBI\Reporting Services\LogFiles to check those log files, you will get the detail information about the reason caused the restart. Since you are running large reports, even the CPU and Memory utilization is normal ,we still suggest improve the report performance. Please go to the ReportServer ExecutionLog to see which part takes more time.
Then we need to do some troubleshooting to improve our report performance. Here we have a article for your reference:
Troubleshooting Reports: Report Performance
If you still can't solve the issue, please feel free to post the error log.