Logs and error codes

All alerts from the QlikView services appear in the Windows event log.

Logging from QlikView Server

Detailed session logs are found in the logging directory, which is specified on the System>Setup>Logging tab in QlikView Management Console (QMC). The default location is %ProgramData%\QlikTech\QlikViewServer.

Log files can be set to split (that is, create new) daily, weekly, monthly, yearly, or never. Performance log intervals can be set from one minute and higher.

Setting the interval to be very small, for example, only one minute, may negatively impact the performance.

Session Log

A session is defined as a single user connected to a single document.

The session log is updated each time a session ends. This means no log entry is created when a session starts.

The file name of the session log is Sessions*.log, where * reflects the server name and the split interval. Each entry of the session log contains the fields listed below.

Field Description
Exe Type

Type of QVS build.

Example: “RLS64” = 64-bit release build

Exe Version

Full version number of QVS.

Example: “11.00.11076.0409.10”

Server Started Date and time when QVS was started.
Timestamp Date and time when the log entry was created.
Document QlikView document that was accessed.
Document Timestamp File timestamp of the document that was accessed.
QlikView User QlikView section access user ID (if used).
Exit Reason

Reason for session termination:

  • “Socket closed” = Client-induced termination
  • “LRU” = Terminated as Least Recently Used in favor of new user
  • “Shutdown” = Server-induced termination for other reasons
This is not a complete list, as the exit value in some cases comes from the operating system.
Session Start Time when the session was started.
Session Duration Duration of session in hours:minutes:seconds.
CPU Spent (s) CPU seconds spent by the session.
Bytes Received Bytes received by the server during the session.
Bytes Sent Bytes sent by the server during the session.
Calls Number of QlikView calls during the session (bidirectional).
Selections Number of QlikView selections made during the session.
Authenticated User Authenticated Windows NT® user ID (if any).
Identifying User Client user identification.
Client Machine Identification Client machine identification.
Serial Number Serial number of the QlikView client (installed clients only, that is, QlikView Desktop and Internet Explorer plugin).
Client Type

Client type used:

  • “Windows Exe” = QlikView Desktop and Internet Explorer plugin
  • “Ajax” = all clients that use the QVPX protocol
  • “Unknown”
Client Build Version Build version of the QlikView client.
Secure Protocol

Secure protocol used:

  • “On” when encrypted communication is used (typically Windows clients).
  • “Off” when non-encrypted communication is used.
Tunnel Protocol “Tunnel” when QVS tunnel communication is used.
Server Port Port used by the server.
Client Address Client IP number for the client that is connected to the server (through the port specified in the Server Port field above).
Client Port Client port.
CAL Type

Client Access License (CAL) type:

  • “User” = Named User CAL
  • “Session” = Session CAL
  • “Usage” = Usage CAL
  • “Document” = Document CAL
CAL Usage Count Number of Usage CALs.

Performance Log

The performance log is updated at the interval specified on the System>Setup>Logging tab in QMC. The default interval is five minutes. Additional entries are added whenever the server is started or stopped. The file name of the session log is Performance*.log, where * reflects the server name and the split interval.

Each entry of the log contains the fields listed below.

Field Description
Exe Type

Type of QVS build.

Example: “RLS64” = 64-bit release build

Exe Version

Full version number of QVS.

Example: “11.00.11076.0409.10”

Server Started Date and time when QVS was started.
Timestamp Date and time when the log entry was created.
EntryType

Entry type:

  • “Server starting” = Startup
  • “Normal” = Normal interval log entry
  • “Server shutting down” = Shutdown
ActiveDocSessions Number of document sessions* that has shown activity during the interval and still exists at the end of the interval.
DocSessions Total number of document sessions* that exists at the end of the interval.
ActiveAnonymousDocSessions Number of document sessions* with anonymous user that has shown activity during the interval and still exists at the end of the interval.
AnonymousDocSessions Total number of document sessions* with anonymous user that exists at the end of the interval.
ActiveTunneledDocSessions Number of document sessions* with tunneled connection that has shown activity during the interval and still exists at the end of the interval.
TunneledDocSessions Total number of document sessions* with tunneled connection that exists at the end of the interval.
DocSessionStarts Number of document sessions* that has been initiated during the interval.
ActiveDocs Number of documents loaded at the end of the interval in which there has been user activity during the interval.
RefDocs Number of documents loaded at the end of the interval for which there is a session at the end of the interval.
LoadedDocs Total number of documents loaded at the end of the interval.
DocLoads Number of new documents loaded during the interval.
DocLoadFails Number of documents that has failed to load during the interval.
Calls Total number of calls to QVS during the interval.
Selections Number of selection calls during the interval.
ActiveIpAddrs

