This SEVERE level log keeps popping up for a service that doesn't have any Attribute Rules applied to it. I've been able to fix the issue on other services that do have attribute rules applied in ArcGIS Pro. However, this one does not. It even crashed the server a couple times because it came up so frequently in the logs. Anyone else run into this error before?
Just now got this for Featureclass with AA rules in ArcPro. Curious, how were you, "... able to fix the issue on other services that do have attribute rules applied in ArcGIS Pro" ? I've not yet found any info but this thread.
I should clarify... I made (empty) featureclasses in ArcPro within a SDE dataset and created an Attribute rule for one field. Upon opening the same FC in ArcMap/Catalog (10.8) I get the error message (so, not quite the same as your issue). But, hoping your fix might help me.
Hi George, I am getting the same error that you describe in your message with a feature class created within an SDE dataset in Pro that has an attribute rule applied to it. When I search the error this is the only relevant result I can find. Did you by any chance ever figure out how to resolve this error?
Hi Mary, George, I am getting the same error with a feature class in an enterprise geodatabase with attribute rules added. Did you manage to find a resolution? We have been working with the attribute rules in the feature class for a while, and the problem only happened recently. In my case, I noticed that we are not able to view feature classes using the data owner connection in the catalogue (AA rules were added with data owner), so I'm not even able to delete the AA rules. Appreciate any advice.
I realized that the problem for me was that I had set up the attribute rules in ArcPro, and then I forgot that once you do that, you then are unable to do any geodatabase administration tasks using ArcGIS Desktop. I was trying to enable versioning and editor tracking on my feature class through ArcCatalog and getting the error, but once I switched to ArcPro, it worked fine. Just something to keep in mind for those of us who have not 100% transitioned from ArcGIS Desktop to ArcGIS Pro!
We are also having the issue on services that DO HAVE attribute rules applied. Have been unable to find any documentation addressing this specifically. This is our first use of the AA rules. Any replies here by those who have been able to resolve this would be greatly appreciated.
This may not be the same issue in full, because your environment is different than mine.
Currently working in FGDBs, with no live links to webmaps or portal (yet)
I am also getting this error when attempting to use a Feature Class with attribute rules created in ArcPro inside an ArcMap mxd. To my understanding, ArcMap does not support AA created in Pro, and after attempting to 'Disable' the AA in ArcPro environment, I was still unable to load the layer.
I had to export a new version of the layer and remove the AA from it in order to go around the error.
I anticipate in the future, we are going to have an EDIT version (w/ AA) of the data, that feeds into a READONLY (w/o AA) in order to go around this issue.