WriteBackExtreme does not start after rebooting server even though it is running as a service

This can have two causes:

1. The WriteBackExtreme application could have experienced an unexpected shutdown. The service is not able to restore the correct configuration files. A common fix for this is to open WriteBackExtreme.exe manually and close it. After closing the application manually, the configuration files are reset and the service should be able to start again.

2. Another common cause of this is when the repository database is mysql, postgresql or sql server on the same machine it could be that WriteBackExtreme is started before the database is started. When this happens you will see database connection errors in the log files. This can be resolved by adding a delayed start in the service configuration.

Linux

Add a sleep to the service file (typically located at /etc/systemd/system/WriteBackExtreme.service)

ExecStartPre=/bin/sleep 15

Windows

• Open services.

• Look for WriteBackExtreme service

• Right click and select properties

• On the general tab, select Automatic (delayed start) as startup type.