Knowledge Base

Search Knowledge Base

KB #240104: Event IDs and Error Codes

Type:

Information

Summary:

Below are listed some of the Events that Encryptionizer writes to the Windows System and Application Event Logs. Some are informational, others indicate errors. This also lists some error and result codes you may see when running installers or utilities.

Additional Information:

Windows System Event Log

Source: nlemsql, nlemsql64, or nlemsys
Event ID:

  • 1170: Encryptionizer Kerner mode drivers started
  • 1171: Encryptionizer Kerner mode drivers expired
  • 1172: Encryptionizer Kerner mode drivers failed to start
  • 1177: Opening encrypted database
  • 1178: Closing encrypted database
  • 1179: Creating encrypted database
  • 1180: Insufficient resources while opening/creating an encrypted database. May also indicate exceeded allowed Instances in License definition.
  • 1181: I/O error reading/writing an encrypted database
  • 1183: First read of an encrypted file
  • 1184: First write to an encrypted file
  • 1185: Encrypted file deleted
  • 1190: File was encrypted
  • 1191: File was decrypted
  • 1192: File was re-encrypted

For 1181: see KB 240067

Windows Application Event Log

Source: Encryptionizer, NLMClient, NLMKey

Event ID:

  • 1002: License expiring in N days.  There is a temporary or evaluation license on the machine. Software will stop functioning when the license passes the expiration date.
  • 1101: parameter is incorrect
    Possible Causes: Likely ran nlrun.exe without specifying .sec file in command line
  • 1102, 1103 – varied messages

Status=2:: The system cannot find the file specified
Possible Causes:
– the Security Profile (secservr.sec) is missing from the BINN directory of the SQL instance that was secured.
– A remote profile was specified when securing the SQL instance but the remote profile file is missing or not accessible see KB240040: http://www.netlib.com/kb/display.php?kbid=240102

Status=32:: The process cannot access the file because it is being used by another process.
Possible Causes:
Occurs when SQL instance attempted to start outside of secservr. Master was encrypted. Since outside of secservr, the master was not opened but was locked by sqlservr. When secservr.exe tried to open the file, it could not access it.

Status=1206:: The network connection profile is corrupted.
Possible Causes:
– UKMK removed or changed after instance/application is secured.
– Hardware fingerprint changed after UKMK set, and the UKMK was locked to the machine. It is not recommended to use the Lock To Machine feature for UKMK on virtual machines.
– Hardware fingerprint changed if “Lock key to machine” option used when securing the instance/application. Could be caused by a machine name change, as well as actual hardware change.

Status=1326:: Logon failure: Unknown User name or bad password
Possible Causes:
A Remote Profile (Key stored in alternate location) was specified when securing the SQL instance but the Netlib Key Management Service does have access to the remote location. see KB #240040: Cannot start SQL Server or encrypted database is inaccessible when profile is on a remote machine

Status=1605:: Unknown Product
Possible Causes:
Most likely reason is the service or application secured is not supported by the license on the machine.

Status=1638:: another version of this product is already installed
Possible Causes:
Most likely reason is the license activated on the machine does not support the SQL edition or version secured.

Status=6006:: No keys defined for user.
Possible Causes:
Failure to complete the procedure outlined in KB Article 24008 – Securing Against the Sysadmin. For example, there may be other logins, besides SA, that are still in the SysAdmin Server Role.

