Latest Contributions by RyanUthoff

‎02-12-2024

This might be what you are looking for. Basically, you'll need change switch out your data source from your old SDE connection file with SQL DB authentication to a new SDE connection file with SQL Windows authentication. You should be able to do it with a little bit of Python. Although, disclaimer, I have attempted to do this and it ended up not working quite right and I just had to do it manually. I'm not sure if I was just doing something wrong or what. But regardless, I think this page will help you bulk change the data sources. https://pro.arcgis.com/en/pro-app/latest/arcpy/mapping/updatingandfixingdatasources.htm Depending on how many layers you need to change data sources on, it might be faster to just manually change them as opposed to trying to write some Python code to do it. Just depends on how fast you are and how well it works for you.

‎01-30-2024

We're good with Windows Updates and we're not noticing any network issues. We have two different ArcGIS Enterprise deployments and both are configured the same way. Only one of them is having this issue and we're not seeing any network related issues.

‎01-30-2024

I'm having an issue with one my ArcGIS Enterprise 11.1 deployments where the two machine, active-active server site randomly re-synchronizes with the site which causes a partial outage. Specifically, I get these error messages in the logs: The server machine 'machine name' is synchronizing with the site. This will take a few minutes and during this operation all administrative operations will be blocked. Resetting the synchronization flag on the machine 'machine name'. Resetting the synchronize flag as synchronization is now running. Failed to update the security configuration. Exception Could not connect to the ArcGIS component at URL 'https://machinename:6443/arcgis/admin/local/manageHandler'. The ArcGIS component on that machine may not be running or the machine may not be reachable at this time.Error: Connection refused: connect There were a couple other variations of that same error message from above. But after a few minutes, it finishes and everything goes back to normal. And while it doesn't happen at the same time, this has happened on both machines. So, it's not isolated to one machine. Is there any reason why this is randomly happening? There are no other errors in the server logs. No errors in Windows event viewer, and the ArcGIS Server service doesn't get restarted or anything. Technically, we don't experience an outage because the other ArcGIS Server site handles the load until the other server site comes back online. But, it's also not ideal for one of our servers to essentially be inoperable for 20+ minutes while this is happening.

‎01-29-2024

According to the What's new in ArcGIS Pro 3.2 documentation, it looks like that functionality was added in 3.2. You can find it under the "Reports" section. https://pro.arcgis.com/en/pro-app/latest/get-started/whats-new-in-arcgis-pro.htm

‎01-24-2024

I believe this is expected behavior. ObjectID columns are columns that are managed by Esri and we typically don't have much control over them. It's typically not recommended to use them for reasons like this. With that being said, the Copy tool (not Copy Features) should maintain the ObjectIDs.

‎01-19-2024

What Esri version of the EGDBs are they? Not the SQL Server version, but the Esri version? Starting at 3.0 (I believe), the DB name is no longer included in the of the feature class. This is actually a huge change because we now have the ability to rename EGDB's without completely breaking them within Esri. But Esri did warn that some workflows would have to change in how the feature classes are referenced. There is documentation about it, but I'm struggling to find it at the moment.

‎01-16-2024

Another question related to WebGISDR. Is changing the Portal Database password in the Portal Admin endpoint going to cause any issues related to this bug? We're testing the WebGISDR but don't know the password to the DB which we need for creating the initial Portal admin account in the new environment in order for the restore to work. Of course we won't do the restore "for real" until after the fix is released. But I can't test the restore without changing the password first. If there is any risk associated with changing the Portal DB password, we'll wait. Otherwise, we'd like to go ahead and do some testing while we wait for the fix to be released. I'm just being overly cautious since I don't want to "trigger" the bug.

‎01-15-2024

I know nothing about fingerprint scanners or what's required of the fingerprint output, but wouldn't you be able to save the output of the fingerprint reader as a photo and save that to the S123 form?

‎01-11-2024

I understand you don't want to use FGDBs, but in this case, does it necessarily matter? The reason I ask that is because the data is going to be stored in AGOL, regardless if you use a FGDB or shapefile. So you could temporarily use the FGDB to enable GPS metadata, then publish to AGOL and then at that point you wouldn't need your FGDB (or shapefile) at that point. Then, the data would be collected in AGOL/Field Maps, and you would have the option to download the data as a shapefile (which would contain the GPS metadata fields). Besides this, I'm not sure if it's even possible to enable GPS metadata on a shapefile.

