ekey Error Codes Error Code Short Name Cause Message Resolution

Transcription

1 ekey s Short Name Cause Message Resolution Keybox Operating s 9026 Bad Cookie Keybox failed to decrypt a cookie Key Expired Keybox determines that a cookie is expired Not Enough Data 9029 Command Denied 902A 902B Unknown Cookie Type Invalid Operation Mode Key did not send enough data for a message during a KeyBox interaction. Command denied during KeyBox interaction not authorized or not permitted. The keybox is sent a cookie type it does not understand. An invalid operation mode was sent to the Keybox in the Start Connection command. 902C Bad Command The command is unknown, has unexpected data, or invalid options. 902D Invalid Expiration 9041 Bad Cookie Lockout The expiration date in the Config Cookie does not decrypt properly. The keybox is in Bad Cookie Lockout mode. Can be returned from any Keybox command Bad ID Cookie The ID Cookie cannot be verified by the Keybox Bad Config Cookie 9044 Not Owner of Keybox 9045 Invalid Challenge Response The Config Cookie cannot be verified by the Keybox. The command was denied because the Owner Only option was enabled for this command. The programming base response is ekey is not configured correctly. Key is expired. Not enough data. Command denied. ekey is not configured correctly. Invalid operation mode. Invalid command. Key is not updated. Authorization invalid. Authorization cannot be verified. Authorization cannot be verified. Connection failed. Please try function Not authorized to open KeyBox. An unknown operation mode was requested. Command unknown or contains unexpected data. Perform a wireless or obtain and enter an emergency update Lockout is in effect. Access only allowed to owner of KeyBox. Please try

2 9046 Copy Protection Violation 9047 No Public Information Area 9048 Clock Not Adjusted The Keybox is unable to retrieve the code (PIN. Shackle. Programming) due to KPin being The Keybox memory map is not configured properly. Clock adjustment values sent with the 0x4A command were invalid or caused an invalid date. The Keybox time does not get updated Key Locked Out The Key Serial number is in the lockout list of the box. 904A 906A 906B Crypto Keys Already Rolled Invalid Memory Address Read Write Permission Denied 906C EEPROM Failed 9070 One Time Access error A second crypto rollover was tried after an initial successful rollover. This error simply indicates that the rollover was already complete. A memory address is out of bounds. The current operation mode and permissions do not allow the memory address to be read or written. The EEPROM cannot be written because of a hardware failure. Keybox reports the GUID associated with One Time Access or One Time Cookie has already been used Incorrect PIN The user entered an incorrect PIN 9072 Incorrect Shackle 9073 Incorrect Programming 9074 Bad Lockout 9075 Obtain Key Lockout 9076 Key Not Updated The user entered an incorrect shackle The user entered an incorrect programming Too many bad codes have been entered. Have to wait 15 minutes and try Too many bad obtain key codes have been entered. Have to wait 15 minutes and try The cookies are not updated. Copy protection violation. Programming error. Clock not adjusted. Crypto already rolled. Operation denied. KeyBox failure. Key not updated. Access Denied. Incorrect PIN Access Denied. Incorrect Shackle Access Denied. Incorrect Shackle Key not updated. Contact Support. Invalid time entered. Key is on lockout list. Memory error. Verify shackle code and re-enter. Contact Field Support. Verify device permissions with administrator or obtain and enter an emergency access Verify PIN code and re-enter. Verify shackle code and re-enter. Verify shackle code and re-enter. Lockout is in effect. Lockout is in effect. Perform a wireless or obtain and enter an emergency update

