SRS not detected as running

Nach der Installation der Reporting Services Point Rolle (die laut srsrpsetup.log erfolgreich war) bin ich kürzlich auf folgenden Fehler im srsrp.log gestossen:

Reporting Services URL from Registry [http://<SCCM-Server>/ReportServer/ReportService2005.asmx] SMS_SRS_REPORTING_POINT 
The request failed with HTTP status 401: Unauthorized. SMS_SRS_REPORTING_POINT 
(!) SRS not detected as running SMS_SRS_REPORTING_POINT 
Failures reported during periodic health check by the SRS Server <SCCM-Server>. SMS_SRS_REPORTING_POINT 
Waiting for changes for 1 minutes SMS_SRS_REPORTING_POINT

Der Dienst „SQL Server Reporting Services (MSSQLSERVER)“ war aber gestartet:

 

Ebenso konnten die URLs http://<Server>/Reports und http://<Server>/ReportServer problemlos geöffnet werden. Selbes galt für oben stehende URL.

Bei der weiteren Fehlersuche ist mir aufgefallen, dass die Product Version der Reporting Services nicht die aktuell supportete ist (SQL 2008 R2 + SP1 + CU6):

Lösung: erneute Installation von SP1 und CU6 für SP1. Zu dieser Konstellation kann es kommen, wenn die SQL Reporting Services nach Installation von SP1 und CU6 installiert werden.

Kurz danach waren auch die Fehler im srsrp.log verschwunden:

Reporting Services URL from Registry [http://<SCCM-Server>/ReportServer/ReportService2005.asmx] SMS_SRS_REPORTING_POINT 
Reporting Services is running SMS_SRS_REPORTING_POINT 
The DataSource does not exist. SMS_SRS_REPORTING_POINT 
Created folder [ConfigMgr_XYZ]. SMS_SRS_REPORTING_POINT 
Creating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_XYZ SMS_SRS_REPORTING_POINT 
Extracting resource language packs SMS_SRS_REPORTING_POINT 
Gathering resource files to deploy from directory [D:\SMS_SRSRP]. SMS_SRS_REPORTING_POINT

12 Gedanken zu „SRS not detected as running

  1. bloguri succes

    That is really fascinating, You are an overly professional blogger.
    I have joined your feed and look forward to searching for extra of your magnificent post.
    Additionally, I’ve shared your website in my social networks

  2. futuristic architecture

    Hello there, just became aware of your blog through Google,
    and found that it’s really informative. I’m going to watch out for brussels.
    I’ll appreciate if you continue this in future. A lot of people
    will be benefited from your writing. Cheers!

  3. sfaturi calculatoare

    Aw, this was an extremely good post. Spending some time
    and actual effort to generate a superb article… but what can I say…
    I procrastinate a whole lot and never manage to get
    anything done.

  4. forex news

    Some really great information, Glad I detected this. „I know God will not give me anything I can’t handle. I just wish that He didn’t trust me so much.“ by Mother Theresa.

  5. Torsten

    Just make sure that the latest SP/CU is applied after SRS is installed. Installing SRS afterwards will result in a non supported configuration resulting in the error described in the article.

  6. Mark Taylor

    Shame I don’t speak German, this looks like my solution but I can’t quite piece together from translators what you are doing to solve it.
    help?

  7. Lukas

    Hi,
    Danke für den Beitrag, war genau mein Problem !

    Gruß Lukas

  8. Manny

    Thanks for posting this. I’ve been trying to figure out this problem for a week now. As soon as I ran the reinstall of SP1, SCCM started deploying all the reports.

    Good thing I speak German, or I would still be searching.

    Thanks, Manny

  9. Pingback: Reproting Service Instanz kann nicht gefunden werden - MCSEboard.de MCSE Forum

  10. Canada99

    Hi
    I’ve actaully huge issues to get the reporting Service running. I’ve got the same error messages within srsrpsetup.log. We do have SP1 with CU6 installed but still have the same Errors. We do run the sccm2012 within a disjoined AD name space. Does anyboy has an help an thiss matter?

  11. An00p

    Just FYI. I’ve installed SP1 with CU6 and then installed SRS. But, I’ve the product version 10. 50.2811.0 in report server.

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert.