Troubleshooting export providers

1. Overview

Dundas BI provides the ability to share dashboards, reports, and other views in exported formats such as PDF, image, Excel and PowerPoint. You can also receive these exports automatically through notifications.

This article describes some error messages you might see when exporting and how to troubleshoot them. 

2. Pre-requisites for export

Exporting has certain requirements on the Dundas BI server, which depend on the server's operating system:

  • For a Windows server, the Chrome Embedded Framework (CEF) plugin used in the exports requires Visual C++ Redistributable Packages and the Microsoft .NET Framework. These are installed automatically as prerequisites in the first step of creating a Dundas BI instance, or you can install them yourself using the links found in the system requirements.

  • For a Linux server, be sure to install the X Virtual Frame Buffer (XVFB) service after adding your instance, using the Dundas BI Deployment Wizard.

3. Internal Application URL configuration

Exporting content relies on the Internal Application URL configuration setting in Dundas BI's administration area, which may need to be confirmed or updated by an administrator. For example, the address used to access the application may have changed since installation. An incorrect setting may lead to various error messages.

4. Application logs

When an error occurs or the exported output isn't as expected, a Dundas BI administrator may find helpful information in the application logs.

Not all messages are included in the logs by default. To view all related messages:

  1. Find and edit the Log Filter configuration setting in Administration.
  2. In the Configure Log Filter dialog, find Standard Export Providers under Extensions, and change its setting to Verbose.
  3. Submit the changes and export your content again.
  4. View the application logs in Administration.

After finding the information you need, you can set the log filter setting back to Default.

5. Errors and issues

5.1. The export process failed (1004): <exception>

This error message means there is a JavaScript exception in the browser, and includes details about the script errors that are preventing export. For example:

The export process failed (1004): Script Exception -  https://reporting/Dundas.BI.Web.WebApp/Scripts/bunches/dundas/base.min.js?v=86694048814(11): Script error - Adapter: 'table1' Event Name: 'datachanged' Script Name: 'script 2' TypeError: Cannot read property 'cellset' of null

This error message would indicate an error from the script added to the Data Changed event of the element with script name table1 is causing the export to fail.

Tip
You can use the Layers window to find an element by its display name and edit its script actions.

5.2. The export process failed (1006): The operation has timed out. Verify the Internal Application URL in configuration is correct.

The export process has timed out before the report could be rendered. This could be because it was unable to access the application due to an incorrect Internal Application URL setting, or you may need to allow a longer time for exporting larger reports by increasing the Export Render Timeout setting from its default of 45 seconds. Dundas BI administrators can change these in the configuration settings in Administration, or you can customize the export timeout on individual views in the Properties window when editing.

5.3. The export process failed (1007): Unexpected error encountered

Any error message starting with The Export Process failed (1007): Unexpected error encountered, and followed by a three digit negative number and short caption, indicates that the internal application URL being used for the export process is incorrect or pointing to a specific page within the Dundas BI instance rather than the root of the website.

Internal Application URL is a configuration setting in Administration.

Common error codes include:

(-102) - Connection Refused - The port number is incorrect

(-105) - Name not resolved - The hostname is incorrect

(-104) - Connection failed - Check the internet connection

Please contact Dundas Support if you encounter any other 1007 error.

5.4. Export file generated with no data

If you are exporting a visualization and it does not show any data, check whether Disable Auto Data Loading was selected on that visualization in the Properties window.

If this setting is meant to be selected, you can add a script in the Before Export action of the dashboard/view to load the data automatically before the export takes place.

For example, the following script can be used to load the data for a table:

e.isAsync= true;
var def = table1.loadData();
def.done(function (results) {
  e.deferred.resolve();
});

5.5. HTTP error code

Any export process failed error message with an error code between 300 and 500 is an HTTP error. More information on these can be found on the internet.

6. Contacting Dundas Support

If you come across any other error message or if the provided solution does not resolve the error, please contact Dundas Support.

When contacting support, send the full error details, and the config.dat file generated during the export process as detailed below.

6.1. Obtaining the config.dat file

To obtain the config.dat file, first turn on Verbose logging and then export your content as described above, then you will find an entry in the application logs with a message starting with config.dat.

View the details of this log entry, and copy the Message contents into your message to support.

7. See also

Dundas Data Visualization, Inc.
500-250 Ferrand Drive
Toronto, ON, Canada
M3C 3G8

North America: 1.800.463.1492
International: 1.416.467.5100

Dundas Support Hours:
Phone: 9am-6pm, ET, Mon-Fri
Email: 7am-6pm, ET, Mon-Fri