Forum Discussion
Hi Jennifer,
It looks like the problem is that your application is not recognized as Open for some reason.
First of all, please make sure that the .NET Open Application Support plug-in is installed and enabled in TestComplete ("File | Install Extension..."). If this suggestion does not help you solve the problem, we need some additional information to investigate the issue. Please answer the following questions:
1. A possible cause of the problem is that some complex actions which take long to be completed are performed in the application's GUI threads when the application is started (the application's main window may become blank or unresponsive in such cases). If so, try increasing the "Method invoke timeout" option described in the "Project Properties - General Open Applications Options" help topic, check whether the problem persists and let us know your results.
2. What version of TestComplete are you using (Help | About...)? If it is earlier than TestComplete 7.52 (the latest version of TestComplete 7), please update the tool and check whether the problem persists in this version.
3. Is your tested application compiled for an x86 platform or for an x64 platform?
4. Exactly how is the application launched? Is it launched as an item of the Tested Applications collection? Is it launched under another account (in the RunAs mode)? Is it launched before or after TestComplete is launched? Please send us a detailed description of the steps you follow to launch the application.
5. Is the application launched from a network folder or from a folder having specific Runtime Security Policy settings? If it is, please make sure that the Runtime Security Policy settings for the folder from which the application is started are set as it is described in the "Working With Network and No-Touch-.NET-Deployment Applications" help topic.
6. Is the application treated as Open according to the Process Filter options? Please see the "Project Properties - Process Filter Options" help topic for details.
7. The problem can be caused by the fact that TestComplete is terminated incorrectly and the tested application is not restarted after that. Is this your case?
8. Does your application's process have child objects named "AppDomain(...)" when the application is not recognized as Open?
Related Content
- 11 months agosanket2799
- 11 months agolalit_singh
- 3 years agoMichal_Ignaczak
Recent Discussions
- 2 days agojstaehlin