System Platform 2023 R2: Upon opening IDE now seeing "New Galaxy: CR Node Computer Name is not set" from WWPackageManager (in logger). IDE will not open and must use task mgr to shut down dialog.
System Platform 2023 R2: Upon opening IDE now seeing "New Galaxy: CR Node Computer Name is not set" from WWPackageManager (in logger). IDE will not open and must use task mgr to shut down dialog.
Hi Dave,
This is not something I've seen before myself. It almost feels like there is a nam resolution issue. IS there perhaps a machine with the same computer name? Or a computer name with underscores ("_") or some other weird character? Is this happening before you create a galaxy? Otherwise, also make sure you are not using the same name for the galaxy and the computer or perhaps the workgroup. One long shot is to change the computer name and perform a repair. If that does not work, I recommend opening a ticket with support so they can look at it a little closer.
- Ernst
Hi Dave, did you rename your computer after you installed System Platform?
Regards,
Klaus
Hi Klaus & Ersnt,
None of the situations you mentioned was the case. I did try renaming the vm and doing a repair. Same results. I did not rename the computer after the install of SP after that though.
This was happening before I was able to open a galaxy. Popup happened immediately after displaying the backstage screen. I closed the case – it took less time to just create a new VM and install 2023 R2 on it.
Also, this not the only case of that message. There was the same error with AVEVA case# 960409951 on April 24, 2024. It was solved after a repair was run.
Thanks for the explanation. We'll keep an eye on it and see if we can reproduce it in-house.
Hi Dave,
Are you using a workgroup in this VM ? If so, can you try the following steps which resolved the reported issue in an earlier case ?
What I would also like to obtain from you is the data under the following registry key
I'll send you an email privately so that you don't need to expose your machine's configuration here.
Jerry
Hi, I have the same problem. I can’t edit my platform, and I can’t even create a new platform. No error appears in the log or at the time of check-in. However, when I try to create a new platform, I get an error, and that only applies to the platform object. System Platform 2023 R2
See the following for resolution:
https://softwaresupportsp.aveva.com/#/knowledgebase/details/000042799?lang=en_us
Hi,
You need an account with a valid support contract to be able to access some parts of the support portal.
But here are the steps from the article.
System Platform versions 2020 and higher.
Resolved with workaround from Development.
Below are the workaround that we need to follow to recover from the above state:
Stop the aaGR service
Make the aaGR service startup type as "Disabled"
Launch IDE and close the "connect to galaxy" dialog if any
Enter Server name in the IDE Home Page as "Node Name" or as "localhost"
Switch to Services window and update the startup types from 'Disabled" to "Automatic"
Start the aaGR service
Switch to IDE window and click on "Connect to server" which will displays the cab files
Thank you Richard! I recorded this solution in the Q-mation Sales Force logs to help stave off any other tech support calls regarding this.
-Dave