External Logs

This topic describes external logs that may be required during troubleshooting. Knowing where to find these logs is useful when scheduled report distributions fail, when report data appears incorrect, or when any other issue occurs.

Log

Purpose

Where to find

IIS

Records all HTTP requests handled by IIS and can help diagnose communication issues between the browser and the server.

Identifies communication issues such as failed page loads, authentication problems, or unexpected status codes.

1. Open File Explorer and navigate to the IIS log folder (where nn is the IIS site ID):
   C:\inetpub\logs\LogFiles\W3SVCnn
2. Open IIS Manager and select the site.
3. Locate the ID value in the right‑hand panel.
4. Return to
   C:\inetpub\logs\LogFiles
   and open the folder matching that ID (for example, W3SVC14).
5. Open the most recent log file and review the status codes. Codes other than 200 indicate an error.

SQL Execution

Records all SQL queries processed by the BI Service, including Product ID, Data Model ID, View ID, User ID, SQL statement, execution time, timestamp, and Environment ID.

Important: This log is not purged automatically. It's recommend to create a SQL Server Agent job to purge the table according to customer requirements.

1. Open SQL Server Management Studio.
2. Connect to the SEI database.
3. Run the following query:
   SELECT * FROM SEI.dbo.LOG_SQL_EXECUTION
   .

SQL Server

Stores SQL Server–level events related to database accessibility, server operations, and internal SQL errors.

Helps explain SQL-related errors found in the BI Service or other SEI logs.

1. Open SQL Server Management Studio.
2. Expand Management.
3. Select SQL Server Logs to view available log entries.

SQL Usage

Records all view executions processed by the BI Service, including Product ID, View ID, Data Model ID, success status, timestamp, and Environment ID.

Important: This log is not purged automatically. It's recommend to create a SQL Server Agent job to purge the table according to customer requirements.

1. Open SQL Server Management Studio.
2. Connect to the SEI database.
3. Run the following query:
   SELECT * FROM SEI.dbo.LOG_VIEW_USAGE
   .

Windows

Captures system and application events through the Windows Event Viewer.

Helps identify BI Service restarts, Job Service failures, unhandled exceptions, and issues with Windows components used by SEI. Highlights that ASP.NET and .NET Runtime logs often contain detailed warnings or errors.

1. Open the Windows Start menu and search for Event Viewer.
2. Launch Event Viewer.
3. Select Windows Logs > Application to view relevant entries.

← Back to Help Center