Using SQL Express R2 on development machine (Windows 7 32-bit) and have no problems deploying. When trying to deploy on test server (Windows 2003 Standard R2 SP2), I get "Operation Timed Out" on almost all reports. I am deploying locally on the test server (http://localhost/reportserver). I have searched this and many other forums and have not found an answer. I was able to deploy a simple report that no joins in the query, but the report I get the error on is not complex by any means. Data Sources always deploy fine. I have checked permissions and they seem to be OK. I found another post that mentioned running the latest Cumulative Update. I ran CU 4 and I still have the problem. Here's the error message from the SSRS log: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeInternalException: RsWorkerRequest::ReadEntityBody., Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeInternalException: An internal or system error occurred in the HTTP Runtime object for application domain ReportServer_SQLEXPRESS_0-2-129342198039201734. ---> System.Runtime.InteropServices.COMException (0x800703E3): The I/O operation has been aborted because of either a thread exit or an application request. (Exception from HRESULT: 0x800703E3) at Microsoft.ReportingServices.HostingInterfaces.IRsHttpPipeline.ReadEntityBody(Byte[] buffer, Int32 offset, Int32 size) at ReportingServicesHttpRuntime.RsWorkerRequest.ReadEntityBody(Byte[] buffer, Int32 offset, Int32 size)

Following might help you http://social.msdn.microsoft.com/Forums/en/sqlreportingservices/thread/575a5474-2da3-4cf9-bcff-f71df732a033 Gaurav Gupta http://sqlservermsbiblog.blogspot.com/

That link is the one that lead me to running the Cumulative Update. I should also add that I initially setup the Database credentials to be Network Service in the Reporting Services Configuration Manager. Since, it seems to be the problem is problem in inserting the correct DB entries, I have also tried a domain user with appropriate rights but that did not work either.

Hi Scott, It seemed to be http limitation. I would suggest you follow this thread http://social.msdn.microsoft.com/Forums/en/sqlreportingservices/thread/0130046d-9313-483c-b7b8-90d915f1c048 to add the maxrequestsbytes. thanks, Jerry

Thanks, Jerry, that seemed to do it. I had seen that post before but dismissed it because the first report that I had this problem with was only 23KB. By reading Microsoft's KB article, this seems to be specific to Windows 2003, which was the server that was causing my problem. There must be something I'm not seeing, though, because that article says the default MaxBytesPerSend is 65KB, which is almost three times the size of my report. But, hey, it's now working, so, as they say, "The proof is in the pudding." Thanks!