Has anyone seen this error, and if so what does it mean?
Thanks in advance
Chad
Hello
We fix a problem like this for 3.3. The problem was caused by bringing in data from DGN (CAD) files. Maybe it's not your case.
What's your ArcPro version?
Can you please post a screenshot of the data ?