Not as such, no. I've had similar problems in the past (not quite the same as yours) and what I ended up doing was throwing together some code around the fail point that, when the object recognition failed, I'd write out to the log the entire hierarchy tree. Unfortunately, I'm not sure that's going to fix your problem because you don't need the hierarchy tree but the properties of the object you're looking for... which you can't get to via code because you can't identify the object.
So... what we need to look for, then, is what is different in TE from your TC configuration that is possibly causing this problem... or, if there's something different in the environment.
I know probably a "duh" question, but is your VM the same OS as your machine running TC? That's something that MIGHT make a difference depending upon the application being tested.
Another thing: In your TC configuration, under Tools -> Options -> Engines -> NameMapping there's a check box for "Search for visible objects first". Whatever setting you have there, make sure that setting is the same in your TE installation. This is an option that's configured as part of the tool and does not transfer with the automation project.
Finally, could you post the "offending" code? What function, section of code, etc, is generating the errors? Please post, if you can, the full function and not just the offending line (or screenshot of the Keyword test if it's not code) as it might not be the fault of the identification of the object but events leading up to it. Additionally, if you can post screenshots of the object itself in the object browser of your TC installation with properties included as well as the NameMapping configuration for the object, that will be helpful as well.