‎12-27-2023

It's a single machine site running Windows Server 2019.

‎12-19-2023

@JonEmch Is WebGISDR affected by this defective patch? Hypothetically, let's say we have an ArcGIS Enterprise deployment with the defective patch installed. If for some reason, we needed to do a WebGISDR restore to a brand new environment with a fresh installation of ArcGIS Enterprise (without the defective patch installed), would we expect to see any problems with that? Also, thank you for adding the additional information to the knowledge article! It is very detailed and thorough which I appreciate! Edit: I realize that doing a WebGISDR restore to workaround this issue isn't ideal and my not be "recommended." I'm asking because we were already considering moving our Enterprise deployment to new machines, before this defective patch was made public.

‎12-18-2023

Yes there is! I can't guarantee it will work depending on your IT security, but theoretically, if your users have access to the floating license, this method should work. Download LMTOOLS by Flexera. I actually downloaded a version from Autodesk. It's not specific to Autodesk, so it works fine for Esri. https://www.autodesk.com/support/technical/article/caas/tsarticles/ts/EB0JPJWkEgBXjZRPBONh1.html Once you install it, open it and on the Server/License File tab, click "Configuration using License File." And in the box, type in your server name that contains the floating license server and put an "@" in front of it. For example, @Servername. Afterwards, click the "Server Status" tab. Click "Perform Status Enquiry" and within the box below, it will include information about who is occupying floating licenses. I'm sure there are more elegant solutions, but this was good enough for me.

‎12-18-2023

I recently upgraded our dev environment from 11.1 to 11.2 and also use Carbon Black and didn't have any issues. Regardless, if you think Carbon Black is the problem, you should be able to see any blocking events in Windows Event Viewer. This is how I determined that CB was blocking parts of an ArcGIS Monitor installation. https://community.carbonblack.com/t5/Knowledge-Base/Carbon-Black-Cloud-How-to-Review-Blocking-Events-in-Windows/ta-p/95358

‎12-14-2023

Thank you for the link to the ArcGIS Trust Center. That gives me the information I was looking for. The technical support articles I've seen haven't included that link, so I wasn't aware it existed. And bug fixes in the corrected patch give the impression that the bug only exists in 11.1, even though the Portal for ArcGIS Validation and Repair tool is available for 10.8.1, 10.9.1, and 11.1. So overall, it's a little confusing to figure out what's going on but I appreciate your response.

‎12-14-2023

I just received notice of this yesterday and have this defective patch installed. Per the email that was sent out, it said the patch defect can have "serious consequences", yet doesn't specify what the "serious consequences" are. As the server administrator, I need to know what these consequences are so I can monitor for aberrant behavior like the original poster mentioned. Edit: I realize that even if we knew what the consequences are, we might not be able to do much about it until Esri releases the fix. But at least I'd be able to immediately pinpoint the problem instead of spending hours trying to find it myself, reaching out to support, etc. We have hundreds of users that depend on Portal being up and running so it is vital that we are kept aware of these sorts of things and know what kind of behavior to expect from defective patches.

Online Status	Online
Date Last Visited	6 hours ago

My Ideas

Latest Contributions by RyanUthoff

Re: Update Data Source for SQL geodatabase from database authentication to operating system authentication

Re: Servers Randomly Synchronize with the Server Site, Causing Partial Outage

Servers Randomly Synchronize with the Server Site, Causing Partial Outage

Re: Create a report template in ArcPro 2.9

Re: When applying CopyFeature the OBJECTID Field changes.

Re: Enterprise Geodatabase item name differences (SQL Server)

Re: ArcGIS Enterprise Security Patch Dec 2023

Re: Collecting Fingerprint using Survey123

Re: Enable GPS metadata for a shapefile

Re: ArcServer Hosting Site 11.2 won't create the ArcGIS Server windows service!

Re: ArcGIS Enterprise Security Patch Dec 2023

Re: How can i see ArcGIS pro licenses in use while not on server

Re: ArcServer Hosting Site 11.2 won't create the ArcGIS Server windows service!

Re: ArcGIS Enterprise Security Patch Dec 2023

Re: ArcGIS Enterprise Security Patch Dec 2023

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