Doors.NET v4.3.7 Release Notes

Doors.NET v4.3.7 Release Notes

Operating System Compatibility

Doors.NET software IS COMPATIBLE with:
(both 32-bit and 64-bit where applicable)

  • Windows 8.1
  • Windows 10 - all versions
  • Windows Server 2012 and 2012 R2
  • Windows Server 2016

All other operating systems are NOT SUPPORTED.

All suported operating systems are compatible with Microsoft.NET Framework v4.6.2 or greater.

 

 

SQL Server Compatibility

If SQL is ALREADY INSTALLED on your computer:

  • The Doors.NET installer will poll the host computer and use the SQL version that is already installed. This is true for both new Doors.NET installations and for Doors.NET upgrades.

If SQL is NOT INSTALLED on your computer:

 

64-bit computers:

  • If SQL server is not present, then SQL Server 2016 Express will be installed.

32-bit computers:

  • You must manually install the SQL revision appropriate for your operating system.
  • Keri recommends installing SQL Server 2014 (the last SQL Server supporting 32-bit computers).

The following link will take you to Microsoft's SQL Server Express 2014 download page:

https://www.microsoft.com/en-us/download/details.aspx?id=42299

 

Please Note

  • Doors.NET software installation will not begin if a Windows Update is in progress or a computer restart is pending due to a Windows Update. Make sure all Windows Updates have been completed prior to installing Doors.NET.

  • Visual Doors and Doors.NET software versions are tied together in terms of compatibility - therefore you should not use Visual Doors v4.3.6 with a Doors.NET version that is older than v4.3.6

 

Advance Notice - End of Maintenance and Development for Modem Communication

Keri is ending maintenance and development for modem communication on PXL and Entraguard products.

The next release of Doors.NET (v4.4.0) will be the final revision that supports modem communication.

 

 

Program Improvements

For Doors.NET

  • Corrected an LDAP Expiration Date issue with new additions via Active Directory.

  • Corrected a time schedules limit issue where if a user created more than 64 time schedules (which exceeds the defined maximum) the Never time schedule would not operate properly.
  • Corrected a grid labeling issue that prevented firmware updates on RIM units.
  • Updated the Doors.NET tray icon with Keri's new corporate logo.

  • Added the ability to recognize Cypress 37-bit format credentials to the Wiegand credential library.
  • Added the ability to recognize AWID 37-bit format credentials to the Wiegand credential library.

  • Added the 56-bit Mifare credential format to the standard Doors.NET credential set.
  • Corrected a report issue that prevented certain cardholder reports from running correctly.

  • Changed how certain field names are displayed. If the onscreen field is not long enough to display the full name, an overflow indicator is displayed in the field. Mousing over the overflow indicator opens a tooltip that shows the full text name.
  • Increased the character count for cardholder names from 16 characters per field to 40.

  • Added more detail to information provided in diagnostic logs.
  • Restored "Reader Offline" and "Reader Online" message triggers to global linkage and local linkage menus.

  • Restored a "select all" feature in cardholder search fields.
  • Corrected a COM address assignment issue with AD300 lock sets.

  • Updated SMS routing information for several carriers.
  • Addressed a connection issue by now having the Application Server close its socket connection to a Gateway should there be no activity from the Gateway after a certain amount of time. This ensures successful reconnection to the Application Server when the Gateway comes back online.

  • Added the ability to select the facility code for NXT-3R/3RE and NXT-5R/5RE, HID capable readers.

 

For Visual Doors

  • Corrected a modem connection issue that did not allow Autoconfiguration to initiate a connection to the access hardware.

  • Corrected a modem connection issue that had remote clients automatically dial the access control system upon starting. Remote clients should not attempt to connect to the system until an action requiring connection is performed.
  • Corrected the Visual Doors client to display an "update required" indicator for any changes that are made when the controller is offine.
  • Visual Doors was allowing the user to add more than the maximum supported number of time schedules for NXT controllers. 64 is the maximum supported number.
  • Corrected Operator Permission assignments for Neutron Controllers in Visual Doors.

  • Corrected an auto-config database refresh issue that prevented certain commands from being performed until Visual Doors was restarted.
  • Corrected an issue where deleting all controllers did not allow an access group to be deleted until after Visual Doors was restarted.
  • Removed the MS credential call out from the credential list for Neutron controllers in Visual Doors as MS cards are not allowed with Neutron.
  • Visual Doors was allowing the user to add more than the maximum supported number of time intervals per week for Neutron controllers. 50 is the maximum supported number.
  • Corrected multiple reporting issues in Visual Doors: 1) the UI only allowed Transaction Reports for specific hardware types, 2) closing, then reopening the program now clears all data for a fresh start instead of recalling past information, 3) removing focus from the report screen and returning to the screen now retains all information instead of resetting on-screen parameters to default values.
  • Change implemented to ensure dialog windows that require acknowledgement before allowing further system operation remain visible until acknowledged.
  • Corrected an issue that affected the creation of Access Groups for PXL controllers.
  • Corrected a Neutron Firmware Upgrade grid refresh issue that caused the same information to be displayed multiple times.
  • The tech support link on the home screen was directed to an out-of-date page. It has been changed to link to the correct page.
  • Corrected an issue where PXL controllers continued to show as online when the LAN/Ethernet communications cable was disconnected. Proper communications state is now displayed.
  • For PXL controller Transaction Reports, all possible inputs and outputs were displayed instead of only the active inputs and outputs.

 

