Since I started running TruClient on a VM with only Avast, I no longer see this issue.
There is definitely a vulnerability to interprocess communication interrpuption. TruClient needs constant connectity to that browser instance, or things get nutty. I think some corprorate security settings are too tight for TruClient to run effectively.
>> "Since I started running TruClient on a VM with only Avast, I no longer see this issue. There is definitely a vulnerability to interprocess communication interrpuption."
Veyr interesting, thanks, James. I suppose you could consider the behavior involved there a bit "malware-like," I guess I'm not shocked it can raise flags.
I get error "TCS has stopped working" most of the times when I open a script in VuGen and click on button "Develop Script". Problem was solved by adding "mrdv.exe" and "TcWebIELauncher.exe" to the ScriptScan whitelist of McAfee.
McAfee scan log was empty (.exe are clean), but the ScriptScan log of McAfee had an entry. This is why the exectuables were not whitelisted at the top level, but only at the ScriptScan level.
Info: TruClient for IE 11, LoadRunner 12.02, Windows 7
I had the TCS stopped working issue starting last week after a security update for MIcrosoft Windows was installed. HP support advised that I remove the security update KB3038314 and reboot. This resolved the issue.
I looked at the updates that our operators pushed to my system and sure enough KB3038314 was there.
Removed it, and I now have TC working again.
I now have a post-it on my monitor with the words "KB3038314 - TC Killer" so I know what to look for next time they push updates.
THANK YOU NeilChikode
Add the KB3049563 to the black list, is killing the IE TruClient scripts like the KB3038314.
Can you please share some documentation on these recommendations?
My desktop team needs some kind of documentation from HP or proof to disable AV or whitelist mdrv.exe and TcWebIELaucher.exe as disabling AV is against the policy.