ArcGIS Enterprise Configuration Wizard: Deployment Error

[JoeKoch]

I've successfully installed all components using the ArcGIS Enterprise 11.5 Builder on a single Windows Virtual Machine (VM) running on Windows Server 2025 Standard. When I go to run the ArcGIS Enterprise Config Wizard as the next step, I continuously encounter the same error during step 4) Register Data Stores with GIS Server:

 

Working with Esri Support Services, we've been able to workaround by manually configuring the remaining steps to complete a base deployment, but I am still curious to know why this error was constantly encountered? I would imagine I am not alone, and that others have experienced this before as well.

Being only 3 steps away from a successful automated build of AE11.5, it was a bit of a disappointment and downer considering everything had executed smoothly up until that point. Any thoughts on what went wrong or how this may have been addressed?

[RichardDaniels]

Did you install the Json file that contains your licenses onto your Portal to provision user types? I see your Admin user account has no User Type defined, it should show Creator.

[JoeKoch]

Yes, I was unable to grab a real-time screenshot of the error, so I pulled the one attached above from the internet as an example to show what I was seeing. The Portal json file did specify the Creator User Type and was listed in the Configuration Summary.

[wizgis]

Hi @JoeKoch 

https://community.esri.com/t5/arcgis-enterprise-questions/unable-to-register-the-portal-with-the-web... please check this, the issue listed is similar to yours.

[JoeKoch]

Hi @wizgis, thanks for sharing the link. Yes, @MartinMcCarry had the same issue as me, went through similar steps to attempt to resolve, but also had to manually configure leading to same result. To me this is still not a clear solution, but rather a workaround when the AEB fails.

I'm glad there is a workaround, however, it does not answer the original question as to why this error occurs. Esri Support Services did not have, and was not able to provide a clear reason for the error either, only suspicions of what may have caused it.

So, the question remains, what causes this issue and how do you address it so that the automated configuration executes successfully?