Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Log on failed. Ensure the user name and password are correct.

[sysadmin101]

Hi,

 

I updated SCCM to CB and now face this error (well it might have been there even before then just that I didn't notice since I hardly used reports).

 

Whenever I try to run a report, I run into this error about incorrect credentials (although the credentials were definitely input correctly during setup/installation).

*It is definitely seen as a 'wrong password' because AD logs it as failed logon attempt under the account

 

An error has occurred during report processing. ---> Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot impersonate user for data source 'AutoGen__5C6358F2_4BB6_4a1b_A16E_8D96795D8602_'. ---> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Log on failed. Ensure the user name and password are correct. ---> System.Exception: For more information about this error navigate to the report server on the local server machine, or enable remote errors

-------------------------------
Microsoft.ConfigurationManagement.ManagementProvider.SmsException
An error has occurred during report processing.


Stack Trace:
at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ParameterPresenter.GetParameters()
at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ParameterPresenter.LoadParameters(IReport report, Collection`1 navigationParameters, IResultObject resultObject)
at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ReportViewerPresenter.Worker_DoWork(Object sender, DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

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

System.Web.Services.Protocols.SoapException
An error has occurred during report processing. ---> Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot impersonate user for data source 'AutoGen__45C6358F2_4BB6_4a1b_A16E_8D96795D8602_'. ---> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Log on failed. Ensure the user name and password are correct. ---> System.Exception: For more information about this error navigate to the report server on the local server machine, or enable remote errors


Stack Trace:
at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ParameterPresenter.GetParameters()
at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ParameterPresenter.LoadParameters(IReport report, Collection`1 navigationParameters, IResultObject resultObject)
at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ReportViewerPresenter.Worker_DoWork(Object sender, DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

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

 

 

I tried updating the Reporting Services Point Account (under the Reporting Services Point role) but it doesn't help.

 

The only workaround that I found is to go to the Report Manager (i.e. http://url_of_ssrs_servrer/Reports_sccm_DB_name)

 

Then go to the Data Source

 

If I click 'Test Connection', it immediately prompts me: Log on failed. Ensure the user name and password are correct.

 

However, if I re-enter the password, and click 'Test Connect' (repeatedly) it works fine.

If I click 'Apply' now, and quickly run a report, it works!

 

But few seconds later, the reports fail to run again with the same error above.

It's as if something is trying to override the credentials I keyed in - and it overrides using wrong credentials?

 

if I refresh the Report Manager and try to 'Test Connection' now again, it again prompts me Log on failed.

And I need to re-apply the workaround each and every time I want to run a report.

 

Any ideas how do I fix this?