Page 1 of 1

About ApplicationNotRespondingException

Posted: Tue Oct 10, 2017 7:27 am
by ranonub
The newly added ApplicationNotRespondingException in version 7.2 seems to be raised very quickly when the application becomes unresponsive (form has duration:0). This is causing most of my test cases the fail as the application might become unresponsive at times (sometimes up to 50-60 seconds) but this doesn't mean that it is crashed.
  • Is there a way to delay the firing of this exception without delaying the execution times of the actions?
    I haven't had the time to try it, but would the duration property in the application form fix this?
    If not is there a way to silence or disable this exception so that ranorex doesn't raise an error, resulting in cancellation of the test case.

Re: About ApplicationNotRespondingException

Posted: Wed Oct 11, 2017 12:55 pm
by Support Team
Hello ranonub,

Thank you for your post.
In order to increase this timeout, please follow these steps:

1. Close Ranorex Studio and navigate to your "AppData\Roaming" folder by entering %appdata% into the navigation bar of your file explorer
appdata.png
2.Open the "Ranorex.Config7.xml" - file

3. Increase the adapter.functionexecutiontimeout in the following line
functionexecutiontimeout.png
I hope this information is helpful.
regards,
Stephan

Re: About ApplicationNotRespondingException

Posted: Wed Oct 11, 2017 1:52 pm
by krstcs
This should probably be a setting in Ranorex's normal settings dialog. Any value which effects tests and timeouts should really be adjustable from the UI.

Re: About ApplicationNotRespondingException

Posted: Thu Oct 12, 2017 8:42 am
by MGBChrome
Hello @Support Team
3. Increase the adapter.functionexecutiontimeout in the following line
Thank you very much for this perfect description of the solution.
I wasn't able to try this "trick" out yet. But I'm definitely sure that it will work.

I'm so happy, that you could help me, because, since I updated to Ranorex 7.2, I have had a lot of problems with exact this exception.

Big up @Support Team!

regards,
Roman

Re: About ApplicationNotRespondingException

Posted: Thu Oct 12, 2017 1:04 pm
by Support Team
Hello everyone,

@MGBChrome:
This timeout was implemented in Ranorex 7.2 in order to report unresponsive applications.
I hope increasing the duration will help.

@krstcs:
Thank you for your input.
If you want, you can leave a feature request in our UserVoice platform. This platform is designed to bridge the gap between our users’ needs and our development focus.

regards,
Stephan

Re: About ApplicationNotRespondingException

Posted: Tue Nov 14, 2017 5:41 am
by ranonub
Thanks Support that resolves to issue, however while running Ranorex as administrator I have realised that the exception comes up quickly again. When I ran the application again in with standard privileges the settings in RanorexConfig7.xml file seem to apply as usual.

It seems like running Ranorex as administrator is overwriting the settings maybe?

Re: About ApplicationNotRespondingException

Posted: Wed Nov 15, 2017 2:51 pm
by Support Team
Hello ranonub,

Usually, starting as administrator should not make a difference here.
However, you could also try to increase this timeout within the Ranorex.rxsettings file of your solution and see if this will help in your case.
Therefore, simply copy the following section from the Ranorex.Config7 file into your Ranorex.rxsettings file.
functionexecutiontimeout.png
I hope, this helps.

regards,
Stephan

Re: About ApplicationNotRespondingException

Posted: Tue Jan 16, 2018 11:35 pm
by SnapJeff
Hi Stephan,

I too was experiencing the ApplicationNotRespondingException. I added the functionexecutiontimeout to the solution settings file, which solved the problem.

BUUUT....now, every time I load the solution, that setting is removed from the Ranorex.rxsettings file. I did not find anything in the settings dialog that allows the functionexecutiontimeout to be changed - only by manually adding the XML to the settings file.

Is there a way to make this a 'permanent' setting?

I am using Ranorex 7.2

Thanks,
Jeff

Re: About ApplicationNotRespondingException

Posted: Wed Jan 17, 2018 2:36 pm
by Support Team
Hi SnapJeff,

Thank you for your post.

In this case, please try to change this setting globally.
Therefore, please open the RanorexConfig7.xml file (In case of Ranorex 8: RanorexConfig8.xml) in your "appdata/Roaming" directory.
In order to open this directory, simply run %appdata% from the run window.
run_appdata.png
Afterwards, please open the RanorexConfig7.xml (In case of Ranorex 8 it is called RanorexConfig8.xml) file and increase the "adapter.functionexecutiontimeout"
functionexecutiontimeout.png
regards,
Stephan

Re: About ApplicationNotRespondingException

Posted: Wed Jan 17, 2018 3:55 pm
by SnapJeff
Stephan,

I did see that method in an earlier post in this thread and it works. However, I was looking for a more 'turnkey' solution. By adding the timeout to the solution settings file it seemed to propagate to the settings file of every project in the solution. That is beneficial because the timeout setting is contained within each executable and the modified Ranorex.Config7.xml does not have to be copied to the DUT at the %APPDATA% folder.

Having a setting in the solution settings file that is not persisted does not help much.

Regards,
Jeff

Re: About ApplicationNotRespondingException

Posted: Thu Jan 18, 2018 1:06 pm
by Support Team
Hello SnapJeff,

Thank you for your reply.
May I ask you to create a support query so we can further discuss this issue and schedule a remote session?
Thank you in advance.

regards,
Stephan

Re: About ApplicationNotRespondingException

Posted: Fri Feb 23, 2018 9:11 am
by swmatisa
Dear Support,

I have only a little part of my application under test that generate an "ApplicationNotRespondingException". Is there a way to set "adapter.functionexecutiontimeout" with user code to change the value in my differents tests.

Best Regards

Re: About ApplicationNotRespondingException

Posted: Fri Feb 23, 2018 11:34 am
by csr
This is not an acceptable solution!
This means that everyone on the team working with Ranorex has to change a file on his machine (every time we want to change this value!) and you have to change it on the build server(s) as well!
Why not put it in the regular Ranorex settings that can be changed within the Ranorex solution? This way, the changes would get propagated by the version control system.

Re: About ApplicationNotRespondingException

Posted: Mon Feb 26, 2018 1:16 pm
by Support Team
Hello csr,

Thank you for your post.
I'm sorry, that this approach is no optimal solution for you.
Therefore, may I ask you to add your idea as a feature request to our UserVoice platform ?
This platform is designed to bridge the gap between our users’ needs and our development focus.
Thank you in advance.

regards,
Stephan

Re: About ApplicationNotRespondingException

Posted: Tue Feb 27, 2018 8:16 am
by swmatisa
Hello,

I create the entry in UserVoice. Please vote for it:
https://uservoice.ranorex.com/forums/15 ... pplication