The OPC Server is capable of generating detailed diagnostics log file that can assist in troubleshooting problems. This is only possible with Debug build of the software, which is only made available to users who have need for it. Note that the Debug build should not be used in normal production scenarios, because it may have lower performance.

The Debug build behaves the same as Release build under normal circumstances. In order to gather the diagnostics information into a disk file, specific changes need to be made into the registry, and the server restarted. The .REG file containing the necessary registry values is here:

Settings-JCN2OPCServer-Diagnostics.zip (465 Bytes)

This .REG file can be passed on a command line to REGEDIT. On 64-bit systems, you must use the 32-bit version of REGEDIT, typically located under C:\Windows\SysWOW64 (yes, SysWOW64 indeed!).

Whenever the server starts, it will create (in the folder where the executable resides) a new file, called CrtReport-YYYYMMDDhhmmss.log, where the letters after the dash will be replaced by current date and time. The file is being appended to while the server's executable is running; it is closed when the server stops.

After you run the tests, you will need to provide the files to OPC Labs technical support. You can use the date and time information contained in the file name to identify and select the logs that are of interest.