Operating System Related Restrictions
Problems May Occur When Using a Virtualization System
The launcher service is operated on a desktop basis. It operates in a way that takes appropriate actions after analyzing the communication data received from the webpage using the Windows service of the local desktop. Even with the same physical desktop, unknown problems may occur in some virtualization systems.
Querying by Message Box is Not Supported
Since the launcher service operates as a background service of the desktop, querying by opening a message box is not supported.
Information May Not be Delivered in Multiple Logins
When multiple users are logged in, the launcher service cannot distinguish which user is logged in, so information cannot be delivered properly when the application is operated.
For example, in the Windows operating system, if User A logged in and the account is switched to User B without logging out, programs in both accounts become active through the process and the launcher service cannot determine which account is issuing the command.
To prevent this, the existing user account should be logged out before another user logs in.
Web Browser Related Restrictions
When Using a Specific Browser, the Webpage Used Must be Registered as a Trusted Site
In the Internet Explorer (IE) version 9 or earlier, an error message saying ‘access denied’ may occur when using the JavaScript XMLHttpRequest.open method in different address access (Cross Domain). In this case, the communication data itself is not transmitted, and to communicate with the Windows service normally, the webpage address must be registered as a trusted site.
Problems May Occur if Different from the Specified JSON Format
Since information is transmitted in JSON format, problems may occur if it is set as not case-sensitive.
When Using Google Chrome, Certain Options Must be Enabled
This restriction has been solved for the launcher service version 1.1.0.24 or later.
Additional settings are required when used in Windows 7 operating system.
If you are using Google Chrome version 88 or earlier and the launcher service version 1.1.0.24 or earlier, then you can use this option. As this option is not supported in Google Chrome version 88 or later, the launcher service must be updated to version 1.1.0.24 or later.
As TLS 1.2 support is not included by default in the Windows 7 operating system, even if the launcher service is updated to version 1.1.0.24 or later, then the communication cannot be performed normally. Refer to the contents below to modify the registry settings of the user’s PC.
https://docs.microsoft.com/en-us/windows-server/security/tls/tls-registry-settings#tls-12
In the process of communicating with the locally installed launcher service, the Google Chrome browser may limit permissions of the localhost. If the option is not enabled, then the launcher service operates normally but the following error occurs when calling from the browser.
To solve this, you must change the Google Chrome browser settings to “allow invalid certificates for resources loaded from localhost”. Follow the steps below to enable this option.
1
Enter "chrome://flags/#allow-insecure-localhost" in the address bar.
2
Change the option of "allow invalid certificates for resources loaded from localhost" to "enabled".
3
Restart the browser and access the execution page again.