Number of distinct IP addresses that has been active during the interval and still exists at the end of the interval.

Tunneled sessions and multiple users originating from the same IP cannot be distinguished.
IpAddrs

Total number of distinct IP addresses connected at the end of the interval.

Tunneled sessions and multiple users originating from the same IP cannot be distinguished.
ActiveUsers

Number of distinct NT users that has been active during the interval and still exists at the end of the interval.

Anonymous users cannot be distinguished.
Users

Total number of distinct NT users connected at the end of the interval.

Anonymous users cannot be distinguished.
CPULoad Average CPU load from QVS during the interval.
VMAllocated(MB) Size in MB of the virtual memory allocated by QVS at the end of the interval**.
VMCommitted(MB) Size in MB of the virtual memory actually used by QVS at the end of the interval. This number is part of VMAllocated(MB) and should not exceed the size of the physical memory in order to avoid unacceptable response times.
VMFree(MB) Size in MB of the unallocated virtual memory available to QVS**.
VMLargestFreeBlock(MB) Size in MB of the largest contiguous block of unallocated virtual memory available to QVS. This number is part of VMFree(MB).
UsageCalBalance “-1.00” = There are no Usage CALs.

*One user + one document = One document session.

**VMAllocated(MB) + VMFree(MB) = Total maximum virtual memory space available to the QVS process.

Event Log

The event log is updated each time a log entry is made in the Windows event log by QVS. The stored information is a mirror of the information written to the Windows event log. The file name of the event log is Events*.log, where * reflects the server name and the split interval.

Use the Event Log Verbosity radio buttons on the System>Setup>QlikView Servers>Logging tab in the QMC to set the verbosity level. Depending on the verbosity level selected, the following entries are written to the Event log:

  • Low: Error messages
  • Medium: Error and warning messages
  • High: Error, warning, and information messages

Each entry of the log contains the fields listed below.

Field Description
Server Started Date and time when QVS was started.
Timestamp Date and time when the log entry was created.
SeverityID

ID for the severity level:

  • 1 = Error
  • 2 = Warning
  • 4 = Information
EventID Unique ID for the event type.
Severity Event severity level:
  • Error
  • Information
  • Warning
Message Event description.

End-user Audit Log

The end-user audit log contains information on user selections, including cleared selections, activated sheets, application of bookmarks, accessed reports, and maximized objects.

A log file called AUDIT_<machinename> is saved to %ProgramData%\QlikTech\QlikViewServer.

Tick the Enable Extensive Audit Logging check box on the System>Setup>QlikView Servers>Logging tab in the QMC to enable detailed audit logging (for example, logging of all selections that come with a bookmark). However, the logging of user selections in QVS is based on how the current selections object works and therefore larger selections may not be logged in detail.
Field Description
Server started Date and time when QVS was started.
Timestamp Date and time when the log entry was created.
Document Path and name of the document that was accessed.
Type

Type of selection made (for example, “Selection” or “Bookmark”).

For an overview of the types available, see the table below.

User User name.
Message

Information on the type of selection or application of bookmark that was made in the document (for example, “Apply Server\Bookmark15”).

For an overview of the messages that can be posted in this field, see the table below.

The types and messages that can be posted in the Type and Message fields in the end-user audit log are listed below.

In the end-user audit log, “XXX” and “YYY” are replaced with values from the QlikView document.
Type Message Description
Bookmark Apply XXX Bookmark XXX was applied.
Bookmark Selection XXX Selection XXX was made because a bookmark was selected. Entries of this type are only logged when detailed audit logging is selected.
Export Sheet Object XXX Sheet object XXX was exported.
Maximize Sheet Object XXX Sheet object XXX was maximized.
Print Sheet Object XXX Sheet object XXX was printed.
Report Accessed report XXX Report XXX was accessed.
Selection Clear All All selections were cleared.
Selection XXX Selection XXX was made.
SendToExcel Sheet Object XXX Sheet object XXX was sent to Microsoft Excel.
Sheet Activated sheet XXX Sheet XXX was activated.
Session Collaboration Session Collaboration Initiated, ID:XXX A session collaboration with ID XXX was initiated.
Session Collaboration Session Collaboration user XXX joined session, ID:YYY User XXX joined the session collaboration with ID YYY.
Session Collaboration Session Collaboration user XXX left session, ID:YYY User XXX left the session collaboration with ID YYY.

