Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED An error has occurred during report processing. SCCM 2111

Messages
14
Reaction score
0
Points
1
Hi Prajwal,
i'm configure new SCCM 2111, i'm using different Server for SQL DB, after completing all configuration, when i'm try to run any report that time facing below error:

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 'DataSource1'. ---> 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 'DataSource1'. ---> 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)

-------------------------------
 
Cannot impersonate user for data source 'DataSource1'. ---> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Log on failed. Ensure the user name and password are correct. ---> System.Exception:

Like @Garth mentioned, check the username and password.
 
Cannot impersonate user for data source 'DataSource1'. ---> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Log on failed. Ensure the user name and password are correct. ---> System.Exception:

Like @Garth mentioned, check the username and password.
Hi Prajwal,
Thanks for reply as i observed issue occurred due to SCCMADMIN account locked out after unlock it report run successfully.
but can you guide me why sccmadmin account locked out frequently and unlock automatically.
 
Account lockouts are common. An account can lock out due to many reasons and you also need to check the defined account lockout policy via GPO.
An account gets locked when it is used to login with wrong password. So what you can do is trace the lockouts and see from what machine are they originating. There are some third-party tools available for that. Hope I have answered your question.
 
Back
Top