Try setting a breakpoint on the test line before the one that gets the error. Let the test pause there so you can click through the test steps manually and see what's happening. That may give you a clue.
Finally figured the workaround for this.
So i used the FindChild method instead of the mapping (still not sure why the mapping didn't work tho):
Aliases.MainWindow.FindChild(["WndClass","ControlId"],["Edit",1745],6,true).SetText(100);
Thank you for the replies!
It depends somewhat on the criteria you are using for the mapping of the dialog. Additionally, there may be a timing issue where you are attempting to act on a window/component before it's available for action. Either one of those could cause behavior where windows and objects are not being recognized and acted on in a timely fashion.
