SQL 2012 SSRS problem with reporting service point in SCCM 2012 R2

This is using MS SCCM 2012 R2 server. MS SQL 2012 R2 was installed with components - Database engine services, reporting services - native, and management tools -complete. After that, in ConfigMgr console, I add-in the "reporting service point"; I then browse to Monitoring workspace > Reporting >reports, and found lots of reports.

But, the problem is, when I double-click any of the report (both from console and web site), the following error occurs:

An error has occurred during report processing. (rsProcessingAborted)
Cannot impersonate user for data source 'AutoGen__5C6358F2_4BB6_4a1b_A16E_8D96795D8602_'. (rsErrorImpersonatingUser)
Log on failed. Ensure the user name and password are correct. (rsLogonFailed)
The user name or password is incorrect

Please see the SSRS configuration as attached.

I can browse to report and reportserver websites, but not when attempt to browse any report.

Appreciate your help.
LVL 1
MichaelBalackAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MichaelBalackAuthor Commented:
Hi Vikas,

 I tried the both articles, but still doesn't work.
0
MichaelBalackAuthor Commented:
Hi Vikas,

At the end, I contact MS support, and eventually, they got the problem resolved.
0
MichaelBalackAuthor Commented:
Please see the activity summary report:

It was my pleasure to assist you during "Unable to run reports and getting error "Logon failed for the unattended execution account"  issue. I hope that you were happy with the service provided to you. I am providing you the summary with the key points of the case for your records. If you ever have any questions please feel free to call me.

ISSUE
=====

 Unable to run reports and getting error "Logon failed for the unattended execution account".

RESOLUTION
===========

  We tried running a report from SCCM console and got the following error:

System.Web.Services.Protocols.SoapException: The report server has encountered a configuration error. Logon failed for the unattended execution account. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. Logon failed for the unattended execution account. ---> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Log on failed. Ensure the user name and password are correct. ---> System.ComponentModel.Win32Exception: The user name or password is incorrect  at Microsoft.ReportingServices.Library.ReportingService2005Impl.GetReportParameters(String Report, String HistoryID, Boolean ForRendering, ParameterValue[] Values, DataSourceCredentials[] Credentials, ParameterInfoCollection& Parameters)  at Microsoft.ReportingServices.WebServer.ReportingService2005.GetReportParameters(String Report, String HistoryID, Boolean ForRendering, ParameterValue[] Values, DataSourceCredentials[] Credentials, ReportParameter[]& Parameters)
Microsoft.ConfigurationManagement.ManagementProvider.SmsException
The report server has encountered a configuration error. Logon failed for the unattended execution account.

  We connected to WBemtest
  Ran the query - Select * from sms_sci_sysresuse where rolename="SMS SRS Reporting Point"
  Changed the value of "EnableRBACReporting property" from 1 to 0
 Restarted SMS Exec and tried to run the report
 Found that from the SCCM console the error has changed now.

An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'ID5C6358F24BB64a1bA16E8D96795D8602'. (rsErrorOpeningConnection)
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider:

 Checked the  “ConfigMgr SQL Server Identification Certificate” was a self-signed certificate and it was showing as not trusted.
 Added the certificate to the trusted root store.
 Now we were able to run the report successfully.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MichaelBalackAuthor Commented:
By following the instructions, problem resolved by MS Support.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SSRS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.