Latest Contributions by JoshuaBixby

While ArcGIS Desktop/ArcMap was licensed at the machine level, HKEY_LOCAL_MACHINE (HKLM), ArcGIS Pro is licensed at the user level, HKEY_CURRENT_USER (HKCU).  The ArcGIS Pro license for a user can inherit from a machine-level setting if configured correctly before the user ever launches ArcGIS Pro, but it gets a little trickier once a user has launched ArcGIS Pro at least once, which is the case here. I have mentioned "user" multiple times, that is because what is important isn't what settings you have for Pro when logged into the IIS server but what settings the credentials running IIS or IIS application pools have for ArcGIS Pro.  Since you have not provided any details about your IIS and application configuration, I can't offer any specifics.  Your issue is in the registry. ... View more

For clarification after looking at your video, the layer isn't failing to draw, it is failing to load.  A layer has to load before it can draw, and nothing shows up in your TOC so it isn't loading. You state the provider shifted from ArcGIS Server to GeoServer, but every HTTP call I see in the logs is for an ArcGIS product, so I don't even see any attempts to connect to a GeoServer service. Your question makes it seem like there are multiple basemaps that aren't loading, can you provide the URLs for some that do and some that don't?   ... View more

Often times when running a script with a service account, the licensing information for ArcGIS Pro is not configured correctly.  Whereas ArcGIS Desktop/ArcMap was licensed at the machine level, ArcGIS Pro is licensed at the user level.  ... View more

Mark, the link you provided was to the tool's page, which doesn't have the historical information.  I did find the toolbox history page, which does address the issue.  Although toolboxes also have a licensing overview page, the licensing information is still documented with the tool as well, so why is Esri handling licensing information and version history information differently?  Why not add history information to the tool as well licensing licensing information? ... View more

Start by going through this site: Esri Careers | Job Opportunities .  There is no one job at Esri, there is a wide range of positions and that wide range has a wide range of degrees and backgrounds that are important.  The bigger question is what do you want to do for a job, specifically.  ... View more

@PhilipWeeks, @LanceKirby2 , @HaseebAnwar , @tigerwoulds , have any of you opened an Esri Support case?  If so, what came of it?  Also, providing more details about your environment is helpful, like version to start. ... View more

Kory, thanks for the update.  Limiting offline time for licenses is definitely a positive step, but lack of "license borrowing" equivalent functionality will definitely keep us using Concurrent Use licensing for the foreseeable future. ... View more

Short answer, not documented, at least that I have ever seen publicly.  However, simple to determine, just run the version.sh or version.bat file in AGSSERVER/framework/runtime/tomcat/bin folder. ... View more

Kory, I agree with Stephen on thanking you for taking the time to put the video together.  I constantly try to tell users in my organization to submit their Ideas, that it can make a difference.  This video will help me promote that argument internally. ... View more

Can you share a stripped down sample of data that exhibits the behavior?  ... View more

SQL date functions tend to vary across data source, so there will be no single SQL that will be widely portable.  See SQL reference for query expressions used in ArcGIS—ArcGIS Pro | Documentation for more information and examples.  A purely Python cursor-based will be much more portable.  ... View more

The error message states some of the form fields are invalid, maybe some requirements changed sometime between 10.9.1 and 11.3 in terms of field values.  I suggest you start troubleshooting by revisiting the form fields and their values. ... View more

The Support analyst that logged this defect didn't realize Esri made intentional corrections to file geodatabase SQL support with Pro 3.3 to be consistent with the SQL standards, including changing how NULL is handled in certain situations.  I saw the documentation for the changes during Holistic testing, but I can't seem to find the public documentation about these changes.  I did find the originally logged defect around mishandling of NULL with file geodatabases that prompted Esri to make the updates, and it shows they made the change at Pro 3.3:  BUG-000168378 for ArcGIS Pro Regardless, I expect this defect gets closed as expected behavior.   ... View more