SQL Server Q&A

As a software engineer, I focus on .NET, especially asp.net, C#, WCF and so on, and I am also very interested in Search Engine Optimization.

Entries Tagged ‘Reporting’

The server that is running SQL Server 2008 Reporting Services stops responding when you use the “Asynchronous Processing = True” setting in the connection string property to generate a report

Symptoms
On server that is running Microsoft SQL Server 2008 Reporting Services, you generate a report from a custom data extension data source. To do this, you use the “Asynchronous Processing = True” setting in the connection string property.When you run the report, the report server stops responding.
Resolution
This issue occurs because the System.Data.SQLclient namespace does not support asynchronous processing in any hosted common language runtime (CLR) environment. Because Reporting Services hosts the CLR within the Reporting Services process, the asynchronous call always fails.
Note The System.Data.SQLclient namespace is the SQL Server .Net Data Provider.

Reporting Services Configuration Manager for SQL Server 2008 Reporting Services does not start when both SQL Server 2005 and SQL Server 2008 are installed on a computer

Symptoms
Consider the following scenario:Both Microsoft SQL Server 2005 Reporting Services and Microsoft SQL Server 2008 Reporting Services are installed on a computer.You start Reporting Services Configuration Manager by using SQL Server Configuration Manager.In this scenario, Reporting Services Configuration Manager for SQL Server 2005 Reporting Services starts instead of Reporting Services Configuration Manager for SQL Server 2008 Reporting Services. Additionally, the instances of both SQL Server 2005 and SQL Server 2008 appear in the Instance Name list.
Resolution
This issue occurs because SQL Server Configuration Manager uses the SQL Server 2005 registry key to obtain the executable path for Reporting Services Configuration Manager instead of using SQL Server 2008 registry key.

Error message when you start the SQL Server 2008 Reporting Services Configuration Manager: “Invalid namespace”

Symptoms
On a computer that is running Windows Vista, you install a default instance of Microsoft SQL Server 2005 Service Pack 2 or alater version of SQL Server 2005. On the same computer, you install a named instance of Microsoft SQL Server 2008. For example, you install an instance that is named “SQL2008.”
In this scenario, you may receive an error message that resembles the following when you start the SQL Server 2008 Reporting Services Configuration Manager:

No report servers were found. Details: Invalid namespace
Resolution
This problem occurs if the SQL Server 2008 Reporting Services Configuration Manager points to the SQL Server 2005 Reporting Services instance, and it cannot find the SQL Server 2008 instance.