[ISS Support Case] Standalone OI Server not appearing in System Management Console

Last updated: March 7th, 2025

Description

Gateway does not appear in the SMC Console App, even though it is installed and functional. I would like to set it to run as an auto service - but not sure how to do this without using SMC it 9.0 talks to OPC link 8.0 upgraded box to server 2019 Got them to a new version of OPC client provided Gateway from 2020 (communication works) Issues: not visible from SMC When rebooted gateway does not auto start.

Author: Kevin Modlin
Published: March 7th, 2025

Details:

Product: Communication Drivers

Version: 2020

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

Date Created:	11/22/2023
Case:	85809

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