Latest Contributions by HannesGrothkopf

One of our customers is expecting similar issues in the "ArcGIS Field Maps" App (Version 23.2.3, iOS) when their users change their password in the connected Active Directory.   The specific issue here is that the users will no longer see content in the app after changing their password. There is no information within the app about the password change or an invalid session/token. In most cases a re-logging into the app solves the problem, but at first this is very misleading.   We are using ArcGIS Enterprise 11.1 with IWA. ... View more

This issue seems to be related to a an upgrade of the underlying openssl version. "ESRI has moved ArcGIS Pro 3.0.2+ to OpenSSL version 3.x and cryptography version 37.0.2" https://community.esri.com/t5/arcgis-api-for-python-questions/fs-overwrite-script-stopped-working-after-updating/m-p/1240320/thread-id/8146 ... View more

Hi Michael,   I can confirm this behaviour. We recently upgraded the ArcGIS PRO installation on a Windows terminal server from version 2.9.6 to 3.1.1 and all our python tasks using arcgis.gis.GIS to connect to our portals stopped working with the named error. It seems like the option "verify_cert" is being ignored, as we have set this to false. The connection is established like this.   from arcgis.gis import GIS GIS(url="[PORTAL_DNS]:7443/arcgis", username=adminUser, password=adminPass, key_file=None, cert_file=None, verify_cert=False)     There is no difference when connecting to the portal using the webadaptor or not (port 7443 or 443). Error (verify_cert=False)   Setting `verify_cert` to False is a security risk, use at your own risk. Error: Could not initialize PortalManager. Please set verify_cert=False due to encountered SSL error: HTTPSConnectionPool(host='[PORTAL_DNS]', port=7443): Max retries exceeded with url: /arcgis/sharing/rest/info?f=json (Caused by SSLError(SSLError(1, '[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation disabled (_ssl.c:1129)')))   Error (verify_cert=True)   Error: Could not initialize PortalManager. Please set verify_cert=False due to encountered SSL error: HTTPSConnectionPool(host='[PORTAL_DNS]', port=7443): Max retries exceeded with url: /arcgis/sharing/rest/info?f=json (Caused by SSLError(SSLError(1, '[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation disabled (_ssl.c:1129)')))   Error (verify_cert=True, using webadaptor URL)   Error: Could not initialize PortalManager. Please set verify_cert=False due to encountered SSL error: HTTPSConnectionPool(host='[PORTAL_DNS]', port=443): Max retries exceeded with url: /arcgis/sharing/rest/info?f=json (Caused by SSLError(SSLError(1, '[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation disabled (_ssl.c:1129)')))   ("PortalManager" is our internal python class used to establish the connection)   Funny thing is, that this error occures only with our staging portal, not with our production portal. Both portals are on enterprise version 11.1 and (should) be configured 100% identically with IWA activated. The python skript version and windows task user used for both portals are the same. And both are run with the same python environment from the updated ArcGIS PRO installation.   kind regards, Hannes Grothkopf ... View more

Hey Scott, thank you for your comment. Sadly security.manager (both "Enterprise" and "NEXT" edition) does not support hosted Feature Layers. https://docs.conterra.de/en/securitymanager-enterprise/latest/userguide/appendix/functional-matrix-interceptors.html https://docs.conterra.de/en/securitymanager-next/latest/index.html   ... View more

More information on the "geoprocessing options" metioned by @DanPatterson can be found here in the "Logging" section: https://pro.arcgis.com/en/pro-app/2.9/help/analysis/geoprocessing/basics/geoprocessing-options.htm   There is also a new tool since version 2.9 called "Diagnostic Monitor" which can be started directly out of ArcGIS PRO (Ctrl+Alt+M) and also has a section "Log". https://pro.arcgis.com/en/pro-app/2.9/get-started/arcgis-diagnostic-monitor.htm ... View more

Hey, I also observe the same problem when I change settings (e.g. disable/enable editing) on certain hosted feature layers via the portal website or when I want to change field information with the update_definition function (FeatureLayerManager) from the "ArcGIS API for Python". Even after overwriting the hosted feature layer with ArcGIS PRO ("Overwrite Web Layer"), the error remains. If I repeat the overwriting, the error sometimes disappears. I also think that the problem was originally caused by performing the "Overwrite Web Layer" function. The original data source of the web layer is a feature class in an Oracle database (without SDE extension), which is added to ArcGIS PRO and published as a web layer.   Our environment is: ArcGIS Enterprise 10.9.1 ArcGIS PRO 3.0.3 Oracle Database 19.18.0.0.0 ... View more

Would love to see this for uploaded files like images as well. And please don't forget ArcGIS Enterprise. ... View more

Thank you, I will contact the support. ... View more

Hey Jonathan, thank you for commenting on this issue. As far as I understand the documentation on Creating a composite address locator correctly, creating of cascading Geocode Services by embedding existing services is possible in general. ("A composite address locator consists of two or more individual address locators and/or geocode services.") I can use the findAddressCandidates interface of such a Composite Geocode Service which also indicates to me that cascading is possible. Unfortunately the documentation does not mention anything about the suggest functionality. Do all of the involved locators/geocode services have to have suggesting enabled? How 'similar' do they have to be configured in general? ... View more

Hello, I am getting the same error with my Composite Locator. It is composed of two Address Locators I created. One of them is hosted as a Geocoding Service, the other is located on my PC. Both the Geocoding Service and the Address Locator are configured identically. The Geocoding Service on its own can be requested via the suggest interface. The Composite Locator is published to an ArcGIS Server. The used Geocoding Service is hosted on the same ArcGIS Server as the Composite Locator gets published to. There is no output in the ArcGIS Server log related to this error. I am using ArcMap 10.5.1, ArcGIS Server 10.31 AND 10.51 (both versions produce the error) ... View more

*necro* Hey folks, @Derek: Just to clarify this. By 'We don't support directly adding a JSON' you mean a JSON file not in the GeoJson format or files ending with .json in general? As you also say: 'You can add a GeoJSON file to Portal, but not a JSON file.' Yet the 'supportet-items' page states: 'GeoJSON file (.geojson, .json)' I'm trying to upload a GeoJson file to ArcGIS Portal. For testing purposes I use the 'example' provided in the wikipedia article about GeoJson Derek referenced in his post. I saved this in a file called test.json. Following the guide on Publish hosted feature layers—Portal for ArcGIS I keep getting an error after hitting the 'Add Item' button (step 8): "ERROR 999999: Error executing function. No geojson found in item. Failed to execute (Publish Portal Service). Failed." Renaming the file to test.geojson leads to a successful upload. Another error I get is related to the proterties object of the single features. Whenever a property value is not a string or an integer, but an array or object I get following error upon upload. "ERROR 999999: Error executing function. The value type is incompatible with the field type. [prop1] The workspace is not connected. Failed to execute (Publish Portal Service). Failed." I am using ArcGIS for Portal version 10.4.1. Thanks in advance ... View more