Error and Event Logs
The application logs events or error messages to certain rolling log files, which may be found in the following locations:
Program |
Log |
Location |
Purpose |
Lucity Desktop |
rolling.log |
%APPDATA%\Lucity\Logs on the workstation machine for the current user |
Records the use of the Lucity Desktop and Lucity Administration Tool programs by the current Windows user on this machine. |
|
gslog.htm |
%APPDATA%\Lucity on the workstation machine for the current user |
Tracks Lucity Desktop's attempts to communicate with and update the geodatabase. |
Lucity Administration Tool |
rolling.log |
%APPDATA%\Lucity\Logs on the workstation machine for the current user |
Records the use of the Lucity Desktop and Lucity Administration Tool programs by the current Windows user on this machine. |
Lucity.User.Import.exe |
rolling.log |
%APPDATA%\Lucity\Logs On the workstation or services server for user running the .exe. |
Records the use and import process for the Lucity.User.Import.exe. |
Server Logs
Lucity Web |
rolling.log |
inetpub\wwwroot\[Virtual Directory]\logs |
Logs the activities of the Lucity Web program for all users connected to it. |
Lucity Web RESTAPI |
rolling.log |
inetpub\wwwroot\[Virtual Directory]\logs |
Logs the activities of processes run by the internal rest api. This includes processes for:
|
Lucity Services |
rolling.log |
%APPDATA%\Lucity\Logs On the server, under the user set to run the services |
Logs the activities of the Lucity PM service. Note: You have the ability to add Information level logging to the General category, which enables you to log stages of the process that creates a Work Order from a PM. Adding this information to the log can be used to troubleshoot issues such as Work Orders not being generated from PMs; however, this information can overload the log and should be removed after testing. Contact CentralSquaresupport for further assistance. |
Upgrade Logs
Client Maintenance |
ClientMaintenanceError.log |
%APPDATA%\Lucity on the workstation machine for the current user |
Records any errors that occur in client maintenance during configuration and the database upgrade. Errors are logged as part of the server/database upgrade, or when run manually from the desktop computer. |
Notes:
- Error logging is enabled by default, but additional logging options can be turned on in the corresponding logging.config. However, if mistakes are made while modifying the logging.config the associated program will not function.
- It is possible to configure the logs to write to the Event Viewer or to other places, such as a SQL database, a text file, or emails. Using alternate logging destinations requires additional coding by the end-user.