I have the task of tracking down and determining why a server running SQL Server 2005 and SSRS is creating hundreds of SQLDmpr {sequential number}.mdmp, SQLDmpr {sequential number}.log, SQLDmpr {sequential number}.mft files. These files are listed in the SQLDUMPER_LOG.log file along with other information.
Besides, you should also check the Email settings properties in Reporting Services Configuration Manager. For more information, please refer to this article: Configure a Report Server for E-Mail Delivery (SSRS Configuration Manager).
According to your description, you cannot connect report server via SSMS after you migrate your SQL Server from SQL Server 2008 to 2012. Right? In your scenario, before the migration, can you connect Report Server on that SQL 2012 instance successfully? You just need to specify servername\instance name to connect in SSMS.
If using the reporting service 2005 web service just to call the path of the items, why does it care if there's generic parameters? Ultimately my goal is to have the treeview populated and allow clickthrough to a report viewer control that will load whatever report the user selects from the treeview. Any hints or code samples would be appreciated.
I am passing a string back from reporting services into a function in SQL 2005. If a single selection is passed back it works but a multiple select fails to return a result. If I manually type the values in example 'where x in ('testa','test2','test3')' it works.
The report server cannot open a connection to the report server database. The logon failed. (rsReportServerDatabaseLogonFailed) Get Online Help Logon failure: unknown user name or bad password.
In Reporting Services (SSRS 2008), there are white spaces preserved in the report body by default. When the white space extends the body size beyond the width of the report, blank pages will be generated. To avoid the issue, you can set the “ ConsumeContainerWhiteSpace ” property of the report to “True”.
Microsoft.Reporting.WebForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection+SoapVersionMismatchException: Remote report processing requires Microsoft SQL Server 2008 Reporting Services or later. I am using vs2010, sqlsever 2005.
Then the query used the variables rather than the parameters. This caused the query to perform consistently whether called from SQL Server Manager or through the SSRS report. Another possibility is that using linked server or openquery in your stored procedure , they may run quickly by themselves but take a long time to render in SSRS.
