Chapter 13. Troubleshooting

This chapter contains some infrequent errors you may encounter and solutions to them.


Windows SmartScreen

In case of installation of CloverETL Designer on Microsoft Windows 8 the installer may be prevented from starting by SmartScreen.

SmartScreen warning

Figure 13.1. SmartScreen warning

To start the CloverETL Designer installer click on More info, check that the publisher is Javlin, a.s. and then click on Run anyway.

Launching installer from SmartScreen

Figure 13.2. Launching installer from SmartScreen

More information about SmartScreen:

User Account Control

On Microsoft Windows, the User Account Control can prevent the installer of CloverETL Designer from running. Click YES to allow the installer to run.

User Account Control Preventing the Intallation

Figure 13.3. User Account Control Preventing the Intallation

Windows 10 Firewall

Windows 10 shows security warning when Designer's Runtime is starting.

Windows 10 Firewall

Figure 13.4. Windows 10 Firewall

CloverETL Designer application starts as two processes: CloverETL Designer GUI and CloverETL Runtime. These processes need to communicate with each other over TCP protocol. You should allow the mutual communication with Allow access button.


Designer Crashes due to Issue in Eclipse

Eclipse 3.8, 4.2 and 4.3 using some versions of WebKitGTK+ crashes. As a workaround, the following line can be added to the end of the eclipse.ini:


See Eclipse bug tracker

Designer Stops Responding

Due to bug in Linux/GTK+, Designer runs out of number of open files as the backend opens the file /etc/cups/client.cont many times.

As workaround, you can configure the printers in /etc/cups/client.conf file, or add -Dorg.eclipse.swt.internal.gtk.disablePrinting to CloverETL.ini file. See, or

Welcome Page not Displayed

Welcome page requires webkitgtk library to be present on your system. Install webkitgtk version 1.


Hints on Edges Have no Content

If hints on edges contain only the frame but no content, you should install webkitgtk.



If you use CloverETL Designer with Subclipse plugin, and perform the following steps: In a project, create a directory aaa, create a file bbb, delete the directory aaa, and rename file bbb to aaa; you may encounter the message:

An exception has been caught while processing the refactoring 'Rename resource'.
Problems encountered while moving resources.

Error deleting markers for resource bbb.
Resource aaa does not exist.

This problem is caused by caching resources by the Subclipse plugin an has nothing to do with CloverETL.

If this message appears, refresh the project in Navigator.