Friday, December 19, 2008

SCOM Reporting, Installation issues. Posting 1, error ‘Server Error in '/Reports' Application.’

SCOM without Reporting installed is using SCOM at is best at 50% of it capacity and benefits
That having said, making SCOM Reporting work can be a bit of a challenge. One can bump into all kinds of errors. My personal experience though is that 80% of these errors are directly related to SQL Reporting Services (SRS) or IIS. So one has to test the correct workings of SRS first before one starts installing SCOM Reporting.

With this posting - and others which will come later - I will talk about the most common errors one can bump into when testing SRS, and how to resolve these. So this posting - and the others to come - presume SRS is already installed AND configured.

Some errors are easy to fix, others can be puzzles on themselves. This one explained here is an easy one to fix.

The most common way to test SRS is to go to the website of SRS on the local server hosting the SRS services AND website. This latter is important since this server hosts the website with the SRS components.

When one tries to open the SRS website (http://localhost/reports) one can bump into this error:

Wow! There is not only an errorstatement but it is an understandable one as well. How neat! One doesn't need to be a rocketscientist to know what goes wrong: authorizations are at matter here.

All one has to do is to adjust the permissions on this folder in such a manner that the group ‘Users( \Users)’ has write permissions on that folder. All will fine afterwards.

No comments: