SQL Server Q&A

Symptoms
When you try to perform a one-phase commit on an XA-, or two phase-, enabled JDBC connection in Microsoft SQL Server 2005, the following exception occurs:

Exception in thread “main” com.microsoft.sqlserver.jdbc.SQLServerException: The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
at com.microsoft.sqlserver.jdbc.IOBuffer.processPackets(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectionCommand(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendCommit(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.commit(Unknown Source)
Resolution
This problem occurs because SQL Server 2005 does not allow a one-phase commit on a two-phase-enabled data source.

Symptoms
When creating a new SQL Server Data Source Name (DSN) using the ODBC API SQLConfigDataSource function, a network library must be specified. If the network library name is in lowercase letters, the Client Configuration dialog box may show it as “Other”.
Resolution
In Control Panel, the Client Configuration dialog box in ODBC Data Source Administrator is case-sensitive. It compares the network library name from the registry to uppercase network library names. See the “More Information” section for information on the registry entries that are affected by SQLConfigDataSource.

Symptoms
You run Report Manager in Microsoft SQL Server 2008. When you try to use Microsoft SQL Server Analysis Services as a data source for a data-driven subscription, you receive the following error message:

The dataset cannot be generated. An error occurred while connecting to a data source, or the query is not valid for the data source. (rsCannotPrepareQuery) Get Online Help The type initializer for ‘module’ threw an exception.The C++ module failed to load while attempting to initialize the default appdomain.Access is denied. (Exception from HRESULT: 0×80070005 (E_ACCESSDENIED))
Resolution
This problem occurs if SQL Server Analysis Services is not installed in the location that is expected by the SQL Server Reporting Services service.