416.467.9100 | Dundas Data Visualization | Login
Welcome Guest
This is the support page for the legacy Dundas Dashboard application. For assistance with the current Dundas BI application please click here.
Dashboard v5.0

This site makes extensive use of JavaScript.

Please enable JavaScript in your web browser and reload the page before proceeding.

Blank Dashboard Troubleshooting

Hide navigation
RSS
Modified on Wed, 19 Feb 2014 05:25 PM

Overview

After installing Dundas Dashboard, or when trying to integrate the Dundas Dashboard into an application, the area where Dashboard is supposed to be shows up blank. This article will help you troubleshoot these issues.

In all the cases listed here, you will see the Silverlight context menu when you press CTRL + right-click in the empty area:

Internet Explorer Standards.

Internet Explorer Standards.


Helpful tools

To help diagnose these problems, a utility which can monitor network traffic between the client and the Dundas Dashboard server application is invaluable.

IE Developer Tools

Internet Explorer 8 and 9 has a built-in tool which monitors network traffic. To open the developer tools window, hit F12 in IE.

Tip: When you hit F12 in IE, make sure you are using Internet Explorer 9 standards under Document Mode. If your IE is using an older standard, select Internet Explorer 9 standards and refresh/reload the browser. See if this helps in resolving the blank dashboard issue.
IE Developer Tools Window.

IE Developer Tools Window.


Firebug

Firebug is a free plugin for Firefox which has a network traffic monitor. It's available at http://getfirebug.com.

Fiddler

Fiddler is freeware application which works with any browser or application. It will not work if the client and Dundas Dashboard server are on the same machine because of the way Windows networking handles local connections. It's available at http://www.fiddler2.com/fiddler2/

Inaccessible .XAP URL

When integrating Dashboard into a web page, your page will contain HTML markup similar to this:

...

The URL inside the source parameter must be accessible from the client (i.e. putting this in your browser's address bar will download the .XAP file). The URL should never begin with http://localhost because this points to the client machine instead of the server.

Network scanners

Corporate networks often employ scanners to protect against malicious files. These scanners employ a whitelist to allow common file types through, while all others are virus scanned and you receive a download page from the scanner. Here's an example of what you might see if you try the source URL above:

Example of a corporate scanner intercepting the XAP file.

Example of a corporate scanner intercepting the XAP file.


This interception of the XAP file will not allow Dashboard to function. You will need your network administrator to whitelist this file type so it comes through without interference.

Missing MIME type*

Dundas Dashboard's viewer is a Silverlight application. All Silverlight applications (.XAP) must be served from IIS with the MIME type application/x-silverlight-app. If the MIME type is wrong, Silverlight will start up but will not load the application. Using your tool of choice, make sure the .XAP file loaded by the browser is the right MIME type. Here are examples with the tools mentioned earlier:

Checking XAP file MIME type in IE Developer Tools.

Checking XAP file MIME type in IE Developer Tools.

Checking XAP file MIME type in Firebug.

Checking XAP file MIME type in Firebug.

Checking XAP file MIME type in Fiddler.

Checking XAP file MIME type in Fiddler.


If the MIME type is wrong, you will need to add the correct MIME type in IIS.




Cross-scheme access (mixed HTTP/HTTPS)

When Dashboard is integrated into an application which uses HTTPS, Dashboard must be configured to run using HTTPS. This is common with SharePoint sites or applications with limited access. Silverlight will not load an application from an insecure site on a secure page.

Cross-domain access*

When integrating Dashboard into an application, if the Dundas Dashboard server application is not on the same server and port as your application, you need to make sure the root of the website where the Dundas Dashboard server application is hosted contains a valid client access policy file. You can also use Macromedia's crossdomain.xml file, though the client access policy is preferrable. Here's what you would see if the client access policy is missing:

Missing client access policy file seen with IE Developer Tools.

Missing client access policy file seen with IE Developer Tools.

Missing client access policy file seen with Firebug.

Missing client access policy file seen with Firebug.

Missing client access policy file seen with Fiddler.

Missing client access policy file seen with Fiddler.


About Dundas | Contact Us Follow us on Twitter! | Privacy Statement | Report Site Issues

Copyright © 2009-2014 Dundas Data Visualization, Inc.