This project has moved and is read-only. For the latest updates, please go here.

Some Helpful Information:

How to get an install log to send if you have a problem:
To obtain a log of an installation use the command line msiexec tool:
msiexec /i Liquesce_Setup.msi /l*v MyLogFile.txt
This will install your application and write a verbose log to MyLogFile.txt in the current directory.

and this for uninstall issues
msiexec /l*v MyLogFile.txt /uninstall Liquesce_Setup.msi

Log file locations

GUI logs will go into "${specialfolder:folder=CommonApplicationData}/Liquesce/Logs"
Service logs will go into "${specialfolder:folder=CommonApplicationData}/LiquesceSvc/Logs"
The above may well be hidden folders.
On XP they appear under C:\Documents and Settings\All Users\Application Data
On Win 7 they can be under C:\ProgramData and / or C:\Users\All Users

Log levels

Each log message has associated log level, which identifies how important/detailed the message is. NLog can route log messages based primarily on their logger name and log level.
NLog supports the following log levels:

* Trace - very detailed logs, which may include high-volume information such as protocol payloads. This log level is typically only enabled during development
* Debug - debugging information, less detailed than trace, typically not enabled in production environment.
* Info - information messages, which are normally enabled in production environment
* Warn - warning messages, typically for non-critical issues, which can be recovered or which are temporary failures
* Error - error messages
* Fatal - very serious errors


The Log levels can be changed in the Management application via the “Advanced Config Settings Menu” :-

Advanced Config Settings Menu

All changes within the dialog that shows up will need to be resent to the Liquesce service via the “Send Configuration” menu.

Last edited Oct 8, 2010 at 9:27 PM by smurfiv, version 9