[ISS Support Case] Installing latest version KOYO on newer core 3.0

Last updated: October 17th, 2025

Description

Direct email: Noticed from an old screenshot that the KOYO version Im using appears to be 1.18.0.0 but today on Aveva product download page there is a version 1.24 released in 2020. On my new VM I have a the install for OI-KOYO OI Server. It says its compatible with all of the following, including 3.0 which is confusing. Sorry if im reiterating but should I start with a G-1.0 series OI Core and upgrade to 3 later? I was originally just going to do 2.2 but not im not sure how picky it is.

Author: Kevin Modlin
Published: October 17th, 2025

Details:

Product: Comm Drivers

Version: 3.0

Solution: [Solution is visible below when you're logged in and have a current subscription]

Date Created:	04/12/2022
Case:	81460

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

[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

[ISS Support Case] Professional license required

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

[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."