Latest Contributions by DavidColey

Yeah who knows @Joshua-Young   My issue was more like what @NicolasGIS encountered.  I think the DS going from pg16.x to ps18x and skipping 17.x may have a role, like I mentioned earlier.  But IDK.  Like @Scott_Tansley - I to now have DS restore in my bag. ... View more

Hi @Joshua-Young - basically yes.  We (Support and I) essentially performed a new install of 12.1 datastore.  Our Relational Datastore is on a stand-alone server in our distributed deploy - i.e. only the Relational is defined on this server and is the Primary. So we had to think of it as a disaster recovery as defined here, so I have to push back a little on @Scott_Tansley here, in that it is documented as a supported recovery method: https://doc.esri.com/en/arcgis-enterprise/latest/administer/dsu-restoredatastore.html?pivots=os-windows "If you cannot recover the data store, install ArcGIS Data Store on a new machine, do not configure the data store, and restore the last full backup to the new machine". For post-install steps, I defined the datastore as a relational store type then stopped.  I did no further configuration on the new 12.1 install.  Then I moved into the command line utility and ran the restore datastore following this example in the above help section: ***** "In this example, the relational store is restored to a new machine using a backup file named movedatastore. When you restore to a new machine, you must specify the location of the backup file and the location of the new ArcGIS Data Store content directory. Because the hosted feature services are still running on the same GIS Server site with which the relational store is registered, --bound true is not required, but the GIS Server URL and administrator credentials are required:  restoredatastore --target movedatastore --source-loc \\buserver\data\backups --data-dir D:\arcgisdatastore --server-url https://gisserver.example.com:6443  --server-admin siteadmin --server-password $Aup.4s ****** I did make sure the datastore was unregistered from the hosting site first by un-registering it from Server Manager.  Then after the restore utility completed, the datastore was discovered as itself using the describedatastore and validate with the hosting site.   I then needed to run the configurebackuplocation with the --change argument to re-set my backup location and then I needed to re-run the replacesslcertificate, and then create a new full backup. Our dump file is 6Gb in size, so the restore operations took about 20 minutes or so So now what we have is a new 12.1 datastore, not an upgraded one, in that in running diskcleanup has nothing to clean up....  ... View more

Yes I agree with @Joshua-Young and @NicolasGIS.  @jill_es - I did work with support as I indicated above, and I am all set with our upgrade but it took a new install of the 12.1 relational datastore type and a restoredatastore command as I indicated above. In my environment the:   Portal for ArcGIS Security 2026 Update 1 Patch D for Windows and Linux is now available  already showed as installed on my 12.0 environment via the Portal patch notification tool.  No other patches for Portal at 12.0 showed as available via the patch notification tool This is why I felt confident going ahead with with the upgrade from 12.0 > 12.1.  So to me, the issue is not resolved. ... View more

Hi @Joshua-Young and @JonEmch  - I too encountered a failed upgrade for the relational datastore going from 12.0 > 12.1.  The initial upgrade error was the same when using the post-upgrade wizard/browser: "dsadmindb not found. Cannot complete upgrade". I said, ok, let me try running upgrade command thru command line.  This produced a different set of errors: Attempt to configure data store failed. Caused by: Database upgrade failed for relational store. Caused by: Failed to start relational store. Caused by: Connection timed out while waiting for relational store machine to start. With esri support, we eventually had uninstall the data store, wipe the install directory, rename the old D:\arcgisdatastore directory to D:\arcgisdatastore_old, Install datastore as a new 12.1 datastore, re-specify the new datastore directory at D:\arcgisdatastore. At this point however, I did not go through the post-upgrade.  Went directly to command line utility and performed the restoredatastore command as specified here: restoredatastore --target movedatastore --source-loc \\buserver\data\backups --data-dir C:\datastore --server-url https://gisserver.example.com:6443 --server-admin siteadmin --server-password $Aup.4s This then validated in both Server Admin and Server Manager. However, we still do not know why the upgrade failed.  I suspect because Entpersrise relational datastore at 12.0 is at pg16.x and relational datastore at 12.1 is at pg18.x and some module was missed.  But I have no idea. @Scott_Tansley  @NicolasGIS  ... View more

sometime next week perhaps after we upgrade to 12.1, thanks. ... View more

Ok thanks for this @Joshua-Young - I'm in the same environment - multi-machine deploy, everything separated.  Like you, I always upgrade with AV disabled. I'm really wondering what the malfunction is here, other than what seem to be issues with the security patch updates, because I had no issues upgrading from 11.5 to 12.0 back on December 6 2025.  The only real issue that arose for us at 12.0  post upgrade was this: BUG-000181250 - Cannot disable or enable ArcGIS REST Services Directory in ArcGIS Server Administrator Directory. At least one reply here: https://community.esri.com/t5/arcgis-enterprise-portal-questions/portal-for-arcgis-upgrade-from-11-5-to-12-1-not/td-p/1704601/page/2 from @NicolasGIS suggests that esri support said they did complete a successful 12.0 > 12.1 But for now it looks like anyone going from 11.5 > 12.1 has to do what @Scott_Tansley did.  Meant to add that then of course having to remove patches before an upgrade is the opposite of what any of us have learned over the years..... ... View more

