How to specify the location of Error Log files. (4220526)

Where are the LiteSpeed log files generated? LiteSpeed error log files may be so large or numerous that they must be stored somewhere other than default location. How can I change the location?

Large or numerous error log files. See LiteSpeed Help file for additional info regarding logging.

Thelocation of thelogis determined by the path in the HKLM/Software/Imceda/LiteSpeed/Engine/ErrorLogPath (the default is %\Program Files\Imceda\LiteSpeed\SQL Server\Engine\Logs or beginning with Version 4.8.4, C:\Documents andSettings\AllUsers\ApplicationData\Quest\Litespeedfolder). The log is a text file and will be named similarly to: SLS_5_8_2008-11_02_01-AM.Log
NOTE: These files must be manually deleted.

The location may be changed by updating the HKEY_LOCAL_MACHINE | Software | Imceda | SQLLiteSpeed | Engine | ErrorLogPath to the desired folder.

Beginning with Version 4.8, for sporadic problems, or problems that cannot be reproduced once logging is enabled, use Log Level 3. Log Level 3 is 'Verbose only on Failure' through the GUI or be set using scripts with the parameter @Logging=3. Log Level 3 generates a Verbose log file on each backup, but if the backup job completes as 'successful' then the log file is deleted. Therefore a log text file is always generated but only kept if the backup job fails.

To enable instance-wide logging settings, you would need to add a new registry key value.
The registry value to add: HKEY_LOCAL_MACHINE > SOFTWARE > IMCEDA > SQLLITESPEED > ENGINE >
Add a DWORD value LoggingMask (hexidecimal) and assign 2 or 3 based off the logging type, keep in mind the LoggingMask value is case sensitive.

IMPORTANT: Before making modifications to the registry, make sure to back it up and that you understand how to restore the registry if a problem occurs.

Note: There is not an automated setting to delete the resulting log files, they must be deleted manually.