Collecting information for troubleshooting: Difference between revisions
From OPC Labs Knowledge Base
(Created page with "Category:How to Category:Troubleshooting This article describes the assets that you need to collect for a successful "deep" troubleshooting. == Preparations == # For...") |
(→Preparations: fix link) |
||
| Line 5: | Line 5: | ||
# For OPC Classic, install OPC Analyzer. For OPC UA, install Wireshark. | # For OPC Classic, install OPC Analyzer. For OPC UA, install Wireshark. | ||
# For OPC UA, enable extended tracing (see [[ | # For OPC UA, enable extended tracing (see [[QuickOPC-UA: How to enable extended tracing]]). Configure it so that the information is logged to a file, and contains timestamps and other details. | ||
# For OPC UA, instrument your code so that EasyUAClient.LogEntry notifications are logged to a file, together with their timestamps and other details. | # For OPC UA, instrument your code so that EasyUAClient.LogEntry notifications are logged to a file, together with their timestamps and other details. | ||
# Instrument your code so that it collects and logs relevant application-specific occurrences, together with their timestamps and other details. | # Instrument your code so that it collects and logs relevant application-specific occurrences, together with their timestamps and other details. | ||
Revision as of 09:15, 24 May 2017
This article describes the assets that you need to collect for a successful "deep" troubleshooting.
Preparations
- For OPC Classic, install OPC Analyzer. For OPC UA, install Wireshark.
- For OPC UA, enable extended tracing (see QuickOPC-UA: How to enable extended tracing). Configure it so that the information is logged to a file, and contains timestamps and other details.
- For OPC UA, instrument your code so that EasyUAClient.LogEntry notifications are logged to a file, together with their timestamps and other details.
- Instrument your code so that it collects and logs relevant application-specific occurrences, together with their timestamps and other details.
- Enable logging on the side of the OPC server, if possible.
Assets to collect
We will need following files from you:
- Trace files from OPC Analyzer (for OPC Classic) or Wireshark (for OPC UA).
- Extended tracing output (for OPC UA only).
- EasyUAClient.LogEntry records (for OPC UA only).
- A log of relevant occurrences in your own application.
- OPC server log(s), if available.
In addition, please include any relevant observations and explanations as to what has been attempted and how the test ran.
