Post Install Error failed to load container images please find log attached
Version 5.1.0
-
Hi Richard,
The first error in the logs indicates that you are missing a configuration step during installation: "encountered an error during CreateContainer: failure in a Windows system call: The virtual machine could not be started because a required feature is not installed."
Depending on what version of Windows Server you are installing on and if you are wishing to install the App Build Service or not, you may need to complete some prerequisite steps, outlined in our help documentation here.
Thanks, Stefan
0 -
Thanks Stefan,
We are installing on an Azure Windows Server 2019 Datacenter VM but the documentation states:
"Few cloud or Virtual Machine (VM) services support Virtualization, so VMs or hosted services are likely to require extra configuration."
But I can't see any information on what that extra configuration is?
Regards,
Richard
0 -
Hi Richard,
As mentioned in the docs, you'll need to ensure that Docker Linux Container support is enabled, along with Nested Virtualization, as outlined here: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/nested-virtualization#enable-the-hyper-v-feature-on-the-azure-vm
Thanks, Stefan
0 -
Hi Stefan,
Any ideas on why the redirect url is returning invalid host when it is one?
?
0 -
0 -
Hi Richard,
In the Post Installer, if you remove the last '/' from the URL, then hit Test, it should correctly find the host. We'll update the logic if that's the case.
Thanks, Stefan
0 -
Thanks Stefan,
Removing that last '/' results in:
'This Redirect URL could not be reached.'
All others settings are as above.
0 -
If you complete the Post Installation, are you able to load:
- https://[servername]/geocortex/mobileviewer/
- https://localhost/geocortex/mobileviewer/ from the server itself
What is displayed? You may need to add DNS entries to the VM to allow the Redirect URL to interact with the item in AGOL.
0 -
Changing from /geocortex/ to /mobile/ in post installer IIS Settings fixed the problem.
0 -
Stefan, how to I add the CORS header?
This is occuring when adding a web map from my portal in mobile designer.
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://brudev.ems.tas.gov.au/server/rest/services/BRU/Community_Protection_Planning/MapServer?f=json. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).
0 -
Hi Richard,
There is a section of the Web Designer docs that also applies to the Mobile Designer; I'll make sure this content is also included in the Mobile docs.
Cross-Origin Resource Sharing (CORS) Requirements
By default, ArcGIS portals (including ArcGIS Online) allow cross-domain requests using Cross-origin Resource Sharing (CORS). In the Esri portal used with Geocortex Web Designer, if you have any domains configured in the Organization | Settings | Security | Allow Origins setting, then you must add the Geocortex Web Designer server as an allowed origin.
On-Premises Portal for ArcGIS with On-Premises Web Designer: If you use an on-premises Portal for ArcGIS with on-premises Web Designer, and your organization has configured the Allow Origins setting in your portal, then you must add your Geocortex Web Designer server as an allowed origin.
Thanks, Stefan
0 -
Thanks Stefan,
I had no allowed origins configured so I added below but the CORS header is still missing.
0 -
0 -
Hi Stefan,
I suspect it's the Azure Load Balancer. Info from
"If incoming CORS requests go through a reverse proxy, a load balancer, or an additional web server prior to reaching your portal, the restrictions made using the following steps may not be honored. In these cases, you will need to configure the reverse proxy, load balancer, or web server to follow the same restrictions as your portal."
0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
14 kommentarer