Im getting the following errors when SCOM 2012 reporting fails & roll back. I dont have proxy settings enabled in IE and SQL agent service is set to 'Automatic'! Anyone can help? I can upload the entire reporting.log if its needed

[02:06:44]: Error: :Application Monitoring reports publishing failed.: Threw Exception.Type: System.Net.WebException, Exception Error Code: 080131509, Exception.Message: The request failed with HTTP status 401: Unauthorized.
[02:06:44]: Error: :StackTrace:   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
[02:06:44]: Error: :Error:Publishing App Diagnostics Reports failed.
[02:06:44]: Error: :FATAL ACTION: ConfigureReportingForInstall
[02:06:44]: Error:: ProcessInstalls: Running the PostProcessDelegate returned false.
[02:06:44]: Always: :SetErrorType: Setting NonVitalFailure. currentInstallItem: Reporting Server
[02:06:44]: Error:: ProcessInstalls: Running the PostProcessDelegate for OMREPORTING failed. but this item is not fatal so we will process the other items.

Hi

Please check here:

How to Install the Operations Manager Reporting Server

http://technet.microsoft.com/en-us/library/hh298611

Here you will find "To verify that Reporting Services is configured correctly"

I did ensure that "Reporting Services is configured properly" and that http://localhost/Reports and http://localhost/ReportServer as well works fine. I could create a folder in the reports page. I'll just brief the environment...2 Management Servers, Ops & DW DBs are on remote servers (both on SQL Named instances). I'm trying to install this reporting component on Ops DB server's default RS instance. This shouldn't be an issue - right?

Hi,

Which account do you use? Please be sure that you use the same account to install Reporting Services as you installed SCOM 2012 or an account with at least the same permissions on the SQL Server and SCOM server. 

Operations Manager Accounts

http://technet.microsoft.com/en-us/library/hh212808.aspx

The account that is used to install SCOM Reporting has enough permissions and so I dont think its an issue with the account!

Ramesh,

Did you try to browse to the sites with the same account you are using for the setup?

also, to confirm account settings, you may want to check http://blogs.technet.com/b/kevinholman/archive/2008/04/15/opsmgr-security-account-rights-mapping-what-accounts-need-what-privileges.aspx

Please let me know if you have any question.

Thanks

Jose

• Edited by José Rodas Wednesday, September 19, 2012 5:33 AM

Hi, Can you upload the log file somewhere? I suppose you explore OpsMgrSetupWizard.log ? Very interesting!

Alexis,

rameshmo has shared the file OM12ReportingFailed.zip with you. To download the file, click the link below:

https://dav-sth-se.diino.com/shared2/e231ed769641ef935b53be48aee5bcf3526b5409/OM12ReportingFailed.zip
<o:p></o:p>

This link will expire after 7 days or 10 uses

Hi, I checked logs, yes ambiguous error, I'd try to find sollutions with "The request failed with HTTP status 401: Unauthorized." such as DisableLoopbackCheck... like http://social.msdn.microsoft.com/Forums/sv/sqlreportingservices/thread/79f47849-4a8c-4dfa-9344-ebd1ce88af2a did you try?

and did you try to completely uninstall reporting services..including registry entries.. and start again? 

Tried reinstalling reporting services, though setup moved little ahead publishing few more Application Monitoring reports, it failed again with same error after ApplicationStatusEventStatisticsSubreport is published. Please see the error part of the log:

[06:54:26]:           Always:                :Publish Advisor reports: Report ApplicationStatusEventStatisticsSubreport is published

[06:56:41]:           Error:     :Application Monitoring reports publishing failed.: Threw Exception.Type: System.Net.WebException, Exception Error Code: 0x80131509, Exception.Message: The request failed with HTTP status 401: Unauthorized.

[06:56:41]:           Error:     :StackTrace:   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)

   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

   at Microsoft.Reporting.Setup.ReportService.ReportingService2005.FindItems(String Folder, BooleanOperatorEnum BooleanOperator, SearchCondition[] Conditions)

   at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportServices.ApplicationDiagnostics.ReportManager.FindItem(String name, String path, ItemTypeEnum itemType)

   at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportServices.ApplicationDiagnostics.ReportManager.PublishReport(FileInfo reportFile, String parent)

   at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportServices.ApplicationDiagnostics.ReportManager.PublishReports(DirectoryParameter directoryParam)

   at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportServices.ApplicationDiagnostics.ReportManager.RunActionForDirectory(Predicate`1 action, DirectoryInfo directory, String currentPath)

   at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportServices.ApplicationDiagnostics.ReportManager.RunActionForDirectory(Predicate`1 action, DirectoryInfo directory, String currentPath)

   at Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.OMReportingProcessor.PublishAppDiagnosticsReports()

[06:56:41]:           Error:     :Error:Publishing App Diagnostics Reports failed.

[06:56:41]:           Error:     :FATAL ACTION: ConfigureReportingForInstall

[06:56:41]:           Error:     :ProcessInstalls: Running the PostProcessDelegate returned false.

[06:56:41]:           Always:                :SetErrorType: Setting NonVitalFailure. currentInstallItem: Reporting Server

[06:56:41]:           Error:     :ProcessInstalls: Running the PostProcessDelegate for OMREPORTING failed.... but this item is not fatal so we will process the other items.

Hi, by reinstalling reporting services do you mean removal and installation SSRS like described in the article below?  usually it helps

article thoughtsonopsmgr.blogspot.com/2012/09/how-to-repair-ssrs-when-resetsrsexe.html

did you try to install reporting server on another dedicated sql seporting services ? same errors?

• Marked as answer by Alex ZhaozxMicrosoft contingent staff, Moderator Tuesday, October 02, 2012 7:33 AM

Yes I did that way, but there was no luck. So I installed SQL & reporting on one of the MS and was able to install reporting successfully. Thanks for all your help and responses!

Hi,

I had the same error. The fix for me was to:
uninstall SRS

remove the DB's

REBOOT

Do a re-install of SRS

manually configure using SRS Manager

Re-install the SCOM reporting feature

1: Uninstall and reinstall SSRS
2: When SCOM 2012 change the SQL Reporting Service 2012 configuration files, it takes the backup of the Reporting Services configuration files as: RSReportServer.config.0 and RSReportServer.config.1.

i) So, go to C:\Program Files\Microsoft SQL Server\MSRSXX.MSSQLSERVER\Reporting Services\ReportServer.

ii) Then remove the file RSReportServer.config. And rename RSReportServer.config.0 to  RSReportServer.config

-------------------------------------------------------------

G.R.V

Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.