The following example shows the resulting log entry when a bookmark (“Bookmark01”) is selected. The log has been put in a table for better overview.

Field Value
Server started 20130506T101733.000+0900
Timestamp 20130506T102328.000+0900
Document C:\ProgramData\QlikTech\Documents\Test.qvw
Type Bookmark
User QlikTech\jsmith
Message Apply Server\Bookmark01

If detailed audit logging is selected, the log entry above may be followed by one or more log entries that detail the selections that were made because the bookmark was selected. In these log entries, the Type field is set to “Bookmark Selection”.

Manager Audit Log

The audit logging provides the possibility to track changes to tasks and settings in the system in order to see who made the changes and when they were made.

The audit logs are stored in %ProgramData%\QlikTech\ManagementService\AuditLog. One folder per table is created. Each folder contains one file per day with the changes made to the tasks. The logs are tab separated files.

The entries found in the logs are listed below.

Entry Description
TransactionID Transaction ID, which is useful for keeping track of changes made simultaneously.
ChangeType Type of operation, Update (new or changed entries) or Delete (entries have been deleted).
ModifiedTime Time and date (in UTC) when the changes were made.
ModifiedByUser The user that made the changes in the user interface. System means that the change was initiated by the system and not by any user.
ID ID of the row (that was updated or deleted) in the table that was changed.

The following example comes from the AlertEmail table. The log has been put in a table for better overview.

TransactionID 455a241d-8428-4dc7-ba67-4ae7cb21cf3d
ChangeType Update
ModifiedTime 20100202T151254.000+0900
ModifiedByUser MyDomain\mjn
ID b3745325-cee7-4fe7-b681-9c9efe22fc5c
DistributionServiceID 8846d7dd-bb3f-4289-9c9b-b0ca71b7c3b2
EmailAddress mjn

The following example comes from the QDSCluster table. Note that TransactionID is the same for both examples. This means that the changes were made simultaneously.

TransactionID 455a241d-8428-4dc7-ba67-4ae7cb21cf3d
ChangeType Update
ModifiedTime 20100202T151254.000+0900
ModifiedByUser MyDomain\mjn
ID a37f242c-6d80-42da-a10c-1742d2ec927f
DistributionServiceID 8846d7dd-bb3f-4289-9c9b-b0ca71b7c3b2
QDSWebAdress http://computer-mjn:4720/qtxs.asmx
CurrentWorkorderID 96bff2dc-f1ea-84d2-b6c4-ea58bf5c98e5

Task Performance Summary

The task performance summary is used to log task performance information.

Proceed as follows to activate the task performance summary:

  1. Open the Settings.ini file in a text editor. The default location of the file is:
  2. C:\Windows\system32\config\systemprofile\AppData\Roaming\QlikTech\QlikViewBatch

  3. Locate the following section in the Settings.ini file:
  4. [Settings 7]

    InterfaceLanguage=English

    InstalledLIBID110={4D121C39-415E-11D1-934D-0040333C91CC}

  5. Add EnableQVBProcessSummary=1 at the end of the section to activate the task performance summary.
  6. The last row in the Settings.ini file must be empty.

  7. Save the Settings.ini file.
  8. Restart the QlikView Distribution Service (QDS).
  9. Once the QDS has restarted, the task log is updated. Example of task output:

    Name: qvb.exe, PID: 1360, Peak CPU: 50,0%, Peak Physical RAM: 26.00 Mb, Peak Virtual RAM: 21.69 Mb, Average CPU: 1,0%, Average Physical RAM: 24.47 Mb, Average Virtual RAM: 20.37 Mb, Peak Total CPU: 58,3%, Peak Total Physical RAM: 6143.49 Mb, Peak Total Virtual RAM: 12285.17 Mb, Elapsed Time: 00:00:36.4692722