![TANDBERG ANALYTICS EXTENSION - Administrator'S Manual Download Page 20](http://html1.mh-extra.com/html/tandberg/analytics-extension/analytics-extension_administrators-manual_3499941020.webp)
Logs
TANDBERG Analytics Extension Admin guide
20
Logs
If you experience difficulties with the TANDBERG Analytics Extension, technical support may ask you
to supply log files along with a description of your issue. The follow sections outline the types of logs
available. For information on installer logs see
TANDBERG Analytics Extension Installation Guide
Application Logs
Problems with the Analytics Extension web interface or the Windows Service that initiates the update
jobs are logged in files located on the web server where the Analytics Extension was installed. Logged
events from the Analytics Extension web interface and the Analytics Extension Service are stored in
the following locations:
<Installation Dir>\TANDBERG\Analytics Extension\ReportingService\Logs
<Installation Dir>\TANDBERG\Analytics Extension \AdminWeb\App_Data\Logs
These files are plain text but are low level and intended for debugging purposes by TANDBERG
personal.
Database Logs
The data warehouse itself also keeps logs useful for troubleshooting; these entries are stored in the
database itself in the
table‟s
orc.ExecutionEventLog
.
orc.ErrorEventLog.
dwh.AppliedPatch
, and
dwh.InstallerEventLog
. These logs may be browsed using any SQL tool. To save all the entries in
these logs to a file:
1. Open
Management Studio
and connect to the database engine instance
2. Expand
Databases
, find your data warehouse database (
tmsng_dwh
by default)
3. Right-click on the database and
select “New Query”.
4. Set the Results to save to a file. Right click in the Query Menu, and select
Results to > Results
to File.
5. In the query window, type in the follow four commands
SELECT * FROM orc.ExecutionEventLog;
SELECT * FROM orc.ErrorEventLog;
SELECT * FROM dwh.AppliedPatch;
SELECT * FROM dwh.InstallerEventLog;
6. Click the
Execute
button to run the query. You will be prompted for a file name to save the results
to. This will be a CSV file of the output you can share with technical support if requested.