System Center Operations Manager by Jonathan Hambrook

May 10, 2007

SRS Server Validation Error

Filed under: Errors, Microsoft, SCOM 2007 — opsmgr @ 10:12 pm

If you receive the error: SRS Server Validation Error while installing SCOM Reporting, dont forget you need to Configure Reporting Server first.

To do this you need to go START -> All Programs -> Microsoft SQL Server 2005 -> Configuration Tools -> Reporing Services Configuration. Then on each of the Items that have a Red X or Yellow ! select them and configure them accordingly.

If you see any grey items this means that they cant be validated and even though you have configured another item it could be incorrect. The most common is the Initialisation option, if this is grey then you probably authentication.

Advertisements

16 Comments »

  1. please can i have more informations about this steps…I have this problem…and i don´t found the solution…
    ciao ciao

    Comment by zied21 — May 17, 2007 @ 12:39 am

  2. I am assuming that when you are installing SCOM Reporting that you recieve this error and even though you have setup SQL Reporting 100% the Validation is failing.

    As for a fix for this, I am working on this more as I have been able to replicate this. In this configuration I have the Data Warehouse database on a different server than where I have SQL Reporting.

    I am talking with Microsoft and we are perfoming a heap of checks and debugs to figure this out. So far it looks like a permission error. Keep you eye out as I will post a fix as soon as I get it working.

    Comment by opsmgr — May 17, 2007 @ 12:00 pm

  3. Hi Jonathan,
    just for your info: Same Error hereover in Germany on several SQL Servers… looks like an issues regarding SQL SP2… couldn`t fix it so far…

    Do you have any further info for this issue?!

    Regards, Guido

    Comment by Guido — May 18, 2007 @ 9:05 pm

  4. So far here is what I’ve found

    Reporting website used to have SSL but was removed because of Reporting Unable to get certificate errors. Certificate was self signed and not trusted.
    SRS error received and logs indicate that the SCOM 2007 Reporting is trying to install to HTTPS still.
    Reinstalled self signed certificate for Reporting website and added to trusted roots. Resolved the SRS error

    Comment by MarkH — May 19, 2007 @ 1:40 am

  5. Guido, I would agree that its an SP2 issue. I am working MS on this one and we will see what happens. Unfortunatly I am going on hoiday soon for a couple of weeks which could put this solution a little behind.

    MarkH, thanks for that as I have not yet used SSL with SCOM Reporting as the businesses I am working with dont regard the data as confidetion but im sure they will change there mind once they see the SLA’s especialy when Distributed Application monitoring is 100% setup and being reported on.

    Comment by opsmgr — May 21, 2007 @ 3:43 pm

  6. It’s a hack and I’m not sure how it’s going to work out. But I had the same SRS error. The work around was to add my account to the SQLServerDTSUser$ account and then attempt to install.

    Comment by erik — June 6, 2007 @ 4:58 am

  7. My issue went away after I cleared the SSL port number from the Default Web Site Properties, as a cert had never been setup for that machine.

    Comment by Terry G Phillips — July 1, 2007 @ 1:44 pm

  8. From what I read an hear about this issue its always an issue with IIS/Web component. The more I read and hear the more I feel some more logging need to be added to this section of the installation process.

    Thanks for the comment.

    Comment by opsmgr — July 3, 2007 @ 1:36 am

  9. I’ve fix this probleme ! Give all right to nt authority\network to c:\windows\microsoft.net\framework !

    Comment by Nicolas M — August 21, 2007 @ 6:27 pm

  10. Has anyone found a real solution to this ? I have SQL 2005 SP1 installed and I get the “SRS Validation Error” during the Reporting Server install.

    I went to START -> All Programs -> Microsoft SQL Server 2005 -> Configuration Tools -> Reporing Services Configuration. And I have all green check marks except the Initialization option is grey.

    I went to the website at http://servername/Reports and screen says Service Unavailable. But everything in IIS seems to be fine.

    If there is a workaround, I would love to here it.

    And by the way, there is no “MOMReporting.log” generated anywhere on my server. Weird ! Anyone have a clue why ?

    Comment by hitesh — September 1, 2007 @ 2:12 am

  11. Hi

    Very interesting site. Hope it will always be alive!

    Bye

    Comment by likopinko — September 11, 2007 @ 12:34 pm

  12. Hi!

    Great!! I had been struggling with this error for quite a while and couldn’t find anything that pointed me in the right direction.
    I changed permission on the framework folder for this network account and installation wnt through like a charm. Removing SSL port in IIS and restart default web site didn’t help.
    I waited for the installation to be finished and now have a reporting button in the operations console. There are no reports listed yet but this might be another issue.

    Comment by Ingrid — September 11, 2007 @ 9:50 pm

  13. This is a great discussion, and I’d really like to use the solution of adding the nt authority\network account to my framework folder. However, I can’t seem to add the nt authority\network account. When I go to add it to the security on that folder, I can add an account just called “Network” or “Network Service” (which I have done, but it doesn’t help), but not “NT Authority\Network”. Is this the same account, and the fix just doesn’t work in my situation, or is there really a separate “nt authority\network” account, and if so, how do I add it? Thanks.

    Comment by Michael Yaeger — September 21, 2007 @ 1:21 am

  14. I had this problem too. I went onto the reporting server. Opened the IIS management tool and expanded default web. Then I right clicked on reports subweb. then clicked on permissions. Then I added the local server account asp.net in with full permissions. Then I did the same for ReportServer

    Comment by Wendy Johnson — November 3, 2007 @ 12:11 am

  15. I had the same error. Everything was good in reporting services except initialization was ticked and grey (using std not ent so it is not available).

    Removed my proxy settings in IE and it all worked. Our proxy settings are forced by Group Policy.

    Comment by Derek Vanderkruk — November 5, 2007 @ 11:01 am

  16. I’ve figured it out (also)! On a x64 platform, SP2 messed up the report configuration, and none of the above were working for me.

    I deleted all reporting sites from IIS, and resubmitted the default configurations in the Reporting Services Configuration Manager, then tried to install SCOM Reporting, and everything worked fine!

    Comment by Dustin — December 11, 2007 @ 9:08 am


RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Blog at WordPress.com.

%d bloggers like this: