Skip to main content

BarChart Troubleshooting Guide

This topic explains how to diagnose and fix the following common problems that can occur when working with the BarChart 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: You receive Network Error message when you try to save data.

Cause: You may get this error typically in the following cases:

  • 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 was specified
  • the license service is stopped unexpectedly
  • in case of on-premises or Gateway installations the Windows Authentication setting is turned accordingly in the visual under Data Entry based on the IIS authentication settings
  • 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: Make sure that the write-back service is up and running and reachable (firewall not interfering) as it is described earlier in this document. Verify that the referenced connection exists in the write-back service configuration and the connection type is selected correctly.

A particular error can indicate a license service failure. Please refer to this article: Error: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state

If you encounter CORS issue, please check the web.config file of the write-back service for typo-s, and also missing DLL-s and config files inside the web service folder. As a last resort, try updating the web service file following these articles:

If you encounter SSL error, make sure that the certificate is issued by a trusted authority for the full qualified domain name of the IIS server, or that the certificate is set to ignore by the client’s browser in case of self-signed certificate, or if the certificate is issued internally by your organization and you try to reach the report outside of the organization domain.

If you are using Power BI Reporting Services on-premises, make sure that the report server URL and the web service URL format matches. Either both must reference the machine name or the full qualified domain name, and both must be http or https. Also, if Windows Authentication is set in the IIS configuration make sure that Windows Authentication is enabled in your visual under Data Entry settings.

In case of on-premises installation in a domain with Windows Authentication, make sure that Service Principal Names are created for your SQL and SSAS servers and the correct domain users are used for the services. An SPN is also needed for the service account that is running the PPWebService on the IIS machine as the Application Pool user. Make sure 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. If these are not set correctly, Kerberos authentication issues can occur, which might result in HTTP 403 or 404 errors or appearing log-in popups. Please refer to the following article and contact your internal IT team: Troubleshooting IIS Windows Authentication with Kerberos

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

Symptom: The visual is not rendered, or BarChart specific setting are not displayed (like Data Entry, General, etc.)

Cause: Generally, there can be two reasons for this:

  • your machine is running out of memory, therefore Power BI Desktop cannot render the elements properly
  • your Power BI Desktop Cache is outdated.

Solution: Free up memory on your computer by closing other applications. For clearing the Power BI Desktop cache, please refer to the article in our Knowledge Base at: Clear Power BI Desktop cache

Save Failed

Symptom: You receive Save Failed message when you try to write-back to the selected table.

Cause: You may get this error if there is a configuration error in your visual, the write-back service is not configured properly, or in the following cases:

  • there is 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

Wrong Figures Were Saved

Symptom: Write-back was successful, but bad number is shown after the visual is refreshed.

Cause: You may get this error if:

  • You are using slicers page-report or visual level filters and you forgot to add SmartFilter helper visuals properly
  • You have an issue with the relationships in your SSAS model
  • You have data quality issues in your underlying database, like duplicate members, incompatible data types, etc.
  • You have a logic error in your DAX measure formula

Solution:

  • Add SmartFilter helper visuals
  • Check your SSAS model relationships
  • Verify your data integrity in your underlying SQL database
  • Check your DAX measure

As there can be various reasons for this error, review the paragraphs in this chapter and please also visit our Knowledge Base to find the solution at https://help.insightsoftware.com/

Was this article helpful?

We're sorry to hear that.