ArcGIS Pro 3.2 - Drawing Alerts - Returning STATE_ID Error when editing Polylines

[PeteJordan]

  I've upgraded to ArcGIS Pro 3.2 and found when editing a Versioned Geodatabase located within SDE that I'm now getting this error now:

  Seems researching it, I'm just finding some information that it could be linked to a corruption of the database somehow or at least something with the linking of the table via SDE.

  We've run some maintenance scripts as well as I've relinked the entire table as I have noticed that in 3.2 the New Database Connection has  changed it's look a little from 2.9.

  I'm notcing this is happening with several different tools, not just one.  Such as creating a new feature, reshapping, etc.  So I'm not thinking it's directly related to Editing of the Versioned Geodatabase on SDE.

  Any suggestions that I or the database side GIS guys can look at to try and resolve this issue?

  I'm assuming it's from 3.2, but not 100% sure as I haven't worked in this database for a little over 2 weeks, but I did notice it after updating to 3.2 at least...

Thanks

[AndreaB_]

same problem occurring here. I will reach out to Esri Tech support also.

[MollyWalkner_1]

Adding a comment to note that we are having the same database error when editing in Pro 3.2.2. 

[CGrant]

Since upgraded to 3.2.2., experiencing same issues everyone else is having as noted in all of the responses to this thread. 

Even not in edit mode, trying to do a simple Select By Attributes, error message shows table does not exist. 

As noted by  stefanieg73  above, tables gray out for no reason;

Using the explore to identify feature sometimes does not work.

ArcGIS Pro often locks up and have to use Task Manager to close it.

This upgrade has severely hampered production. 

[Dakota]

Do we need to create a new post for this issue so that it is noticed? This post is marked "Solved" so I don't know if that filters it out for ESRI folk... I upgraded from 10.9.1 to 11.2 to get my desktop application and geodatabase version more in line in hopes that would fix it but no dice. Hoping with the next path of 3.2 or the release of 3.3 this will be remedied.

[Shawnzeecatz]

I agree, this is most definitely NOT SOLVED, but I am not sure who/how it is marked solved/unsolved.

[PeteJordan]

At the time George_Thompson suggested it was our version of SQL that was causing the issue amd we needed to upgrade and then move to PostGreSQL.  At the time, it was marked as the solution (forgot if it was by me or George_Thompson.

  Since then, there was a work around @MartinWong1 explained involving enabling the enable/disable editing as ArcMap had which solved the issue for many of us until the issue got fixed in later updates.  @joonpark also submitted a bug ticket on this as well from this thread since I hadn't done that at the time.

  After that, it seems a lot more people are not even able to work even with the work around that was proposed, but since it was marked as "solved" I'm not sure I can un-solve it if I was the one that did that.  Either way, @George_Thompson might be able to Unsolve it on ESRI's end to keep this a current issue...

[George_Thompson]

I did not mark as a "Solution". I just removed the solution as to not cause confusion. As mentioned, I think early on, before the defect was identified, that may have worked.

Should be updated now.

[PeteJordan]

Thanks, I couldn't remember if I had done it or not, but I couldn't figure out how to remove it at all if it was me (which I guess it was)...

[RachelSinclair]

I've raised a case with ESRI support, I'll provide updates on this thread.

[TanuHoque]

hello all,

duplicating what I mentioned in my comment from Dec 20th, 2023... 

here is a bug id: BUG-000163841

The issue is not resolved in ArcGIS Pro yet. It is being investigated by the development team with an intention to fix it as soon as we can.