| title | ms.custom | ms.date | ms.service | ms.reviewer | ms.suite | ms.subservice | ms.tgt_pltfrm | ms.topic | ms.assetid | caps.latest.revision | author | ms.author | manager |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Compatibility with Exported CAP Files | Microsoft Docs |
10/26/2016 |
windows-server-threshold |
networking |
article |
43a7fd36-f3ad-45df-8685-3b31af9f0913 |
15 |
greggigwg |
greggill |
ronstarr |
As previously stated, Message Analyzer enables you to export trace data in the .cap file format, which is the native file format for Microsoft Network Monitor. If you export Message Analyzer data to the .cap file format, it enables Network Monitor and other protocol analysis tools that support this format to open such a file. However, Message Analyzer only supports certain media types when exporting data to the .cap file format. Therefore, if you are saving trace data that contains frames that are unsupported, that data will not be exported. In addition, if no frames of the supported type are found in the trace data being exported, Message Analyzer will not export any messages and displays the following Trace Save Error message:
None of the messages could be written to file, therefore the file was not created
The media types that are supported by Message Analyzer when exporting trace data in .cap file format are described in the table that follows:
| Media Type | Value |
|---|---|
| Cap frame | 0 |
| Ethernet frame | 1 |
| ETW provider message (NetEvent) | 0xFFE0 |