Latest Contributions by DEWright_CA

Very curious why it takes 12 minutes in Pro 3.1 to build a Multi-Role locator using Tom-Tom or Here Address-Points and Street-Lines, but in Pro 3.3 it now takes 2.5 HOURS for the same source-data and same configuration. ... View more

Be aware - While upgrading our DEV Environment from 11.1 to 11.3; the Portal installation steps ran well until the final screen. When I was presented with this: Upgrade Status: success with warnings  Backup content, database, and index directories: completed Upgrade portal content: completed Upgrade database: completed Migrate configuration settings: completed Update configuration settings: completed Configure index service: completed Reindex: completed Warnings:  Failed to configure languages content during an upgrade. I was advised by my Tech-Advisor that this might be the same issue as https://support.esri.com/en-us/bug/esri-content-is-missing-postupgrade-in-arcgis-enterpris-bug-000167282 ; and was advised to open a ticked to get attached to the bug. Currently, Customer-Service/Support has no analysis about a root-cause of the issue; so you are not able to review your system to see if upgrading your system will result in the same failure and there currently is no known repair method except to roll-back using a WebGISDR and re-upgrading and hoping it works properly this time/ ... View more

When publishing a GP tool (after a tool is run in ArcGIS Pro) to become a geoprocessing tool it is possible to see a major breaking issue.  Recently we found that a shared path: "\\server\share\contentfolder\myDB.sde\myFeatureLayer" Was being mangled in the publication/conversion process. Pro is taking in these strings\paths and inferring in them that they need to be made "Server" friendly based on assumed needs. The above folder was being turned into: "%scratchworkspace%\\server\share\contentfolder\myDB.sde\myFeatureLayer" This then means that all connections/functions depending on these strings are now broken. The big issue we have is that this script/tool is now broken, and while the tool will publish the function will not work and will return a lovely 99999 error that the tool could not be executed. What we need is a way to review/approve the changes being made to a GP tool that is being published so that Pro is not making a change that in fact is not needed to happen and breaking the script in such a way that renders it inoperative. Troubleshooting and diagnosing this issue was complex, it required connecting to the ArcGIS-Config folder where it was published and running the script locally to the server to get to the "path not found" level issue from where the folder/string was changed. ... View more