Events that occur on Microsoft Dynamics NAV Server instances are recorded in the following logs:

• Microsoft Dynamics NAV Server channel logs in the Applications and Services Logs
  By using event channels, events that occur on a Microsoft Dynamics NAV Server instance are recorded to specific Microsoft Dynamics NAV Server logs in the Applications and Services Logs. Channels provide a way to collect and view events from a specific provider, which in this case, Microsoft Dynamics NAV Server. This differs from the Windows Application log which contains system-wide events from multiple publishers (applications and components).
  To view Microsoft Dynamics NAV Server instance events in Event Viewer, in the console tree, choose Applications and Services Logs, Microsoft, DynamicsNAV, Server. The events are recorded in the following logs, according the event channel to which they belong:
  

  Log	Description
  Admin	Includes events that target end users and IT administrators. These events typically indicate a problem that requires action to resolve the problem. An example of an admin event is a tenant database failing to mount on the Microsoft Dynamics NAV Server instance.
  Operational	Includes events that provide information about an operation that occurred on Microsoft Dynamics NAV Server instances. These events are typically ordinary operating events that do not require any action but can be used to analyze and diagnose a problem. An example of an operational event is the shutting down of the Microsoft Dynamics NAV Server instance.
  Debug	Includes trace events that occur on Microsoft Dynamics NAV Server instances. For more information about the different trace events and others ways to monitor them, see Microsoft Dynamics NAV Server Trace Events and Monitoring Microsoft Dynamics NAV Server Event Traces. Note In Event Viewer, this log is hidden and disabled by default. For information about how to show and enable this log, see How to: Use Event Viewer to Collect and View Trace Events.

• Application log in the Windows Logs
  The Windows Application log includes admin and operational type events (errors, warnings, and information messages) that occur on the Microsoft Dynamics NAV Server instance.
  To view the Application log in Event Viewer, in the console tree, choose Windows Logs, Applications.
  The events in this log are the same events that are recorded in the Admin and Operation channel logs for Microsoft Dynamics NAV Server in the Applications and Services Logs. Therefore, you can consider the Windows Application log to be a secondary log for Microsoft Dynamics NAV Server events. Unless you are using System Center Operations Manager to monitor Microsoft Dynamics NAV Server events, you can disable logging Microsoft Dynamics NAV Server events to the Windows Application log and rely on Applications and Services Logs instead. For more information, see How to: Disable Logging Events to the Windows Application Log.
  

  Note
  Trace events are not included in this log.

For more information about how to use Event Viewer, see Windows Event Viewer.

Filtering Microsoft Dynamics Server Events in Event Viewer

You can use the Get-WinEvent cmdlet of Windows PowerShell to view Microsoft Dynamics NAV Server instance events and trace events in the event logs and event tracing log files on the Microsoft Dynamics NAV Server computer. The Get-WinEvent cmdlet retrieves the same events that can be viewed in the Microsoft Dynamics NAV Server logs (Admin, Operational, and Debug) in the Applications and Services Logs of Event Viewer.

The Get-WinEvent cmdlet includes several parameters that enable you to filter the events that you view and specify how the events are displayed. Windows PowerShell enables you can create scripts that perform complex operations for extracting and displaying specific event data. For more information about the Get-WinEvent cmdlet, see Get-WinEvent.

For more information about installing and getting started with Windows PowerShell, see Getting Started with Windows PowerShell.

To use the Get-WinEvent Cmdlet to view Microsoft Dynamics NAV Server events

To enable the Microsoft Dynamics NAV Server Debug Log from Windows PowerShell

1. On the computer that is running Microsoft Dynamics NAV Server, start Window PowerShell as an administrator.

2. At the command prompt, enter the following command:

   	Copy Code
   wevtutil.exe set-log “Microsoft-DynamicsNav-Server/<Debug>” /q:true /e:true

Tip
You can also enable the Debug log from Event Viewer. For more information, see Enable Analytic and Debug Logs.

Filtering Microsoft Dynamics NAV Server Events

You can filter the events that you view in a Microsoft Dynamics NAV Server log by setting the FilterXpath parameter of the Get-WinEvent cmdlet. The following examples illustrate how you can use the FilterXpath parameter to filter the Microsoft Dynamics NAV Server events.

Example 1

The following example uses the Get-WinEvent cmdlet to view errors in the Microsoft Dynamics NAV Server Admin log for the tenant MyTenant1 on the server instance MyNavServerInstance1.

	Copy Code
Get-WinEvent -LogName 'Microsoft-DynamicsNav-Server/Admin' -FilterXPath "*[System[(Level=2)]] and *[EventData[Data[@Name='tenantId'] and (Data = 'MyTenant1')]] and *[EventData[Data[@Name='serverInstanceName'] and Data='MyNavServerInstance1']]" | Format-List -Property Message-

Example 2

The following is an example of a Windows PowerShell script that you can create and run to view trace events in the Microsoft Dynamics NAV Server Debug log. The script returns the start and stop C/AL function trace events that take more than four seconds to execute on the tenant MyTenant1 of the server instance MyNavServerInstance1.

Copy Code

$maxAllowedSeconds = 4 $xPath = "*[System[(EventID = 400 or EventID = 401)]] and " +          "*[EventData[Data[@Name='tenantId'] and (Data  = 'MyTenant1')]] and " +          "*[EventData[Data[@Name='serverInstanceName'] and Data='MyNavServerInstance1']]"            $events = Get-WinEvent -LogName 'Microsoft-DynamicsNav-Server/Debug' -FilterXPath $xPath -Oldest -MaxEvents 10000 Write-Host "List of AL functions that took more than $maxAllowedSeconds  seconds to execute :" -ForegroundColor DarkYellow for($i = 0; $i -lt  $events.Length; $i+=2) {    $seconds = ($events[$i + 1].TimeCreated - $events[$i].TimeCreated).Seconds    if ($seconds -ge $maxAllowedSeconds )    {      Write-Host $events[$i].Message `r`n -ForegroundColor Magenta    } }

You can create the script by using, for example, Notepad or Windows PowerShell Integrated Scripting Environment (ISE). You save the script as .ps1 file type, and then run it from the Windows PowerShell.

Concepts

Other Resources