In some cases, we may need to get detailed logs from your system. To get the highest level of detail, we'll need to enable trace logging.
This will produce a log file, which can then be emailed to our support team.
- In Windows file explorer, browse to the base directory for the application
- For the POS / Printer Service, this is usually C:\Program Files\Online Ordering\POS Integration for Online Ordering or C:\Program Files (x86)\Online Ordering\POS Integration for Online Ordering
- In that directory, there should be an existing NLog.config file
- Copy the Trace Logging code file into the directory, replacing the existing file
- Restart the app or service in question to enable the new log settings
- Reproduce the issue in question, to generate a log file
- The log file will be located at C:\online_log.txt
- Email the log file to Orders2me Support
- After the error is resolved, trace logging should be disabled to avoid creating very large files. Repeat the above process with the Normal Logging code file
---------------------------------
Trace Logging
<?xml version="1.0" encoding="utf-8" ?> <nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <targets> <target name="logfile" xsi:type="File" fileName="C:\online_log.txt" layout="${longdate}|${level:uppercase=true}|${logger}|${message}|${exception:format=tostring:maxInnerExceptionLevel=2}|${callsite}" /> </targets> <rules> <logger name="*" minlevel="Trace" writeTo="logfile" /> </rules> </nlog>
---------------------------------
Normal Logging
<?xml version="1.0" encoding="utf-8" ?> <nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <targets> <target name="logfile" xsi:type="File" fileName="C:\online_log.txt" layout="${longdate}|${level:uppercase=true}|${logger}|${message}|${exception:format=tostring:maxInnerExceptionLevel=2}|${callsite}" /> </targets> <rules> <logger name="*" minlevel="Error" writeTo="logfile" /> </rules> </nlog>