June 28, 2006 at 8:50 am
Hello everyone,
We have SQL Server 2000 SP4 and Reporting Services SP1 installed on one of our database servers and we never had issues with Reporting Services, at least up until last week anyway. For some reason, we were suddenly seeing the following error:
aspnet_wp!library!3f10!6/26/2006-23:59:52:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., Error getting running jobs;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. ---> System.InvalidOperationException: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
Now what could have changed in our environment to cause such an error? No new hardware was introduced no were there any environment changes. The application developers said they haven't made any changes either.
We did solve the problem by executing the rsconfig utility but I would like to know what have caused this error.
Thank you for your input.
Peter
Peter M. Florenzano
Database Administrator
June 28, 2006 at 9:02 am
Peter,
I never got the error you got. But, going through the event log you posted I'm basing my argument. Reporting Services have a Virtual Directory in IIS. Each virtual directory runs under a application pool. When there are more requests for the application pool, the application pool kinda hangs when max requests is reached. You could also have recycled the application pool to get around the problem rather than re running rsconfig utility. What I do in our environment is, some time around 10:30 every night I recycle the application pool. Go to IIS and find the virtual directory for reporting services. Right click on the Virtual directory (for both reports and report server), and click on properties. In virtual directory Tab, the last field is Application Pool. Note down the application pool. Now, Go to Application Pools folder under IIS. By default it will be DefaultAppPool. Right click on the DefaultAppPool, you can see the actions you can perform. Stop / Start / Recycle.
You can also click on properties and set up to Recycle the Worker process at certain times or whatever you want. I hope this helps.
Regards
June 28, 2006 at 12:37 pm
Hi Chandrasekhar,
Are these instructions for IIS 5.0 or 6.0? We are using 5.0 and I don't see an Application Pools folder under IIS not a DefaultAppPool folder.
Thanks again,
Pete .
Peter M. Florenzano
Database Administrator
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply