Hi all, I am working with TestComplete9 with the license server in a virtualized computer and from time to time, TestCompleteService9.exe process gets 99% of CPU and it blocks this computer. It is needed to kill this process manually.Could anybody help me to solve this issue?Thank you very much.Regards, Raul

Hi Geeth,You need to apply the patch Alex mentioned. Have you done this?

Hi Raul,To help us collect information about the problem, please follow the steps below:1. Download the Debugging Tools for Windows package from hereand install it.2. When the problem occurs, open the "Start | Run..." dialog and execute the following command:"C:\Program Files\Debugging Tools for Windows (x86)\windbg.exe" -pn TestCompleteService9.exe -Q -pd -c ".dump /m C:\Dump1.dmp;q"This command will make WinDbg write a memory dump of the TestCompleteService9.exe process to the "C:\Dump1.dmp" dump file. After the dump is written, WinDbg will be closed.3. Correct the dump file name in the above command line (for example, change it to Dump2.dmp), wait for two minutes and execute the command again.4. Repeat step 3.5. Send us all of the generated dump files.Also, please clarify whether your project contains the Network Suite node.Thanks in advance.

Hi Lexi,thanks for your detailed answer.When I got this error, I have tried to obtain the information with the debugger utility but I did not have enough permissions in the company domain. I have called IT and neither do them.Then, we should raise this to global IT service (in Switzerland) and this is not realistic because of politicals reasons.--> Do you have a workaround to get this information?I have created a local account in the computer, with the computer out of the domain and this error did not reproduce.Looking in suppport, I have found this could be because of windows firewall or the working on a network distributed environment script.This has not worked.It is very strange but normally we found this error in the afternoon. --> Could it happen because an internal TestComplete service procedure? Or could it be because the domain processes perform some kind of checking or ...?--> Is this service needed once you have openede Testcomplete and load yiour project?Looking forward to hearing from you.Best regards,Raul

Hi Raul,You can try collecting additional information in the following way:1. When TestComplete 9 Service gets the most of CPU, wait for about five minutes and run WinDbg ("C:\Program Files\Debugging Tools for Windows\windbg.exe"). 2. Attach WinDbg to TestComplete 9 Service's process (File | Attach to a Process | TestCompleteService9.exe). In the Attach to Process dialog, check the Noninvasive check box.3. Type the following command in the Command window:.dump /m "C:\TCServiceDump.dmp"and press Enter.4. Wait for one minute and repeat step 3 to save another dump file with a different name.5. Repeat step 4 two more times. 6. Send us all of the dump files created in the above steps.Could it happen because an internal TestComplete service procedure? Or could it be because the domain processes perform some kind of checking or ...?Unfortunately, without getting memory dumps from you, we cannot predict what is the reason for the problem.Is this service needed once you have openede Testcomplete and load yiour project?No, the TestComplete 9 service is not required for running TC and loading a project.

We regularly have the same problem running TC9 directly on desktop client PCWe get the same problem on all three of our test machines

TestCompleteService9 gets 99% of CPU

rrubio
Contributor
13 years ago

Hi Alex,

thanks for your help. I have obtained some of the information but there is an error (I guess at the beginning).

I put here all the console information to ease you to identify what has happened.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86

Copyright (c) Microsoft Corporation. All rights reserved.

*** wait with pending attach

Symbol search path is: *** Invalid ***

****************************************************************************

* Symbol loading may be unreliable without a symbol search path.           *

* Use .symfix to have the debugger choose a symbol path.                   *

* After setting your symbol path, use .reload to refresh symbol locations. *

****************************************************************************

Executable search path is:

ModLoad: 00400000 00457000   C:\Program Files\SmartBear\TestComplete 9\Bin\TestCompleteService9.exe

ModLoad: 77150000 7728c000   C:\Windows\SYSTEM32\ntdll.dll

ModLoad: 77290000 77364000   C:\Windows\system32\kernel32.dll

ModLoad: 75560000 755aa000   C:\Windows\system32\KERNELBASE.dll

ModLoad: 77370000 77375000   C:\Windows\system32\PSAPI.DLL

ModLoad: 739e0000 739ed000   C:\Windows\system32\WTSAPI32.dll

ModLoad: 76f00000 76fac000   C:\Windows\system32\msvcrt.dll

ModLoad: 74920000 74937000   C:\Windows\system32\USERENV.dll

