Test Execute 11 error message

[lowens]

Hello

  since upgrading to Test COmplete 11 and Test Execute 11 we sometimes get a message box when we try to start Test Execute.  the error dialog is:

Either the installation files or registry data are corrupted or not accessible. Reason: The TCHookX64.exe process either does not respond or does not exist.
The application will be shut down.

does anyone know what could be causing this?

[anhvu]

1- Go to the folder ...SmartBear\TestComplete 11\x64\Bin

2- Check the TCHookX64.exe is located in there or not.

if not, re-installed your testcomplete.

if it is there, try to run it. then launch your test complete.

Usually, when we launch the testcomplete tool, it will start automatically.

[TanyaYatskovska]

Hi Guys,

Our R&T Team has fixed this issue. Starting from TestExecute 11.20, you shouldn’t face it anymore. So, please update to the latest product version.

[Nethra30]

Hi Madam,

                 we are using Test Complete 11.2 in our system and we still facing this TCHookX64.exe issue in one of our MCAfee installed 64bit system. We observe this issue after upgrading system from Test Complete 10.3 to 11.2. With Test Complete 10.3 this issue was not observed and its observed only in 11.2 and its not produce often. Every time we are reinstalling 11.2 so first 2 or 3 times this issue wont come but later same problem.

Please find the attach screenshot for the same. can you specify any workaround method to avoid this error in future ? 

[TanyaYatskovska]

Hi Nethra30,

I would suggest that you contact our TestComplete Customer Care Team to troubleshoot this issue. You can get in touch with them here: http://support.smartbear.com/product-list/

[bknutson]

Iowens, or Nethra,

Did either of you get your issues with TCHookx64.exe figured out?

We see this message as well with TestExecute, currently on Version 11.30.2298.7.

This seems to be vary random though so I haven't been able to see a common reason as of yet.

I was just curious as to what you may have found out.

Thanks

[Nethra30]

Hi,

I found this reply from support team, have implemented same and till now not faced issue.

There is timeout associated with TestComplete (or TestExecute) attempting to communicate with its TCHookX64 helper process. The timeout was made configurable in a patch to version 11.10 and as part of the base product in version 11.20. There are two timeouts . . . one for when TestComplete (or TestExecute) is started normally and another for when it is started in Silent Mode. For more information on Silent Mode, see https://support.smartbear.com/viewarticle/69415/ "TestComplete Command Line" The normal and silent mode default timeouts are 5 and 30 seconds respectively. The following examples show how to double those times for TestComplete and TestExecute. (In the examples, the angle brackets are not part of the .REG files.)

 still you face same problem : 

Try increasing the NormalModeTimeout.

After increasing Timeout we are not facing this issue till now and will update if we find it in future.

Regards,

Nethra 

[Nethra30]

the angle brackets are not part of the .REG files

For TestComplete, create a .REG file with the following content and run it on the problematic PC:

>> 

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SmartBear\TestComplete\11.0]

"TCHookX64NormalModeWaitTimeout"=dword:0000000a

"TCHookX64SilentModeWaitTimeout"=dword:0000003c

[HKEY_LOCAL_MACHINE\SOFTWARE\SmartBear\TestComplete\11.0]

"TCHookX64NormalModeWaitTimeout"=dword:0000000a

"TCHookX64SilentModeWaitTimeout"=dword:0000003c

<< 

For TestExecute, create a .REG file with the following content and run it on the problematic PC:

>> 

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SmartBear\TestExecute\11.0]

"TCHookX64NormalModeWaitTimeout"=dword:0000000a

"TCHookX64SilentModeWaitTimeout"=dword:0000003c

[HKEY_LOCAL_MACHINE\SOFTWARE\SmartBear\TestExecute\11.0]

"TCHookX64NormalModeWaitTimeout"=dword:0000000a

"TCHookX64SilentModeWaitTimeout"=dword:0000003c

<< 

[bknutson]

Nethra30, thanks for the reply.  I will run the .reg commands and see how it goes.

Before I do though, I would like to clarify something since I have multiple computers to apply this to.

In your first post, it reads "The timeout was made configurable in a patch to version 11.10 and as part of the base product in version 11.20". 

I am not sure if you can answer these or not but:

Are you saying that in the current versions, this registry entry should be there by default?  I am on 11.30.x and I do not see that registry entry.

Also, if it was added to the base product, is there now a setting within the project or program properties that I can set the values to so they will go down to all my machines when I deploy changes?

As I said, I have multiple machines that I would have to run the .reg files on, not a big deal but, if there was now a built in way to set these values then I would use that.   If not, I will set these registry settings and give it a try.

Thanks for you help.

[joseph_michaud]

You don't see the registry entries unless you create them.  With no entries present, the defaults apply.

No, there is no project-level setting for this.  It is a per-machine setting.