I am having problem with SCCM reports on my UAT enviroment, on my production it works fine.
When I go into Monitoring > Reporting > Reports - On all the reports I get an error message:
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__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
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)
Check out your Accounts which your using for the reports. It seems that the user or Password is not correct. Also check your Reporting User Service Accounts
Check your user accounts and your runas user accounts
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
0
Kelly GarciaSenior Systems AdministratorAuthor Commented:
I am logged in using an administrators account, I am in the SCCM-Admin group on AD, where are the group configurations on AD?
0
Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.
Check out the reporting Service configuration...maybe some screenhots
0
Kelly GarciaSenior Systems AdministratorAuthor Commented:
I was thinking of running reg compare with my production environment as it is the same setup, any one know what hives the registry configs are for sccm 2012?
0
Kelly GarciaSenior Systems AdministratorAuthor Commented:
sorted ! the service account was not part of the sql admin group!
0
Kelly GarciaSenior Systems AdministratorAuthor Commented:
I've requested that this question be closed as follows:
Accepted answer: 0 points for kay07949's comment #a39894906
for the following reason:
The service account was not part of the SQL admin group
0
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Managing Active Directory does not always have to be complicated. If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why