Latest Contributions by DougGreen

We have just had this start happening on a 10.7.1 on windows 2016 with a federated server. It started being observed a couple days after updating our ArcGIS Server to use a new self-signed wildcard cert. We have tried using the same cert on our portal machine to see if that resolved the issue but it has not. Our architecture is as follows: Server A: ArcGIS Server, Data Store (inside firewall, Self-signed Cert) Server B: Portal for ArcGIS (inside firewall, Self-signed Cert) Server C: Web Adaptor for Server, Web Adaptor for Portal (outside firewall, CA Cert) We are somewhat surprised that this is still just sitting here with a bug like this unresolved. How have you all moved past this or are you just using this method to delete the orphaned items constantly? ... View more

Yep, that version is fine. It's the one used when the error is produced. It continues to happen even when unregistering so version specific errors are ruled out.  I heard back from them and they ended up telling me that this is a bug. #BUG-000125941 ... View more

Joshua, I am running these queries in SSMS. These two feature classes are not versioned but on feature classes that are, I append "_evw" to the end of the name to select from the multi-version view of the table/featureclass. Good thought though. Doug ... View more

I found this as I was getting the same exact error in Desktop. I use backend STIsEmpty(), STIsValid(), STIsSimple() as mentioned in previous comments. All were valid and simple, none were empty. We are on 10.5. I have discovered something after thorough testing. I have narrowed it down to an issue with Enterprise GDBs in SQL server (haven't tested in Oracle etc).  Place two feature classes with non-overlapping extents from an EGDB in a map. Run "Select by Location" in the following scenarios: Select one feature in FC1 and then run "Select by Location" selecting features from both FCs within a distance that will not reach features in FC2. Error occurs Select one feature in FC1 and then run "Select by Location" selecting features from both FCs within a distance that will reach features in FC2. Error does not occur Select one feature in FC1 and then run "Select by Location" selecting features only from FC1 within a distance that will not reach features in FC2. Error does not occur Select one feature in FC1 and then run "Select by Location" selecting features only from FC1 within a distance that will reach features in FC2. Error does not occur Repeat the inverse of this (swapping FC1 with FC2 in each scenario) and you will get the same results. Conclusion: Error is produced when selecting features from both FCs when the search radius does not intersect the second FCs extent. If this same test is performed with the feature classes in a File GDB, no errors are shown. I have called and I'm waiting for a call back from Tech Support. I have tested this in a 10.4.1 and 10.5 GDB. I don't know if perhaps it is fixed in a newer release. ... View more

We are having related but not identical issues. We have some of our layers dropping from a map but not from the actual service itself. We have put a ticket in and they are researching it. We are not 100% sure it's windows updates because we only update on Mondays and this occurred on a Wednesday night. We will post more as we learn more. Glad you shared this though. ... View more

I found a solution to our problem and felt the need to share it here. What ended up fixing the issue was to drop and recreate the login for the AD group at the instance level and then also drop and recreate the user at the database level for that AD group. I am not exactly sure how this solved the issue but I needed to do it for another issue and we discovered it fixed this issue as well. ... View more

Dan, This is more than I was able to find through searching so it is helpful. However, I landed on this thread searching for a scenario that is not documented. I think others may be asking it in other words but instead, I'll try this approach. We have users that have their phone fall in the sewer or the stream or get mangled by kids and wiped, etc. This basically deletes the device data without ever letting the replica parent know. How do I find out that a replica version needs deleted and its associated replica needs unregistered? For all my script knows, there's still a device with collector installed that has that version checked out. I am not close enough to the staff to know of these occurrences and they don't think to tell us these sort of things. ... View more

Rex Robichaux‌, thank you for your additional info. If I understand you correctly, you wanted to confirm that we did not modify the default database role "public"? Correct, it appears as shown below: I likely will create a new case for this. To further the confusion, there are other enterprise geodatabases in the same instance using the same active directory group, that we are able to view data in. That started me thinking it was something to do with the database. Then I tried importing a map into ArcGIS Pro that contained layers from the database that we cannot view layers in and it still shows all the layers without red exclamation points. However, it does take a bit longer to open a map containing layers from that database. ... View more

We currently have a map that we've just started seeing this behavior on as well but I am reluctant to provide a link because it might unnecessarily inflate our usage statistics . It has one line layer that has enabled popups but the popup shows up when clicking on empty space in the map and simply says "No Information Available." This is leading our users to think something is broken. ... View more

Hi Rex, Thanks for your reply. It is good to know it is actively being researched. Our support ticket #02071470 was closed, due to the fact that we could explicitly grant each user permissions to each individual feature class or table and no other fix was available. For us, that meant that we rolled back to 10.5 since our other engineering extensions did not support 10.6. For now, this has got the majority of our users up and running. However, we are now seeing this behavior in the latest release of ArcGIS Pro (2.1.2). I have to explicitly grant permissions to each user for each feature class or table. That's not really going to work for us moving forward because that's hundreds of items to manually a good number of users to. If you have any pull to get this issue resolved, that would be really helpful. Just to more clearly state the issue: gdb items stored in sql server with privileges set to an AD group are not visible to members of that group when connecting to the database in ArcGIS Pro 2.1.2. We are in SQL Server 2012. Our GDB is still at version 10.4.1 because we are not able to upgrade until a few remaining clients are able to upgrade. Thanks, Doug ... View more

We have this same issue. However, our situation is that we have some features in the database that are not to be viewed by those that have not been made aware of a non-disclosure agreement. So we use active directory groups to grant viewing privileges to different sets of data. I just got off of the phone with support and she indicated that this patch may only work for explicit user permissions and not groups. I tested by adding an explicit permission to a feature class for a particular user and she was correct. Using group permissions nothing is visible but with a specific user granted permission, the only thing visible in that database is that one feature class. Is this also being addressed? We are not able to move to 10.6 because of other extensions that are not yet compatible. So that would mean a rollback to 10.5. ... View more

Doh! Thanks Morten. I tried finding that in the documentation. Is it in there somewhere and I missed it? ... View more

This is an excellent idea and carries an idea I recently posted to the next step. Is there a way we can combine these ideas to gather more support. Everyone I'm talking with in our region is trying to accomplish the auto-populating of fields using collector. https://community.esri.com/ideas/13688  ... View more

We have not seen any trouble with this. No corruption. And this GDB is used to publish layers to ArcGIS Server. It has worked flawlessly since implemented. Just noticed you asked if there were any users who had issues. There are no MXD's pointed to this data other than those used for creating the map services. Therefore, the locks are created by ArcGIS Server. In our case, the server refreshes bad connections every 30 min so we don't have a problem. I don't know what it would look like to a user if they had a map open and you ran this. ... View more