Errors

This page contains a list of errors previously encountered and their probable cause

Database

Error	Component	Probable cause
Unexpected response from server during a HTTP connection: Could not refill buffer.	Databricks	SSL Option is not selected in odbc settings
Driver not found		This error can happen when using an ODBC driver like snowflake, databricks, teradata on linux systems. It indicates there is probably a problem in the installation of the php dependency of WriteBackExtreme that has been compromised. Run `php -m` command to check what version you are on and run the install.sh again.

Single Sign-On

Undefined array key "sp_entity_id"

This error occurs when the Single Sign-On provider does not include the relayState in its response to the return URL. Because the relayState is missing, the extension cannot read the expected sp_entity_id, which leads to the “Undefined array key sp_entity_id” message.

To resolve this issue, make sure your SSO provider is configured to always return the relayState parameter in its authentication response. Once the IdP passes the relayState correctly, the sp_entity_id can be read and the error will be resolved.

Startup

Service Error: stop: Failed to stop WriteBackExtreme PHP App Server: The specified service does not exist as an installed service.

When there is an unexpected shutdown of the system, it occasionally happens that Windows removes the WriteBackExtreme service from Windows Services. Upon startup WriteBackExtreme tries to startup the service that is not there anymore.

Steps to resolve this

1. Start WriteBackExtreme manually as an administrator.

2. Go to configuration

3. Toggle the switch 'Initiate upon startup using a background service' off and on again

4. Click Start WriteBackExtreme

5. Open Windows services and verify WriteBackExtreme is listed again.

Failed to extract PHP:open C:\[path]\.wbe-runtime\php\ext/[filename].dll: The process cannot access the file because it is being used by another process.

This typically happens when the system or application experienced an unexpected shutdown. Our application tries to remove the .wbe-runtime/php directory but it was not successful due to a dangling php processes that could not be killed properly. Upon startup it will not be able to start properly due to missing files in the php directory.

Similar error messages

• No valid json: In Connection.php line 822: could not find Driver

• openssl signature could not be verified: openssl not loaded

• Error while stopping: open C:\[path]\.wbe-runtime\php-appserver.pid: The system cannot find the file specified

Steps to resolve this

1. Start the application manually

2. Stop the application properly (this will remove the php directory)

3. Start application again. (this will reinstall the php directory again)