Forum Discussion
Unfortunately, the TestExecute version of your log is coming up empty so it's hard to determine what's going on there. The TestComplete version I'm only seeing one line where anything resembling "ClickItem" is being referenced.
However, my best guess, based upon your description of the error message, is possibly one of several things:
1) A timing issue where, on your TestExecute machine, the item you are attempting to click on or even the control "linkManage" is not fully rendered when the test is attempted, hence a "not found" error. Solution - Increase the auto-wait timeout either globally on your project or (better solution) on the individual action in your keyword test
2) An environment issue where, on your TestExecute machine, a different version of the browser or other environmental factors is causing the item in question ("linkManage") to be recognized or rendered differently. Solution - Verify configurations between the two machines and make sure that everything is the same.
3) A mapping issues where, on your TestExecute machine, for some reason, your Alias mapping of your components is not the same as it is on your TestComplete machine, possibly due to an incomplete our outdated copy of the NameMapping file on the remote box. Solution - Pull down the latest project version to the remote box (usually done using some sort of version control system)
BUT... these are just guesses... without the actual log file from your TestExecute machine, can't really precisely give an answer.
I checked your 3 solution already but it didn't seem to be that :
1- Global wait time is already 13000
2- Browser version and other environement parameters seem correct
3- Project in Virtual Machine is exactly the same than my local copy
You can find the "not empty" log in copy.
Best regards,