HI @Joshua-Young - is this a base deploy on a single machine or are you trying to upgrade a multi-machine deployment?  And was Active Virus scanning running during your upgrade or were you able to suspend AV? I'm at 12.0 on a multi-machine deploy and am wondering if anyone has attempted that upgrade 12.0>12.1 Sorry I didn't see this thread: https://community.esri.com/t5/arcgis-enterprise-portal-questions/portal-for-arcgis-upgrade-from-11-5-to-12-1-not/td-p/1704601 Still wondering on a course of action then for 12.0 > 12.1.  Datastore has no patches to remove at 12.0 on my multi-machine deploy ... View more

I can confirm that I too can publish a vector tile package that uses a state plane coordinate system and the ArcGIS Online tiling scheme.  I overwrite one every week for our State Plane basemap tile. Currently I am in ArcGIS Pro 3.7, Enterprise 12.0.  For tlpk (like an old map tile package or a tiled image layer), that is still not the case.  I cannot use our state plane coordinate system and the ArcGIS Online tiling scheme together.  ... View more

Hi @DerekLaw  - there doesn't seem to be an 'Issues Addressed' section in the current 2026 Release Notes: https://support.esri.com/en-us/patches-updates/2026/arcgis-monitor-2026-0-release-notes#features-and-enhancements Will the tech / document support team be updating this document to include an issues addressed section? Thanks -  ... View more

Hi @RobertKrisher - in doing a lot more troubleshooting on this it does appear that the gp tool for validate un topology will now only run against a named user version... It simply will not run against the sde.DEFUALT version as the unowner portal account when connecting to the Utility Network service in Pro 3.7, or when trying to connect to portal via a python workflow, whether in the instant window, a model, or a notebook. Thanks @rlyding  ... View more

If this is true then this is a total disaster.  Are they telling me that I will no longer be able to publish different layers from the same file geodatabase source?  Or the same sde data source?  What's the problem?  Too many malicious AI's stealing publicly share resources and 're-publishing' as their 'own' resources? I can tell anyone who cares that an insurance company has been 'harvesting' our publicly available Image Server image services via a 'pythonx' method performing an 'export image'.  When I reversed the IIS call I could see that the company does 'predictive roof failure' analysis. In the meantime, my services are experiencing 10s of 1000s of requests per second.  All the company had to do is to ask for the imagery and we would provide it.  Instead, they decided to make their own shortcut.   Why? Because now they can. Will this 'service update' or 'service impact' address these BAD ACTORS??  Somehow I doubt it.  Probably the reverse. Have a nice weekend. ... View more

Yes thanks @RobertKrisher and that's what I told @rlyding - IDLE is simply when you right-click an *.py file in windows and select 'Edit with IDLE (ArcGIS Pro): There is no configuration of that environment, other than like setting indents vs spaces, etc. Could be something with dot10 is messing it up for that tool.    ... View more

Yes @RobertKrisher the tool did run successfully inside ArcGIS Pro using the toolbox tool from both the default arcpy environment and then from the cloned environment (after I ran the conda install -c esri untools --insecure).   The validate portion of the script runs nightly from a Windows task where it calls the python.exe from the command and uses the unc path to the full script as the task argument - our standard Windows Task Scheduler procedures we've been doing for years. Regardless, when I try to run my UNMaintenance.arcpy script from the python IDLE window, I get the error.   All of my other scripts that use arcpy like FeatureSharing run this way and are just fine.  @rlyding  ... View more

Well I'm at a loss.  The tool simply will not run from the python IDLE, whether the arcpy environment is set to the default or to the clone. All of my other hundreds of scripts run just fine from the IDLE, including ones that use the: import arcpy arcpy.SignInToPortal(https://myorg.net/portal, 'username', 'password') L950SewerUN_Utility_Network = "https://myorg.net/agsfed/rest/services/CollectorServices/Sewer_Utility_Network/FeatureServer/950" arcpy.un.ValidateNetworkTopology(in_utility_network=L950SewerUN_Utility_Network, extent='474063.442811626 1070897.65903111 474156.933218947 1070963.47578807')   so who knows. Everytime I try this run from the idle as the unowner user it comes back as ERROR 004403: Unable to validate network topology because another session is currently validating.Failed to execute (ValidateNetworkTopology).     ... View more

Thanks for the replies @rlyding @RobertKrisher @gis_KIWI4  - We may have narrowed this down some.  I ran a test on a disconnected Service Connection sewer device in our Sewer UN.  I set up a version off the sde.Default, dropped the point disconnected to from its service line to create a dirty area and then used the Validate topology toolbar GUI tool. The validate was successful. Now - because I am our org admin I set up an arcpy clone so that I am able to take advantage of adding in packages and being able to update the arcgis. I switched back to the default arcpy environment, repeated the edit steps above except this time I ran the validate topology from the toolbox tool. The validate was again successful. Long story short, I may have a bad clone.  Typically when I upgrade pro I always delete the clone, perform the update, re-clone the environment to the default clone location then run the conda update -c esri arcgis command. However, when I completed the conda update and searched for the untools package, it was not present for 3.7.  Now it is: Last week, I did not get these options when updating the clone for conda install -c esri untools --insecure    The following packages will be downloaded:       package                    |            build     ---------------------------|-----------------     certifi-2026.5.20          |  py313haa95532_0         131 KB     untools-3.7.0              |          py313_0         867 KB  esri     ------------------------------------------------------------ So we'll see.     ... View more