Troubleshoot

Application startup

When the application does not start, the cause can probably be found in the log files. they are located in <installation_path>/.wbe-runtime/storage/logs/*.log. When opening a support ticket, please provide these files.

Could not startup server, Contact Apps For Tableau support when the problem persists

The app server is unable to start. This can have multiple causes like:

• Application is configured as administrator but is currently not running with administrator previleges.

• Check if there is no other WriteBackExtreme proces running in the background. Open Task manager and select the Details tab. You should have only one process called WriteBackExtreme.

• Check if there is no other process running on the port that is configured in WriteBackExtreme. You can do that with this command in cmd:

netstat -aon

• Open powershell and navigate to the directory where WriteBackExtreme.exe is located. run this command to manually trigger the application server:

./WriteBackExtreme.exe serve

This command might give more details about what went wrong.

listen tcp :443: bind: Only one usage of each socket address (protocol/network address/port) is hormally permitted

When this error appears in your wbe-application.log it is not able to spin the server because the port you have configured is already in use by another program.

WriteBackExtreme is slow or unresponsive

A typical reason of a slow experience is the database connection itself. Especially databases that are not running in the same network could potentially be slower.

When the management console for example is also slow you can take a look at the application performance. Open Powershell and navigate to the directory where writebackextreme.exe is located. Run this command to see the statistics of the internal workers:

./WriteBackExtreme.exe workers

This will generate a statistics table like so:

Extension

The tableau Extension does not show any schemas

The main cause of this is that your user account does not have the correct permissions to view a schema. Check in the management console if this user belongs to any groups. Then check on the connections page if there are connections for any of the groups of this user. If that is the case, check if there are schemas attached to these connections. If there this is the case, go to the permissions tab of the schema and check if the groups this user belongs to has permissions enabled.

The tableau extension does not show (all) data

1. A cause of this could be Row level Security (RLS). RLS restricts the data shown base on policys set on the schema. Check in the management console if RLS is active.

2. Check in the management console in the Data tab if the data you are looking for is there. When RLS is active you can simulate what the extension should display by selecting the user.

3. Extension configuration can limit the data based on the `Show data when` setting.

Single Sign On (SAML)

Authentication method by which the user authenticated with the service doesn't match requested authentication method

Whenever you suddenly get an error with Single Sign On related to the authentication method Password Protected does not match the .... with Microsoft please follow this link:

https://learn.microsoft.com/en-us/troubleshoot/azure/active-directory/error-code-aadsts75011-auth-method-mismatch

Solution 1:

Logout from your Edge browser and login again to reset the user profile in the browser.

Solution 2:

Set the requestedAuthnContext to false by adding the following lines to your wbe.config.yaml:

PORTAL:
  SAML:
    XML_VALIDATION: true
    REQUESTED_AUTH: false