3 9077 Wrong CBS 9078 Wrong Permissions 9079 Wrong Serial or System 907A 907B 907C 907D 907E Access Hour Restriction Key Container Lockout Charge Pump Invalid Update No More Access Log Entries User entered an incorrect CBS Cookie permission bytes to not match. A cookie does not match the serial number or system code of the Keybox. The keybox access hours do not allow access. The user did not respond in time to lift up the key container. The shackle or key container could not be opened due to internal hardware failure. Keybox fails to decrypt the renewal bytes in a cookie. No more entries are available in the access log. 907F Invalid time An invalid time is sent to the Keybox in the Write RTC command Low Battery Charge Pump 90E5 90E6 9A01 Firmware Flashing Started Invalid Checksum No Devices An Obtain Key or Release Shackle operation resulted in a low battery. Indicates firmware flashing has started and that the box will be inaccessible for a few minutes. The firmware written into memory is invalid and does not get flashed. Bluetooth discovery does not find any devices to communicate with. 9A02 Invalid Frame The key received a frame that was less than 2 bytes long. 9A03 9A04 Invalid Frame Ack Receive IO The first byte of a response frame does not equal the command ID or Ack ID. An IOException was caught while receiving a frame. Incorrect CBS Incorrect permissions. Incorrect serial or system Timed access restriction. Key container timed out. KeyBox failure. Key is not updated. No entries in the access log. Invalid date and/or time. Low battery. KeyBox not accessible. Invalid checksum. No devices are in range. Invalid Frame Ack Receive IO Send IO Verify CBS code and reenter. Access not allowed outside timed access hours. Please call listing agent. Perform obtain key operation Contact Field Support. Perform a wireless or obtain and enter an emergency update Contact Field Support. Please wait. Firmware flash not complete. Please make sure ekey is in range of Bluetooth ibox and try

4 9A05 Send IO An IOException was caught while sending a frame. 9A06 Parse An incorrect number of bytes were returned from a command. 9A07 KPin Lookup ekey failed to read the kpin value from local storage. This means that the local database is not initialized or corrupt. 9A08 Null Happens if a Null (Pin. Shackle, Programming) is passed to a java KeyboxClient command. 9A09 Too Long Happens if a code (Pin, Shackle, Programming) longer than 12 digits is passed to a java KeyboxClient command. 9A0A Client Busy Occurs if a Keybox command is started while a command is currently in progress. 9A0B 9A0C 9A0D 9A0E 9A0F 9A10 Cookie Lookup Discover Bluetooth Connect IO No Auth Cookies Update Keybox Update Pending SW Change Occurs when the Keybox Client cannot read a cookie from the Local Database. Occurs when a BluetoothException occurs during the device discovery sequence. Occurs when an IOException occurs while trying to connect to a Bluetooth device. Occurs when no Authorization Cookies are in the Local Database when sending the Obtain Key Authorize command. Occurs when a Keybox Snapshot cannot be saved to local storage. Occurs during a Release Shackle, Read Showings, Read Keybox, and Write Keybox. Occurs when a Keybox Software Pending Change record cannot be saved to local storage. Occurs during a Write Keybox command. 9A11 No Response Occurs when a zero length frame is returned from a Keybox or Translator. Parse Parse KPin Lookup Null Too Long Client Busy Cookie Lookup Discover Bluetooth Connect IO No Auth Cookies Update Keybox Update Pending SW Change No Response

5 9A12 9A13 9A14 9A15 Receive Timeout Authorization Cookie Not Bluetooth Disabled ekey Adapter Disconnected Occurs when the handheld does not receive a response from the Keybox or Translator within 30 seconds. This can occur during any command. Occurs when someone tries to communicate with a Keybox from a different system The error occurs because ekey will search its local database for an authorization cookie that matches the current keybox, and when the cookie is not, this error is returned. Occurs when the Bluetooth radio is disabled when attempting to start a keybox operation. (Android only) Occurs when the iphone ekey Adapter is disconnected during a keybox operation. 9A16 Wrong Keybox Occurs when you make changes to a Keybox and attempt to program a different keybox. 9D5D ekey Adapter IrDA Occurs when you point an iphone ekey Adapter away from a keybox after it has begun communicating. 9AFE Interrupted Occurs when the user cancels the operation. 9AFF 9B00 Unhandled Connect IO Occurs when an unhandled Exception is caught. esync s Indicates an IOException occurred when connecting to the server. 9B01 Send IO Indicates an IOException occurred while sending to the server. 9B02 9B03 Receive IO Receive HTTP Indicates an IOException occurred while receiving from the server. returned when an HTTP response does not return 200 OK from the server. 9B04 Verify IO Indicates an IOException occurred while parsing a response from the server. Time out waiting for Authorization not. Bluetooth Disabled. ekey Adapter was disconnected. Access Denied. IrDA communication failure. The operation was canceled. Unhandled Failed connecting to server. Failed sending data to server. Failed receiving data from server. Http error during receive. verifying Not authorized to open KeyBox. Enable Bluetooth in Android. Please connect the ekey Adapter and try Invalid keybox or keybox swapped during operation. Please keep the ekey Adapter pointed at the keybox and try

