Skip to main content

Version 2.8.9 (Build No. 2.8.9.53)

Release|2020-12-29

New Features and Improvements


  1. Stabilization of features for Mobile Access.

    • Supports Dynamic site.

    • Displays user information, such as photo, department, title, and period on the Mobile Access Cards.

    • Improves a user interface for resending Mobile Access Cards.

  2. Provides a guide on the screen when registering Visual Face on the mobile device.

  3. Renamed 'Email Setting' menu.

    • Before: Email Contents

    • After: Email Setting

  4. Renamed some events related to scheduled unlock zones.

  5. Updated some language resource files.

  6. Changed the names of db-converter log files.

  7. Changed to possible to edit the device's T&A settings only while the device is connected.

Main Fixes


  1. Extended auth mode gets disabled intermittently when multiple FaceStation F2 devices try to connect to the server simultaneously. Affects version2.8.8

  2. Punch logs were not displayed if the punch type was null in the updated individual reports by selecting the 'All Punches' option. Affects version2.7.10

  3. Punch logs were not recorded properly in the individual reports updated by selecting the 'All Punches' option. Affects version2.7.10

    • The 'Check In' log was only recorded in the report even though the user selected 'Check Out' on the T&A device.
  4. BioStar 2 could not connect with the TA database if using a port other than the default port when installed using MS SQL Windows authentication. Affects version2.7.14

  5. PIN authentication failed due to the device default hash key transmission error. Affects version2.4.0

  6. If both user data registered with a face template and user data registered with a visual face template were sent to FaceStation 2 and FaceStation F2 at the same time, the authentication failed on FaceStation F2. Affects version2.8.6

  7. T&A device synchronization problems

    • Devices added in DEVICE menu were not synchronized with the TIME ATTENDANCE menu.

    • FaceLite added in DEVICE menu were not displayed in the T&A device list. Affects version2.7.10

    • Devices added in DEVICE menu were not displayed in the T&A device list because the value of device group ID became null due to a synchronization problem. Affects version2.7.5

  8. When starting the T&A service, a user was automatically signed out of BioStar 2 and was not able to sign in again. Affects version2.8.4

    • When accessing the T&A service while a user was signed in to BioStar 2, 'Unknown error. Check the log file for detailed information' error message was displayed.
  9. If clicking Apply in the SERVER menu after setting the mobile access card option to 'Use', the setting was changed to 'Not Use'.

  10. An email notification about users who have reached their specified working hours was not sent even after configuring the SMTP setting of Automated Email. Affects version2.8.6, 2.8.8

Bug Fixes


  1. An error occurred when creating work history after running user sync with personal information DB turned on or off. Affects version2.8.0

  2. A migration error occurred when encrypting and decrypting personal information DB since the table name was checked incorrectly during the Swap process. Affects version2.8.0

  3. The calculation was not possible if the calculation scope of the parity bit was overlapped with the scope of the other parity bits when setting the Wiegand format.

  4. BioStar 1.x logs did not appear in the event log list after the log migration since the Temper column was not supported on BioStar 1.x. Affects version2.8.6

  5. BioStar 2 occupied excessive memory when logging in as a custom level administrator with permissions for a lot of user groups in an environment using the MS SQL Server database. Affects version2.8.7

  6. When issuing mobile cards, model names of some devices were not correctly displayed in the pop-up message. Affects version2.6.0

  7. Delay occurred when uploading event logs related with temperature from FaceStation F2 to the server and unnecessary logs, such as temperature data with zero value, were uploaded. Affects version2.8.6