About Event Logging
The In-Sight OPC Classic Server Event Log maintains a history of various events that occur during configuration and while the server is in its Running state.
Events can be generated from different sources. The following table lists common events that are logged, along with a description of the event:
Event Source |
Event Description |
What This Means... |
---|---|---|
<sensor> |
Connection Closed |
The OPC Classic Server has disconnected from the sensor. |
<sensor> |
Connection Dropped |
The socket was closed. This can occur when Telnet recyclingTelnet recycling occurs when the maximum number of Telnet or Native Mode connections has been exceeded. The first connection will be terminated, thereby allowing the new connection to be established. is enabled. |
<sensor> |
Connection Established |
The OPC Classic Server was able to successfully connect to the sensor. |
<sensor> |
Connection Rejected |
This message can occur under the following circumstances:
|
<sensor> |
Incorrect Logon |
Either the server is configured with an incorrect logon for the sensor, or the sensor has a User Name or Password which does not match the OPC Server's configuration. |
<sensor> |
Initialized |
The OPC configuration was loaded and initialized. |
<sensor> |
Log On Successful |
The supplied user credentials were accepted by the sensor. |
<sensor> |
No Response Received |
This message can occur when communication to the sensor is lost (for example, if the sensor is disconnected from the network.) |
<sensor> |
OPC Failed to Initialize |
OPC is not supported on this sensor. Please verify the following:
If the sensor does not have at least 3.1.0 firmware, use In-Sight Explorer to update the firmware to the latest version. |
<sensor> |
Connection Closed |
The OPC Classic Server has disconnected from the sensor. |
<sensor> |
Connection Established |
The sensor has acknowledged the OPC Classic Server. |
<sensor> |
Failed to Send Data |
This error can occur:
|
Configuration File |
Config file was not found |
Either you have not yet created a configuration, or have saved an empty one. |
Configuration File |
New configuration was written |
A new configuration has been saved. |
Server |
Running |
The OPC Classic Server has been placed into its Running state. |
Server |
All clients disconnected |
The OPC Classic Server has been disconnected from each sensor in its configuration. |
Server |
No sensors found in configuration |
The configuration does not contain any sensors. |
Server |
DNS Resolution Failed |
The OPC Classic Server was unable to resolve the specified DNS name into an IP address; therefore, it was unable to establish communication with the sensor. |
Server |
Library Failed to Load |
An internal error has occurred. Please contact Technical Support. |
Server |
Server offline, clients still connected |
The server is suspended (no longer Running), but remote clients are still connected to it. |
Server |
XML Error |
A communication error has occurred between the OPC Classic Server and sensor. Please contact Technical Support. |
Related Topics
- Changing the Number of Log Entries
- Saving the Event Log
- Printing the Event Log
- Clearing the Event Log