Skip to content

Troubleshooting🔗

hinfo utility🔗

If you have trouble starting HDevelop or a HALCON application, you can run the hinfo utility from a command shell. This program will display various information about HALCON, including the values of environment variables relevant to HALCON, the version of HALCON, the license being used, etc. If no valid HALCON license is found, hinfo will display each found license and an error message explaining why it cannot be used.

Log files🔗

Each time you run HDevelopEVO, a logfile is stored but only the last 10 session will be stored. To access your log files of HDevelopEVO, go to File > Open Log File and your stored log file(s) will be displayed. The exact folder location of your files depends on your operating system.


Problems during installation🔗

HALCON Variable Inspect (VSIX) cannot be installed🔗

Problem
The problem is caused if users with different permissions are involved. If an older version of HALCON Variable Inspect has been installed as administrator, it cannot be upgraded by a general user.
Solution

The old HALCON Variable Inspect has to be uninstalled before the SOM package can be installed. To uninstall HALCON Variable Inspect from your Visual Studio:

  1. Open Visual Studio.
  2. Open the menu Extensions > Manage Extensions.
  3. Change to Installed.
  4. Select HALCON Variable Inspect and click Uninstall.
  5. Try installing HALCON Variable Inspect again. If the installation still fails, continue with the next step.
  6. Open a command prompt as administrator.
  7. Execute the following command to uninstall all instances of HALCON Variable Inspect.

    Warning

    This will remove all instances of HALCON Variable Inspect in all installed versions of Visual Studio.

    VSIXBootstrapper.exe /admin /uninstall:4159242D-A658-4E33-BD2F-7F4ED4CFC420
    
  8. Try installing HALCON Variable Inspect again. If the installation still fails, continue with the next step.

  9. Open a command prompt as user.
  10. Execute the following command to uninstall all instances of HALCON Variable Inspect.

    Warning

    This will remove all instances of HALCON Variable Inspect in all installed versions of Visual Studio.

    VSIXBootstrapper.exe /uninstall:4159242D-A658-4E33-BD2F-7F4ED4CFC420
    

Problems concerning licenses🔗

Starting HDevelopEVO fails (License)🔗

Problem
Trying to start HDevelopEVO fails.
The dialog shows the error message HALCON License Error.
Possible Solution
Check whether HDevelop can be started.
Install a valid license file. For more information, see About HALCON licenses.

Problems when extracting host IDs🔗

If you encounter problems with your HALCON license even though your license file exists and is located in the correct directory, check if the host ID identifying your network card or dongle matches the entry in the license file. If the two do not match, send the new identifying information to your distributor.

hhostid does not return a dongle ID.
Only HALCON dongles (orange) are reported by hhostid. Other dongles (for example, blue MERLIC dongles) are not supported.
hhostid does not return a MAC address.
This can happen if you call hhostid from a virtualized environment using locally administered MAC addresses. HALCON only supports MAC-based licenses bound to universally administered, permanent MAC addresses. Locally administered MAC addresses are rejected.
hhostid shows the dongle ID on Linux only when run as root.
If HALCON is run without root permissions, HALCON needs read/write permissions on the hidraw device created for the dongle. The following udev rule is required to achieve this:
# udev rules to allow access to hidraw device for CodeMeter dongles
ACTION=="remove", GOTO="halcon-cm_end"
SUBSYSTEM=="hidraw", ATTRS{idVendor}=="064f", ATTRS{idProduct}=="2af9", MODE="666"
LABEL="halcon-cm_end"
You can add this rule to /etc/udev/rules.d yourself, or copy the file $HALCONROOT/misc/linux/udev/rules.d/59-halcon-codemeter.rules to that directory. The udev rule must be activated after installation, which can be achieved by a reboot, for example.
hhostid shows no dongle ID on Linux even though a HALCON dongle is plugged in.

To be able to use the dongle on Linux, you must be running kernel version 2.6.39 or later with the following configuration options enabled:

  • CONFIG_HID
  • CONFIG_HIDRAW
  • CONFIG_TMPFS

These options are usually enabled on most Linux distributions. A common exception are embedded systems, for which one or more of these options may be disabled. In this case, hhostid is not able to access the dongle and a custom kernel including the required components must be built. To check if the running kernel has been built with CONFIG_HIDRAW enabled, run the following command:

gunzip -c /proc/config.gz | grep CONFIG_HIDRAW
Check the other configuration options analogously.

Returning floating licenses on Windows🔗

Problem
Applications using a HALCON floating license should return the license to the license server on exit so that it can be reused immediately. As socket communication is not possible during process termination, a process using HALCON cannot return floating licenses automatically on Windows by itself and requires the help of the license watchdog process hlwdog.
Solution

If the license watchdog is not available, return the license either by calling FinalizeHALCONLibrary() as described in Terminating HALCON Library or by calling the operator set_system with the parameter return_license.


Errors with HALCON/Python and floating licenses under Linux🔗

Problem
When using HALCON/Python and floating licenses under Linux, internal licensing errors (HALCON error #2082: Internal licensing error: Could not initialize HTTP session for URL) happen.
Solution
This problem can occur when the libcurl.so library shipped with HALCON cannot be loaded. This library uses the OpenSSL libraries, which are usually provided by the system. As some systems do not ship the OpenSSL 3 libraries, HALCON provides them as an extra SOM package. The problem arises because Python has already loaded the system libcrypto.so.3 library, which can be incompatible with the version shipped with HALCON.
If you encounter the licensing error above, ensure that this extra SOM package is not installed, by verifying that the $HALCONROOT/lib/x64-linux/thirdparty directory does not contain the libssl.so.3 and libcrypto.so.3 files.
In general, we recommend using the OpenSSL libraries of the system if possible.

License error after system time was changed🔗

Problem
After changing the system time, HALCON won’t work anymore.
For time-limited licenses like evaluation and Progress licenses, the system time must be synchronized to the real-world time and must not be changed. When changing the system time, the license became invalid.
Solution
If you encounter this problem, set the system time correctly. You may need to contact your distributor to get a new license file.

Starting HDevelopEVO fails (Backend)🔗

Message “There was a problem during startup of HDevelopEVO backend”🔗

Problem
Trying to start HDevelopEVO fails.
The dialog shows the error message There was a problem during startup of HDevelopEVO backend.
Possible Solution
Check that the backend executable (%HALCONROOT%\bin\x64-win64\hdevelopevo_backend[xl].exe file) was installed correctly. Re-run the installation via SOM.
A security software or antivirus software may interfer with hdevelopevo_backend.exe. On Windows, use the “Windows Event Viewer” to check for related crash events. Add an exception in the security software for hdevelopevo_backend.exe.

Message “Backend executable could not be found”🔗

Problem
Trying to start HDevelopEVO fails.
The dialog shows the error message Backend executable could not be found.
Possible Solution
Probably the backend executable (%HALCONROOT%\bin\x64-win64\hdevelopevo_backend[xl].exe file) was not installed correctly. Re-run the installation via SOM.

Other messages🔗

Problem
Trying to start HDevelopEVO fails.
The dialog shows error messages such as Failed to start HDevelopEVO backend, Backend tried to restart too often, or Backend exited unexpectedly.
Possible Solution
Verify that HDevelopEVO and HALCON are properly installed. If in doubt, re-run the installation via SOM.
Check the logs of security and antivirus software. The backend needs to be able to open a network port on 127.0.0.1.
The backend uses anti-debugging measures. Make sure the system does not have forensic analysis software installed.