[ISS Support Case] Please contact...technical support...licensing error VerifyFileSignature

Last updated: March 7th, 2025

Description

These licensing errors appear each time we reboot the OI_Server. This is for each of the MBTCP and ABCIP modules we have in the system: Please contact Schneider Electric Software technical support regarding licensing error VerifyFileSignature(C:\Program Files (x86)\Wonderware\OI-Server\CommonFiles\bin\SELicensing.dll) No other explanation is presented, and no affects are apparent.

Author: Kevin Modlin
Published: March 7th, 2025

Details:

Product: Communication Drivers

Version: 2017

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

Date Created:	10/20/2023
Case:	85598

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