Thursday, January 31, 2008

SQL Server 2005 Reporting Services Configuration

This post talks about SQL Server 2005 Reporting services configuration across multiple servers.

Specifically in my configurations, I use x64 Machines so this adds snags to the setup because IIS can only run in 32bit or 64bit mode.

If you are running in 32bit mode, you will have to re-register your IIS server in the 32 bit .NET framework directory and run the command aspnet_regiis -i to install the 32bit on IIS.

Don't run any 32bit sites along side your 64bit reporting services, keep them seperate or you'll have a nice big headache with setup.

Of course the way I like to configure servers, I always prefer to have logical seperations for all my server applications, that way if anything fails, it is isolated and easier to trouble shoot and fix. However, this seperation comes with a cost since there is an increased level of complexity.

I never install my reporting services server on the same machine as my SQL Server box, always on a seperate machine. With this, you will need to configure a form of delagation to pass authentication requests from the reporting services machine to the SQL Server machine. The following are the most common and time consuming errors to troubleshoot and fix that I have experience with Reporting Services setup.

With the Reporting server setup on a seperate server, you will probably confront the "rsAccessDenied" error since this is what happens unless your permissions are configured correctly.

Some good links for the resolution of this issue

If you get the "The ReportServerVirtualDirectory element is missing" error check your RSWebApplication.config file.

If you get the error message: The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version.

No comments: