• State Suggested Answer
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 20 subscribers
  • Views 2346 views
  • Users 0 members are here
Options

AVEVA system plattform 2023 R2 : Galaxy Undeployed still OCMC plattform manager shows the galaxy and not allowing to deploy or undeploy further galaxy..

Hemant

Hii,

As mentioned in subject line,  Praviously galaxy is undeployed...in IDE status of the galaxy componant shows the undeployed state, however when trying to deploy, deployement fails giving error messege that plattform is already deployed...

On checking in OCMC, under plattform manager only galaxy name can be seen but no plattform can be seen running/stopped condition.

We tried to remove local plattform from OCMc but its not woeking..

I restarted the services bootstrap and galaxy repository but still problem unresolved.

Please help 

regards

Hemant

  • 0

    Please open a support ticket in our Knowledge and Support Center (aveva.com), or call 1-800-WONDER1

  • 0

    This looks like it needs to go through customer support ! initial thoughts are it's not correctly undeployed, if the AOS is in another machine, check the comms, undeploy it again with failed to undeploy state , and then try to redeploy. But please go through customer support as this case needs to be assessed

  • 0

    Hi Hermant, I agree that situations like this is good to manage through Techsupport, but either way its beneficial for the community to get some insights in the error and the outcome of the troubleshooting with techsupport :)

    For example you could post the Error messages that you get, for future references.

    A question based on my previous experiences, is your system platform installed in the default location or did you specify some alternative drive?

    Ie. D:\

    I have seen some similar issues when this is the case.

  • 0

    Hi Hermant

    Have you found solution to this case, am having similar issue in System platform 2023.

    Regards,

    Gehad

  • 0 in reply to Gehad Morad

    Hi Gehad,

    After several restart,  We have external OPC server configured for communication, we make sure that external OPC Server service is in stop state while we doing deployement then deployement was a success.

    But i am not sure is this cause for our problem.

    regards

    Hemant 

  • 0 in reply to Richard Köhlerstrand

    Sorry for very delyaed reply..all installation is in default drive C:

  • 0

    We have seen this issue on every v.2023 R2 upgrade on our GR nodes.  It appears to be an installation issue where the updated SystemManager.dll is not properly registered.  Here is the solution we use:

    Try to Unregister the platform manager dll then register it again following below steps:

    1. Confirm if SystemManager.dll is present in "\Program Files (x86)\ArchestrA\Framework\Bin" folder after deployment.
    2. Close the SMC/OCMC.
    3. Run the Command prompt console in administrator mode.
    4. Unregister aaPlatformManager.dll component by executing the following command in the command console window

    c:\>regsvr32/u "C:\Program Files (x86)\ArchestrA\Framework\Bin\SystemManager.dll"

    1. Register aaPlatformManager.dll component by executing the following command in the command console window.

    c:\>regsvr32 "C:\Program Files (x86)\ArchestrA\Framework\Bin\SystemManager.dll"

    1. Open the SMC/OCMC.
© 2025 AVEVA Group Limited or its subsidiaries. All Rights Reserved.