This article can be used to debug all Panorama versions.

Should some component of Panorama NovaView malfunction, Panorama Support might ask you to provide some logs in order to better understand the problem. There are several log files available for NovaView and Necto

Prior to sending any log, add the following two string values to the registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Panorama\Novaview X.X\Admin
DebugServer, value 1
DebugNewAdmin, value 1 

Notes:
1. DebugNewAdmin is only applicable to : Necto and NovaView  version 6.x
2. If your server is a 64-bit machine, the above registry path would be different:

 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Panorama\Novaview X.X\Admin

Video Guide to logs in Necto

#1 - Event Viewer Log (see detailed artice)

1. Clean the Event log before recreating the problem. This will help to identify the event that causes the issue
2. Go to Start -> Run -> eventvwr -> right-click on Application -> Save Log File As. Make sure that you send Support the file in .EVT format (or EVTX, if this is Windows Server 2008).
   

#2 Administration Service Log

(applicable to Necto11.x  and NovaView 6.x)

The file server-log.txt, found under :

yourdrive:\Program Files\Panorama\E-BI\Administration Service

If you are using 64 bit server, the location would be:

yourdrive:\Program Files (x86)\Panorama\E-BI\Administration Service

#3 Cube Service Log

(applicable to Necto11.x  and NovaView 6.x)

The file server-log.txt , found under yourdrive:\Program Files\Panorama\E-BI\Cube Service

If you are using 64 bit server, the location would be:

yourdrive:\Program Files (x86)\Panorama\E-BI\Cube Service

#4 Administration Database Log

(applicable to Necto11.x  and NovaView 6.x)
For this, you will need to open the Panorama Log Viewer.

Go to Start -> Programs -> NovaView -> Administration -> Log Viewer, choose "DB" as Log Source, click Load Log and then Export to Excel.

Note: This will not work on a 64bit machine.

#5 Flash Console (detailed article)

1. Open flashconsole.htm from client browser: http://panorama-server/flash/flashConsole/flashconsole.htm
2. Open another browser with welcomef.htm page ? and replicate the error
3. All the connection strings to and from the Server will be written to the Flash Console page.
4. Copy-paste its contents into notepad and send to Support.

#6 IIS Log

Useful to debug authentication and performance issues

Windows Server 2003

By default, it is the file last modified in the following directory: C:\WINDOWS\system32\LogFiles\W3SVC###, where ### is the site number of the Panorama site. This can be found in IIS. The default number for NovaView 5.5 is 1, and for NovaView 6.0 is 2.

Windows Server 2008

By default, it is the file last modified in the following directory: C:\inetpub\logs\LogFiles\W3SVC###, where ### is the site number of the Panorama site. This can be found in IIS. The default number for NovaView 5.5 is 1, and for NovaView 6.0 is 2.

#7 Java Log

(applicable to  NovaView 6.x, Web Access client)

There's 2 types of Java logging: standard and advanced.

When a problem has to be debugged on the client side, whether using Microsoft or Sun JVM, a Java console is used to output errors, exceptions and software debugging information.
When a problem has to be debugged on the client side, whether using Microsoft or Sun JVM, a Java console is used to output errors, exceptions and software debugging information.
Sun Java Console is under Tools->Sun Java Console in IE, or is also accessible from the Sun system tray icon (cup of Java). For detailed debugging please turn on the next options:

Then make the console visible in IE options:
If this is Sun Java: Tools>Sun Java console
If this is MS Java: View>Java console
There are two levels of logging in Panorama: 1. Standard ? always on by default unless specifically disabled
2. Extended ? this one is often required by Panorama support to debug problems. To activate:

1. Load the Panorama Applet
2. Move the mouse to the left top corner, point to the header of the view
3. Hold down Ctrl+Alt and double-click > A red triangle should appear in the corner of the title, it is the high debugging indicator:
   Whether in simple or advanced mode, the debugging information should be collected in the following way:
   
   1. Open a web browser and make sure Java Console is enabled
   2. Show it, make it visible > Load the problematic view and reproduce the problem.
   3. Switch to Java console, mark all the output and copy it to notepad
   4. Save the file as .txt file in UTF-8 encoding (!)

#8 Tree file log

(applicable to Necto and NovaView , all versions)

This logs all the MDX queries sent to the Analysis Services server. Follow these instructions

#9 Dashboard Internal Log

This log can help diagnose problems specific to the Dashboard. To enable it, find the file (on the server) ...\Panorama\E-BI\Dashboard\include\config.asp. In line 23 of the file, you will find the line :

• const LOGGER_ENABLED = False

change it to:

• const LOGGER_ENABLED = True

Re-open the Dashboard (no need to restart the services), and perform the problematic action. A log file with the name log_XXXXXXXX.txt (where XXXXXXXX is the date) will be generated under ...\Panorama\E-BI\Dashboard.

• NovaView 5.0 and above
• Log #1 ,2-3 and #5 (Flash console) applies to Necto 11.x