6 9B05 9B06 9B07 Verify XML SOAP Envelope Not SOAP body not Indicates an XmlPullParserException occurred while verifying a response from the server. returned when the response XML does not contain a node with an XML namespace = soap/envelope/ and name = Envelope. returned when the response XML contains a Soap Fault. 9B08 SOAP Fault returned when the response XML does not contain an XML node that is {soapaction}response where {soapaction} was the soap command that was just sent. 9B09 9B0A 9B0B 9B0C 9B0D 9B0E 9B0F 9B10 9B11 SOAP response not SOAP result not Prepare IO Authorize DS Sync Challenge DS Sync Challenge not Sync Not Invalid Sync format KPIN code not returned when the response XML does not contain a node with an XML namespace = soap/envelope/ and name = Body. returned when the response XML does not contain an XML node that is {soapaction}result where {soapaction} was the soap command that was just sent. Indicates an IOException occurred while preparing a command to send to the server. Indicates a DSSync tag was in an Authorize Client Indicates a DSSync tag was in an Challenge Indicates the Challenge tag was not in an AuthorizeClient Indicates the Sync tag was not in an AuthorizeClient Indicates the Sync tag was not in the correct format, which is non-null and divisible by two. Indicates the Kpin tag was not in an AuthorizeClient verifying XML Soap fault. preparing data for upload. Failed to authorize client. Challenge failed. Data format Please enter an ekey Authorization Please enter an ekey Authorization Please enter an ekey Authorization Please enter an ekey Authorization

7 9B12 9B13 9B14 9B15 9B16 9B17 9B18 9B19 9B1A 9B1B Invalid KPIN code format Save Sync Save KPIN Sync Location not Invalid Sync Location format New Sync Not Invalid New Sync Format Read Sync failure Security Response Not Save New Sync Indicates the Kpin tag was not in the correct format, which is non-null and divisible by two. Indicates that the Sync could not be saved to the database. Indicates that the Kpin could not be saved to the database. Indicates the SyncLoc tag was not in an AuthorizeClient Indicates the SyncLoc tag was not in the correct format, which is non-null. Indicates the NewSync tag was not in an AuthorizeClient Indicates the NewSync tag was not in the correct format, which is non-null and divisible by two. Indicates that the Sync could not be read from the database. Indicates that the SecurityResponse tag was not in the RespondToChallenge Indicates that the New Sync token could not be saved to the database after a valid response to the RespondToChallenge command. 9B1C Not Authorized returned when the Respond To Challenge SecurityResponse node does not contain the text Authorized. 9B1D 9B1E 9B1F 9B20 Server Response Not Meta data mismatch Upload status not Downlaod Data not Indicates that the ServerResponse tag was not in the SyncData Indicates that the AppID attribute of the ServerResponse tag did not match the value in the applications current meta data. Indicates that the UploadStatus tag was not in the SyncData Indicates that the DownloadData tag was not in the SyncData Data format saving data. saving data. Data format Data format Challenge failed. saving data. Not authorized. Unexpected Reset auth tokens.

8 9B21 9B22 9B23 9B24 Acknowledge not Acknowledge Failed Cookie Lookup failure Key Config Lookup Indicates that the Acknowledgement tag was not in the SyncAcknowledge returned when the Acknowledgment status is not equal to OK. returned when the Key Config cannot be loaded from local storage. returned when the Key Config cannot be loaded from local storage. 9B25 No Coverage returned when the Blackberry does not have BIS-B coverage available. 9BFE Interrupted Occurs when the user cancels the operation. 9BFF Unhandled Occurs when an unhandled Exception is caught. Failed to acknowledge sync. reading data from local storage. reading data from local storage. No network coverage. The operation was canceled. Unexpected.