During the last weeks we have received several support queries concerning two issues with HALCON 12 and dongle-bound licenses on Windows Systems. Here they are and the solutions to date:
- On 64-bit Windows, the Visual Studio extension HALCON Variable Inspect does not work out of the box in combination with dongle-based licenses. This issue is caused by a bug in the current HALCON installer: For using the 32-bit application Visual Studio in addition to the dongle drivers, the auxiliary DLL haspsrm_win32.dll has to be installed accordingly. As a quick workaround, please manually copy the file %HALCONROOT%FLEXlmx64-win64flexid9haspsrm_win32.dll into the directory %SystemRoot%SysWOW64.
After copying the file, the HALCON Variable Inspect can also be used in Visual Studio running on 64-bit Windows with dongle-based licenses.
- In specific cases, starting a HALCON application on Windows may take approx. 30 seconds. In particular, this occurs in cases when using a dongle-based license on a Windows system that is connected to a local network, but without access to the Internet. The reason for this delay is that Windows by default performs certificate revocation checks on signed DLLs like the ones used by our licensing software when connected to a network. If the network has no access to the Internet, Windows waits until the connection times out – which takes approx. 30 seconds.
This issue can be resolved by either connecting the PC to the Internet (which often will not be the intended solution) or adjusting the system settings concerning the Windows certificate checks. For this, please follow the official instructions to configure the revocation settings on your local computer. For more information, see the following MS Tech Net article: https://technet.microsoft.com/en-us/library/cc753863.aspx