Log Files

You can use the Longview Server Manager to manage and view various types of log files generated by the Longview Data Server. You can view detailed server activity, troubleshoot issues, review user activities, and more through the log files.

Note: During server startup, the Longview Data Server logs all lvsrvr.cfg configuration parameters and their values to the lv_dataserver.log file for auditing purposes.

To access the Log files page, click the Log files tile under the Functionality section on the Server Manager home page.

Refresh button

Click the Refresh button to refresh the log file lists when new log files have been added or deleted outside the Server Manager.

Search in Log files

In each functionality page, you can use the Search field to easily find the items you need. The search functionality allows to filter a list based on the text you type in the Search box. The Search functionality is available for all the tabs in each page. If you switch between the tabs in a functionality page, and apply the Search filter, each tab will display only the matched items.

Additionally, the Search functionality allows you to search folders and files under the sub-folders. For example, if you want to search a log file with the name starting from "event", then in the Search box, start typing event. The Search box will display all the files under folders and sub folders with the name event. For more information, see the following image:

To clear the search, delete the text in the Search box or click the Close button in the Search box.

Log File Tabs

The log files are organized into the following tabs according to their type:

Data server

Data Server logs (lv_dataserver.log) record all activities that occur on the Longview Data Server. This includes, but is not limited to, symbol maintenance, user maintenance, server model maintenance, specific activities performed by individuals, any errors encountered during the process, starting and stopping of servers, and restatement.

Note: If an error occurs during the restatement, the error is logged in the lv_dataserver.log, and a restatement error log is also created. The restatement error log is named restate_recalc_Errors_<timestamp>.log file. This allows you to more easily identify when a restatement has failed or encountered errors, as such issues could affect your data. Restatement errors can now also be found in the Recalc tab. For more information, please refer to the Recalc tab.

A server error log file (server_errors_<timestamp>.log) will now be generated whenever an error triggers the "servers have encountered errors" database status flag. This log captures detailed information about the error to aid in troubleshooting.

You can also archive Data Server logs, but the server_error log file cannot be archived. The archived logs are displayed on the Data Server tab. Please refer to Archiving Data Server log file below for more information.

Duplicate data

Duplicate data files (duplicates.txt) record duplicate data in your system. Please refer to Checking for duplicate data section in Application Administrator Guide for more information on the duplicate data.

Event

Event logs allow users to view error, history, and log files for event rules. These files are read-only and cannot be deleted from this location.
To delete these files, refer to the Deleting Event Information section in the Monitoring Events documentation.

Export

Export logs (<ExportName>_export.log) record the status and details of the export operation. The log file includes comprehensive information such as the number of rows exported from each table, the version the export was taken from, the success status, and any errors encountered during the export process. This detailed logging helps you to monitor and troubleshoot exports effectively.

The export log files are named <ExportName>_export.log, where <ExportName> is the name specified for the export at the time it was created.

Import

Import logs (<ImportName>_import.log) record the status and details of the import operation. The log file includes comprehensive information such as the number of rows imported into each table, any rows not imported, the success status, and any errors encountered during the export process. This detailed logging helps you monitor and troubleshoot exports effectively.

The import log files are named <ImportName>_import.log, where <ImportName> is the name specified for the export that was selected for the import.

Install

Install logs are created during the installation and upgrade of Longview. They contain information about changes made during the installation or upgrade of Longview Tax or Longview Close. These logs are organized into folders named based on the date and time of the installation.

Metadata Audit

Metadata audit logs are created when a metadata audit is reset. The log file includes the cleared metadata audit data, reset date, date range, categories, and comment if provided, the user who performed the reset, and the number of records reset. The file name contains the date and timestamp of the reset.
For more information on resetting metadata audits, refer to the Resetting the Metadata Audit Trail section in the Performing General Server Tasks of the Application Administrator Documentation.

Recalc

Restatement logs are generated in the Recalc tab whenever an error occurs during the restatement process. These logs provide detailed information to help identify the cause of any failures and track the progress of restatement activities. By reviewing the logs, you can quickly detect issues and take corrective actions to resolve them.

REST API

REST API logs include errors, import and export logs, generated when invoking Longview REST APIs. These logs are organized into folders named by the endpoint, method, and date and timestamp. For example: \restapi\solutions\data\na1401\get\20250317_134143.

Opening log files

To open log files in the Server Manager, follow these steps.

1. Click a required tab on the Log files page based on the type of log file you want to open. The tab button turns blue when selected and the log files associated with that tab are listed on the page.

   

2. Click the appropriate log file name, or the More options menu (ellipsis) in the Actions column of that row, and select Open.The log file opens in a text editor such as Microsoft WordPad. From here, you can read or save the file to local or network drives.

3. The log file opens in a text editor such as Microsoft WordPad. From here, you can read or save the file to your local or network drives.

   

Archiving Data Server log file

To archive a Data Server log file, follow these steps.

1. Click the Data server tab.

2. Select the lv_dataserver.log, click the More options menu (ellipsis) in the Actions column.

3. On the drop-down menu, select Archive.

   

4. In the Archive file pop-up that opens, rename the file for archiving if needed, and click Save.

   

5. The archived file appears on the log file list, and you receive a toast notification on the success of the archiving process.

Deleting log files

To remove a log file, follow these steps.

1. Click a tab on the Log files page based on the type of log file you want to delete. The tab button turns blue when selected and the log files associated with that tab are listed on the page.

2. To delete one or more log files, click the checkbox on the log file(s) you want to delete. To delete all log files under the tab, click the checkbox on the header row of the table and all log files are selected.

3. Click the Delete icon which appears on the right side of the tabs. A confirmation dialog opens.

   Note: You cannot delete the Longview Data Server Log (lv_dataserver.log) or all log files on the Data Server tab at once. However, you can delete multiple archived versions of the lv_dataserver.log file at once.
   Additionally, event log files cannot be deleted from Longview Server Manager.

4. Click Delete to delete the log file(s).

   

The selected log file(s) are deleted, and you receive a toast notification on the success of the deletion process.