Hi all, do you like Microsoft SQL Server 2000 Reporting Services? I like RS much, I can say I love it.
If you like to use SQL Server 2000 Reporting Services in your applications as a report server I believe you also like the new version with the SQL Server 2005. Although I'm very keen on migrating to the newest application versions, as a nature of our job - I mean the software development - I'm still working with RS 2000 on my main applications.
For some small applications, I'm using Reporting Services 2005 in test environments.
So enough for a short entry :) Ok, now I'm on my first post's topic. I was installing Reporting Services 2005 on a web farm. By the way, I must say that the new Reporting Services Configuration tool is great and makes tasks easier for managing configurations especially for installation on web farms. Some tasks are requires working on the .config files, you know on RS2000. Again a small note here, I'm planning to prepare a short article on how configurations are done for reporting services 2005 running on more than one web servers sharing one ReportServer database. Ok, on the web servers making up the web farm, there also were running SQL Server 2000 Reporting Services applications as well as some ASP.NET web applications of .Net Framework 1.1
After the Reporting Services 2005 installations and configurations are completed on the web farm servers, new reporting services 2005 virtual directories were working successfully. But unfortunately, on one of the servers Reporting Services 2000 sites were down as well as ASP.NET applications.
The error is displayed as the awesome error message : Server Application Unavailable
I hate this error message.
Later, while lost among the virtual directories and application pools, I realized that Reporting Services 2000 and Reporting Services 2005 were sharing the same application pool. At a glance, I thought .Net Framework 1.1 and 2.0 applications may not be sharing the same application pool. But on other server, Reporting Services 2005 and ASP.NET 1.1 web applications were running without a problem.
So my conclusion, Reporting Services 2005 may work within same application pool with any other application then the Reporting Services 2000. If you have similar problems, please make sure that the application pools they are running are different. Control the ReportServer and Reports virtual directories of both Reporting Services versions for application pools.
After configuring the application pools, the Server Application Unavailable problem is now solved on the server. Everyone works successfully. Delighted :)