You are here:

Doors.NET Version 4.0.3.4

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.0.3.4 with a Doors.NET version that is older than v4.0.5.

Program Improvements

For Doors.NET

Updated our logo graphics to embrace our new, modern corporate branding.
Increased SQL database protection from Username/Password hijack attempts.
Added a check for SQL Server software when starting the License Manager. SQL Server must be installed before running the License Manager.
Now providing automatic cleanup of SQL backup files to protect hard drive storage space.
Changed the number of SQL backups to match the number of Doors.NET backups, protecting free space on the PC hard drive.
Added filtering to prevent each open client from managing Daylight Savings Time changes. It only needs to be done once.
Added an overflow indicator should data in a field be longer than the screen space provided for that field. Click on the overflow indicator to see all the dates in the selected field.
Corrected a grid refresh issue that could display the same information twice.
Updated corporate contact information within the software to reflect Keri's new address/location.
Added a check on Doors.NET software start up that prevents a login failure for having duplicate operator entries - This situation only appears if this is a new installation using a database upgrade from Doors32 to Doors.NET, and that database upgrade included an existing operator that has the Doors.NET default "admin" operator name.
Corrected an issue that prevented Global Linkage macros from being saved when the macro included specific combinations of multiple hardware types.
Changes implemented to ensure Live Event viewing rights per Operator permissions.

For Visual Doors

Corrected an issue when scanning for MSC controllers that caused the scanning grid to continually update making it difficult to select a specific controller.
Added auto-config progress messages to provide positive feedback on an ongoing controller search.
Corrected a cardholder name display issue that truncated a name being displayed at 16 characters.
Increased grid data entry checking to ensure program limits and boundaries are not exceeded.
Corrected several grid refresh issues ensuring immediate display of entered data rather than requiring closing then reopening the grid.

For PXL Controllers

Addresses PXL gateway instabilities when performing cardholder downloads. Ensures a credential download task has fully completed across all Secondary controllers before initiating the next download task.
Added checks to the PXL gateway to manage when multiple, concurrent tasks are performed to ensure all tasks are completed in a logical, sequential order, and are completed in a timely manner.
Improved the integrity of event collection on the PXL gateway when dealing with both gateway and controller offline conditions.

For Mercury Security Controllers

Added support for the Mercury Security LP hardware set.

Current Firmware Revisions

For NXT Controllers and Peripherals:

Standard NXT Controllers - 2.05.78
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)

Firmware Improvements

NXT Firmware v2.05.78

Improved internal message checking and handling to ensure proper system operation.

For Mercury Powered NXT Controllers:

MSC controllers - 1.27.2

The PHY IC used by Keri’s NXT and MSC controllers has gone end-of-life and was replaced by a newer PHY IC. Because of this, Mercury Security has made a change to the firmware to allow the firmware to detect and work with the new PHY IC. -

- This firmware revision is backwards compatible with older MSC controllers that are using the original PHY IC.

- MSC controllers using the new PHY IC must use this firmware revision or greater. This firmware revision will not allow manual firmware downgrades to revisions earlier than v1.27.2 on MSC controllers using the new PHY IC. On these controllers it will only allow upgrades to newer firmware revisions.

Click here for the software release history.