Latest Contributions by NicolasGIS

Hello, I am testing the replication of an Enterprise 11.5 deployment on Windows Server 2022 with 3 datastores (tileCache, relational, and objectStore). I set up a standby environment on a different set of VMs and restore a webgisdr backup. At first sight, everything is in order and all the components are properly restored and connected one another. But when having a closer a look at the objectStore, I realized that is now pointing to the original objectStore. You can notice it: - from the ArcGIS Server manager when validating the objectStore: the _proxyUrl parameter is: https://myoriginaldatastoreVM.company.com:2443/arcgis/datastoreadmin/machines/MYORIGINGALDATASTOREVM.COMPANY.COM/validate   - from the ArcGIS Server admin interface when checking the machines of the cloud store "objectStore": https://myags.company.com:6443/arcgis/admin/data/items/cloudStores/AGSDataStore_objectstore_oz_aev7q1p/machines  it is the name of the original datastore VM which is written (ie: "myoriginaldatastore").   Also, if you now check the replicatedDataStore VM, and browse: https://localhost:2443/arcgis/datastore/ You will see that it is no longer "attached" on the replicated deployment.   I am confused: is it a BUG or a feature ? Did I miss anything @JonathanQuinn maybe ?   Thanks,   /cc FYI @PhilippeVDV @CedricDespierreCorporon  ... View more

Hello,   I am facing an issue with publishing a webmap composed of 8 point layers with each one having a unique value renderer of 4 values: so nothing crazy... When publishing it, ArcGIS Pro says it fails and the following message is displayed: Status: Failed ErrorMessage: Failed to add web item Debugging the issue with Fiddler, it is failing on the following request: POST /portalwebadaptor/sharing/rest/content/users/foo/additem An error occurred while processing the request. If I remove a single layer, it works. So I thought the issue was specific to this one layer, but when I added it back and removed another one, it worked as well. I then thought about a size limitation thinking my CIMSymbols were too complicated and the JSON generated was too big but it is actually only 10MB and according to the documentation "Add Item" operation should be able to handle up to 5GB: https://developers.arcgis.com/rest/users-groups-and-items/considerations-and-limitations/ I debugged a little more and try to upload my webmap directly on the HTML Sharing API copy/pasting the parameters send by ArcGIS Pro captured from Fiddler ('title', 'type', 'typeKeywords', 'extent', and of course the 'text' one which contains the webmap) and surprise... it worked ! So what could be the difference ? The answer is the type of POST ! - ArcGIS Pro is sending the webmap using 'x-www-form-urlencoded' while - ArcGIS HTML Sharing API using 'multipart/form-data' I then wrote a simple Python script (attached) with 2 methods: - one POSTing the webmap using 'x-www-form-urlencoded': it fails - one POSTing the webmap using 'multipart/form-data': it works. And the webmap then is fully functionnal on the MapViewer.   I then wonder whether it was an IIS WebAdaptor issue or a Portal for ArcGIS issue but it actually fails on both: - on IIS: the error is: An error occurred while processing the request. - on Portal for ArcGIS: ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None)   But I am now stuck and I can't upload a relatively simple webmap except manually on the Sharing API after having captured the webmap JSON generated by ArcGIS Pro with Fiddler which is really not scalable... Any experts around having an idea ?   Thanks,   Nicolas ... View more