Home > 09 Matrix42 internal > 98 Article Depot > Errors on report configuration via DBUtil

Errors on report configuration via DBUtil

 

15 Aug 2017Last updated
0votes
10updates
39views
Written by Jürgen Markart (Customer Service)
2nd Level Support Engineer

Overview

On setting up reports via DBUtil with the Microsoft Reporting Services some errors may occur which are described and solved.

 


Problem

Following message is displayed when the reports are being configured:

Unable to connect to the remote server.

Solution

The user who has been used to launch DBUtil must be permitted to launch the SQL server report manager vie the link 'http://ReportServerName/VirtualReportManagerDirectory'.


Problem

Following message is displayed when the reports are being configured:

Error for request with http status 404: Not Found
or
Invalid URI: The hostname could not be parsed

Solution

  • First you must install the Microsoft Report Server.
  • The report server name in the DBUtil Report Configurator is not correct or has been specified with the SQL instance name.
  • The name of the virtual directory in the DBUtil Report Configurator is not identical with the virtual directory of the web service URL in the SQL report configuration manager.

 


Problem

Following message is displayed when the reports are being configured:

The report server has encountered a configuration error. No DSN present in configuration file.

Solution

The report server database must be created via the SQL configuration manager for reporting services.


Problem

The following message is displaced when the reports are being configured:

The report server cannot open a connection to the report server database

Solution

It is not possible to access the report server database configured in the SQL configuration manager for reporting services; a wrong server may have been specified.


Problem

The following message is displaced when the reports are being configured of when the report manager is being launched:

The report server installation is not initialized. (rsReportServerNotActivated).

Solution

Either you must create the report server database via the SQL configuration manager for reporting services or it must be executed in the section 'Encryption keys' under 'Delete Encrypted Content'.


Problem

The following message is displaced when the reports are being configured:

System.Web.Services.Protocols.SoapException: The operation you are attempting requires a secure connection (HTTPS).

Solution

In the file '%Programs%\Microsoft SQL Server\MSRSxx.InstanceName\Reporting Services\ReportServer\rsreportserver.config' modify the entry <Add Key="SecureConnectionLevel" Value="2"> into <Add Key="SecureConnectionLevel" Value="0">.


Problem

The following message is displaced when the reports are being configured:

Error for request with http status 403: Forbidden.

Solution

Check whether it is possible to launch the report manager URL directly in the SQL configuration manager for reporting services. If this is not possible, the error may be caused by a proxy server that blocks the system’s address.


Problem

The following message is displaced when the reports are being configured:

Error for request with http status 401: unauthorized.

Solution

The user who is logged into the system where the reports are configured must have access rights to the SQL report server.


Problem

The following message is displaced when the reports are being configured:

This action is not supported on a report server that has been configured for execution in the integrated SharePoint mode.

Solution

Either switch the report server database to the native mode on the SQL configuration manager for reporting services; please refer to the following Microsoft link: http://technet.microsoft.com/en-us/library/bb326407.aspx. Or install a second report server in the native mode; please refer to the following link: http://technet.microsoft.com/en-us/library/ms159114.aspx. It has not been possible yet to configure respective access rights.


Problem

The following message is displaced when the reports are being configured:

Error for request with http status 417: Expectationfailed.

Solution

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


Problem

The following message is displaced when the reports are being configured:

Application Usage Tracking grouped by Computer: The permissions granted to user 'JMDOM\Report' are insufficient for performing this operation…

Solution

The displayed user is the one who has started DBUtil. He must be granted the 'Content Manager' role in the folder settings in the report manager of the SQL configuration manager for reporting services.


Problem

The following message is displaced when the reports are being configured:

Application Usage Tracking grouped by Computer: Client found response content type of '', but expected 'text/xml' …

Solution

None yet.


Problem

Not all reports can be installed. The following message is displayed in the DebugView log:

Error : Caught WebException: 'Unable to connect to the remote server'

Solution

The missing report RDL files must be loaded manually via the report manager of the SQL configuration manager on to the SQL reporting server. This could be done with the script 'DeployReports.cmd'.

 


Problem

When the reports have been installed, the following message is displayed:

The report server cannot decrypt the symmetric key that is used to access sensitive or encrypted data in a report server database. You must either restore a backup key or delete all encrypted content. …

Solution

Execute 'Delete Encrypted Content' in the 'Encryption keys' section of the SQL configuration-manager.

Attention!

Take into account that this action may prevent opening reports of other applications!

 

 

 

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
17:03, 15 Aug 2017

Tags

Classifications

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