Some content on this site is available only to logged-in subscribers. Contact Us for information on becoming a subscriber.

InSource.Solutions | InSource Training | InSource Client Portal
InSource Solutions Logo
Log In Sign Up
InSource.Solutions InSource Training InSource Client Portal Log In Sign Up
  • Home
  • AVEVA Application Server
  • AVEVA Application Server Tech Notes

Repairing Platform Common Services

Last updated: August 27th, 2025

Description

  • Author: Rich Brooks
  • Published: August 27th, 2025

Details:

The AVEVA Common Services Portal Scan sometimes indicates a need to repair the Platform Common Services installed with Aveva System Platform 2023R2 and higher. 

Start by undeploying the platform running on the machine needing the repair.

Mount the Aveva System Platform installation media ISO file.

Navigate to the \InstallFiles\CD-ASBFramework\x64 folder.  Right-click on the ASBFrameworkInstallx64.msi file to select Install from the list. 

Click on the Next button.

Click on the Next button on the next window.

Click on the Repair button on the next window.

Click on the Repair button on the next window.

Click on the Yes button on the next window.

Click on the OK button on the next window.

Wait for the repair to complete, and then click on the Finish button.
 

Click on the Yes button to reboot the server on the next window.

Redeploy the platform.  The repair is complete.

pc restoration system reset
Give feedback about this article

Recommended articles

[ISS Support Case] Platform deployment failure

Failed to deploy failed to find target platform aa bootstrap register platform failed.

Read More

[ISS Support Case] Platform Deployment Failure

Client reached out as when user was attempting to deploy WinPlatform user was receiving the following error: "Cannot find the target PC on the network OR target PC can not communicate back to the Galaxy Repository using the NIC that is top in the binding order."

Read More

[ISS Support Case] Create new galaxy Error: Failed to connect to the GR node...has platform deployed from another GR node

He clicks new galaxy, galaxy type is blank and gets message: failed to connect to GR node. It says there is a platform deployed already. He recently installed p01 on 2020 r2. SMC: Failed to connect to the GR node: NEWNODENAME. The node: OLDNODENAME cannot be used as GR node since it has platform deployed from another GR node

Read More
Support Icon

CONTACT SUPPORT

How to reach us

10800 Midlothian Turnpike Tpke, Suite 209, Richmond, VA 23235

1.877.INSOURCE

Technical Support - 1.888.691.3858

Contact Us

  • InSource Solutions
  • InSource Training
  • InSource Client Portal
  • Log In
InSource Solutions Logo

© 2025 InSource Solutions. All Rights Reserved.

Knowledge Base Software powered by Helpjuice

Expand