this_is_ridiculous wrote:Now about the report file. To be honest i don't know what is that
Ranorex uses a report file to print out warnings, errors, and informative messages if you configure it to do so. See the corresponding chapter in the Ranorex User Guide:
http://www.ranorex.com/support/user-gui ... gging.htmlthis_is_ridiculous wrote:May be it's because of window nature? It's a custom window with overriden style. it uses side caption and can change it's opacity.
That should not be a problem. If Ranorex can find an element with Ranorex Spy/Studio, then you can do that by runtime as well. There must be a problem in the setup of your Ranorex test code. From the error you posted I see that you use threads to execute Ranorex code. Please, make sure that all threads use an STA apartment state (
see MSDN documentation).
Another thing I noticed from the path you posted: Is this application implemented using .NET 1.1 controls? If not, then Ranorex has problems identifying Windows Forms 2.0 controls inside your application. This can be a security issue: Please, make sure that neither the Ranorex executable, nor the automated application reside on a network drive or in an encrypted folder and that both applications are started with the same user rights (same user accounts)!
Another possible cause are 32/64 bit issues, but these should be taken care of automatically if you use an installed version of Ranorex 2.3. Are you working on a 64 bit operating system? Do you get any technology limitation warning popups?
Regards,
Alex
Ranorex Team