ORD Plan View Labeler Randomly Terminating Far (North) From Snapped Coordinates - HELP!

I am currently using the latest version of ORD CONNECT Edition - 2019 Release 2 Update 7 - Version 10.07.03.18 and have started having problems with the Plan View Labeler and Place Named Boundaries tools in my files.  It seems that anything that involves placement of elements using ORD 'decision making' is resulting in a significant shift in coordinates.  I have no idea where this error may have originated, but hoping it's an easy/quick fix (and likely something stupid).

The only other string I can find that it similar to my issue is from 2017 (never did continue the discussion so unresolved) is located here:

https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/138484/place-label-settings-with-leader-not-working

The basic rundown of how it first started showing itself is as follows:

Using Plan Labeler to label Station and Sta/Offset values in the plan view of my design files.  When placed without a leader line, the resultant values are correct for my coordinate system and design file elements.  So the Northing/Easting values are correct for my design plane and have been vetted outside of the ORD with data points converted and plotted in Google Earth, showing exactly where they are supposed to be.  Similarly, the station and offset values are correct for the location in the design model.

The PROBLEM comes in when I try to place with a leader line.  While manipulating the tool, appears to show a leader line attached at the snap point, but when it is accepted, ORD places the STA or STA/OFF data where I snapped, but then creates a leader line that shoots off far to the north.  Specifically, the leader snaps to a point 253,0XX feet away at an angle of 225 degrees.

I have posted a video to YouTube showing the error and the shift that ORD is creating at the point of acceptance when placing a leader.  Also shows that the data at the point of placement is accurate in both leader and leaderless methods, but the snap for the leader line shoots off the screen.

Video can be seen here:

https://youtu.be/G1vnvCUsmaQ

This is happening in all files now, without exception, so it is not project specific.  The shift for the leader line is always 253,000 feet away from the snap point at an angle of 225 degrees (plus or minus fractions).

I am also getting a similar issue with placement of Named Boundaries for cutting profiles and cross sections and Profile Labeling (actually an opposite problem). 

Named Boundaries for cutting cross sections are created way off in 3D space, about the same distance away from the actual model.

For the profile labeling, the shift is not the same distance as noted above, but the profile label data is incorrect and does not reflect the correct station or elevation for the snapped point.  In contrast to the plan labeling error, the leader line doesn't shift, but something has shifted in how ORD is reading the model.  Profile line work looks correct relative to the profile grid datum and associated datum callouts, but the profile grades and VPIs created by the profile sheet creation tool are shifted in space away from the profile linework and any labeling snapped in using the profile labeler are returning incorrect values relative to where they are snapped in the profile sheet view.

In case it was something that was somehow corrupt in the ORD dataset, I have already performed a complete reboot of my installation, removing all settings, etc. before reinstalling the program.  That didn't work.

Any suggestions?