Latest Contributions by danbecker

‎02-10-2023

This problem was fixed by simply rebooting the VM, all is well now, Lol. I uninstalled datastore from C:\, then reinstalled on E:\ without rebooting in between.

‎02-08-2023

Maybe this issue is related? My install path was E:\Program Files\ArcGIS\DataStore ..with a space https://support.esri.com/en/technical-article/000015832

‎02-08-2023

ArcGIS Datastore (Windows) is installed in C:\program files\arcgis\datastore When I use this command to create the datastore, the data directory defaults to c:\arcgisdatastore. configuredatastore.bat azarcgissvr01.ad.domain.com server_admin password123 E:\arcgisdatastore\ --stores relational I figured I could create a Premium SSD disk (Azure) then have datastore read/write to that directory. So, I uninstalled DataStore and instead installed it in E:\. After this, when datastore was created, I was able to set as E:\arcgisdatastore. But....now none of the cmd line utilities work when accessed from E:\....tools\. Error: the system cannot find the path specified. Is this expected behavior? B

‎02-02-2023

On-prem deployment has https://gis.domain.com being passed through our firewall to our webadaptor vm, port 443 only. *.domain.com CA signed cert is installed on webadaptor VM, IIS. 2 webadaptors are installed on this same machine, /portal(443) and /server(443) We just finished a base configuration deployment in Azure: portal, server, datastore and webadaptor VMs. We deployed Azure application gateway in front of the webadaptor VM. Our *.domain.com cert has to be installed on both the azure app. gateway and the backend webadaptor VM. The application gateway supports TLS termination, which offloads it from the webadaptor VM. This got me thinking, is it beneficial, (CPU wise) to configure ArcGIS Enterprise communication solely over :80 ? Is this possible? Azure application gateway terminates *.domain.com TLS session, then passes requests: :443/portal --> http://webadaptorvm.internal.com/portal :443/server -->http://webadaptorvm.internal.com/portal I would install new webadaptors with the same names, listening on port80. Would this also require me to configure the portal and server VMs to listen on http also? Portal doc: https://enterprise.arcgis.com/en/portal/latest/administer/windows/configure-https.htm Server doc: https://enterprise.arcgis.com/en/server/latest/administer/windows/secure-arcgis-server-communication.htm

‎01-18-2023

Thanks for the help. Yes, we're aware of the ArcMap services, and are staying at 10.9.1 during the migration. I figured it was best to not upgrade versions in the middle of the lift-and-shift to Azure. How about we deploy an Azure VM for PostgreSQL, replicating our on-premise environment. We can deploy it as newdb.ourdoamin.com, migrate the db's, then, when we edit the external DNS record to point traffic to Azure, disjoin currentdb.ourdomain.com from AD, then rename the Azure equivalent? We can then casually start using Azure hosted PostGresql, and eventually re-publish all services pointing to the hosted instance and shut down the Azure PostgreSQL VM.

‎01-18-2023

After migration, (ArcGIS Enterprise site & SDE gdbs from on-prem to Azure db for Postgres), what if we had the oldhostname.ourdomain.com FQDN resolve to the IP of the Azure db for Postgres, where the dbo and password are identical. Would this split-horizon DNS setup require re-publishing every service?

‎01-18-2023

Can someone elaborate on the process of updating the SDE connections after migration? Our old on-premise DNS name will be different in Azure and there are issues with setting up a split-horizon DNS policy that resolves Azure requests to the new hosted postgres instance. After migration, do we just update the datastore connections, or does it require re-publishing each service?

‎12-29-2022

Does anyone know if a mixture of operating systems is supported for each component? Linux Machines: (ArcGIS Datastore, ArcGIS Portal) Windows Machines (ArcGIS Server) how would we specify "SHARED_LOCATION" parameter in this case?

‎12-08-2022

Here's what I tried: 1) Created a checkpoint of VM (obivously) 2) Installed PostGIS 3.0.1 on the PostgreSQL 11.12 instance (that's currently configured for ST_Geometry storage) 3) Used Create Enterprise Geodatabase tool to create "demogdb", specifying spatial type as POSTGIS 4) Created appropriate users in demogdb 5) Created appropriate feature datasets in demogdb 6) Feature class to feature class tool in Pro to move data from ST_Geometry gdb to new demogdb. 7) demogdb feature classes show: ST_geometry (original) feature classes show this: The above workflow seemed to work fine. What's the purpose of exporting/importing the configuration keywords? I did export both the orginal and demogdb configuration keyworks and they each correctly show "ST_GEOMETRY" and "PG_GEOMETRY", respectively. thanks!

