Portable Link Audit Trail Events
| # | Event | Description |
|---|---|---|
| 22 | key configuration loaded | The key was given a file that changed its configuration settings. |
| 23 | key configuration transferred | The key was sent a command or configuration file. |
| 24 | key downloaded | The key produced a file containing events or other information about the key. |
| 0 | Portable Link already in database | Client attempted to issue an already present Portable Link (rare). |
| -1 | Portable Link is not in database | The Portable Link is not in the database and thus needs to be issued. |
| -2 | key is not in database | The key being used is not in the database and thus needs to be issued. |
| -3 | data file was bad | A key file uploaded to the server appears to be corrupt. |
| -4 | error talking to server | A generic event indicating unexpected error conditions on the server. |
| -5 | key download file invalid | The key file uploaded to the server is intact but malformed in some way. |
| -6 | valid PIN required | A personnel identification number is required before configuring this key. |
| -7 | programming job number required | A login number or programming job number is required. |
| -8 | programming job number not found | The given login number or job number was not found. |
| -9 | key/data mismatch | The file uploaded to the server does not appear to be from the correct key. |
| -10 | key addition denied | The server denied issuing the key for one or more reasons. |
| -11 | key already exists in database | Client attempted to issue a key that is already in the database. |
| -12 | unknown issue number | Given key or Portable Link issue number does not exist. |
| -13 | high security bit set | The key cannot be issued because its database flag is set (it's already being used in another database). |
| -14 | catalog does not exist | The client specified an account name that doesn't exist on the server. |
| -15 | key is not initialized | The key is new and thus the server needs to see its hardware information before further processing is allowed. |
| -16 | user is not logged in | (CyberAudit-Web Lite only) User is not allowed to configure keys because they are not logged into the web application. |
| -17 | cannot auto issue (IR Link or key) | Failed to automatically issue the Portable Link device or CyberKey (rare). |
| -18 | information from the grandmaster is missing | The Grand Master is new to the system and thus the server needs to download information specific to the Grand Master. |
| -19 | mission not cached | Client attempted to download a mission configuration that was not checked out to it. |
| -20 | locklist download doesn't match event download | The two files submitted for event processing are from different keys. |
| -21 | key type mismatch | The type of key presented to the client does not match the type as it exists in the database. For example, the user is trying to configure a programmer key as a normal user key. |
| -22 | Firmware update required | Not implemented at this time. |
| -23 | No permission to add new locks | The user gave a login number that does not have permission to add new locks to the system (and the key has new lock events). |
| -45 | Key Reset | The CyberKey was reset to clear invalid or corrupt data. |
| 1 | New PIN Accepted | The user entered and confirmed a new PIN as prompted. |
| 5 | Inspect CyberLock Blue | CyberLink has discovered a CyberLock Blue via an IR Encoder 10 |
| 6 | Access Codes Set for CyberLock Blue | Access Codes were loaded into a CyberLock Blue |
| 7 | CyberLock Blue Reset | Access Codes were cleared from a CyberLock Blue. It is now unprogrammed. |
| 8 | Configuration Verified CyberLock Blue | CyberLink has verified the CyberLock Blue received the correct configuration. |
| 9 | Clock Set CyberLock Blue | CyberLink set the clock on a CyberLock Blue from the server's clock. |
| 10 | Events Uploaded CyberLock Blue | CyberLink downloaded the audit trail from a CyberLock Blue and sent it to the server. |
| 11 | CyberLock Blue Programmed | CyberLink programmed a CyberLock Blue with a configuration from the server. |
| 12 | New CyberLock Blue Added to System | |
| 22 | Key configuration file loaded | This event is recorded by the CyberKey but reported with portable link audit trails. It occurs with Gen1 CyberKeys only. It indicates the CyberKey loaded a new configuration into its operating memory. |
| 23 | This event is recorded by the CyberKey but reported with portable link audit trails. It indicates it received a configuration update via the communicator. | |
| 24 | This event is recorded by the CyberKey but reported with portable link audit trails. It indicates the key's audit trail data was downloaded by the communicator. | |
| 82 | Mobile activation completed | A Generation 2 CyberKey Blue 2, CyberKey Blue 3 or CyberKey Flash met a delayed activation requirement via its Bluetooth® connection. |
| 84 | Deactivated by Bluetooth device | A CyberKey Blue 2 or CyberKey Flash CyberKey received a deactivation command from an Android or iOS Bluetooth device and will not open locks until it is activated again using the Bluetooth device. |
| 85 | Bluetooth connection verified | A CyberKey Blue 2 or CyberKey Flash CyberKey connected was verified to a permitted Android or iOS Bluetooth device. |
| 86 | Bluetooth disconnected | A CyberKey Blue 2 or CyberKey Flash CyberKey disconnected from a verified Android or iOS Bluetooth device. |
| 300 | key clock correction required | The key's clock has drifted from the server clock and needs to be corrected. |
Additional links