ModLoad: 76e50000 76ef1000   C:\Windows\system32\RPCRT4.dll

ModLoad: 752e0000 752eb000   C:\Windows\system32\profapi.dll

ModLoad: 75db0000 75e79000   C:\Windows\system32\USER32.dll

ModLoad: 76dd0000 76e1e000   C:\Windows\system32\GDI32.dll

ModLoad: 75740000 7574a000   C:\Windows\system32\LPK.dll

ModLoad: 77010000 770ad000   C:\Windows\system32\USP10.dll

ModLoad: 770b0000 77150000   C:\Windows\system32\ADVAPI32.dll

ModLoad: 75f10000 75f29000   C:\Windows\SYSTEM32\sechost.dll

ModLoad: 75fe0000 76c29000   C:\Windows\system32\SHELL32.dll

ModLoad: 76fb0000 77007000   C:\Windows\system32\SHLWAPI.dll

ModLoad: 755e0000 7573c000   C:\Windows\system32\ole32.dll

ModLoad: 75e80000 75f0f000   C:\Windows\system32\OLEAUT32.dll

ModLoad: 747d0000 747d9000   C:\Windows\system32\VERSION.dll

ModLoad: 734a0000 734b1000   C:\Windows\system32\NETAPI32.dll

ModLoad: 74c70000 74c79000   C:\Windows\system32\netutils.dll

ModLoad: 75020000 75039000   C:\Windows\system32\srvcli.dll

ModLoad: 73490000 7349f000   C:\Windows\system32\wkscli.dll

ModLoad: 76e30000 76e4f000   C:\Windows\system32\IMM32.DLL

ModLoad: 75a60000 75b2c000   C:\Windows\system32\MSCTF.dll

ModLoad: 10000000 10017000   C:\Windows\system32\AMINIT32.dll

ModLoad: 75230000 7523c000   C:\Windows\system32\CRYPTBASE.dll

ModLoad: 752a0000 752c9000   C:\Windows\system32\winsta.dll

ModLoad: 71380000 71395000   C:\Windows\system32\utildll.dll

ModLoad: 76c30000 76dcd000   C:\Windows\system32\SETUPAPI.dll

ModLoad: 755b0000 755d7000   C:\Windows\system32\CFGMGR32.dll

ModLoad: 75540000 75552000   C:\Windows\system32\DEVOBJ.dll

ModLoad: 74ba0000 74bc2000   C:\Windows\system32\LOGONCLI.DLL

ModLoad: 71ae0000 71aed000   C:\Windows\system32\BROWCLI.DLL

ModLoad: 72ff0000 72fff000   C:\Windows\system32\SAMCLI.DLL

ModLoad: 30300000 303f6000   C:\Program Files\SmartBear\TestComplete 9\Bin\aqReporter.dll

ModLoad: 71f80000 71fd1000   C:\Windows\system32\WINSPOOL.DRV

ModLoad: 75750000 75785000   C:\Windows\system32\WS2_32.dll

ModLoad: 75be0000 75be6000   C:\Windows\system32\NSI.dll

ModLoad: 74000000 7419e000   C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16661_none_420fe3fa2b8113bd\Comctl32.dll

ModLoad: 03000000 03113000   C:\Program Files\SmartBear\TestComplete 9\Bin\dbghelp.dll

ModLoad: 759d0000 75a53000   C:\Windows\system32\CLBCatQ.DLL

ModLoad: 74d60000 74d76000   C:\Windows\system32\CRYPTSP.dll

ModLoad: 74af0000 74b2b000   C:\Windows\system32\rsaenh.dll

ModLoad: 752d0000 752de000   C:\Windows\system32\RpcRtRemote.dll

ModLoad: 00f50000 00f68000   C:\Program Files\SmartBear\TestComplete 9\Bin\aqMarshaller.dll

ModLoad: 01870000 0193d000   C:\Program Files\SmartBear\TestComplete 9\Bin\tcRTL.bpl

ModLoad: 71c20000 71c32000   C:\Windows\system32\mpr.dll

ModLoad: 01940000 01d04000   C:\Program Files\SmartBear\TestComplete 9\Bin\tcComponents.bpl

ModLoad: 71c40000 71cc4000   C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7600.16661_none_ebfb56996c72aefc\comctl32.dll

ModLoad: 75b60000 75bdb000   C:\Windows\system32\comdlg32.dll

