Applies to: Exchange Server 2013, Exchange Online

Topic Last Modified: 2013-01-13

Use the Get-CalendarDiagnosticAnalysis cmdlet to troubleshoot calendar-related reliability issues. You can use this cmdlet to analyze calendar log data captured in your calendar diagnostic log files.

For information about the parameter sets in the Syntax section below, see Syntax.

Syntax


`Get-CalendarDiagnosticAnalysis -CalendarLogs <CalendarLog[]> <COMMON PARAMETERS>`


`Get-CalendarDiagnosticAnalysis -LogLocation <String[]> <COMMON PARAMETERS>`


`COMMON PARAMETERS: [-DetailLevel <Basic \| Advanced>] [-GlobalObjectId <String>] [-OutputAs <HTML \| CSV \| XML>]`

Examples

EXAMPLE 1

This example reads the logs for a user with alias Tony into memory, analyzes the logs, and produces the output in a CSV file.

This command collects the logs for a meeting with a specified MeetingID:

	Copy Code
$logs = Get-CalendarDiagnosticLog -Identity Tony - MeetingID 040000008200E00074C5B7101A82E008000000009421DCCD5046CD0100000000000000001000000010B0349F6B17454685E17D9F9512E71F

This command returns a detailed analysis in a CSV file.

	Copy Code
Get-CalendarDiagnosticAnalysis -CalendarLogs $logs -DetailLevel Advanced > analysis.csv

This command returns a basic analysis in the Exchange Management Shell output.

	Copy Code
Get-CalendarDiagnosticAnalysis -CalendarLogs $logs

EXAMPLE 2

This example pipes the output of the Get-CalendarDiagnosticLog cmdlet to the Get-CalendarDiagnosticAnalysis cmdlet and analyzes it.

	Copy Code
Get-CalendarDiagnosticLog -Subject "Weekly Development Meeting" \| Get-CalendarDiagnosticAnalysis

Detailed Description

You run the Get-CalendarDiagnosticAnalysis cmdlet to analyze calendar data you've retrieved using the Get-CalendarDiagnosticLog cmdlet. For more information, see Get-CalendarDiagnosticLog.

You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Calendar diagnostics" entry in the Recipients Permissions topic.

Parameters

Parameter	Required	Type	Description
CalendarLogs	Required	Microsoft.Exchange.Management.StoreTasks.CalendarLog[]	The CalendarLogs parameter specifies the Message ID of the calendar item you want to analyze. You can specify the logs you want to analyze by using the CalendarLogs parameter or the LogLocation parameter, but not both.
LogLocation	Required	System.String[]	The LogLocation parameter specifies the location of the calendar log files you want to analyze. You can specify the logs you want to analyze by using the CalendarLogs parameter or the LogLocation parameter, but not both. If you use this parameter and the logs you want to analyze are located in the C:\logs directory on the computer you're running the cmdlet on, use `"C:\logs"` as the parameter value. If the logs you want to analyze are located on a share, use the format `"\\ServerName\ShareFolder"` where ServerName\ShareFolder is the location of the log files on your network.
DetailLevel	Optional	Microsoft.Exchange.Management.StoreTasks.AnalysisDetailLevel	The DetailLevel parameter specifies the level of detail you want to see in the analysis output. The default value is `Basic` and returns a summary of the analysis. Specify `Advanced` to see a detailed report which includes all of the properties from the calendar logs. `Advanced` should be used only when detailed debugging is necessary.
GlobalObjectId	Optional	System.String	The GlobalObjectId parameter specifies the Global ID of the calendar item you want to analyze.
OutputAs	Optional	Microsoft.Exchange.Management.StoreTasks.OutputType	The OutputAs parameter specifies the file format you want to output into the Logging directory. The default value is `HTML`. The other output options are `CSV`, and `XML`.

Input Types

To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn’t accept input data.

Return Types

To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types. If the Output Type field is blank, the cmdlet doesn’t return data.