Troubleshooting

Unlike OPC Classic, which relied upon the Microsoft COM/DCOM framework, OPC UA is a much simpler solution and requires fewer troubleshooting steps. See also:

Common problems are shown below:

Error

Description

Resolution

Bad_SecureChannelClosed when connecting a client to the server.

UA Server has rejected the certificate and closed the channel.

Launch the Configuration Tool and verify the UA Server and UA Client both trust each other's certificate. See:

Exception (AddressAlreadyInUseException)

When launching the Generic UA Server application you see:

HTTP could not register URL http://+:51211/UA/Sampleserver/. Another application has already registered this URL with HTTP.SYS.

This application can run interactively and as a Windows Service. In this case, the application has been launched interactively, but the Windows Service is already running. You can either:

  • Close the server you just opened.

  • Shutdown the service which is identified as: "UA COM Server Wrapper"

Tracing

Each application has a configuration file (*.Config.Xml) containing parameters for tuning the trace output from the UA .NET API. All logs are output to:

<application installation directory>\Logs\