Unable to publish hosted tile layers after installing ArcGIS Enterprise 10.9.1 with HA

[makariw]

Hi,

I have install ArcGIS Enterprise using the cinc client and the latest ESRI cookbooks v3.8.0. My primary machine has the following. Please note I add the hostname and hostidentifier to the server and portal nodes as shown below (without these the federation stage was failing)

{
"arcgis": {
"version": "10.9.1",
"run_as_user": "domain\arcgisadmin",
"run_as_password": "acc_password",
"configure_windows_firewall": true,
"repository": {
"archives": "C:\Software\Archives",
"setups": "C:\Software\Setups"
},
"iis": {
"keystore_file": "C:\Software\Certificates\gis01v.pfx",
"keystore_password": "mypassword",
"replace_https_binding": true
},
"server": {
"install_dir": "C:\Program Files\ArcGIS\Server",
"install_system_requirements": true,
"private_url": "https://lb.domain.com/server",
"web_context_url": "https://lb.domain.com/server",
"admin_username": "siteadmin",
"admin_password": "mypassword",
"authorization_file": "C:\Software\AuthorizationFiles\10.9.1\arcgisserver1091.ecp",
"directories_root": "\\FILESHARE\arcgisserver",
"log_dir": "D:\arcgisserver\logs",
"log_level": "WARNING",
"config_store_type": "FILESYSTEM",
"config_store_connection_string": "\\FILESHARE\arcgisserver\config-store",
"wa_name": "server",
"hostname": "portal1machine.domain.com",
"hostidentifier": "portal1machine.domain.com",
"system_properties": {
"WebContextURL": "https://lb.domain.com/server"
}
},
"python": {
"install_dir": "C:\Python27"
},
"data_store": {
"install_dir": "C:\Program Files\ArcGIS\DataStore",
"install_system_requirements": true,
"data_dir": "D:\arcgisdatastore",
"preferredidentifier": "hostname",
"types": "tileCache,relational",
"tilecache": {
"backup_type": "fs",
"backup_location": "\\FILESHARE\arcgisbackup\tileCache"
},
"relational": {
"backup_type": "fs",
"backup_location": "\\FILESHARE\arcgisbackup\relational"
}
},
"portal": {
"install_dir": "C:\Program Files\ArcGIS\Portal",
"install_system_requirements": true,
"admin_username": "portaladmin",
"admin_password": "mypassword",
"admin_email": "myemail",
"admin_full_name": "Administrator",
"admin_description": "Initial account administrator",
"security_question": "",
"security_question_answer": "",
"data_dir": "D:\arcgisportal",
"log_dir": "D:\arcgisportal\logs",
"log_level": "WARNING",
"content_store_type": "fileStore",
"content_store_provider": "FileSystem",
"content_store_connection_string": "\\FILESHARE\content",
"object_store": "",
"authorization_file": "C:\Software\AuthorizationFiles\10.9.1\Portal_1091.json",
"user_license_type_id": "creatorUT",
"wa_name": "portal",
"root_cert": "",
"root_cert_alias": "hostedserver",
"hostname": "portal1machine.domain.com",
"hostidentifier": "portal1machine.domain.com",
"system_properties": {
"privatePortalURL": "https://lb.domain.com/portal",
"WebContextURL": "https://lb.domain.com/portal"
}
},
"web_adaptor": {
"admin_access": true,
"reindex_portal_content": false
}
},
"run_list": [
"recipe[arcgis-enterprise::system]",
"recipe[arcgis-enterprise::disable_loopback_check]",
"recipe[esri-iis]",
"recipe[arcgis-enterprise::install_portal]",
"recipe[arcgis-enterprise::webstyles]",
"recipe[arcgis-enterprise::portal]",
"recipe[arcgis-enterprise::portal_wa]",
"recipe[arcgis-enterprise::server]",
"recipe[arcgis-enterprise::server_wa]",
"recipe[arcgis-enterprise::datastore]",
"recipe[arcgis-enterprise::federation]"
]
}

The standby machine as the following

