Issues
For details on each issue, see the relevant topic from the link of the management number below.
HULFT IoT Manager
|
Management number |
Brief description |
Affected versions |
Version when it was corrected |
|---|---|---|---|
|
An update installation from HULFT IoT Manager for Linux (Region Edition) may fail |
2.2.0 |
2.3.0 |
|
|
File distribution function may not delete temporary files and may cause excessive storage usage |
1.2.0 - 2.1.0 |
2.2.0 |
|
|
Resources leak when Manager refers to the product information |
1.0.0 - 1.5.0 |
2.0.0 |
|
|
Even if the product key update failed, the screen might show as if the product key is updated correctly. |
1.3.0 - 1.5.0 |
2.0.0 |
|
|
If HULFT fails to start by some reasons during the users install HULFT IoT Manager, the installation fails. |
1.1.0 - 1.5.0 |
2.0.0 |
|
|
Files can be distributed to the HULFT IoT Agent instance whose status is "Standby". |
1.1.0 - 1.5.0 |
2.0.0 |
|
|
The deletion of HULFT IoT Agent might fail |
1.1.0 - 1.5.0 |
2.0.0 |
|
|
When the users update HULFT IoT Manager, if the application.properties file includes commented out lines, HULFT IoT Manager may convert only the rows that are commented out. |
1.4.0 - 1.5.0 |
2.0.0 |
|
|
The file upload to HULFT IoT Manager might fail. |
1.0.0 - 1.5.0 or 1.1.0 - 1.5.0 |
2.0.0 |
|
|
If the value of the particular items in a transfer log includes one or more commas, HULFT IoT Manager cannot register transfer logs that HULFT IoT Agent output. |
1.4.0 - 1.5.0 |
2.0.0 |
|
|
Next Scheduled Sync Time might show the later time than the intended schedule. |
1.0.0 - 1.5.0 |
2.0.0 |
|
|
The Change Profile screen might show the unintended profile. |
1.0.0 - 1.5.0 |
2.0.0 |
|
|
HULFT IoT Manager might fail an API authentication. |
1.3.0 - 1.5.0 |
2.0.0 |
|
|
When the incorrect value is set to the register a whitelist entry API function, the returned HTTP status code is not appropriate. |
1.0.0 - 1.5.0 |
2.0.0 |
|
|
The logs other than the target of truncation might be deleted by using the log truncation function. |
1.0.0 - 1.5.0 |
2.0.0 |
|
|
The registered job might not run |
1.1.0 - 1.4.1 |
1.5.0 |
|
|
Backup of PostgreSQL may fail when the user updates HULFT IoT Manager |
1.3.0 - 1.4.1 |
1.5.0 |
|
|
Services of HULFT IoT Manager for Windows might not start |
1.2.0 - 1.4.1 |
1.5.0 |
|
|
A login user who has an admin privilege cannot change own password |
1.4.0 - 1.4.1 |
1.5.0 |
|
|
HULFT IoT Manager does not restart after the change of host name |
1.3.0 - 1.4.0 |
1.4.1 |
|
|
If the characters that are longer than the specifiable length are written in a successful job or an unsuccessful job by using the "Modify Transfer Settings details" API function, the returned HTTP status code is not appropriate |
1.4.0 |
1.4.1 |
|
|
Unavailable characters can be set to the user password by using the "Create User" API function |
1.4.0 |
1.4.1 |
|
|
The maximum values for session timeout written in the User's Guide are wrong |
1.0.0 - 1.3.1 |
1.4.0 |
|
|
If you update Manager when an uploaded module is there, the module becomes unavailable |
1.2.0 - 1.3.1 |
1.4.0 |
|
|
If an auto resend retry is repeated more than 255 times, you may not refer or delete the receive logs correctly on the management screen of HULFT |
1.0.0 - 1.3.1 |
1.4.0 |
|
|
A MAC address of which the length is not 48 bits (6 bytes) can be registered to the whitelist |
1.0.0 - 1.3.1 |
1.4.0 |
|
|
You can register an incorrect MAC address to the whitelist |
1.0.0 - 1.3.1 |
1.4.0 |
|
|
You can specify transfer settings by using the existing file ID when you register transfer settings |
1.0.0 - 1.3.1 |
1.4.0 |
|
|
If Agent fails to connect Manager just after Agent started, the information that an Agent status display command (huliotinfo) outputs is incorrect |
1.3.0 - 1.3.1 |
1.4.0 |
|
|
On the Change Module Version screen, "Change Version" button is valid when no module is selected |
1.0.0 - 1.3.1 |
1.4.0 |
|
|
The Unit list on the Permission Settings tab cannot be sorted |
1.0.0 - 1.3.1 |
1.4.0 |
|
|
"Access Log Type" column in the Access Log screen cannot be sorted |
1.0.0 - 1.3.1 |
1.4.0 |
|
|
"File Name at Send Destination" column in Reception Settings cannot be sorted |
1.0.0 - 1.3.1 |
1.4.0 |
|
|
Symbol characters can be entered in the Agent Operation Settings screen |
1.0.0 - 1.3.1 |
1.4.0 |
|
|
The whitelist entry that includes colons cannot be registered |
1.0.0 - 1.3.1 |
1.4.0 |
|
|
Alphanumeric characters using 2 bytes codes for MAC address can be entered |
1.0.0 - 1.3.1 |
1.4.0 |
|
|
When you maximize or minimize the browser screen while the list of Units is displayed in the Change Unit screen, a part of the pulldown menu is displayed across the frame |
1.0.0 - 1.3.1 |
1.4.0 |
|
|
"User name or password is incorrect." is displayed when you log in Manager while the process of the database (PostgreSQL) has been stopped |
1.0.0 - 1.3.1 |
1.4.0 |
|
|
When you change Unit, no errors are displayed if you select the deleted Unit |
1.0.0 - 1.3.1 |
1.4.0 |
|
|
When you display the Transfer Settings Details screen by using FireFox, the long monitored file name is displayed across the frame |
1.0.0 - 1.3.1 |
1.4.0 |
|
|
Even if "DEFLATE compression" was specified for a transfer, "No compression" was displayed in the Compression Ratio field of the Transfer Log Details screen when the transfer failed |
1.0.0 - 1.3.1 |
1.4.0 |
|
|
No Units are displayed in the Unit list on the Permission Settings tab under Security |
1.0.0 - 1.3.1 |
1.4.0 |
|
|
When you search Unit by using Port Number on Receiver in the Unit List screen, an error does not occur even if you enter characters other than numerals |
1.0.0 - 1.3.1 |
1.4.0 |
|
|
When you change a Unit name, even if the number of entered characters exceeds the 64 characters, the text box appears without changing to red |
1.0.0 - 1.3.1 |
1.4.0 |
|
|
When you search trace logs by using a date and time on the Trace Logs screen, the Trace Logs of the unexpected date and time is displayed |
1.0.0 - 1.3.1 |
1.4.0 |
|
|
The messages to inform that an error occurred for the specific operations are not displayed while the connection to the database is disconnected |
1.0.0 - 1.3.1 |
1.4.0 |
|
|
The candidate names that do not coincident with the characters that are entered as a search condition in the Agent List screen are displayed |
1.0.0 - 1.3.1 |
1.4.0 |
|
|
If you enter multiple spaces in sequence when you specify a monitored file name, the monitored file name in which the multiple spaces become one space is displayed in the Transfer Settings screen |
1.0.0 - 1.3.1 |
1.4.0 |
HULFT IoT Agent
|
Management number |
Brief description |
Affected versions |
Version when it was corrected |
|---|---|---|---|
|
If the file size is changed while transferring a file, an incorrect end code is output to the receiving-side host |
1.0.0 - 2.3.1 |
2.3.2 |
|
|
Registering or updating the transfer settings of Profile causes memory leak in HULFT IoT Agent |
1.0.0 - 2.1.0 |
2.2.0 |
|
|
Starting HULFT IoT Agent causes memory leak |
2.0.0 - 2.1.0 |
2.2.0 |
|
|
In the Windows environment, when 2,147,483 seconds (approximately 24.8 days) elapses after OS starts, HULFT IoT Agent might continuously execute file triggers and polling processing without waiting time |
1.0.0 - 1.4.1 |
1.5.0 |
|
|
HULFT IoT Agent might fail to register the log to HULFT IoT Manager and it cannot record logs anymore |
1.0.0 - 1.4.1 |
1.5.0 |
|
|
If HULFT IoT Agent fails to establish a connection to HULFT at a start of file transfer, HULFT IoT Agent might not perform according to the "Connection retry count" that you set by using Operation Settings |
1.0.0 - 1.4.1 |
1.5.0 |
|
|
HULFT IoT Agent might execute a send processing of log information to HULFT IoT Manager every second |
1.4.0 - 1.4.1 |
1.5.0 |
|
|
If a file that is used by Agent is broken, Agent might not start |
1.3.0 - 1.4.0 |
1.4.1 |
|
|
When you specify one or more tags without an equal sign (=) in the settings file for Agent, start of Agent fails |
1.3.0 - 1.3.1 |
1.4.0 |
|
|
Remote Update is not executed very rarely |
1.0.0 - 1.3.1 |
1.4.0 |
|
|
If you specify a path that includes one or more spaces when you execute new installation, Remote Update fails |
1.3.0 - 1.3.1 |
1.4.0 |
|
|
Agent remarks information is once registered, you cannot erase it |
1.3.0 - 1.3.1 |
1.4.0 |
|
|
If you specify a path that includes one or more spaces when you execute new installation, automatic start may fail |
1.3.0 - 1.3.1 |
1.4.0 |
|
|
If you specify an existing directory for the installation directory, new installation may fail |
1.3.0 - 1.3.1 |
1.4.0 |
|
|
If a file whose data includes one or more '\0' characters is transferred by using a text transfer, the data is not transferred correctly |
1.2.0 - 1.3.1 |
1.4.0 |
|
|
When Agent activation fails, the information that an Agent status display command (huliotinfo) outputs is incorrect |
1.3.0 - 1.3.1 |
1.4.0 |
|
|
A monitored file may be detected repeatedly |
1.0.0 - 1.3.1 |
1.4.0 |
|
|
When you specify "job_exec_module" in the settings file (lockdown.conf), if one or more spaces are included in the path to the execution module, execution of the job fails |
1.3.0 - 1.3.1 |
1.4.0 |
|
|
When Agent automatically resends files, duplicate data might be transferred |
1.2.0 - 1.3.0 |
1.3.1 |
|
|
Agent might perform unexpectedly when a job before or after transferring files or a job after receiving files is executed |
1.3.0 |
1.3.1 |
|
|
When "job_exec_module" is specified in the settings file (lockdown.conf), the parameters that are used for starting a user command are not divided by spaces |
1.3.0 |
1.3.1 |
|
|
When "job_exec_module" is specified in the settings file (lockdown.conf), Agent might not transfer or receive files |
1.3.0 |
1.3.1 |
HULFT IoT EdgeStreaming
|
Management number |
Brief description |
Affected versions |
Version when it was corrected |
|---|---|---|---|
|
During insertion processing by the MySQL adapter, if writing to a database fails due to any reason, the data may become inconsistent |
2.1.0 - 2.3.1 |
2.3.2 |
|
|
For floating point number type data, if the value after the decimal point is "0", all digits after the decimal point are truncated and the number is processed as an integer |
2.0.0 - 2.3.1 |
2.3.2 |
|
|
When certain versions and later of JDBC driver for MySQL adapter are used, some functions cannot be used |
2.1.0 |
2.3.0 |
|
|
HULFT IoT EdgeStreaming Studio may hang when you stop a remote device execution from HULFT IoT EdgeStreaming Studio |
2.1.0 - 2.2.0 |
2.3.0 |
|
|
Multi-byte characters can be entered when importing projects |
2.2.0 |
2.3.0 |
|
|
Contents of the array-type script variables are not displayed in the debug information |
2.0.0 - 2.2.0 |
2.3.0 |
|
|
The "Show BQL" menu from "File" may be enabled even when a script is not selected |
2.2.0 |
2.3.0 |
|
|
Execution of a script may fail when the user creates and executes a script whose name includes a symbol |
2.0.0 - 2.2.0 |
2.3.0 |
|
|
When a script for a remote device is placed, errors cannot be detected even if data loss occurs |
2.2.0 |
2.3.0 |
|
|
When the plugin processing on the input side stops unexpectedly, many error messages may be output |
2.0.0 - 2.2.0 |
2.3.0 |
|
|
An invalid value is inadvertently set in some logics of mapping |
2.0.0 - 2.1.0 |
2.2.0 |
|
|
During insertion processing by the PostgreSQL adapter, acquisition of the column names for a table with table name "%" does not operate correctly |
2.1.0 |
2.2.0 |
|
|
When you select a script and execute "Open explorer" on EdgeStreaming Studio, the directory one level above the directory where the script exists is displayed |
2.0.0 - 2.1.0 |
2.2.0 | |
|
Floating point number type decimals cannot be written to integer type fields during insertion processing by the PostgreSQL adapter |
2.1.0 |
2.2.0 | |
|
Double-byte numeric characters are inadvertently entered in Numeric constant (integer) of the Mapper logic |
2.0.0 - 2.1.0 |
2.2.0 | |
|
If the installation path includes a space, when you open a script from Designer using "Open explorer," the "My Documents" folder opens |
2.0.0 - 2.1.0 |
2.2.0 | |
|
When all the scripts on the script canvas are selected using the Select All hot key ([Ctrl] + [a]) and then copied, an End operation, which is not available in EdgeStreaming, is inadvertently saved to the clipboard |
2.0.0 |
2.1.0 |
|
|
Double-byte characters are inadvertently entered in the value input fields for a portion of the adapters |
2.0.0 |
2.1.0 |
|
|
If [Run] is executed repeatedly on a remote device, unnecessary files may remain in the Work directory |
2.0.0 |
2.1.0 |
|
|
When a script is executed using the 32-bit Runtime module, where a value of 2147483648 or greater is specified for "Zero Padding" in mapping, an error occurs |
2.0.0 |
2.1.0 |
|
|
A double quotation mark (") is included in a column name of the CSV adapters, and the script cannot be executed correctly |
2.0.0 |
2.1.0 |
|
|
[Apply] on the Options setting window for Designer remains inactive |
2.0.0 |
2.1.0 |
|
|
When the input data in mapping is the largest value for INT64, "9223372036854775807", a negative value is output in Absolute Value |
2.0.0 |
2.1.0 |
|
|
When executing build a script, an incorrect message may be output |
2.0.0 |
2.1.0 |
|
|
A negative value or a value in exponential notation is inadvertently saved in "Size" in Zero Padding of mapping |
2.0.0 |
2.1.0 |
|
|
"-9223372036854775808" is inadvertently saved in Numeric Constant (Integer) for mapping |
2.0.0 |
2.1.0 |