Home > 09 Matrix42 internal > 98 Article Depot > Errors when reports are launched by the Empirum console

Errors when reports are launched by the Empirum console

 

27 Jul 2017Last updated
0votes
7updates
61views
Written by Jürgen Markart (Customer Service)
2nd Level Support Engineer

Overview

On launching reports by the Empirum console some errors may occur which are described and solved.

 


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' within 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

Go 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' to 'Integrated Windows security'. You can do this also via DBUtil by executing the SQL script SetReportAccessToIntegratedSecurity.sql .


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' to 'Integrated Windows security'. You can do this also via DBUtil by executing the SQL script SetReportAccessToIntegratedSecurity.sql .


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' to 'Integrated Windows security'. You can do this also via DBUtil by executing the SQL script SetReportAccessToIntegratedSecurity.sql .


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.

 

 

You must to post a comment.
Last modified

Tags

Classifications

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