Error through configuration via DBUtil

Problem:

The 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:

The 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:

The 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 displayed 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 displayed 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 displayed 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 displayed 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 displayed 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 displayed 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 displayed 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 displayed 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 RDLs must be loaded manually via the report manager of the SQL configuration manager on to the SQL reporting server.

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.

Errors in the SQL configuration manager for reporting services

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, 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:

The user’s access rights are not sufficient.

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 in 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.

Errors when reports are launched

Problem:

The following message is displayed when a report has been launched via the EMC:

An error occurred in the HTTP Runtime object for application domain 'ReportServer_MATRIX42_0-6-130106627457901127'. Most likely, the HTTP request contains an unsupported verb or invalid syntax. (rsHttpRuntimeError)

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 in the <system.web> section. Then restart the web service.

Problem:

The following message is displayed when a report has been launched via the EMC:

(Reporting Services error). For more information about this error navigate to the report server on the local server machine, or enable remote.

Solution:

Create a new connection to the reporting services in the Object Explorer of the SQL Server Management Studio. Use ServerName\InstanceName as server name and apply the Windows authentication mode.

Open the properties via the context menu of the reporting server node.

Click Advanced and set the EnableRemoteErrors to True.

Launch the report again. Now a detailed error description will be displayed.

Problem:

The following message is displayed when a report has been launched via the EMC:

The permissions granted to user 'mydomain\myAccount' are insufficient for performing this operation. (rsAccessDenied).

Solution:

Got to the SQL configuration manager for reporting services to assign the domain/user the Browser role via the web site of the report manager URL under Folder Settings > Security / Assign new role. It might also be necessary to launch the console with administrator privileges.

Problem:

The following message is displayed when a report has been launched via the EMC:

It is not possible to access the application directory C:\Programs\Microsoft SQL Server\MSSQL.2\Reporting Services\ReportServer\. The directory does not exist or cannot be accessed due to the security settings.

Solution:

An IIS report service is still active. The correct path must be specified in the IIS Manager in the properties of Websites\Reports and ReportServer (e.g., MSRS12.EMPIRUM rather than MSSQL.2).

Problem:

The following message is displayed when a report has been launched via the EMC:

The current identity (NT Authority/Network Service) does not have write access to"C:\Programs\Microsoft SQL Server\MSRS12.EMPIRUM\Reporting Services\RSTempFiles\".

Solution:

Write access must be granted for Network Service on C:\Programs\Microsoft SQL Server\MSRS12.EMPIRUM\Reporting Services.

Problem:

The following message is displayed when a report has been launched via the EMC:

Error occurred during report processing. (rsProcessingAborted). Cannot impersonate user for data source Matrix42_LocationDB. (rsErrorImpersonatingUser)

Logon failed (rsLogonFailed) Logon failure: unknown user name or bad password. (ReportingServicesLibrary)Ensure that user name and password are correct. (rsLogonFailed)

Logon failure: Unknown user name or bad password.

Solution:

The connection process for the Matrix42_LocationDB must be changed in the reporting manager of the SQL configuration manager for reporting services (maybe to Domain Administrator or Integrated Windows security).

Problem:

The following message is displayed when a report has been launched via the EMC:

The report server has encountered a configuration error on reporting server: Logon failed for the unattended execution account. (rsServerConfigurationError)

Error during log-in. Ensure that user name and password are correct. (rsLogonFailed)

Logon failure: unknown user name or bad password

Solution:

The connection process for the Matrix42_LocationDB must be changed in the reporting manager of the SQL configuration manager for reporting services (Integrated security of Windows).

Problem:

The following message is displayed when a report has been launched via the EMC:

An error has occurred during report processing. (rsProcessingAborted). Cannot create connection to data source Matrix42_LocationDB (rsErrorOpeningConnection). Logon failed for user ‚Sa‘.

Solution:

The connection process for the Matrix42_LocationDB must be changed in the reporting manager of the SQL configuration manager for reporting services (Integrated Windows security).

Problem:

It is not possible to log in via the Windows Security window when launching the report via the EMC. The window is displayed again and again and finally, an empty page is displayed.

Solution:

If this is not a problem with server name resolution (use IP address), the entry <RSWindowsNegotiate> from the file %Programs%\Microsoft SQL Server\MSRSxx.InstanceName\Reporting Services\ReportServer\rsreportserver.config must be removed. The entry <RSWindowsNTLM> must exist.

Problem:

You must always log on via the Windows Security windows when launching reports via the EMC.

Solution for Internet Explorer:

Enter the address of the reporting server under Trusted Sites and set the option User authentication to Automatic logon with username and password under Custom level.

Solution for Firefox:

Launch the address about:config and search for network.automatic-ntlm-auth.trusted-uris. Double-click this entry and enter the address of the reporting server, e.g. http://servername. Additional addresses can be added, separated by comma and blank.

Other problems

Problem:

The memory is fully occupied by the SQL reporting engine.

Solution:

To limit the occupied space, for instance, to a maximum of 4 GB, you must insert the entry <WorkingSetMaximum>4000000</WorkingSetMaximum> in the file %Programs%\Microsoft SQL Server\MSRSxx.InstanceName\Reporting Services\ReportServer\rsreportserver.config.