Latest Contributions by RyanUthoff

‎06-12-2024

Thanks for the reply! We've already made sure that all the Esri directories have full permissions to the service account running server, so unfortunately that wasn't the issue.

‎06-10-2024

I've tested an already existing 2016 EGDB with ArcGIS Pro 3.3 and I was able to connect to it, but I wouldn't recommend it since it's not officially supported.

‎06-07-2024

This is going to be an organization dependent question. It all depends on the organization's requirements. With that being said, best practice dictates to have as few Administrators as possible. Organization's should follow the principle of least privilege. Only give users the privileges they need and nothing more. If necessary, create a custom role for them that gives them what they need. Unfortunately, some people aren't happy with the principle of least privilege as you're experiencing now and they just want full access to everything. But I agree with your approach with working with them to create a custom role with only what they need.

‎06-07-2024

This isn't the first time there have been inconsistencies with the ArcGIS Enterprise installation/upgrade documentation. I called it out here for the 11.1 documentation. https://community.esri.com/t5/arcgis-enterprise-questions/inconsistent-arcgis-enterprise-upgrade-order-in/m-p/1302531 In reality, maybe the order doesn't matter and that's fine. But it doesn't give me a warm and fuzzy feeling when we have inconsistent documentation and that even Esri staff is deviating away from the "official" documentation in their own upgrades. I mean someone made the decision to change the upgrade order in the documentation and there must be a reason behind it. What is that reason?

‎06-05-2024

Currently, when attempting to create a hosted feature service in Portal and when the ArcGIS Data Store is in read only mode, there is no notification in Portal and the page just endlessly spins saying "Creating feature layer." This results in wasted time for server administrators going down the rabbit hole of trying to troubleshoot the problem when a simple notification in Portal when trying to create a hosted feature service stating that the ArcGIS Data Store is in read only mode would be an easy and informative fix. I think it is odd behavior that Portal still allows you to attempt to create hosted feature services when the ArcGIS Data Store is in read only mode. It should either block that functionality completely, or at least notify you that it is unable to due to being in read only mode, as opposed to Portal just endlessly attempting to create a hosted feature service with no success and no error messages.

‎06-04-2024

Oh wow, I'm surprised someone else has this issue! I'm still working with Esri support. I highly highly highly recommend you create an Esri support case if you can. The more people who create cases about this issue, the more likely we'll get a resolution. One thing that might be worth testing is if you can create hosted feature services directly through Portal. It might take a few attempts to receive an error though since sometimes it works, and sometimes it doesn't. I'm curious if our environments are similar. By any chance do you have multiple ArcGIS Server machines in the same site?

‎06-03-2024

My views of WebGISDR have changed since I previously replied to this post. I definitely agree with what you said, but now I believe that WebGISDR should be used to supplement other forms of backups, and not be used as a replacement. We were affected by a bug in the WebGISDR that resulted in an inability to do a restore. It took Esri 10 months to fix it and release a patch for it...... Luckily we were using WebGISDR to duplicate our environment to a test environment and not actually restore in a disaster recovery scenario. But if we needed to do a recovery, our ArcGIS Enterprise deployment would be gone and we would have lost everything because of bugs within Esri's software. So my advice for those wondering about DR solutions is to use Esri WebGISDR to supplement other DR backups, such as VM snapshots, but to not solely rely on it.

‎05-24-2024

I was referring specifically to enterprise geodatabases. Not sure about file geodatabases.

‎05-24-2024

When you upgraded, did you upgrade the geodatabase to a 3.3 database as well? Alternatively, is this a new geodatabase you created after you upgraded to 3.3?

‎05-21-2024

What parameters are you using in Pro to export to PDF? I just tried exporting to PDF using the default and it opened fine for me with no errors.

‎05-08-2024

I'm running the latest version of ArcGIS Monitor and I'm also experiencing this behavior. I just migrated from the ArcGIS Monitor host being the agent for all our machines to having Monitor agents installed on each machine. I removed the ArcGIS Server component and replaced it with the new Server component pulling from the agent installed on the ArcGIS Server. But now I have duplicate feature services in Monitor. One feature service pulling from the host agent (which isn't collecting any metrics), and one feature service pulling from the Monitor agent installed on the ArcGIS Server machine (which is correctly collecting metrics). Edit: And like OP mentioned, there is no way for me to remove those duplicate feature services associated with the old Monitor agent.

‎05-07-2024

This is a great point, and quite frankly, something that has frustrated me as I've found out these compatibility requirements the hard way. For example, high precision date fields are only compatible with 3.2/11.2. I didn't realize that until it was too late. I think having a feature compatibility matrix would be VERY helpful. Something that is very easy to look at and quick to reference. Because right now, I have to dig through and research the release notes for each version to determine compatibility requirements which even then, isn't 100% clear.

‎05-06-2024

I've used the WebGISDR to consolidate a multi-machine deployment (Portal, 2 servers, data store) to a single machine. It worked fine for me. They key is ensuring your destination public URL is the same as your source public URL. This can be easily done by modifying your hosts file in the destination environment. Below is a good blog post from Esri describing how to do it. https://www.esri.com/arcgis-blog/products/arcgis-enterprise/administration/migrate-to-a-new-machine-in-arcgis-enterprise-two/ We also migrated from on-prem to AWS. And while we chose not to go the WebGISDR route, our third party GIS consulting firm recommended WebGISDR as an option to do that migration.

‎04-29-2024

There really isn't a right answer to this question. The "best" answer is placing the EGDB on a SQL Server instance that has enough resources to meet demand AND has good connectivity to all GIS users who will be interacting with it (whether it be through ArcGIS Pro, Enterprise, etc.). There are no issues with mixing non-EGDBs and EGDBs together on the same SQL Server. What matters is that the SQL Server has enough resources to meet the demand.

‎04-29-2024

This doesn't directly answer your question/idea with ArcGIS Monitor, but you might be able to accomplish this with webhooks outside of ArcGIS Monitor. For example, I've configured webhooks with MS Power Automate to write an entry to a SQL DB table anytime a feature service or web map is created/modified/deleted. And it includes the feature service/map name, the name of the person who made the change, and the time they made the change. It won't tell you what the change is, but it's very good at telling you who made the change and at what time.

Online Status	Online
Date Last Visited	Thursday

My Ideas

Latest Contributions by RyanUthoff

Re: Intermittently Unable to Create Hosted Feature Services

Re: SQL Server 2016 Compatibility with ArcGIS Enterprise 11.3

Re: AGOL Administrator Question

Re: ArcGIS Enterprise 11.3 vs 11.1 Portal Web Adaptor Install Order

Portal Notification that Data Store is in Read Only Mode when Creating Hosted Feature Service

Re: Intermittently Unable to Create Hosted Feature Services

Re: WebGISDR tool vs. snapshot

Re: Geodatabase not compatible with older versions?

Re: Geodatabase not compatible with older versions?

Re: Urgent: Exported pdfs no longer open after 3.3 ArcGIS Pro Update

Re: How to remove Service Components?

Re: New Geodatabase Features Add Functionality But Complicate Compatibility and Interoperability

Re: Consolidation and migration of Enterprise 10.9.1 to Azure

Re: sql server database location for enterprise

Re: ArcGIS Monitor for change management

Re: Best Practice to see video data via Online

Re: Best Practice to see video data via Online

Re: SAML Authentication for Third Party

Re: SAML Authentication for Third Party

Re: SAML Authentication for Third Party