AppLock Error Messages
Any messages whose first word is an ‘ing’ word is output prior to the action described in the message. For example, “Switching to
For all operations that can result in an error, an Error level message is displayed when a failure occurs. These messages contain the word “failure”. These messages have a partner Extended level message that is logged which contains the word “OK” if the action completed successfully rather than with an error.
For processing level messages, “Enter…” is logged at the beginning of the function specified in the message and “Exit…” is logged at the end (just before the return) of the function specified in the message.
Message | Explanation and/or corrective action | Level |
|
|
|
Error reading hotkey | The hotkey is read but not required by AppLock. | LOG_EX |
|
|
|
Error reading hotkey; using | A hotkey is required. If there is a failure reading the hotkey, the internal factory | LOG_ERROR |
default | default is used. |
|
|
|
|
App Command Line= | Command line of the application being locked | LOG_ |
<Command line> |
| PROCESSING |
|
|
|
App= <Application name> | Name of the application being locked | LOG_ |
|
| PROCESSING |
|
|
|
dwProcessID= <#> | Device ID of the application being locked | LOG_EX |
|
|
|
Encrypt exported key len | Size of encrypt export key | LOG_EX |
<#> |
|
|
|
|
|
Encrypt password length= | The length of the encrypted password. | LOG_EX |
<#> |
|
|
|
|
|
Encrypted data len <#> | Length of the encrypted password | LOG_EX |
|
|
|
hProcess= <#> | Handle of the application being locked | LOG_EX |
|
|
|
Key pressed = <#> | A key has been pressed and trapped by the hotkey processing. | LOG_EX |
|
|
|
***************** | The status information is being saved to a file and the file has been opened suc- | LOG_EX |
| cessfully. |
|
|
|
|
Address of keyboard hook | AppLock found the kbdhook.dll, but was unable to get the address of the initial- | LOG_ERROR |
procedure failure | ization procedure. For some reason the dll is corrupted. Look in the \Windows |
|
| directory for kbdhook.dll. If it exists, delete it. Also delete AppLock.exe from the |
|
| \Windows directory and reboot the unit. Deleting AppLock.exe triggers the Ap- |
|
| pLock system to reload. |
|
|
|
|
Address of keyboard hook | AppLock successfully retrieved the address of the keyboard filter initialization | LOG_EX |
procedure OK | procedure. |
|
|
|
|
Alt pressed | The Alt key has been pressed and trapped by the HotKey processing. | LOG_EX |
|
|
|
Alt | Processing the hotkey and backdoor entry | LOG_EX |
|
|
|
Application handle search | The application being locked did not complete initialization. | LOG_ERROR |
failure |
|
|
|
|
|
Application handle search | The application initialized itself successfully | LOG_ERROR |
OK |
|
|
|
|
|
Application load failure | The application could not be launched by AppLock; the application could not be | LOG_ERROR |
| found or is corrupted. |
|
|
|
|
Backdoor message re- | The backdoor keys have been pressed. The backdoor hotkeys provide a meth- | LOG_ |
ceived | od for customer service to get a user back into their system without editing the | PROCESSING |
| registry or reloading the device. |
|
|
|
|
Cannot find kbdhook.dll | The load of the keyboard filter failed. This occurs when the dll is missing or is | LOG_ERROR |
| corrupted. Look in the \Windows directory for kbdhook.dll. If it exists, delete it. |
|
| Also delete AppLock.exe from the \Windows directory and reboot the unit. De- |
|
| leting AppLock.exe triggers the AppLock system to reload. |
|
|
|
|
Converted Pwd | Converted password from wide to mbs. | LOG_EX |
|
|
|
10 - 8