LXE vx3x Verweisanleitung

Seite von 316
270 
AppLock Error Messages 
VX3X Reference Guide 
E-EQ-VX3XRG-D 
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 admin-hotkey press” is logged after the administrator has 
pressed the hotkey but prior to starting the switch process.  
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 
hotkey, the internal factory default is used. 
LOG_ERROR 
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 
processing. 
LOG_EX 
***************** 
The status information is being saved to a file and the 
file has been opened successfully. 
LOG_EX 
Address of keyboard hook 
procedure failure 
AppLock found the kbdhook.dll, but was unable to 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. 
LOG_ERROR 
Address of keyboard hook 
procedure OK 
AppLock successfully retrieved the address of the 
keyboard filter initialization procedure. 
LOG_EX