Troubleshooting Open Access

General Troubleshooting

Check that you are using the latest version of Squared Up. The version number is shown in the bottom right corner of Squared Up. Download the latest version of Squared Up here.

Check Open Access is configured correctly

  1. In Squared Up browse to the right-hand menu ☰ then system and then click on the Open Access perspective. Check you see a message saying Squared Up is correctly configured for Open Access. If you do not see this message continue to the next step.

  2. Browse to http://SquaredUpServer/SquaredUpv3/setup?stage=openaccess (where SquaredUpServer should be replaced by the name of the server where Squared Up is installed). Check you see a message saying that Squared Up is correctly configured for Open Access. If you do not see this message click next to configure Open Access.

  3. If Squared Up is unable to automatically configure Open Access please see the following article How to manually configure Open Access.

  4. Re-run the Squared Up permissions tool to ensure the application pool identity has the correct permissions to the Squared Up directory, as described in section 3 of How to check and modify the application pool identity

Specific Problems

Open Access dashboards stop at “Preparing your Open Access dashboard, please wait”

When you visit an Open Access URL the rendering software prepares to take a snapshot of the dashboard. It renders the dashboard by acting as a browser and visiting a Squared Up URL, it takes a snapshot and this image is then served back to the user who originally requested the page.

The Squared Up URL, known as the Open Access loopback URL, is usually determined programmatically by checking the IIS bindings. With default IIS settings of localhost:80 the loopback URL that the system would automatically try would be http://localhost. Occasionally this default loopback URL can be determined incorrectly, however this problem can be overcome by specifying a oa-loopback-base-url in the openaccess.json file as described below.

First we need to determine what the Open Access loopback URL should be. You may need to try a few different options.

  1. Look at the bindings to see if a hostname is specified. On the server where Squared Up is installed open IIS Manager and click on Default Web Site, then on Bindings on the right hand menu under Actions. If there is a hostname and port specified note them down. Do not edit the bindings.

    • If port 80 is shown, then the loopback URL to try is http://hostname

    • If port 443 is shown, then the loopback URL to try is https://hostname

    • If no hostname is specified, but the port is 443, then the loopback URL to try is https://localhost

    • If no hostname or port is specified, but you do use a specific URL to access Squared Up you should try the hostname from this URL.

    • If you’re not sure which settings to use, please run the Squared Up Diagnostic Script and send the zipped up results to [email protected].

      Next we need to specify the loopback URL in the openaccess.json file.

  2. Run Notepad as administrator (File, Run, type notepad, and then right-click and select Run as administrator), and then open the following file:

    C:\inetpub\wwwroot\squaredupv3\User\Configuration\openaccess.json

  3. If openaccess.json is blank or only contains {} then add the following and replace https://hostname with the required value:

     {
         "oa-loopback-base-url": "https://hostname"
     }
  4. If openaccess.json already contains settings, then you will need to add a comma at the end of the previous line to look something like this:

     {
         "oa-refresh-interval": 120,
         "oa-loopback-base-url": "https://SquaredUpURL"
     }
  5. Save the file.

  6. In IIS recycle the SquaredUpv3 application pool for the setting to take effect.

    If you are unable to access Squared Up (Server Error in ‘/SquaredUpv3’ Application) after editing openaccess.json then there is an error in the file. Correct openaccess.json and recycle the SquaredUpv3 application pool again.
  7. If you are using Windows authentication with Kerberos delegation you may need to configure additional SPNs. The application pool identity will need an SPN added for the newly added loopback URL hostname. Additional information on checking and adding SPNs can be found here (see section 4).

  8. If you are running Squared Up across multiple servers, e.g. primary and secondary, you will need to repeat these steps specifying the appropriate loopback URL for each server. As above, you will also need to add an appropriate SPN for each server.

Some tiles on the Open Access page are not shown

You may need to increase the time between the dashboard being loaded and snapshot being taken. This is the oa-capture-lead-time setting, which defaults to 100 ms if not specified. You may need to adjust the figure you specify.

  1. Run Notepad as administrator (File, Run, type notepad, and then right-click and select Run as administrator), and then open the following file:

    C:\inetpub\wwwroot\squaredupv3\User\Configuration\openaccess.json

  2. If openaccess.json is blank or only contains {} then add the following:

     {
         "oa-capture-lead-time": 200
     }
  3. If openaccess.json already contains settings, then you will need to add a comma at the end of the previous line to look something like this:

     {
         "oa-loopback-base-url": "https://SquaredUpURL",
         "oa-capture-lead-time": 200
     }
  4. Save the file.

  5. In IIS recycle the SquaredUpv3 application pool for the setting to take effect.

  6. You may need to adjust the oa-capture-lead-time figure.

“Error loading dashboard - A valid mapping was not found for the given ID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx, there may be more information available in your log file.”

This means the dashboard is no longer available on this Open Access URL. It may be that the dashboard is no longer available in Open Access mode, or that the Open Access URL has changed.

If you remove a dashboard from Open Access mode and later re-enable it then the dashboard will be given a different Open Access URL, and any external bookmarks or links will need updating.

“You do not have the required permissions or your current license does not include Open Access”

  1. You may see this message if you are not licensed for Open Access. The Enterprise Starter Pack and above is required for this feature. Open Access is not supported with the Test & Dev (Lab) license. If you are trialing Squared Up and see this message please contact us (all features should be present on a trial license, regardless of the user limit).

  2. A user may see this message if they are not a SCOM administrator and they do not have the manage-open-access permission, see How to manage user profiles.

Some things won’t work on Open Access pages

  • Open Access dashboards are non-interactive so users will not be able to hover or drill down for more information you may wish to design your dashboards slightly differently with Open Access in mind. For example, you should consider adding a key to a performance line graph.

  • Web Content tiles are not supported with Open Access, because in many cases they do not work. Slow webpages may show as blank in Open Access. Webpages requiring authentication will not work because Open Access does not use any authentication.

  • SCOM On-Demand tasks cannot be run on Open Access dashboards, because Open Access is unauthenticated, so you will see the error MISSING_SCOM_PERMISSION.

About Open Access

How to publish dashboards with Open Access

How to configure Open Access

Collecting Diagnostic Information label: Troubleshooting Open Access keywords: open access oa readonly read-only anonymous anonymously hostname host name MISSING SCOM PERMISSION tasks