I'm seeing a lot of problems running reports in SCE. Does not matter which report, as any I've tried to run generate some sort of error 98% of the time. The usual error I get is"An internal error occurred on the report server. See the error log for more details."A few times now today, I'm getting a different error:System.InvalidOperationException: Some parameters or credentials have not been specified at Microsoft.Reporting.WinForms.ServerReport.GetDocumentMap(String rootLabel) at Microsoft.Reporting.WinForms.Report.GetDocumentMap() at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ReportForm.OnRenderingCompleteJob(Object sender, ConsoleJobEventArgs args)Any help would be appreciated. Thanks!J.MichaelEdit 4/10/09:In doing some further research, another posting in the SCE Monitoring forum linked to KB946082 (http://support.microsoft.com/kb/946082). The error log generated when I run a report looks like the one in the KB, however when I query the SQL server, it's returning v9.00.4035.00 - SQL Server 2005 Express Edition with Advanced Services, SP3.

Hi Michael,Please installl SQL 2005 Cumulative update 5 which applied to SQL express edition:http://support.microsoft.com/kb/943656#appliesto

Hi Eric,The SQL 2005 CU5 that you directed me to will not install because the SCE server is already running SQL Express SP3. Is there another update available for post-SP2 installs?J.Michael

Hi,Please reconfigure SRS with default settings, restart OpsMgr services.Also, please do not forget to verify the Data Warehouse Run As Profiles settings, they should be default and configured properly.Related Links: http://support.microsoft.com/kb/945946

Hi Eric,As far as I can tell, everything is configured with the default settings. I restarted the OpsMgr services, but am still running into the same problem. I can run a report or two, but then another action will cause it to error out again.J.Michael

Hi Michael,Please try the following stepsto reset reportingng in SCE:1. Open up the Reports site (probably <http://localhost/Reports$SCE>) . 2. Click New Data Source3. Enter the following:a. Name: WSUS Databaseb. Check both Hide in list view and Enable this data sourcec. Connection Type: Microsoft SQL Serverd. Connection string: data source=[servername]\[instancename];initial catalog=SUSDB;Integrated Security=SSPI ([servername]\[instancename] is the database server the WSUS database is on. If this was originally an upgrade of WSUS, then the name may also be different from SUSDB)e. Choose Credentials are not requiredf. Click OK or Apply4. Click New Data Source5. Enter the following:a. Name: Data Warehouse Mainb. Check both Hide in list view and Enable this data sourcec. Connection Type: Microsoft SQL Serverd. Connection string: data source=[servername]\[instancename];;initial catalog=OperationsManagerDW;Integrated Security=SSPI(servername]\[instancename] is the database server SCE was installed on.)e. Choose Credentials are not requiredf. Click OK or Apply6. Wait about 10-20 minutes for Reports to deploy7. Make sure reports run in SCE Console

Eric,The existing information for both data sources was as it was in the post above. I went ahead and tried to recreate the data sources anyway, in case there was a problem that I wasn't seeing; however, after doing so (and waiting about 20minutes), trying to run any of the reports generates the error:Microsoft.Reporting.WinForms.ReportServerException: The report server cannot process the report. The data source connection information has been deleted. (rsInvalidDataSourceReference) at Microsoft.Reporting.WinForms.ServerReport.GetExecutionInfo() at Microsoft.Reporting.WinForms.ServerReport.GetParameters() at Microsoft.EnterpriseManagement.Mom.Internal.UI.Reporting.Parameters.ReportParameterBlock.Initialize(ServerReport serverReport) at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ReportForm.SetReportJob(Object sender, ConsoleJobEventArgs args)If I edit the settings of the report to use the newly created data sources, I get the following error:Microsoft.Reporting.WinForms.ReportServerException: An error has occurred during report processing. (rsProcessingAborted) ---> Microsoft.Reporting.WinForms.ReportServerException: Query execution failed for data set 'StatusList'. (rsErrorExecutingCommand) ---> Microsoft.Reporting.WinForms.ReportServerException: For more information about this error navigate to the report server on the local server machine, or enable remote errors --- End of inner exception stack trace --- --- End of inner exception stack trace --- at Microsoft.Reporting.WinForms.ServerReport.GetExecutionInfo() at Microsoft.Reporting.WinForms.ServerReport.GetParameters() at Microsoft.EnterpriseManagement.Mom.Internal.UI.Reporting.Parameters.ReportParameterBlock.Initialize(ServerReport serverReport) at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ReportForm.SetReportJob(Object sender, ConsoleJobEventArgs args)Microsoft.Reporting.WinForms.ReportServerException: Query execution failed for data set 'StatusList'. (rsErrorExecutingCommand) ---> Microsoft.Reporting.WinForms.ReportServerException: For more information about this error navigate to the report server on the local server machine, or enable remote errors --- End of inner exception stack trace ---Microsoft.Reporting.WinForms.ReportServerException: For more information about this error navigate to the report server on the local server machine, or enable remote errorsI'm not sure where to go from here.J.Michael

Hi,Pleae Open Reporting Services Configuration Console andin the Execution Account, updated the password for the <Account>. Also, check the following: 1. Open the registry edit, go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.2. Go through all the time zones. Find the all time zones to check if any time zone without TZI key in them.3. If so, please import a known good time zone registry key from another server or delete this time zone key if you don't use it.

Hi Eric,I updated the password in Reporting Services Configuration and checked that all time zones have the TZI key. Waited another 30min before trying to run any reports, but they still returned the same errors as in my post from yesterday.J.Michael