The Web Player start page does not load correctly, showing text labels like {{labels.startPageAbout}}.

The Web Player start page does not load correctly, showing text labels like {{labels.startPageAbout}}.

When going to the start page of the Spotfire Web Player, you will see some text labels such as {{labels.startPageAbout}}. This KB article lists some of the common reasons why and how to resolve them.

When going to the start page of the Spotfire Web Player, you will see some text labels such as {{labels.startPageAbout}} instead of the expected buttons.

There can be several reasons for this to happen. Below is a list of some of the common reasons.

• The case of the text in the URL entered does not match the case of the Web site defined in IIS(Internet information services)

• Compatibility mode is enabled in Internet Explorer

• .NET Framework is not registered correctly with IIS or 'ISAPI and CGI restrictions' in IIS are not set to 'Allowed' in IIS.

• The Web player is embedded into an Iframe that has a meta tag like ""

• is set in web.config

The following is a list of ways to resolve some of the common reasons for a blank startpage.aspx .

• The case of the text in the URL entered does not match the case of the Web site defined in IIS (Internet Information Services).

o The URL is case sensitive, so it is important that the name of the site defined in IIS matches what is used in the URL. The default site name is "SpotfireWeb". In that case, the URL to be used should be http://webplayerserver:port/SpotfireWeb/

• Compatibility mode is enabled in Internet Explorer.

o Spotfire Web Player does not support running in compatibility view. See KB article 40904 for instructions on how to disable compatibility view.

• .NET Framework is not registered correctly with IIS or "ISAPI and CGI restrictions" in IIS are not set to "Allowed" in IIS.

o To make sure .NET is correctly registered in IIS, run the following command from a command prompt on the Web player server "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe /i"

o To make sure "ISAPI and CGI restrictions" are set to "Allowed" in IIS, follow the instructions in the Web player server manual chapter 2.2.1 on page 24.

• The Web Player is embedded into an Iframe that has a meta tag like ""

o If you are embedding the Web Player into an Iframe, it is important that the correct headers are set in the main page of the Iframe. Make sure that no headers like the above mentioned are set in the main frame. You can use the browser developers tools (f12) to inspect the source code, or you can use something like Fiddler to look at what headers are sent to and from the web page.

• is set in web.config.

o All cookies except a few are by default set to be "httponly". The few cookies not set to be httpolny do not contain sensitive information and are only used to initiate and set a few parameters for some of the JavaScript scripts being used to initialize the startpage.aspx. You do not need to set the httponly flag, and doing so will make the startpage.apsx fail to load.

blank, startPageAbout, angular, startpage.aspx, curly brackets, troubleshooting guide