Some content on this site is available only to logged-in subscribers. Contact Us for information on becoming a subscriber.

InSource.Solutions | InSource Training | InSource Client Portal
InSource Solutions Logo
Log In Sign Up
InSource.Solutions InSource Training InSource Client Portal Log In Sign Up
  • Home
  • AVEVA Communication Drivers
  • AVEVA Communication Drivers Support Cases

[ISS Support Case] OI Server

Last updated: October 17th, 2025

Description

OI Server started having random failures 4 to 6 weeks ago. The failure is the NIC (virtual network interface card) no longer works. The OS continues to run. The OI server continues to run, although all it does is generate thousands of errors like "The xxxxx message timed out", "Failed to Connect to...", "Device connection attempt to nn.nn.nn.nn timed out, socket closed". The Windows Event logs are clean - well, plenty of stuff in them but no warnings or errors along the lines of "NIC is dead". So I'm getting no clues in the logs, the OS continues to run, the DA server continues to run, but the NIC can not reach anything. My VMWare find no errors, and are convinced that something on the OS/Application side is "locking up" or "corrupting" the NIC. It never did before. And it doesn't do it on our other 2 DA servers that we run at our remote plant sites. Please help us determine the cause of the failures, or eliminate possible causes like configuration. Our VMWare team specifically asks us to: "When running Wonderware on a Windows 2016 virtual machine running the Vmxnet 3 adaptor we experience an outage of the NIC card only. Everything else on the operating system is fine." When the DA server no longer can communicate with PLCs we lose all data collection until the server is rebooted. Please help.

  • Author: Kevin Modlin
  • Published: October 17th, 2025

Details:

Product: Comm Drivers
Version: 2017
Solution: [Solution is visible below when you're logged in and have a current subscription]
Date Created: 08/05/2022
Case: 82210
Give feedback about this article

Recommended articles

[ISS Support Case] TI 500 - Disconnected Post CDP 2023 R2 P01

Upgraded to 2023 R2 P01 experienced a disconnect at 8am this morning. Describes loaded log file. Seems like this happened once before shrugged it off Firmware 1.27 South parkway WWTP

Read More

[ISS Support Case] OI Gateway Servers disconnecting every 7 minutes

They stay offline for about 2 minutes then they reconnect. They don't see any reconnect scripts that could cause it. They are waiting to reboot until they have a good opportunity. System platform 2020R2 SP1 They recently migrated to a new server. Suggested it may be a firewall or security program interfering with the connection. They will check with the IT department about that. Not available until the afternoon on 9/6/2024

Read More

[ISS Support Case] Professional license required

Were creating a new instance of the OI server the error, professional license required as displayed

Read More

[ISS Support Case] Failure to Create Additional MBTCP Server Instance

Client reached out as when user was attempting to create additional MBTCP server instance they received the following error message: "Multi-Instance configuration is only supported with a professional level license or higher. Please upgrade the license to create additional instance's." Client also had the following error in the logger: "LicAPISvcProxy.NET failed to communicate with Aveva Enterprise License product service."

Read More
Support Icon

CONTACT SUPPORT

How to reach us

10800 Midlothian Turnpike Tpke, Suite 209, Richmond, VA 23235

1.877.INSOURCE

Technical Support - 1.888.691.3858

Contact Us

  • InSource Solutions
  • InSource Training
  • InSource Client Portal
  • Log In
InSource Solutions Logo

© 2025 InSource Solutions. All Rights Reserved.

Knowledge Base Software powered by Helpjuice

Expand