[ISS Support Case] OI gateway Crashed
Last updated: March 7th, 2025Description
-Log's show nothing (All Blank since the 6th). -Virtual Server. -OI Gateway, is communicating. -Applied HF from previous case. -Event Viewer shows a crash 1/7/2023. -1:30 EST 1/9/2024 Teams meeting, will send event Logger information. -Escalated Case. Referenced previous SR's in which a HF was applied, in hopes to resolve. Uploaded, to AVEVA, the Up to date screen captures of the present issues and errors seen, from a teams meeting on 1/9/2024
- Author: Kevin Modlin
- Published: March 7th, 2025
Details:
Product: DA / OI Servers |
Version: 2023 |
Solution: [Solution is visible below when you're logged in and have a current subscription] |
Date Created: | 07/03/2024 |
Case: | 87165 |
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