Troubleshoot Server & Database Connexion Problems with Reporting Services

  • Article
  • ten minutes to read

Use this topic to troubleshoot problems that you feel when connecting to a report server. This topic likewise provides information well-nigh "Unexpected error" messages. For more information virtually data source configuration and configuring study server connectedness information, see Specify Credential and Connection Data for Report Data Sources and Configure a Report Server Database Connection (Written report Server Configuration Director).

Cannot create a connection to information source 'datasourcename'. (rsErrorOpeningConnection)

This is a generic error that occurs when the report server cannot open up a connection to an external data source that provides data to a report. This error appears with a 2nd error bulletin that indicates the underlying crusade. The following additional errors can appear with rsErrorOpeningConnection.

Login failed for user 'UserName'

The user does not accept permission to access the data source. If you are using a SQL Server database, verify that the user has a valid database user login. For more than information about how to create a database user or a SQL Server login, encounter Create a Database User and Create a SQL Server Login.

Login failed for user 'NT AUTHORITY\Bearding LOGON'

This error occurs when credentials are passed across multiple computer connections. If you are using Windows Authentication, and the Kerberos version 5 protocol is non enabled, this fault occurs when credentials are passed across more than one estimator connection. To work around this mistake, consider using stored credentials or prompted credentials. For more data near how to work effectually this issue, run into Specify Credential and Connection Information for Written report Information Sources.

An error has occurred while establishing a connection to the server.

When connecting to SQL Server, this failure may be caused by the fact that nether the default settings SQL Server does non allow remote connections. (provider: Named Pipes Provider, error: 40 - Could non open up a connection to SQL Server). This mistake is returned by the instance of the Database Engine that hosts the report server database. In nigh cases, this error occurs because the SQL Server service is stopped. Or, if y'all are using SQL Server Express with Advanced Services or a named instance, this fault will occur if the report server URL or connection string for the report server database is not correct. To work through these issues, exercise the post-obit:

  • Verify that the SQL Server (MSSQLSERVER) service is started. On the computer that hosts the instance of the Database Engine, click Start, click Administrative Tools, click Services, and scroll to SQL Server (MSSQLSERVER). If it is non started, correct-click the service, select Properties, in Startup Type select Automatic, click Utilize, click Showtime, and then click OK.
  • Verify that the report server URL and study server database connection cord is correct. If Reporting Services or the Database Engine was installed as a named instance, the default connection string that is created during Setup will include the instance name. For example, if you installed a default case of SQL Server Express with Avant-garde Services on a server named DEVSRV01, the web portal URL is DEVSRV01\Reports$SQLEXPRESS. Furthermore, the database server name in the connection string will resemble DEVSRV01\SQLEXPRESS. For more information nigh URLs and data source connectedness strings for SQL Server Limited, see Reporting Services in SQL Server Limited with Advanced Services. To verify the connection string for the study server database, starting time the Reporting Services Configuration tool and view the Database Setup page.

A connectedness cannot be made. Ensure that the server is running.

This error is returned by ADOMD.NET provider. There are several reasons why this error can occur. If you specified the server as "localhost", try specifying the server name instead. This error can also occur if memory cannot exist allocated to the new connection. For more than data, see Cognition Base Article 912017 - Mistake message when you connect to an instance of SQL Server 2005 Analysis Services:.

If the error also includes "No such host is known", information technology indicates that the Analysis Services server is non bachelor or is refusing the connexion. If the Analysis Services server is installed equally a named instance on a remote computer, you might have to run the SQL Server Browser service to go the port number used by that instance.

(Report Services Soap Proxy Source)

If you become this mistake during report model generation, and the additional data department includes "SQL Server does not exist or access denied", you might be encountering the following conditions:

  • The connexion string for the data source includes "localhost".
  • TCP/IP is disabled for the SQL Server service.

To resolve this error, you can either modify the connexion cord to use the server name or you tin enable TCP/IP for the service. Follow these steps to enable TCP/IP:

  1. First SQL Server Configuration Manager.
  2. Expand SQL Server Network Configuration.
  3. Select Protocols for MSSQLSERVER.
  4. Right-click TCP/IP, and select Enable.
  5. Select SQL Server Services.
  6. Correct-click SQL Server (MSSQLSERVER), and select Restart.

WMI fault when connecting to a written report server in Direction Studio

Past default, Management Studio uses the Reporting Services Windows Management Instrumentation (WMI) provider to establish a connection to the written report server. If the WMI provider is not installed correctly, you volition get the following fault when attempting to connect to the report server:

Cannot connect to <your server name>. The Reporting Services WMI provider is not installed or is misconfigured (Microsoft.SqlServer.Management.UI.RSClient).

To resolve this error, you should reinstall the software. For all other cases, as a temporary piece of work-effectually, you can connect to the report server through the SOAP endpoint:

  • In the Connect to Server dialog box in Direction Studio, in Server Proper name, blazon the report server URL. By default, information technology is https://<your server proper noun>/reportserver. Or if you are using SQL Server 2008 Express with Advanced Services, it is https://<your server proper name>/reportserver$sqlexpress.

To resolve the fault then that you lot tin connect using the WMI provider, you lot should run Setup to repair Reporting Services, or reinstall Reporting Services.

Connection error, where login failed due to unknown user proper name or bad password