Status=6007:: The specified file is not encrypted
Possible Causes:
In Encryptionizer for SQL, this may happen because “master must” is on, but Master is not encrypted. Can also happen if SEC profile indicates a particular file is required to be encrypted via the rules string, but was found not encrypted.

  • 1140: FIPS self test passed. Encryptionizer Key Management service started.
  • 1141: FIPs Software integrity test is failing. Encryptionizer Key Management service won’t start.
    Possible Cause: The module is corrupted or tampered. Incorrect module for version installed.
  • 1142: AES Known Answer Test failed
    Possible Cause: The algorithm test is failing. Error in the utility or registry entry is missing
  • 2000: Instance unsecured [InstanceName]
  • 2001: Instance secured [InstanceName]
  • 2002: UKMK Removed
  • 2003: UKMK Added
  • 2006: Instance resecured [InstanceName]
  • 2050: Removed SQL API’s
  • 2051: Added SQL API’s
  • 2060: Folder Unprotected [Folder path]
  • 2061: Folder Protected [Folder path]
  • 2062: Folder Unprotection Failed
    Possible Cause: Folder is open in browser or files are in use
  • 2063: Folder Protection Failed
    Possible Cause: Folder is open in browser or files are in use
  • 3004: NLMKey retrieved (EKM)
  • 3005: NLMKey warning (EKM)
  • 3006: NLMKey error
    Possible Error codes:

    • 1169: Key not found on EKM or insufficient permissions
    • 1231: Could not reach EKM server
    • 2601: Certificate not matched
  • 3201: EKM Client started
  • 3202: EKM Client start but there are issues access to EKM
  • 3203: EKM Client stopped
  • 3205: EKM Client connected
  • 3206: EKM Client attempting connection
  • 3207: EKM Client could not connect
  • 3208: EKM Client error. Host returned error [error code]
  • 5001: File encryption started
  • 5002: File encryption finished
  • 5003: File encryption unsuccessful
  • 5011: File decryption started
  • 5012: File decryption finished
  • 5013: File decryption unsuccessful
  • 5021: File re-encryption started
  • 5022: File re-encryption finished
  • 5023: File re-encryption unsuccessful
  • 5032: File validation successful
  • 5033: File validation unsuccessful
  • 6001: License Activated
  • 6002: License Activation attempt failed
    Possible Error Codes:

    • 5006: Too many failed activation attempts
    • 5008: Invalid License ID or activation password
    • 5010: Invalid License for Product installed, or invalid Product for License already activated
    • 5013: No Remaining Activations
    • 5018: No Remaining Deactivations (can still remove license but will not gain an activation to use elsewhere)
    • 5019: License expired (or support has expired when trying to activate or refresh)
    • 5022: Invalid system time. Time on machine does not match universal time. Clock out of sync.
  • 6003: License Refreshed
  • 6004: License Refresh attempted failed (see above error codes)
  • 6005: License Deactivated
  • 6006: License Deactivation attempt failed (see above error codes)
  • 6011: License has expired
  • 6012: Support for License has expired.

Other Error Codes:

This is a list of some other error codes you may see when installing, using a scripted installer, using the User Interfaces or the CLI’s:

  • 2, 3 = System cannot find the file/path specified. Typically a profile is missing or inaccessible
  • 82 = Could not create profile. Most likely bad path or insufficient permissions to path
  • 86 = Invalid password buffer. Likely invalid syntax when defining keys for scripted installers and CLI.
  • 87 = Invalid parameter was specified
  • 110 = Could not open executable or insufficient permissions
  • 1605 = Using a workstation license on a Server; or License does not support executable/service being secured.
  • 1608 = Invalid rules string was specified
  • 1638 = Insufficient License for level of SQL or MySQL  to be secured,
  • 5006 = Too many failed activation attempts
  • 5008 = Invalid License ID or activation password
  • 5010 = Invalid License for Product installed, or invalid Product for License already activated
  • 5013 = No Remaining Activations
  • 5018 = No Remaining Deactivations (can still remove license but will not gain an activation to use elsewhere)
  • 5019 = License expired (or support has expired when trying to activate)
  • 5022 = Invalid system time. Time on machine does not match universal time. Clock out of sync.
  • 6000 = Attempted to encrypt a file already encrypted
  • 6001 = Attempted to decrypt a plain text file
  • 6006 = Encryption key cannot be set. Causes could be expired license or drivers not loaded.
  • 6007 = Required file not encrypted. Key not delivered to secured process
  • 7000 = Attempted activation. License input file not found.
  • 7001 = Attempted activation. License ID not found.
  • 7002 = Attempted activation. License Activation Password not found.
  • 7003 = Attempted activation. License input file not correct format.
  • 7004 = Attempted License update. License Update file not valid.
  • 7005 = Attempting to activate an Evaluation license over a perpetual license.
  • 7053 = License information not found when attempting installation.
  • 7006 = Attempted activation. Cannot apply workstation license on server.
  • 7007 = Licensing server could not be reached.
  • 7008 = Cannot install newer build after support expiration. If support renewed, refresh license with the licensing server to update support expiration date stored on machine.
  • 7009 = Invalid System time.
  • 7010 = Invalid Product for License.
  • 7011 = This license must be activated with a downloaded License file.

    Last modified: 3/11/2025

    Top