TN - AppSrv09112601 - Platform Deployment Failure: "Could not CoCreate IPlatformInfoServer"

• Document Version: 001
• Applies to Version(s): AVEVA System Platform 2020 R2 through 2023 R2 SP1 P04

Description  

This article describes how to resolve AVEVA System Platform deployment failures caused by an invalid or improperly registered aaPlatformInfoSvr.exe on a remote platform. 

Important: This is an advanced repair procedure. Perform the steps in this article only after standard AVEVA System Platform deployment troubleshooting has been completed and the issue has been isolated to a missing, corrupted, or improperly registered aaPlatformInfoSvr.exe.

One indication of this issue is the following message(s) appearing repeatedly in the OCMC Logger:

GetEnginesFromPlatformInfoServer - Could not CoCreate IPlatformInfoServer, hr=0x800703fa
GetEnginesFromPlatformInfoServer - Could not CoCreate IPlatformInfoServer, hr=0x8000401a

When this condition exists, platform deployment may fail or the platform may not start correctly because the Platform Information Server (IPlatformInfoServer) COM object cannot be created on the target node.

In some cases, aaPlatformInfoSvr.exe may be corrupted (for example, a 0-byte file) or its COM registration may be damaged. This condition has been observed after incomplete software installations, antivirus interference, or file corruption.

Note: Additional errors/warnings may also appear, but these are generally secondary symptoms resulting from the platform failing to initialize correctly after the Platform Information Server cannot be created.

Before you Begin

Before performing the steps in this article, verify that standard AVEVA System Platform deployment troubleshooting has already been completed. This procedure is intended only for systems that continue to experience deployment failures after common configuration issues have been ruled out.

Confirm the following:

• The aaBootstrap service is installed and running on the target platform
• Change Network Account has been successfully run on both the Galaxy Repository (GR)  node and the target platform.
• OS Configuration Utility has been successfully run on both the GR node and the target platform.
• Basic network connectivity and name resolution have been verified between the GR node and the target platform.
• Windows Firewall, antivirus software, or endpoint security software is not preventing required System Platform communication.
• DCOM permissions on the target platform allow the necessary service accounts to activate and launch the relevant COM components.
• The deployment failure persists after completing the above troubleshooting.

If these prerequisites have not been verified, complete the standard deployment troubleshooting process before proceeding with the steps in this article.  Additional troubleshooting steps can be found in the Related Articles section at the end of this document. 

Solution Steps:

Step 1: Verify aaPim Permissions

On the target platform, verify that the following local service account is a member of the Local Administrators group:

NT SERVICE\aaPim

If it is not present, add the account and reboot the node.

Step 2: Obtain a Known-Good Copy of aaPlatformInfoSvr.exe

From the GR node, copy aaPlatformInfoSvr.exe from the following directory to the desktop or a temporary location on the remote platform:

C:\Program Files (x86)\ArchestrA\Framework\FileRepository\<GalaxyName>\Vendors\ArchestrA

Replace <GalaxyName> with the name of your Galaxy.

Caution: Confirm the GR node and the target platform are running the same System Platform version and patch level before copying this file. Using a mismatched version can introduce a new compatibility issue. 

Step 3: Replace the Existing Executable

On the remote platform,  navigate to:

C:\Program Files (x86)\ArchestrA\Framework\Bin

Rename or copy the existing aaPlatformInfoSvr.exe to preserve a fallback copy. Then copy the known-good file (obtained in step 2) into this same folder, overwriting if prompted. 

Step 4: Re-register the COM Server

On the remote platform, open an Administrator Command Prompt and execute:

"C:\Program Files (x86)\ArchestrA\Framework\Bin\aaPlatformInfoSvr.exe" /unregserver

followed by:

"C:\Program Files (x86)\ArchestrA\Framework\Bin\aaPlatformInfoSvr.exe" /regserver

Successful completion re-registers the Platform Information Server COM component.

Note: the command echo %errorlevel%  can be used to confirm the commands completed successfully. A return value of 0 indicates the command completed successfully. 

Step 5: Deploy the Platform

From the IDE, deploy the affected platform.  This confirms the immediate deployment failure is resolved. 

If deployment completes successfully, proceed to the next step.

Step 6: Verify Registration

To confirm that the registration has been fully restored and is stable across deployment cycles:

1.Undeploy the platform.
2.Deploy the platform again.

If both deployments complete successfully and the platform starts normally, the COM registration has been successfully restored.

Additional Notes

• This procedure specifically addresses deployment failures associated with IPlatformInfoServer COM registration and the hr=0x800703fa, hr=0x8000401a errors. 
• If aaPlatformInfoSvr.exe is found to be 0 bytes, replacing the file is required before attempting to register it. Simply running /regserver against a corrupt executable will not resolve the issue.
• Always replace the executable with a known-good copy before attempting to re-register the COM server.
• If the issue persists after completing these steps, continue troubleshooting other deployment prerequisites such as Change Network Account configuration, Windows Firewall, name resolution, DCOM permissions,  and OS Configuration Utility validation.

Please refer to the articles below for more troubleshooting or contact technical support:

Related Articles

Troubleshooting Deployment Failures (TN 1283)
https://knowledge.insourcess.com/aveva-application-server-tech-notes/tn_-_1283_troubleshooting_deployment_failures

Troubleshooting AVEVA Bootstrap Errors
https://knowledge.insourcess.com/en_US/troubleshooting-aveva-bootsrap-errors?draft=true

                                     _____________________________________________________________________________________________________