How to install a missing OI Server when prompted for installation files
Last updated: March 18th, 2026Description
- Author: Ernest Lee
- Published: March 18th, 2026
Details:
Description
This Technote discusses the necessary steps to install an OI Server if it was not installed during the initial installation.
Solution Details
Solution Steps:
If a particular OI Server was not initially installed, you can manually install it afterwards
In Control Panel, locate the Aveva Communication Drivers Pack, right-click and choose uninstall and then Modify
Next, find the OI server that is not installed and check the corresponding box.
If you see the message below, it is looking for OI server setup.msi file.
Navigate to the directory below and choose the Setup.msi file to begin the installation process.
Give feedback about this article
Recommended articles
[ISS Support Case] License Reservation & Checkout
Client reached out looking for guidance on License reservation and checkout process.
Read More[ISS Support Case] Error, unable to communicate with the activation server or proceed with offline activation.
Client has a 2023 R2 development license and is getting the following error when trying to add license to schnedier electric license manager: "Error, unable to communicate with the activation server or proceed with offline activation. "
Read More[ISS Support Case] Issue Deploying ViewApp
Client reached out as he was neither able to deploy/undeploy ViewApp. The ViewApp was stuck in data synchronization status (orange Indicator). I attempted to undeploy both with/without "Marked as Undeployed When Failure" checked. but it continued to fail and was showing as deployed. I attempted this on each level. (Winplatform, ViewEngine,ViewApp) When attempting on ViewApp error message stated that previous deployment had not been completed. Each of these attempts was unsuccessful so I requested the user shut down the target node which allowed me to undeploy the platform and then unassign the ViewEngine and ViewApp to troubleshoot them separately. Once they were separated when trying to deploy Winplatform received error message about Platform ID mismatch so I exported the platform and then deleted it and created a new one. After this I attempted to deploy the Winplatform and received error: "Unable to Deploy Platform - Failed to get bootstrap's version" Requested that client put in port allowances for ports in the range 49152 to 65535 and Bootstrap.exe. (support article 000035913) Confirmed pings between GR node and target node as well as correct PC name being used in configuration. After this attempted to deploy Winplatform again which led to this error: "Error Failed to deploy Winplatform : The installations version is different from the one in the remote node." Checked versions and Application Server Version on GR node was 10.6.002 and target node was 10.1 so updated target node to same patch version and the same error message persisted.
Read More