AppLock Error Messages
Any messages whose first word ends in ‘ing’ 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 default | A hotkey is required. If there is a failure reading the | LOG_ERROR |
| hotkey, the internal factory default is used. |
|
|
|
|
App Command Line= <Command line> | Command line of the application being locked | LOG_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 | LOG_EX |
| processing. |
|
|
|
|
***************** | The status information is being saved to a file and | LOG_EX |
| the file has been opened successfully. |
|
|
|
|
Address of keyboard hook procedure | AppLock found the kbdhook.dll, but was unable to | LOG_ERROR |
failure | get the address of the initialization 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 AppLock system to reload. |
|
|
|
|
Address of keyboard hook procedure OK | AppLock successfully retrieved the address of the | LOG_EX |
| keyboard filter initialization procedure. |
|
|
|
|
Alt pressed | The Alt key has been pressed and trapped by the | LOG_EX |
| HotKey processing. |
|
|
|
|
Alt | Processing the hotkey and backdoor entry | LOG_EX |
|
|
|
Application handle search failure | The application being locked did not complete | LOG_ERROR |
| initialization. |
|
|
|
|
Application handle search OK | The application initialized itself successfully | LOG_ERROR |
|
|
|
Application load failure | The application could not be launched by AppLock; | LOG_ERROR |
| the application could not be found or is corrupted. |
|
|
|
|
Backdoor message received | The backdoor keys have been pressed. The | LOG_PROCESSING |
| backdoor hotkeys provide a method for customer |
|
| service to get a user back into their system without |
|
| editing the registry or reloading the device. |
|
|
|
|
6 - 13