Installation issue

Hi Thierry!

On a system where System Platform 2023 R2 P01, the process of creating a new blank galaxy will patch the new created galaxy as part of the creation process. This unfortunately lead to long waiting time for creating the final galaxy, up to 5 -10 minutes even on a good performing server.

I can agree that the Patch should deliver an updated version of the Default_Empty.cab that is used as a template, but I guess that would impact the final size of the Patch 01 and it was not part of the patch. It has been similar scenarios in previous versions.

Hopefully this does not case to much issues for you since creating galaxies might not be such a frequent action (it is a pain when performing Application Server trainings or if you have the role as techgeek though :) )

As your second issue you mention that you experience the same issue in version 2012 R2 P01? as with 2023 R2 P01?

I am running both of these versions without the same issue so could it be related to your environment?

Access denied with WWCdi and WWPackageServer errors could be caused by several things and I agree with David that contacting tecsupport might be the best way to resolve it quickly. even though 2023 R2 SP1 is soon to be release I would not wait for that to resolve your problem, and if you are using 2012 R2 you can not expect any patches or fixes on such an old product.

But general suggestions that applies, 

Is you computer part of a domain or act in workgroup mode?

could there be policies that restrict your server?

Focusing on version 2023, are your local admin group still have the aaPim user (could be removed by policy).

Are you running the galaxy creation with your local administrator or a domain account?

Are you experiencing any other issues other that these errors during galaxy creation?

Can you deploy without issues and so on?

Any other errors that could indicate issues?

I hope this helps you even though I did not provide a final solution for your issues.

Hi Thierry!

On a system where System Platform 2023 R2 P01, the process of creating a new blank galaxy will patch the new created galaxy as part of the creation process. This unfortunately lead to long waiting time for creating the final galaxy, up to 5 -10 minutes even on a good performing server.

I can agree that the Patch should deliver an updated version of the Default_Empty.cab that is used as a template, but I guess that would impact the final size of the Patch 01 and it was not part of the patch. It has been similar scenarios in previous versions.

Hopefully this does not case to much issues for you since creating galaxies might not be such a frequent action (it is a pain when performing Application Server trainings or if you have the role as techgeek though :) )

As your second issue you mention that you experience the same issue in version 2012 R2 P01? as with 2023 R2 P01?

I am running both of these versions without the same issue so could it be related to your environment?

Access denied with WWCdi and WWPackageServer errors could be caused by several things and I agree with David that contacting tecsupport might be the best way to resolve it quickly. even though 2023 R2 SP1 is soon to be release I would not wait for that to resolve your problem, and if you are using 2012 R2 you can not expect any patches or fixes on such an old product.

But general suggestions that applies, 

Is you computer part of a domain or act in workgroup mode?

could there be policies that restrict your server?

Focusing on version 2023, are your local admin group still have the aaPim user (could be removed by policy).

Are you running the galaxy creation with your local administrator or a domain account?

Are you experiencing any other issues other that these errors during galaxy creation?

Can you deploy without issues and so on?

Any other errors that could indicate issues?

I hope this helps you even though I did not provide a final solution for your issues.

I only use AVEVA System Platform 2023 R2, Actually P01 is on test. We use SP 2023 R2 locally on vm under W10, and under an active directory, on a ESXi as a vm w10 who is acting as an Azure Devops in order to launch pipelines. But actually, pipelines failed after creating 5 galaxy through GrAccess.