Reports Related Issues

 

The Report Builder button is not visible

Cause

You may not have appropriate privileges.

Solution

Check that you have Report Builder privilege from the Security tab under Site Settings.

 

No datasets returned

Cause

Your data source may be incorrect.

Solution

Check that your Data Source is correct (Connection String) and that it refers to the Seabed Database, Check that you can connect to the Database using ProSource.

 

Report reference shows '!'

The following error message is shown in the Quality Reports section in Data Loading > Drop Box > QC tab.

Cause

The SQL Statement in the ReportConfig.xml file is not correct and will cause the reference not to load.

Solution

Fix the SQL statement for the Data Count on the PSFO server, in the ReportConfig.xml file and the corresponding report definition file.

 

User is prompted while launching reports

Cause

Mismatch between parameter names in the ReportConfig.xml file and the actual report on the Report Server.

Solution

Check that the parameter name set in the report matches the ones in the ReportConfig.xml file, revise that your Parameter Data types are correct and that the browser is not caching (Do an IISreset).

 

Reports are not working for projects created using Individual ProSource Account

Cause

Reports installation is out-of-date.

Solution

Ensure that the previous installation of reports has been removed and run the updated script contained in ReportConfig.xml.

Deploying Reports requires an HTTPS Connection

In some cases while you are deploying reports you receive the following error: The Operation you are attempting requires a secure connection (HTTPS).

Cause

The report server (SSRS) is configured to require HTTPS when publishing reports

Solution

  1. Open the publish-reports.ps1 script.
  2. Replace the text “HTTP” with “HTTPS”

Note: When running the script, the first argument (which is the machine name where the report server is running) must match the server name in the HTTPS certificate. On servers joined to a domain this is typically the domain-qualified name, such as reportserver.domain.com. One can verify this name by browsing to the URL resembling:  https://reportserver.domain.com/Reports and making sure the browser does not report certificate errors.