{
"arcgis": {
"version": "10.9.1",
"run_as_user": "domain\arcgisadmin",
"run_as_password": "mypassword",
"configure_windows_firewall": true,
"repository": {
"archives": "C:\Software\Archives",
"setups": "C:\Software\Setups"
},
"iis": {
"keystore_file": "C:\Software\Certificates\gis02v.pfx",
"keystore_password": "mypassword",
"replace_https_binding": true
},
"server": {
"install_dir": "C:\Program Files\ArcGIS\Server",
"install_system_requirements": true,
"primary_server_url": "https://portal1machine.domain.com:6443/arcgis",
"admin_username": "siteadmin",
"admin_password": "mypassword",
"authorization_file": "C:\Software\AuthorizationFiles\10.9.1\arcgisserver1091.ecp",
"log_dir": "D:\arcgisserver\logs",
"wa_name": "server"
},
"python": {
"install_dir": "C:\Python27"
},
"data_store": {
"install_dir": "C:\Program Files\ArcGIS\DataStore",
"install_system_requirements": true,
"data_dir": "D:\arcgisdatastore",
"preferredidentifier": "hostname",
"types": "tileCache,relational"
},
"portal": {
"install_dir": "C:\Program Files\ArcGIS\Portal",
"install_system_requirements": true,
"primary_machine_url": "https://portal1machine.domain.com:7443",
"admin_username": "portaladmin",
"admin_password": "mypassword",
"data_dir": "D:\arcgisportal",
"log_dir": "D:\arcgisportal\logs",
"wa_name": "portal"
},
"web_adaptor": {
"admin_access": true,
"reindex_portal_content": false
}
},
"run_list": [
"recipe[arcgis-enterprise::system]",
"recipe[arcgis-enterprise::disable_loopback_check]",
"recipe[esri-iis]",
"recipe[arcgis-enterprise::install_portal]",
"recipe[arcgis-enterprise::webstyles]",
"recipe[arcgis-enterprise::portal_standby]",
"recipe[arcgis-enterprise::portal_wa]",
"recipe[arcgis-enterprise::server_node]",
"recipe[arcgis-enterprise::server_wa]",
"recipe[arcgis-enterprise::datastore_standby]"
]
}

However, I am not able to publish a shared tile package (.tpkx) to a hosted layer both from ArcGIS Pro 2.9 and from Portal.

Portal logs has several warnings saying

"Using defaults for some properties of the self resource (ex:supportsSceneServices). The hosting server may not be reachable"

The status of the federation is all ok from Portal and both relational and tile cache datastores validate successfully from ArcGIS Manager.

Is there anything not right in the values that I have used in the json files that would caused the publishing of hosted map layers to fail?

Regards,

Makari

[pbobov]

Hi @makariw,

"Using defaults for some properties of the self resource (ex:supportsSceneServices). The hosting server may not be reachable" warning is logged by portal if it cannot validate the hosting server health check URL (the HTTP response code is not 200).

Please check if URL https://lb.domain.com/server/rest/info/healthcheck is available from both primary and standby machines.

[makariw]

@pbobov,

Thanks for getting back to me. Yes I can verify that https://lb.domain.com/server/rest/info/healthcheck is available from both the primary and standby machines and the healthcheck is OK from both machines.

Is there anything else I can check?

Regards,

Makari

[makariw]

@pbobov,

Further to my comment above the one of the arcgisserver logs has the following entry
"Server license version does not match effective current version." I am certain that the license file I have used is 10.9.1. Any idea why I have this message in the log file?

[pbobov]

@makariw

Maybe publishing fails because of failed license validation...

Check the ArcGIS Server licenses versions and status at https://lb.domain.com/server/admin/system/licenses.

[makariw]

Publishing referenced data works fine. It only fails when I try to publish a hosted tile layer. I will check the licences as described above.

Regards,

[makariw]

@pbobov

On the home page of https://lb.domain.com/server/admin the current version is listed as 10.9.1. However when I browse to https://gis.airwave.pri/server/admin/system/licences the version is listed as 10.9. Should they be exactly the same? Could this be the source of my issue? I can publish a hosted feature layer, referenced data from my enterprise Oracle db. Publishing a tile package is failing from both ArcGIS Pro and Portal UI. I need to be able to publish tile packages to use a basemaps in Portal as I work in a closed environment.

Any pointers will be much appreciated.

Regards

[pbobov]

https://lb.domain.com/server/admin returns the software version. https://gis.airwave.pri/server/admin/system/licences returns the license version. 10.9 license should work with ArcGIS Server 10.9.1. I wonder why "Server license version does not match effective current version." message is there...

[pbobov]

Publishing hosted tile layers is not a new feature in 10.9.1, but maybe something else related to licensing is in play here. I recommend reaching out to Esri Technical Support for further assistance as they are better equipped to troubleshoot issues like that.