window name

Hi Cyril,

The problem is caused by the fact that the application is not recognized as Open for some reason (this is when the problematic names appear). 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 a 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 RunAs mode)? Is it launched before or after TestComplete is launched? Please send us a detailed description of the steps you perform 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 the tested application in question use a non-standard controls library (WPF, VCL.NET, etc.)?

9. Do you see AppDomain(...) objects in the application's process when the application is not recognized as Open?

Hi,

I check everythting and it seems ok, but what is a non-standard control library (WPF, VCL.NET, etc.)?

Hi Cyril,

A "non-standard control library" means any set of controls different from the standard controls defined in the System.Windows.Forms namespace. Could you please provide us with your answers so we can continue working on the problem?

Hi Krishna,

Microsoft has recently released some .NET Framework updates that were installed automatically on many computers by the Windows Update service. The changes are related to the core .NET Framework functionality used by TestComplete.

After the updates are installed, tests created for .NET 1-3.5 applications may stop working correctly - you may see the "Object Not Found" and related errors in test results.

To resolve the problems, please apply the relevant hot fix:

TestComplete Ent: http://downloads.automatedqa.com/net_patch/NET_TestComplete_Enterprise.zip

TestComplete Std: http://downloads.automatedqa.com/net_patch/NET_TestComplete_Standard.zip

TestExecute: http://downloads.automatedqa.com/net_patch/NET_TestExecute.zip

TestRecorder: http://downloads.automatedqa.com/net_patch/NET_TestRecorder.zip

Here are the hot fix installation steps:

1. Unpack the downloaded archive to your hard disk drive.

   The archive contains two folders: 'x86' and 'x64'.

2. Close the product you are applying the fix to.

3. Copy the 'x86\tcClrHook.dll" file to the Extensions folder of the product.

   For TestComplete and TestExecute, the folder path looks like this:

     <Product Installation Folder>\Bin\Extensions\

   For TestRecorder, the path is as follows:

     <Product Installation Folder>\Bin\

4. If you are running an x64 operating system, you will also need to copy the 'x64\tcClrHook.dll' file to the following folder:

   TestComplete, TestExecute:

     <Product Installation Folder>\x64\Bin\Extensions\

   TestRecorder:

     <Product Installation Folder>\x64\Bin\

The fix can be applied only to version 7.52 of TestComplete, TestExecute or TestRecorder.