January 16, 2008 at 8:12 am
ReportingServicesService.exe on my 64-bit SQL Server 2005 Enterprise Edition SP2 instance seems to crash quite regularly due to connection and command timeouts with the ReportServer database. Periodically our server experiences a very heavy load, during which times the Reporting Services Windows service experiences connection and command timeouts.
It seems as though increasing the connection and command timeouts would avoid this problem. According to Microsoft's documentation, the SQLCommandTimeoutSeconds value in rsreportserver.config is not used, and I have confirmed this by examining the Reporting Server libraries (specifically the Microsoft.ReportingServices.Diagnostics.dll assembly). The DatabaseQueryTimeout value is not used for connection timeouts, either. Through analyzing the ReportingServicesLibrary.dll assembly, it appears the only connection timeout that could possibly be used would be in the connection string, which is stored in the Dsn value in the rsreportserver.config file. This, of course, is encrypted. While it is possible for me to decrypt the connection string using the encryption key, add a connect timeout=x value, and encrypt the connection string again, I would rather avoid this for maintenance purposes.
I can configure the Windows service to restart automatically (with however many attempts are necessary by setting the "Reset fail count after" value to 0). Again, though, I prefer not to implement this, as there are many other situations that may cause the service to fail when I would not want the service to restart.
Any ideas?
March 8, 2008 at 2:02 am
Hi Mike,
Please explain me how can we add connection timeout to the "DSN" content inside the reportserver.config. I cannot able to decrypt the content. please tell this in detail. It will be great help to me.
Regards
Durai
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply