Skip to main content

Power XL Table Troubleshooting Guide

This topic explains how to diagnose and fix some of the problems that may occur when working with the Power XL Table visual.

Note: To review all cases, log in to https://help.insightsoftware.com/ and access the Power ON Knowledge Base articles. For further assistance, you can also submit a ticket through this support portal.

Network Error

Symptom: A network error message is displayed when you try to save data.

Cause: Listed below are some of the possible reasons for this error:

  • The Write-Back Service URL is not set correctly – or it is malformed - in the Data Entry settings
  • The Write-Back Service is not reachable or off-line
  • Bad connection name or/and type specified
  • License service is stopped unexpectedly
  • If it is a on-premises or Gateway installation, the Windows Authentication setting is available by pressing the Writeback Settings button in the Power XL tab.
  • Missing files in the web service folder, or typo / malformed strings in the web.config file
  • Windows / Kerberos authentication issue
  • Missing Service Principal Names
  • Missing active directory permissions for service accounts
  • Report server URL web service URL format mismatch
  • Invalid SSL certificate

Solution: Ensure that the Write-Back Service is operational and accessible, without interference from the firewall. Confirm the existence of the referenced connection in the Write-Back Service configuration, and ensure that the right connection type is selected.

  • To understand the license service failure type, refer to the following article:

  • If you encounter the CORS issue, check the Write-Back Service's web.config file for typos. Also check for missing DLL-s and config files inside the web service folder. If the issue is still not resolved. update the web service file following the guidelines provided in the following articles:

  • If an SSL error occurs, ensure that the certificate is issued by a trusted authority for the fully qualified domain name of the IIS server. Alternatively, confirm that the client's browser is set to ignore the certificate if it is self-signed. If the certificate is internally issued by your organization and you are attempting to access the report outside of the organization's domain, take necessary precautions.

  • If utilizing Reporting Services On-premises, ensure that the report server URL and the web service URL formats align. Both URLs should either reference the machine name or the fully qualified domain name, and both should be either HTTP or HTTPS. Additionally, if Windows Authentication is configured in the IIS settings, ensure that Windows Authentication is enabled in your visual under the [Data Entry] group.

  • For an On-premises installation within a domain utilizing Windows Authentication, ensure that Service Principal Names (SPNs) are created for your SQL and SSAS servers, and that the correct domain users are assigned to the services. An SPN is also required for the service account responsible for running the PPWebService on the IIS machine as the Application Pool user. Verify that delegation is enabled in your Active Directory from the App Pool's user (which must be a trusted user) to the SQL/SSAS services. Incorrect configurations in these areas can lead to Kerberos authentication issues, potentially resulting in HTTP 403 or 404 errors, or prompting login popups. Refer to the following article and liaise with your internal IT team for further assistance:

The Visual is Not Working in Power BI Desktop or the Settings are Not Shown

Symptom: The visual fails to render, or Power XL-specific settings are not displayed.

Cause: The following are the two potential reasons for this error:

  • Your system might be running out of memory, resulting in Power BI Desktop's inability to render elements correctly.
  • Your Power BI Desktop cache is outdated.

Solution: To resolve these issues, free up memory on your system by closing other applications. For instructions on clearing the Power BI Desktop cache, refer to the Clear Power BI Desktop cache article available in the Knowledge Base.

Save Failed

Symptom: You encounter a Save Failed message when attempting to write-back to the selected cell.

Cause: This error may occur due to a configuration error in the visual, improper configuration of the Write-Back Service, or due to one of the following reasons:

  • A custom validation implemented that prohibits write-back
  • SQL objects are interfering with the data modification TSQL statements (like security policies, triggers, unique constraints, etc.)
  • The service account used by the Write-Back Service does not have permission on the underlying SQL database to make the necessary modification on the source table

Solution:

  • Check if the service account has the necessary permissions, the password has not expired
  • Verify that RLS policies or triggers are not prohibiting the operations

Was this article helpful?

We're sorry to hear that.