Ranorex Unable to Identify WinForms Application

Technology specific object identification, supported applications, web technologies, and 3rd party controls.
zouyong0229
Posts: 7
Joined: Sat Jan 05, 2013 8:33 am

Ranorex Unable to Identify WinForms Application

Post by zouyong0229 » Sat Jan 05, 2013 9:43 am

Hi guys,

I use Ranorex 4.0.1 and my AUT run on Windows Server 2008 R2 Enterprise SP1, for detail please
reference the attachment.

I'm an Automation case developer, I met a problem when use Ranorex to identify the controls
on customer's soft, the soft seems to developed by WinForms, Once I use Ranorex Spy to trace
control , it always popup a tip says: "The automation does not process not have required security
permission to access the process 'mmc'. ......", For detail please see the screenshot in attachment.

For this issue, I review your user guide, but not very clear your comment as below, because I
started the AUT and Ranorex Spy under the same User. It's due to the difference between
Windows XP and Windows Server 2008, do you know that?

"The automating process (Ranorex executable) and the automated application (AUT)
are not started with the same security rights, i.e. not as the same Windows user."

Another strange thing is when using Ranorex Spy to trace a tree control's, I can click on tree's
child node. I save the screenshot with name: Success.jpg and Success.rxsnp.

But fail to click on another tree control's child node, only can click on the root node of the tree,
I save the screenshot with name: Fail.jpg and Fail.rxsnp.

So My concern questiones are:
1) why the tip always popup when trace using Spy, the AUT has problem or some wrong setting
with Ranorex. How Can i to fix it?

2) The unstable identify control problem is due to the first issue or has another reason.

Thanks
Attachments
ScreenshotAndLog.zip
screenshot and log
(1.25 MiB) Downloaded 215 times

zouyong0229
Posts: 7
Joined: Sat Jan 05, 2013 8:33 am

Re: Ranorex Unable to Identify WinForms Application

Post by zouyong0229 » Sat Jan 05, 2013 11:36 am

Hi,

The problem fixed, caused by using a domain User to run the AUT and Ranorax Spy, Change to
'Administrator' login, the problem gone. Seems Windows's process 'mmc' need more security permission
that domain user owned.

FYI, because the soft is a Microsoft Management Console application, so it seems rely on 'mmc' process.