Do you have any modals/dialogs in the actions prior to the error? Is the test running in Internet Explorer? I've seen that in IE sometimes there are memory issues where TC thinks a modal is still open even if it's clearly not.
We do have modals that we handle within some of our tests but none of our tests prior in our projects deal with modals anywhere before the error occurs.
And yes, we are running all of our projects within Internet Explorer.
I have had some success getting around the error by wrapping the drop down click in an If statement with a WaitAliasChild and then a 1 second delay prior to clicking the dropdown, which makes me think TestExecute is trying to click the item in the dropdown too quickly and is setting it's own coordinates for the item it has to click incorrectly. This is a terrible solution for us though because we have a couple thousand tests with tens of thousands of lines of code and I can't seem to pinpoint the problem to one area.
For me, it came down to IE. When we run the test in Firefox, the problem doesn't occur. So for the project where the issue pops up, we have to run the test in FF instead of IE. We know it's not an issue with the site because it doesn't happen when interacting with it naturally, so it's an acceptable workaround for us.
