Troubleshooting Reports
This topic contains answers to some common report issues.
To fix this:
- Download and install the stand-alone Report Builder 3.0: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=d3173a87-7c0d-40cc-a408-3d1a43ae4e33&displaylang=en
- If the Report Builder installer requests that .NET Framework 3.5 SP1 be installed first, go to http://www.microsoft.com/en-us/download/details.aspx?id=22 and install.
|
To add support for browsers in distributed locations covering multiple countries, use the Microsoft SSRS Report Builder to add query parameters to detect the current browser culture.
For example, you can edit the parameter to account for Great Britain, which displays date ranges differently than the U.S.
Add Support for a Distributed Browser
1. | Open the Microsoft SSRS Report Builder. |
2. | Make the parameter governing browser culture visible. |
- Select the CurrentBrowserCulture parameter governing browser culture from the Report Data pane. The Report Parameter Properties window opens.
- Click Visible in the Select parameter visibility area. When running the report, this parameter will be used to detect the browser culture.
- Click OK to save your changes.
3. | Add support for a local browser culture to your report query. |
- In the Report Data pane, right-click on the Datasets folder and select Add Dataset. The Dataset Properties window opens.
- On the Query panel, check Use a dataset embedded in my report.
- Select SaaSAppModel from the Data Source drop-down list.
- Check Text.
- Click Query Designer, located below the Query field.
- In the Enter Data Source Credentials window, enter your Microsoft SSRS user name and password, then click OK. The Query Designer window appears.
- Enter your query text in the field provided.
The following simple query is an example:
SELECT
Incident.CreatedDateTime
FROM
Incident
4. | Add fields to the template. In each field using date/time fields, use the Properties pane to change the Language properties to add an expression using the current browser culture value: |
=Parameters!CurrentBrowserCulture.Value
5. | Complete the template design, and click OK to save your changes. |
By default, records are stored in UTC time. However, you can use the Microsoft SSRS Report Builder to change the report parameters to display the record time as local time. For example, you can display a report in Pacific Time when run from a browser in that time zone.
This can be combined with the CurrentBrowserCulture parameter to change the format in which the time is displayed.
You can change the browser offset value in:
- A report template field.
- A report template query.
1. | Open the Microsoft SSRS Report Builder. |
2. | Make the parameter governing displayed time zones visible. |
- Select the BrowserTimeZoneOffset parameter governing browser time zone displays from the Report Data pane. The Report Parameter Properties window opens.
- Check Visible in the Select parameter visibility area. When running the report, this parameter will be used to detect the browser time zone.
- Click OK to save your changes.
3. | Add support for a browser offset to your report field. |
- In the Report Data pane, right-click on the Datasets folder and select Add Dataset. The Dataset Properties window opens.
- On the Query panel, check Use a dataset embedded in my report.
- Select SaaSAppModel from the Data Source drop-down list.
- Check Text.
- Click Query Designer, located below the Query field.
- In the Enter Data Source Credentials window, enter your Microsoft SSRS user name and password, then click OK. The Query Designer window appears.
- Enter your query text in the field provided. The following simple query is an example:
SELECT
Incident.CreatedDateTime
FROM
Incident
4. | Add fields to the template. In each field using date/time fields, use the Properties pane to add an expression specifying the browser offset to the Language properties: |
=Code.AdjustBrowserOffsetToDatetime(Fields!createddatetime.Value,Parameters!BrowserTimezoneOffSet.Value)
5. | Complete the template design, and click OK to save your changes. |
Create a Browser Offset within a Report Template Query
1. | Open the Microsoft SSRS Report Builder. |
2. | Make the parameter governing browser culture visible. |
- Select the BrowserTimeZoneOffset parameter governing browser time zone displays from the Report Data pane: The Report Parameter Properties window opens.
- Click the Visible radio button in the Select parameter visibility area. When running the report, this parameter will be used to detect the browser time zone.
- Click OK to save your changes.
3. | Add support for a browser offset to your report query. |
- In the Report Data pane, right-click on the Datasets folder and select Add Dataset. The Dataset Properties window opens.
- On the Query panel, check Use a dataset embedded in my report.
- Select SaaSAppModel from the Data Source drop-down list.
- Check Text.
- Click Query Designer, located below the Query field.
- In the Enter Data Source Credentials window, enter your Microsoft SSRS user name and password, then click OK. The Query Designer window appears.
- Enter your query text in the field provided.
The following simple query is an example of using the browser offset within the query:
select IncidentNumber,DATEADD(mi,@offset,createddatetime) as createddatetime from incident
From the Dataset Properties panel, edit the @offset parameter using the following expression:
=Code.GetBrowserTimezoneOffsetAsInt(Parameters!BrowserTimezoneOffSet.Value)
4. | Add fields to the template. No editing of the date/time fields is required in this procedure. |
5. | Complete the template design, and click OK to save your changes. |
Under certain conditions, reports created while Daylight Savings Time (DST) is in effect might not show events on the proper days. To prevent incorrect reporting, ensure the event time does not occur exactly at midnight (12:00 AM) on the day DST ends.
For example, if you specify a date of 4 Nov 2012 12:00 AM, the record will appear on the report as having occurred on November 3. Set the event time to something other than midnight (such as 1:00 AM) to yield a correct report. The following illustrates this concept:
Target Times Set at Midnight on the Last Day of DST Yields an Incorrect Report
Set Target Times to Other Than Midnight (such as 1:00 AM) to Yield a Correct Report
You can add query parameters to account for changes in date and time when creating interval reports.
For example, you can change the interval used in the Executive Scorecard report template to produce a report gathering data for the past two fiscal quarters.
The browser culture (CurrentBrowserCulture parameter) cannot be changed from that of the report server. |
Create a Time-Based Report Template
1. | Open the Microsoft SSRS Report Builder. |
2. | Make the parameters governing time ranges visible. |
- Select the Last parameter governing report intervals from the Report Data pane.
- Click Visible in the Select parameter visibility area.
When running the report, this parameter will be used to detect the report runtime defined in the query.
- Click OK to save your changes.
- Repeat these steps for the DataRangeOptions and BrowserTimeZoneOffset parameters.
3. | Create the interval report query, including the date ranges (start and end date). |
For example, you could create the following query:
select incidentnumber,createddatetime from incident where createddatetime>(@startdate) and createddatetime <(@enddate)
4. | From the Dataset Properties Parameters pane, set the expression for the values: |
@startdate |
=Code.getStartDateTime( Parameters!DataRangeOptions.Value, Parameters!BrowserTimezoneOffSet.Value, Parameters!Last.Value ) |
@enddate |
=Code.GetEndDateTime( Parameters!DataRangeOptions .Value, Parameters!BrowserTimezoneOffSet.Value ) |
5. | Complete the template design, and click OK to save your changes. |
When run, the startdate and enddate query parameters return the dates in the format defined by the user (year, month, quarter, etc.).
Sample Report Template
The following shows a portion of a report template with localization parameters:
Last 1 Year and Last 4 Quarters (as seen in the Executive Scorecard report) are figured differently and can produce different results.
For example, if you run the report on January 8, 2014, then
Last 4 Quarter =
[Current Quarter(1/1/2014 - 1/8/2014(Today)[1st Quarter]]
+
[Quarter 10/1/2013 - 12/31/2013 [2nd Quarter]]
+
[Quarter 7/1/2013 - 31/09/2013[3rd Quarter]]
+
[Quarter 4/1/2013 - 30/06/2013 [4th Quarter]]
Last 1 year =
Current year 1/1/2014 - 1/8/2014(Today)
At the same time:
- Last 1 Last Year - ignores the current year
- Last 1 Last Year = 1/1/2013 to 12/31/2013
In the same way, Last 1 Last Quarter will ignore the current quarter:
- Last 1 Last Quarter = Quarter 10/1/2013 - 12/31/2013
Whenever you choose last year, quarter, month, week, or day, the system ignores the current year, quarter, month, week, or day. |
SYMPTOM. When I click Provision Report Now, an error message appears stating that the report server cannot decrypt the symmetric key…
1. | Click OK, but do not close the System Configuration Wizard. |
2. | Start the Reporting Services Configuration Manager and connect to your Microsoft SRSS instance. |
3. | Select Encryption Keys from the list in the left panel. |
4. | Click Delete, then Yes to Delete All Encrypted Content. |
5. | Return to the System Configuration Wizard, then click Provision Report Now. |
The operation should continue as normal.
SYMPTOM: When I click Provision Report Now, an error message appears stating that the report server cannot decrypt the symmetric key…
This is a known issue (fixed in HEATRelease 2014.1.1) that occurs in configuration with Microsoft SQL 2008R2 SP2 (Release 10.50.4295.0). This issue is specific to your version of Microsoft SQL Server and the cumulative patch.
You must update the data.xml file to match your Microsoft SQL version and patch level. This file is on your Microsoft SQL Server at:
C:\Program Files (x86)\FrontRange Solutions\HEAT\SystemConfigurationWizard\
Within the SupportedDatabasesForReporting section, change the ProductVersion to match your version of Microsoft SQL.
SYMPTOM: The Cannot Start Application error message appears when launching the Report Builder when using Chrome.
Any attempt to edit a report results in trying to download the Report Builder. An error message appears stating that the Report Builder cannot be started.
- Download and install the Click-Once for Google Chrome extension, located at:
https://chrome.google.com/webstore/detail/eeifaoomkminpbeebjdmdojbhmagnncl#
The Report Builder should download and run as normal.
SYMPTOM: The Cannot Start Application error message appears when launching the Report Builder when using Firefox.
Any attempt to edit a report results in trying to download the Report Builder. An error message appears stating that the Report Builder cannot be started.
- Download and install the Microsoft .NET Framework Assistant extension. located at:
https://addons.mozilla.org/en-US/firefox/addon/9449
- Restart Firefox and edit a report.
The Report Builder should download and run as normal.
SYMPTOM: When launching the Reports page, an error message appears stating that the page cannot be opened.
Microsoft SSRS might not launch when using Internet Explorer because of your security settings.
To fix the settings:
1. | Within Internet Explorer, go to Tools > Internet Options. |
2. | From the Security tab, go to Trusted Sites > Sites. |
3. | Click Add to add the current website to your trusted site. |
4. | Click Close |
Microsoft SSRS should launch as normal.