ModLoad: 73a30000 73a62000   C:\Windows\system32\winmm.dll

ModLoad: 71400000 7141c000   C:\Windows\system32\oledlg.dll

ModLoad: 75240000 7529f000   C:\Windows\system32\SXS.DLL

ModLoad: 30200000 30231000   C:\Program Files\SmartBear\TestComplete 9\Bin\aqComm.dll

ModLoad: 74d20000 74d5c000   C:\Windows\system32\mswsock.dll

ModLoad: 74860000 74865000   C:\Windows\System32\wshtcpip.dll

(1ba8.1a7c): Break instruction exception - code 80000003 (first chance)

eax=7ffde000 ebx=00000000 ecx=00000000 edx=771ed5cb esi=00000000 edi=00000000

eip=77183258 esp=0146ff5c ebp=0146ff88 iopl=0         nv up ei pl zr na pe nc

cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000             efl=00000246

*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Windows\SYSTEM32\ntdll.dll -

ntdll!DbgBreakPoint:

77183258 cc              int     3

I am sorry for asking you so much.

Regards,

Raul
AlexanderM
Staff
13 years ago

Hi Raul,

No problem.

This is not actually an error - you can proceed with the steps:

1. Generate a dump file by executing the following command in the Command window:

.dump /m "C:\TCServiceDump.dmp"

2. Then resume the process by clicking "Debug | Go" in the main menu;

3. Wait a bit, and pause the process using "Debug | Break", and generate another dump report:

.dump /m "C:\TCServiceDump1.dmp"

4. Repeat steps 2-3 several more times (with different files names) to get more dump files.

Send us all of the dump files.
bapsniche
13 years ago
Hi,

I am having the same issue. I have attached the dump file.

Thanks
Dump11.zip9 KB
AlexanderM
Staff
13 years ago

Hello Princess,

We need several dump files captured one after another, with continuing the execution after every capture - please see the steps below.

Please submit all your files to Support - we are not investigating deeply technical issues in a Forum, this is not convenient.

Please note that the dump files need to be captured when the problem is happening, not before or after this moment.

In your submission, make sure to give a link to this thread - it will help us understand the context quicker. Thanks!
rrubio
Contributor
13 years ago
Hi Alex,

please find attached my dumpfiles as you requested in previous mails.

Thank you very much.

Regards,

Raul
Dump_files.zip45 KB
AlexanderM
Staff
13 years ago

Hello Raul,

Thanks for the files!

What we see is that some software in your network is establishing TC connections with the service on ports 60000 and 60001, and send it a lot of data causing the service consume CPU to process the data. So, we need your help to find out what software is causing this:

1. If you know what software may be using ports TCP 60000 and TCP 60001, please let us know.

2. Are you using the Network Suite functionality of TestComplete before the problem starts?

3. Collect information about the network activity on the computer where the service is running.

To do this:

- run Command Prompt (in Win7, WinVista, or Win Server 2008, please run it with elevated rights by right-clicking cmd.exe, and clicking Run As Administrator);

- enter this command and press Enter:

netstat -a -b > C:\connections.txt

- send us the file.

4. In your network, do you have any software related to the X-Server technology?

Thanks in advance for the info!
RichK
New Contributor
13 years ago
Hi,

Were getting the same issue here on 3 machines, 2 are running Test Complete9 and one is running Test Execute9 I have attached my dump files these have come from the machine running Test Execute. Test Execute was not open at the time of this, the machine just locks up and on looking in the process manager you can see that the service is using around 75% of the cpu.
Dump+files.zip23 KB
AlexanderM
Staff
13 years ago

Hello Richard,

Thanks for the files. It looks like all those situations have the same root cause - some software is sending a whole bunch of TCP packets on port 60000, which is used by the service for the Network Suite communication. The service is getting swamped with those packets trying to handle all of them.

Everyone:

We have a patch to try - it changes the port number to avoid the problem. Please contact Support to get the patch, and try it in your environment. Based on the results, we will plan the further steps.

Thanks!
geethwind
Contributor
13 years ago
Does anybody got this issue resolved? I observed Port 6000,6001 and 6002 all are being used by TestcompleteService9.exe and Testcomplete.exe.
VRamisetty
11 years ago
Hi Irene and Geeth

Can you please email me real quick that same patch which you are refering to Geeth to vramisetty AT rapiscan DOT com

Thank you,

Venkata Vivek