Contributions
Re: The TCHookX86.exe process has not responded for 5000 ms
TanyaYatskovska tristaanogre Support help me get up an running. The issue was the process did not have enough time to start on my machine. I had to increase the wait period. Not sure what the bottleneck is when I try to start TC. My computer is a Dell T7600 with with 2x Xeon Processors and 32 gb of RAM. ...................................... Anyway here are the steps if anyone has the issue. When starting TestComplete, you may get the The TCHookX86.exe process either does not respond or does not existerrors. Usually, theseerrors occuron machines which do not have enough system resources. The error is caused by a delay that occurs during the communication of TestComplete.exe and the hook processes that attach themselves to applications running on your machine. There is an auto-timeout value that can be changed to give the hook processes more time to "get ready" with the TestComplete application. Those values can be found in your registry at these locations: [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SmartBear\TestComplete\14.0] "TCHookX86NormalModeWaitTimeout" - set 10 (0000000a in hex) "TCHookX86SilentModeWaitTimeout" - set 60 (0000003c in hex) (I had to create ....SmartBear\TestComplete\14.0) [HKEY_LOCAL_MACHINE\SOFTWARE\SmartBear\TestComplete\14.0] "TCHookX86NormalModeWaitTimeout" - set 10 (0000000a in hex) "TCHookX86SilentModeWaitTimeout" - set 60 (0000003c in hex) Please note that the values may not exist in the registry on your machine. You may have to add these dword values into the registry key. Note that the values are in the hex numerical format. It makes sense to double the current values as a preliminary step and work upward until you would find a value that works. Note: remember to always back up your registry before modifying it, just in case.2.3KViews1like0CommentsRe: Should Test Execute honor on error properties?
Error: Same for both TC and TE I started with a clean new project and only put 1 test in to simplify things: TC test first: I ran a tested app with the script below: function RunWellExplorer() { Log.Enabled=false Delay(3000) TestedApps.WellExplorer.Run() Delay(30000) Log.Enabled=true } After about 20 seconds my app was open on the left with the error I expected in the log: Closed TC and launched TE, ran the same script. My app tried to start and closed after about 20 seconds. Everything appears the same as TC In the windows event logger, same error only the case is different.1.7KViews0likes1CommentRe: Should Test Execute honor on error properties?
I agree, I think TC and TE should be the same, but I cant see what else it could be. I created a new blank project to simplify everything. First test is TC: I set all the project properties to continue running: TestedApp I launch with script: function RunWellExplorer() { //Log.Enabled=false Delay(3000) TestedApps.WellExplorer.Run() Delay(30000) //Log.Enabled=true } Run TC: After about 20 seconds my app launches alongside TC as seen in image below. It shows the error which is expected since I have logging turned on. Close TC and open TE: My app briefly try to open after 20 seconds it closes. Same Error as TC by no app running. In the event logger of windows, the errors are the same except for the case, but that shouldn't matter.1.7KViews0likes0CommentsRe: Should Test Execute honor on error properties?
I didnt notice that property before now and it was set to stop on error. I have changed it to continue, but it did not help. My application still closes when test execute tries to launch it. It still launches correct through test complete1.8KViews0likes4CommentsShould Test Execute honor on error properties?
Hi all, I have some tests failing with TE that are not failing when I run TC. Scenario: I have an application that is only part of the main overall build. When I launch it standalone, it throws a crash in the background that’s expected because it’s looking for another part of the build that is not there. User doesn’t see the crash. Now when I set up my environment in TC, I said continue running on error, and set up that step to not log the error. The whole suite of tests pass. When I move it to TE to run, it fails immediately when it sees the background crash and I cannot run my test. Is there something I am missing and can I get test execute to ignore the crash?Solved1.8KViews0likes8CommentsRe: The TCHookX86.exe process has not responded for 5000 ms
No solution yet. Our antivirus does not appear to be blocking it. Is there and log or dump file I can look at that may give me another reason? The windows event logger doesnt help and only shows the same message test complete gives.2.3KViews0likes2CommentsRe: The TCHookX86.exe process has not responded for 5000 ms
Not yet, I am waiting on IT to take a look at my machine to see if the antivirus is causing the problem. There are no notification on my machine that anything is being blocked. I am not sure what kinda of antivirus programs IT is monitoring with. Interesting though, I found a temporary workaround by logging out or restarting my computer. When I log back in, I can immediately lauch TC and have no problems. If i wait too long I cant launch it.2.4KViews0likes4CommentsRe: The TCHookX86.exe process has not responded for 5000 ms
Thanks, I will whitelist in Windows Defender. I think IT has a program on our machines called crowdstrike, but we have no access to it. It interesting that none of the other machine are having this issue. Only this one.2.4KViews1like6CommentsThe TCHookX86.exe process has not responded for 5000 ms
Hi all, I have a machine that I am trying to install Test Complete 14.20 on. It will not run in x64 mode. I get the following error: Either the installation files or registry data are corrupted or not accessible. Reason: The TCHookX86.exe process has not responded for 5000 ms. The application will be shut down. TC will run if I launch the x86 mode but not x64 More Info: I have 2 Machines. I installed Test Complete and Test Execute 14.20 with no problems on a new machine Win 10 enterprise 1903. It works fine. I have another machine that had wiped and reinstalled the OS. Win 10 Enterprise 1903. Both machines are setup and on a domain that is managed by IT. It will not run in x64. I installed in the default location. After I got the error the first time, I uninstalled the product. I went and found every folder related to smart bear and deleted them. I have reinstalled this twice. Still the same error. Before I wiped the OS, I had TC 12 on the machine and it ran no problem. Anyone else having this issue? What are my next steps? Any log files besides event viewer that I can look at? Event viewer: The description for Event ID 0 from source TestComplete cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: Either the installation files or registry data are corrupted or not accessible. Reason: The TCHookX86.exe process has not responded for 5000 ms. The application will be shut down. ThanksSolved2.5KViews0likes8Comments