Home > 09 Matrix42 internal > 98 Article Depot > Errors in the SQL configuration manager for reporting services

Errors in the SQL configuration manager for reporting services

 

26 Jul 2017Last updated
0votes
4updates
20views
Written by Jürgen Markart (Customer Service)
2nd Level Support Engineer

Overview

On setting up the Microsoft Reporting Services via the 'SQL Konfiguration-Manager für Reporting Services' some errors can occur which are described and solved.

 


Problem

When an attempt is made to connect the reporting configuration manager with the reporting server instance, the following message is displayed:

RPC server could not be reached.

Solution

This problem can be solved by switching off the proxy or by entering the address in the proxy.


Problem

The following message is displayed when a report server database is being created in the Reporting Configuration Manager:

System.Data.SqlClient.SqlException: CREATE FILE encountered operating system error 5(Access is denied.) while attempting to open or create the physical file '….\ReportServer$EMPIRUM_log.ldf'.
CREATE DATABASE failed. Some file names listed could not be created. Check relatederrors.

Solution

The account used to run the SQL report server service must have full access to the specified database data directory.


Problem

The following message is displayed in the browser when the web service URL in the reporting configuration manager is launched:

Web site not found.

Solution

Port 80 might be busy with other programs, for instance, Empirum Remote Control or Skype.

List the current port utilization with the command 'netstat –ano' in the prompt. Use the displayed PID and the task manager to determine the respective program.


Problem

The following message is displayed in the browser when the web service URL in the reporting configuration manager is launched:

Web site not found.

Solution

  • The user’s access rights must be extended in the domain controller.
  • Use 'another account' in the 'Service Account' section must be specified with a user with sufficient permissions.

 


Problem

The following message is displayed in the browser when the report manager URL in the reporting configuration manager is launched:

HTTP 500 Error … Web site not found…
The following message is displayed in the report server log:
System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

Solution

'FIPS-compliant cryptographic algorithms' in the 'system cryptography option' has been enabled in the local security guidelines. Insert the line

<machineKeyvalidationKey="AutoGenerate,IsolateApps" decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>

in the file '\Programs\Microsoft SQL Server\MSRSxx.InstanceName \Reporting\Web.config' within the <system.web> section. Then restart the web service.

 


Problem

The following message is displayed in the browser when the report manager URL in the reporting configuration manager is launched:

The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. . (rsReportServerDatabaseUnavailable)

Solution

The name of the report server database in the reporting configuration manager is not identical with the name of the report server database in the SQL server.

 

 

More Information

Keep in Mind

You can find log files of failing logins or similar connetcion errors

within the default folder of the reporting services under

C:\..\Microsoft SQL Server\MSRSxx.Instanzname\Reporting Services\LogFiles

 

You must to post a comment.
Last modified
12:01, 26 Jul 2017

Tags

Classifications

Article available in EN & DE
Customer
(not set)
icons-access-c.png