Concordance Server.log

C:\ProgramData\LexisNexis\Concordance Desktop\Working Path

This is the tab separated database output for the "logging" tab in the Admin Console. It is less complete and detailed

Limited effect

Concordance Server - YYYY-MM-DD.log

C:\ProgramData\LexisNexis\Concordance Desktop\Working Path

Saved copy of 'Concordance Server.log' for the day listed in the file name.

Limited effect

CNServer.YYYYMM.log

C:\ProgramData\LexisNexis\Concordance Desktop\Working Path

* Required when escalating issues*

Logs the action taken by the server. For example, removal of DCB's, Job indexing/reindexing, packing etc., license information/authentication, Ports, number of users allowed to connect to server (per proc limit) - all for the month listed in the file name.  

See Extended logging table

ServerCPU YYYY-MM-DD.txt

C:\ProgramData\LexisNexis\Concordance Desktop\Working Path

Internal data format for the Admin Console. This is now the charts get their data.

No effect

OverallCPU YYYYY-MM-DD.txt

C:\ProgramData\LexisNexis\Concordance Desktop\Working Path

Internal data format for the Admin Console. This is now the charts get their data.

No effect

Server Memory YYYY-MM-DD.txt

C:\ProgramData\LexisNexis\Concordance Desktop\Working Path

Internal data format for the Admin Console. This is now the charts get their data.

No effect

OverallMemory YYYY-MM-DD.txt

C:\ProgramData\LexisNexis\Concordance Desktop\Working Path

Internal data format for the Admin Console. This is now the charts get their data.

No effect

Concordance Admin Server.log

C:\ProgramData\LexisNexis\Concordance Desktop\Working Path

This is the tab separated data output for the "logging" tab in the Admin Console. It is a less complete and less detailed version of the CNSAdmin.YYYYMM.log for the Admin Console.

Limited effect

Concordance Admin Server - YYYY-MM-DD.log

C:\ProgramData\LexisNexis\Concordance Desktop\Working Path

Saved copy of "Concordance Admin Server.log" for the day in the day listed in the file name.

CNSAdmin.YYYYMM.log

C:\ProgramData\LexisNexis\Concordance Desktop\Working Path

* Required when escalating issue *

Logs/captures the settings in the Admin Console for the month listed in the file name.

See Extended logging table

DATImportLog_MM_DD_YYYY_HH_MM_SS.log

DatabaseLocation\logs

Logs the initial import of documents. (aka: the first load at db creation)

Name depends on the type of database created (initial load)

No effect

EdocImportLog_MM_DD_YYYY_HH_MM_SS.log

DatabaseLocation\logs

Logs the initial import of documents. (aka: the first load at db creation)              

Name depends on the type of database created (initial load)

No effect

EmailImportLog_MM_DD_YYYY_HH_MM_SS.log

DatabaseLocation\logs

Logs the initial import of documents. (aka: the first load at db creation)              

Name depends on the type of database created (initial load)

No effect

ImportLog_MM_DD_YYYY_HH_MM_SS.log

DatabaseLocation\logs

Logs the append import of documents into the database.

No effect

NAMEOFDATABASE YYYY-MM.LOG

DatabaseLocation\logs

Logs all log on/off activity to the database for that month.

No effect

OverlayLog_MM_DD_YYYY_HH_MM_SS.log

DatabaseLocation\logs

Logs the Overlay import of information into the database.

No effect

Concordance Desktop.YYYMM.log

C:\Users\"Username"\AppData\Local\LexisNexis\Concordance Desktop

* Required when escalating issues *

Logs all actions executed by the EXE for the month listed in the file name.

See Extended logging table

ImageBaseManagement.log

C:\Users\"Username"\AppData\Local\LexisNexis\Concordance Desktop

Each module has its own individual log file, as .NET programs do not share a log file.

No effect

CDV.log

C:\Users\"Username"\AppData\Local\LexisNexis\Concordance Desktop

Each module has its own individual log file, as .NET programs do not share a log file.

No effect

ProductionModule.log

C:\Users\"Username"\AppData\Local\LexisNexis\Concordance Desktop

Each module has its own individual log file, as .NET programs do not share a log file.

No effect

PrintingModule.log

C:\Users\"Username"\AppData\Local\LexisNexis\Concordance Desktop

Each module has its own individual log file, as .NET programs do not share a log file.

No effect

Admin Console Management

Enables logging for actions in the Admin Console that alter definitions such as, editing the name of a database.

Licensing

Actions such as, adding a license or verifying if a license is valid or expired, are logged with this options. Advanced diagnostics are available when Low Level is enabled as well.

When licenses that appear to be valid are not registering.

Tagging

Tag errors (note that at this time, tag operations are not heavily logged).

Server Commands

Shows the CNServer command diagnostics for all messages being sent to the server. This can become quite noisy, but may be required for some diagnostics.

When you want to verify that command traffic is happening.

Connections

Shows details of connections to the server, and actions upon those connections. Advanced diagnostics are available when Low Level is enabled as well.

Enable when extra information is needed, regarding needed  when a client successfully connected and disconnected. This information can help diagnose things that aren't errors, by tracking when the client signed on and left, and the extra information about their connection.

Networking

The details of lower level network protocols and traffic are exposed with this option. Advanced diagnostics are available when Low Level is enabled as well.

When you need to review network traffic, like packet sends and socket ports, showing extra information around the traffic.

Low Level

Enables extended logging of more data than the Base Options. For example, with Licensing enabled the log displays messages about a license registered. However, with Low Level enabled, the log also shows debug information that is used to diagnose even more details.

Enable this when development needs detailed logs. This expands and affects many of the other options. Some options require this option to be enabled in order to log detailed information, while others provide details without having to have this option enabled.

SQL

Internal Query Engine states and operations such as, when you have a failure to insert a record for a user. Most of these only show up in the log if Love Level is also enabled.

If there are problems where things are not getting inserted or queried, enabling this may help diagnose the SQL statements. This may be useful when unexpected data, for example, a user name with a Unicode character may have issues inserting.

Databases

Actions that happen on a database (DCB) such  as, creation or registration. Most of these only show up in the log if Low Level is also enabled.

Problems with opening databases or related.

Unicode Files

Shows extended information during the reading of Unicode files, helpful when diagnosing why a text file doesn't read correctly in some situations.

When trying to figure out if a file is Unicode, and if so, what type. This log data will  diagnose the path of that. For example, if you convert an OPT to Unicode, when the database is opened for any operation, that  information about the file will be logged.

Profile

Extends information during reading of profile data such as, a home directory from the user's profile.