For the PXL Gateway/Hardware

  • Keri no longer supports the Situation Manager via modem communication. The Situation Manager is intended for use in urgent situations and the slow performance of modem comunication makes the response time of this application unaccepatble.

  • Corrected an issue that prevented a manual request for PXL status via modem connection.
  • Corrected a modem connection issue that had remote clients automatically dial the access control system upon starting. Remote clients should not attempt to connect to the system until an action requiring connection is performed.
  • Corrected a modem issue that required multiple connection attempts before a successful connection was made for autoconfiguration and network updates.
  • Corrected a modem issue that prevented modem disconnection following lock, unlock, and temp unlock commands. This meant a manual disconnection had to be performed.
  • Corrected an error when determining whether or not an Entraguard unit required a Legacy license. Certain unit types were incorrectly being reported as Legacy.
  • Corrected a PXL controller offline reporting issue to ensure the controller's offline/online status is always correctly reported.

 

For the Neutron Gateway/Hardware

  • Corrected a communication issue that takes the Neutron gateway offline should the Neutron USB adapter be disconnected. The gateway now stays online, waiting for communication to be re-established.
  • Increased the LED display time used when annunciating certain events to ensure visual recognition.

  • Corrected a communication issue caused when the communication channel between PC and Neutron controllers is moved from one COM port to another or is moved between a COM port and an Ethernet port.

 

For the NXT Gateway/Hardware

  • Improved gateway memory usage in databases that have very large numbers of controllers and cardholders by pausing controller operations and  ensuring data processing commands are complete before restoring controller operations.
  • Corrected an NXT-6RK keypad configuration issue that affected dual verification and PINs with six or greater digits.

 

For Mercury Gateway/Hardware

  • Corrected an issue preventing Alarm Shunt reassignment from being recognized unless the gateway was reset.

 

For Assa Abloy Locks

  • Removed all configuration settings for ASSA Wi-Fi lock sets as Doors.NET no longer supports this product line.

 

 

Current Firmware Revisions

For NXT Controllers and Peripherals:

  • Standard NXT Controllers - 2.05.79
  • NXT Readers - 4.00.03
  • Standard Reader Interface Modules (RIMs) - 3.03.21
  • Wiegand-Only Reader Interface Modules (RIMs)
    • 3.03.21 provides single-line LED support for Wiegand-only RIMs
    • 3.03.10 provides dual-line LED support for Wiegand-only RIMs
  • 4x4 I/O Modules - 3.00.03
  • GIOX Motherboard - 1.00.21
  • GIOX Input Module - 1.00.10
  • GIOX Output Module - 1.00.10

 

For PXL:

  • Standard PXL Controllers - 8.6.09
  • Legacy PXL Controllers - 8.5.22 (requires a Legacy license for operation)

 

For Entraguard:

  • Standard Titanium and Silver - 7.8.02
  • Standard Platinum - 9.2.02
  • Legacy Titanium and Silver - 7.6.13 (requires a Legacy license for operation)
  • Legacy Platinum - 9.1.09 (requires a Legacy license for operation)

 

For Mercury Powered NXT Controllers:

  • MSC controllers - 1.291

 

For Mercury Security controllers

  • Mercury EP and LP controllers - 1.291 - Corrects a Mercury Security firmware issue - LP intelligent controllers will not properly handle leap year time calculations. After February 29th, 2020, Leap Day, the intelligent controller will report time and date incorrectly. LP intelligent controllers that are deployed in “legacy” mode are not affected. Additionally, MSC and EP series controllers, bridge products (M5, MS, and MI), and legacy controllers such as the SCP series are not impacted by this issue.

  • Corrects an issue where if more than one outgoing DHCP connection (SIOs or Host Comm) is configured, only one connection will be established.

 

For Neutron Controllers:

  • 01.00.19

Firmware Upgrades

NXT Firmware v2.05.79

  • Corrected an issue processing 8-bit burst PINs on keypad readers.

    • Related Articles

    • Doors.NET v4.9.0 Release Notes

      Doors.NET Release Notes - 01298-010 Rev. A Doors.NET v4.9.0 Software - 02635-010 Operating System Compatibility Doors.NET software IS COMPATIBLE with: Windows 8.1 Windows 10 - all versions Windows Server 2012 and 2012 R2 Windows Server 2016 Windows ...
    • Doors.NET v5.0.0 Release Notes

      Doors.NET v5.0.0 Release Notes Doors.NET Release Notes - 01298-011 Rev. A Doors.NET v5.0.0 Software - 02635-011   Operating System Compatibility Doors.NET software IS COMPATIBLE with: Windows 8.1 Windows 10 - all versions Windows Server 2012 and 2012 ...
    • Doors.NET v4.8.0 Release Notes

      Operating System Compatibility Doors.NET software IS COMPATIBLE with: (both 32-bit and 64-bit where applicable) Windows 8.1 Windows 10 - all versions Windows Server 2012 and 2012 R2 Windows Server 2016 Windows Server 2019 All other operating systems ...
    • Doors.NET v3.5.1.20 Release Notes

      Please read this document. It contains a summary of the latest information regarding this software release. Doors.NET v3.5.1.20 replaces previous release v3.5.1.19 SP1. NOTE: The Ingersoll/Rand reader line has been spun off into its own company. This ...
    • Doors.NET v3.5.1.22 SP1 Release Notes

      Operating System Compatibility Beginning with v3.5.1.22, Doors.NET software is NO LONGER COMPATIBLE with any version of Windows XP.   Doors.NET software IS NOT compatible with the Home/Basic version of Windows Vista and Windows 7. This is due to ...