An rsReportServerDatabaseLogonFailed error can occur if you are using a domain account for the connection from the report server to the report server database connection, and the password for the domain business relationship has been changed.

The total mistake text is: "The report server cannot open a connexion to the report server database. The logon failed (rsReportServerDatabaseLogonFailed). Logon failure: unknown user name or bad password."

If you reset the countersign, y'all must update the connection. For more than information, see Configure a Report Server Database Connection (Report Server Configuration Manager).

The written report server cannot open a connection to the study server database. (rsReportServerDatabaseUnavailable).

Total Message: The report server cannot open a connectedness to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable)
This error occurs when the report server cannot connect to the SQL Server relational database that provides internal storage to the server. The connexion to the written report server database is managed through the Reporting Services Configuration tool. Yous can run the tool, become to the Database Setup page, and correct the connection information. Using the tool to update connectedness information is a best exercise; the tool ensures that dependent settings are updated and that services are restarted. For more information, see Configure a Report Server Database Connection and Configure the Report Server Service Account.

This fault can also occur if the Database Engine instance that hosts the report server database is non configured for remote connections. Remote connection is enabled by default in some editions of SQL Server. To verify whether it is enabled on the SQL Server Database Engine case y'all are using, run the SQL Server Configuration Managing director tool. You lot must enable both TCP/IP and named pipes. A report server uses both protocols. For instructions on how to enable remote connections, see the section "How to Configure Remote Connections to the Report Server Database" in Configure a Report Server for Remote Assistants.

If the error includes the following additional text, the password expired on the account used to run the Database Engine case: "An fault has occurred while establishing a connectedness to the server. When connecting to SQL Server, this failure may be acquired past the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Server Network Interfaces, fault: 26 - Error Locating Server/Instance Specified)." To resolve this error, reset the password.

"RPC Server is non listening"

The Study Server service uses Remote Procedure Call (RPC) server for some operations. If you become the "RPC Server is not listening" error, verify that the Study Server service is running.

Unexpected error (General network error)

This error indicates a data source connection fault. You should check the connection cord, and verify that yous accept permission to access the data source. If you lot are using Windows Authentication to admission a data source, you must take permission to access the computer that hosts the data source.

When you have configured Reporting Services to integrate with a SharePoint product or applied science on Windows Vista or Windows Server 2008, you might receive the following error message when you try to grant access on the Grant Database Access page in SharePoint Key Administration: "A connection to the computer cannot be established."

This happens considering User Account Control (UAC) in Windows Vista and Windows Server 2008 requires explicit acceptance from an ambassador to drag and use the administrator token when performing tasks that require administrator permissions. In this example, however, the Windows SharePoint Services Administration service cannot be elevated to grant the Reporting Services service business relationship or accounts access to the SharePoint configuration and content databases.

In SQL Server 2008 Reporting Services, only the Report Server service account requires database access; in SQL Server 2005 Reporting Services SP2, both the Report Server Windows service business relationship and the Study Server Web service account require database admission. For more information well-nigh the Study Server service account in SQL Server 2008, see Service Business relationship (Reporting Services Configuration).

At that place are ii workarounds for this issue.

  1. In 1 workaround, you can temporarily turn off UAC and use SharePoint Central Administration to grant access.

Of import

Utilize caution if you turn off UAC to piece of work around this issue, and turn on UAC immediately afterward you grant database access in SharePoint Central Assistants. If you exercise not want to plow off UAC, apply the second workaround provided in this department. For information about UAC, see the Windows production documentation.
2. In the second workaround, yous tin can manually grant database access to the Reporting Services service account or accounts. Yous tin can use the post-obit procedure to grant access by calculation the Reporting Services service business relationship or accounts to the correct Windows group and database roles. This process applies to the Report Server service business relationship in SQL Server 2008 Reporting Services; if yous are running SQL Server 2005 Reporting Services, perform the procedure for the Study Server Windows service business relationship and the Report Server Web service account.

To manually grant database access

  1. Add the Written report Server service account to the WSS_WPG Windows grouping on the Reporting Services computer.
  2. Connect to the database instance that hosts the SharePoint configuration and content databases, and create a SQL database login for the Report Server service account.
  3. Add the SQL database login to the following database roles:
  • db_owner office in the WSS Content database
  • WSS_Content_Application_Pools role in the SharePoint_Config database

Unable to connect to the /reports and /reportserver directories when the report server databases are created on a virtual SQL Server that runs in a Microsoft Cluster Services (MSCS) cluster

When you lot create the report server databases, ReportServer and ReportServerTempDB, on a virtual SQL Server that runs in a MSCS cluster, the remote name in the format <domain>\<computer_name>$ might non be registered to SQL Server equally a login. If y'all have configured the Study Server service account every bit an account that requires this remote name for connections, users cannot connect to the /reports and /reportserver directories in Reporting Services. For example, the built-in Windows account NetworkService requires this remote name. To avoid this issue, use an explicit domain account or a SQL Server login to connect to the report server databases.

Run across Besides

Browser Support for Reporting Services and Ability View
Errors and events (Reporting Services)
Troubleshoot Data Retrieval bug with Reporting Services Reports
Troubleshoot Reporting Services Subscriptions and Delivery

Need help? Need help? Microsoft Q & A, Stackoverflow, SQL Server product feedback