Recently I had to change the password for our administrative SCCM account which was also used to run reports on a remote SQL database. Since the change however I receive an error stating that reporting services cannot impersonate the user. Full error message listed below from the SCCM side.
Microsoft.Reporting.WinForms.ReportServerException
An error has occurred during report processing. (rsProcessingAborted)
Stack Trace:
at Microsoft.Reporting.WinForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension)
at Microsoft.Reporting.WinForms.ServerReport.InternalRender(Boolean isAbortable, String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension)
at Microsoft.Reporting.WinForms.AsyncMainStreamRenderingOperation.RenderServerReport(ServerReport report)
at Microsoft.Reporting.WinForms.AsyncRenderingOperation.PerformOperation()
at Microsoft.Reporting.WinForms.ReportViewer.AsyncReportOperationWrapper.PerformOperation()
at Microsoft.Reporting.WinForms.ProcessingThread.ProcessThreadMain(Object arg)
-------------------------------
Microsoft.Reporting.WinForms.ReportServerException
Cannot impersonate user for data source 'AutoGen__5C6358F2_4BB6_4a1b_A16E_8D96795D8602_'. (rsErrorImpersonatingUser)
Stack Trace:
at Microsoft.Reporting.WinForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension)
at Microsoft.Reporting.WinForms.ServerReport.InternalRender(Boolean isAbortable, String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension)
at Microsoft.Reporting.WinForms.AsyncMainStreamRenderingOperation.RenderServerReport(ServerReport report)
at Microsoft.Reporting.WinForms.AsyncRenderingOperation.PerformOperation()
at Microsoft.Reporting.WinForms.ReportViewer.AsyncReportOperationWrapper.PerformOperation()
at Microsoft.Reporting.WinForms.ProcessingThread.ProcessThreadMain(Object arg)
-------------------------------
Microsoft.Reporting.WinForms.ReportServerException
Log on failed. Ensure the user name and password are correct. (rsLogonFailed)
Stack Trace:
at Microsoft.Reporting.WinForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension)
at Microsoft.Reporting.WinForms.ServerReport.InternalRender(Boolean isAbortable, String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension)
at Microsoft.Reporting.WinForms.AsyncMainStreamRenderingOperation.RenderServerReport(ServerReport report)
at Microsoft.Reporting.WinForms.AsyncRenderingOperation.PerformOperation()
at Microsoft.Reporting.WinForms.ReportViewer.AsyncReportOperationWrapper.PerformOperation()
at Microsoft.Reporting.WinForms.ProcessingThread.ProcessThreadMain(Object arg)
-------------------------------
Microsoft.Reporting.WinForms.ReportServerException
For more information about this error navigate to the report server on the local server machine, or enable remote errors
Stack Trace:
at Microsoft.Reporting.WinForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension)
at Microsoft.Reporting.WinForms.ServerReport.InternalRender(Boolean isAbortable, String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension)
Now I have looked through the forums to find similar issues to the one I am having and have attempted the solutions. However, it appears to be changing the password on the SQL side back to something else even after I go in and tell it what the new password is. I hit 'Test Connection' and it gives me the green 'Connection created successfully'. Then I hit apply and all seems well. I can run a report in Report Manager but the second I attempt to run from SCCM it reverts back to some other password and fails. This results in the error message above. I have made sure that the password is correct across the board and even made sure to change it again in AD just in case I mistyped the first time.
Now within Report Manager I have changed it as well. When it tries to connect it gives the option to enter and save the new credentials. Which I have done and that doesn't seem to work either. When I go to manage the data source and change the credentials I select the 'Impersonate the authenticated user after a connection has been made to the data source'. For me it just seems that something else is telling the data source to revert back to a different password but I can't for the life of me figure out where. Someone please help!