Versions 2020.2.19.0 and later:
LP360 and True View EVO 2020.2 introduce a new logging feature that can be enabled via the Diagnostics tab of the Project Settings dialog (File -> Project Settings -> Diagnostics).
- Enable Logging: Enables logging of information at the desired Log Level.
- Rotating Log Files: Recommended to use this setting to limit the space on disk that log files may consume on the machine. When the number of log files is reached and the file size attained for the last one , the logging will begin overwriting with the first log file.
- Number of Log Files: The total number of log files to generate.
- File Size (MB): Maximum log file size before a new log file will be created.
- Log File Path: The location and name of the log file to be generated. Ensure the users have write permissions to this location. For example, “C:\ProgramData\LP360\LP360Diagnostics.log”.
- Log Level: If user sets “Critical” as the level, then only Critical messages will be logged to log file. Here is a table to explain what will be logged when a log level is set.
|Log Level||Log types written to log file|
|Error||Critical + Error|
|Warning||Critical + Error + Warning|
|Information||Critical + Error + Warning+ Info|
|Debug||Critical + Error + Warning+ Info + Debug|
|Trace||Critical + Error + Warning+ Info + Debug + Trace|
What is log at each of these levels?
- Critical – The errors that should never happen and can bring down the processing or application get logged as critical.
- Errors – These errors can be user errors or data errors. The process stops or can produce the wrong results.
- Warnings – The warnings are like errors but the process can complete with these warnings and produces correct results.
- Information – Logs information like the process has started, obtained license…etc.
- Debug – The debug log information that may not be useful to an end user but can help a developer diagnose the problem.
- Trace – Logs any tracing information or the flow of the code. Trace logs may not be useful to the end user but will be useful to a developer to help diagnose the problem.
Versions prior to 2020.2.19.0:
|How do I enable/disable additional logging information within LP360?|
|To enable additional LP360 logging information: |
1. Create a text file called “EnableLP360Logging.reg”.2. Paste this into the contents and save the file:
Windows Registry Editor Version 5.00[HKEY_CURRENT_USER\Software\GeoCue Group\LP360]
“optDoEventLogging”=hex:013. With LP360 and ArcGIS closed, and as an administrator on the machine, double-click to add the entry into the registry.
4. Open ArcGIS and then desired MXD file.5. Browse to “C:\Users\%UserName%\AppData\Roaming\LP360”, where %UserName% is the user that is currently logged into the machine. There should be a file called LP360.log.
To disable additional LP360 logging information:1. Create a text file called “DisableLP360Logging.reg”.
2. Paste this into the contents and save the file:Windows Registry Editor Version 5.00
3. With LP360 and ArcGIS closed, and as an administrator on the machine, double-click to modify the entry in the registry.
|When logging is enabled a log file will be generated at “C:\Users\%user%\AppData\Roaming\LP360”. When requested, this may assist with some support cases. |
If you have any questions about the information provided in this article please contact support@LP360.com at any time.