‎11-23-2022

Thanks everyone, this should be enough to get me started with the test environment! Yes, we have ~90 PostgreSQL databases, but I would guess only 1/2 of them will make the migration. A lot of db cleanup needs to happen for projects (db's) that are no longer active. Sounds like the best path is to convert on-prem SDE.ST_GEOMETRY columns to PostGIS Geometry, then pg_dump. Transfer that pg_dump (.post file) to Azure Storage Account, then use pg_restore to the Azure instance. Our IT consultant is following this doc: Deploy Esri ArcGIS Pro in Azure Virtual Desktop, except Azure db for PG, not SQL. Our entire base Enterprise deployment is being moved to Azure VMs that are in the same region (Azure GOV) as the Azure db for PG instance. Our analysts' workstations are also being moved to Azure Virtual Desktops, and our file share (Pro projects, FGDBs, ect.) is being moved to Azure NetApp files. So, everything should be co-located in the same Azure region for minimal latency. I didn't even want to attempt on-prem workstations accessing cloud databases.

‎11-22-2022

Existing on-prem server: Ubuntu Server 18.04 LTS PostgreSQL 11.12 Contains ~90 SDE Geodatabases; total size ~500GB ST_GEOMETRY is used All ArcGIS Enterprise components are getting moved to Azure VMs, workstations will be Azure Virtual Desktops and we want to deploy Azure database for PostgreSQL (database-as-a-service). Since ST_GEOMETRY cannot be enabled on databases in the cloud can anyone provide instructions for converting the existing ST_GEOMETRY spatial types to POSTGIS? thanks.

‎06-13-2022

This continues to happen for me also. I just never hit Apply button on field calculator. That always negates this issue.

‎01-05-2022

I tried all of those suggestions, see above. Field names in my case are always lower case, since the backend is PostgreSQL. Realize objectid > 0 would return everything, I was just trying to determine if the problem was Filter() or FeatureSetByName(). See below, problem was Filter().

‎01-05-2022

Here's the solution, scrap the Arcade Filter() function, it simply does not work with globalid while offline. This expression works fine both online/offline. Upper/Lower case globalid wasn't the issue, both FM and map viewer BETA in Enterprise 10.9 were displaying Upper case. But, just for safety I used Lower. var relate_guid = $feature["rel_guid_pcs"]; var featSet = FeatureSetByName($map,"Point Count Stations", ['pcs_id','globalid'], false); for(var feat in featSet){ if(Lower(feat.globalid)==Lower(relate_guid)){ return feat.pcs_id; } }

‎01-05-2022

Online, both app and Map Viewer BETA both of these filter expressions work, offline in app, neither of them work. "globalid = '" + relate_guid +"'" "globalid = @relate_guid" Online/Offine, this filter expression works: 'objectid > 0' @DougBrowning, can you try a filter expression in your environment that uses globalid? It would be great if you could repo this.

Online Status	Offline
Date Last Visited	Wednesday

My Ideas

Latest Contributions by danbecker

Re: ArcGIS Datastore, Different Data Disk (directory)

Re: ArcGIS Datastore, Different Data Disk (directory)

ArcGIS Datastore, Different Data Disk (directory)

Azure application gateway and TLS termination

Re: Migrate on-prem PostgreSQL to Azure db for PostgreSQL (DBaaS)

Re: Migrate on-prem PostgreSQL to Azure db for PostgreSQL (DBaaS)

Re: Migrate on-prem PostgreSQL to Azure db for PostgreSQL (DBaaS)

Re: webgisdr - mixed Linux/Win Environment

Re: Migrate on-prem PostgreSQL to Azure db for PostgreSQL (DBaaS)

Re: Migrate on-prem PostgreSQL to Azure db for PostgreSQL (DBaaS)

Migrate on-prem PostgreSQL to Azure db for PostgreSQL (DBaaS)

Re: Field Calculator Overwrites Previously Selected...not currently selected.

Re: FeatureSetBy Arcade Functions Supported in Field Maps App?

Re: FeatureSetBy Arcade Functions Supported in Field Maps App?

Re: FeatureSetBy Arcade Functions Supported in Field Maps App?

ESRI Survey123 Website Sending Report API Requests...

Re: Portal for ArcGIS upgrade from 11.5 to 12.1 no...

Re: Azure Files premium file share - SLOW File Geo...

arcpy layout.export - hosted feature layers not sh...

Re: Survey123 Date Only shows incorrectly on Repor...