BioStar2 RevisionNotes V2.7.5 EN
BioStar2 RevisionNotes V2.7.5 EN
Revision Notes
Version 2.7.5
EN 301.00.BS2 V2.7.5
Precautions when upgrading BioStar 2
· Do not install BioStar 2 on a PC where BioStar 1 is installed. This may cause performance problems.
· If BioStar 2.3.0 is installed on top of a BioStar 2.2.1 or 2.2.2 installation, all information stored in the SQLite
database is migrated to a new MariaDB database.
· To upgrade BioStar 2.5.0 or less versions of BioStar 2 to the latest version, you must install all versions of
BioStar 2.5.0 or less. For example, to upgrade from BioStar 2.3.0 to BioStar 2.7.5, you need to install the all
of BioStar 2.5.0 or less version. BioStar 2.5.0 or later can upgrade to the latest version immediately.
· If you are using Windows 8.1 or Windows Server 2012 R2, install the KB2919355 update by referring to the
following web page.
https://support.microsoft.com/en-us/help/2919355/windows-rt-8-1--windows-8-1--and-windows-
server-2012-r2-update-april-2
· If you are using MS SQL 2014 Express, install the Service Pack 2 by referring to the following web page.
https://www.microsoft.com/en-us/download/details.aspx?id=53168
· If MS SQL Server and BioStar 2 are installed on different PCs, you should install the Native Client on a PC
with BioStar 2 installed.
https://www.microsoft.com/en-us/download/details.aspx?id=50402
· When backing up a database from an older version of BioStar 2, disable all services and procedures.
Furthermore, if you do not back up and restore the AC database and the TA database together, you will
not be able to use the TA database.
· If you want to back up the database of BioStar 2.7.5, be sure to also back up the enckey in the \Program
Files\BioStar 2 (x64)\util folder. Otherwise, the database will be unavailable.
2. Bug Fix
2.1. The iCLASS Seos and DESFire Advanced card formats are not applied when the administrator sets
up the smart card layout.
2.2. If an administrator set a device as an Arm / Disarm device in the Intrusion Alarm Zone, and then
exclude the door that is configured by that device, a 'Failed to parse JSON (700)' error occurs.
2.3. If user group information is not created normally when an administrator adds or edits a user group,
the user list is not displayed when that group is selected.
2.4. Even if an administrator adds more than 249 custom levels, only 249 are displayed on the screen.
1.1. If you set a language that has more than two characters for the language delimiter in the resource
file, that language will not properly be applied to the T & A menu.
1.2. One of the BioStar 2 configuration files, the nssm.exe, is not installed or has been deleted from
the T&A and Video web server services list because some antivirus programs have determined
that the file is a malicious program.
1.3. The door information of access level setting is displayed differently from the setting.
1.4. When operating the Delete From Device in the USER menu, devices belonging to the group
cannot be selected.
3. Bug Fix
3.1. The Dual Authentication setting does not display properly in the user interface even if you enable
that option in elevator settings.
1.1. Arabic does not display properly if an administrator exports the T&A report in PDF.
1.2. When an administrator logs in as the custom level, even though the administrator has
permissions to a specific device and the user, cannot transfer users to that device.
1.3. If upgrading to version 2.7.0 or later, the administrator cannot add a leave in a previously
set schedule.
1.4. When there are more than 50 user groups, you cannot export the T & A report to a CSV file if
any groups contain subgroups.
3. Bug Fix
3.1. When creating an Access Group, the setting is not applied properly if you add the same user to the
User Group and User at the same time.
3.2. If an administrator edits the settings of the device on the server, Server Private Msg option on that
device will always change to disabled.
3.3. The T&A function does not work properly if you upgrade from version 2.7.0 or earlier to 2.7.2.
1.1. If more than 16 cameras are added to the server, the camera screen is not output.
1.2. In an environment that uses an MS SQL Server database, the server restarts when an
administrator adds more than one signal input event to the trigger & action of the device.
3. Bug Fix
3.1. The HTML tag is displayed in the daylight saving time settings page.
3.2. Once an image file set with a graphics map is deleted, the graphics map image cannot be modified.
3. Bug Fix
3.1. Support to the OM-120 Relay time setting value from 1 second.
1. Bug Fix
1.1. The duplicate logs are output when a user runs CSV export.
1.2. The server receives requests with a version lower than TLS 1.1 (Supports TLS 1.1 and above).
1.3. The user cannot set the same action for different triggers when setting Trigger & Action, Intrusion
Alarm Zone, or Interlock Zone.
1.4. The assignment complete message is displayed even if a user assigns an already assigned card to
another user using the API.
1.5. When a user who does not have permission on the door menu logs, the door list of the zone menu
is disabled.
1.6. The Add Zone option is not displayed when a user right-clicks each item in the zone menu.
2. Bug Fix
2.1. The Video menu in Settings is not displayed on the screen if the PC with BioStar 2 is not connected
to the network.
2.2. If an elevator group that contains subgroups moves to a child of another elevator group, it causes
an error and BioStar 2 does not work normally.
2.3. RTC and DHCP are displayed on Display/Sound of XPass D2(XPD2-GKDB) device page.
2.4. The firmware upgrade notification does not appear even though connecting XPass D2(XPD2-GKDB)
that has a previous version firmware to BioStar 2.
2.5. XPass D2(XPD2-GKDB) succeeds in authentication if AoC ID is entered as keypad even though server
matching is enabled.
2.6. If an upper and lower group without elevator is moved at the same time, the group is not displayed
normally.
2.7. If the date format is set on the device and then it is connected to BioStar 2, the date format changes
to the different option.
2.8. Scanning the fingerprint on the BioMini causes an error and BioStar 2 does not work normally.
2.9. If the user name is set to Arabic, the name does not display normally.
2.10. Fixed a security vulnerability that allows a user account to acquire an administrator permissions.
2.11. BioStar 2 version upgrade fails when using Java 1.8.0 or later on PC with BioStar 2 installed.
2.12. Some records are missing in T&A reports.
2. Bug Fix
2.1. Issue where BioStar 2 log continues to be displayed as daylight saving time even after the set period
of daylight saving time has ended.
2.2. Issue where the video server does not work if the video license is activated offline.
2.3. Issue where it is not possible to change configurable options when a user with administrator logs
in from a mobile device.
2.4. Issue in version 2.4.1 or earlier where database does not migrate and login page does not appear
when a version upgrade has been carried out while HTTPS default port is used.
2.5. Issue where server does not retry after failing to connect to database.
2.6. Issue where device is not auto-synced when face template has been deleted.
2.7. Issue where device secure communication status can be changed to ‘Disabled' even when user login
ID, password, and PIN have been set.
2.8. Issue where page display error occurs when device details page is accessed with OM-120 and DM-
20 disconnected.
2.9. Issue where after a daylight saving time schedule has been set up on BioStar 2 server, a daylight
saving schedule cannot be assigned to FaceStation 2 device.
2.10. Issue where model names of XPass D2 and BioLite N2 are not correctly displayed in the firmware
upgrade list.
2.11. Issue where daylight saving time cannot be set up for FaceStation 2 device when version 2.6.0 has
been installed newly.
2.12. Issue regarding selecting start date for daily schedule or selecting holiday dates where an extra
month is added to the resulting screen in the case of months without a 31st day.
2.13. Issue where it is not possible to set system log storage period to 120 days.
2.14. Issue in a version upgraded from version 2.5.0 where USB Agent does not start automatically when
user account control is set to default value.
2.15. Issue where incorrect IP address notification pop-up appears when a string is entered in the server
address field.
2.16. Issue where video server does not shut down when changing database port.
2.17. Issue where NVR details screen is displayed when scrolling the page with arrow keys at the upper
1. Bug Fix
1.1. Issue where it is not possible to sync new logs to Time Attendance and Video when using MSSQL.
1.2. Execution time error when upgrading version 2.4.1 > 2.5 > 2.6.
1.3. A change has been made so that moving is possible only when upgrading to a new version and the
version of existing BioStar 2 is 2.5.