A while ago there was a problem with Toad and McAfee (with 10.5.1 if I’m not mistaken). This morning at our office, ‘all’ Toad-versions (confirmed with 10.1, 10.6 and 11.0beta) have problems starting up and McShield eating up the whole CPU. Yes, we can put it in the exclude-list, but this one is automatically overwritten a few minutes later. Here internally I have to raise this to a higher level.
Kind regards / Met vriendelijke groet / Mit freundlichen Grüßen / Con respeto bueno / avec de sincères amitiés / Pozdrawiam / hardik Shubhkamnaye / с дружеским приветом / 드림,
Ah, that explains it. I’m seeing the same thing this morning too. Will have to notify our systems support people. Anyone know why this is suddenly a problem?
McAfee is supposed to be placing a support article on their site on why this
happens and what to do. The problem is on their end. It’s very possible that
daily virus definition updates will cause the problem to recur without their
workaround (whatever that is). John Pocknell the product manager should ring in
on the progress for this issue ….
For corporate users this might be a solution but only temporarily as the
exclusion-list is maintained centrally. So after approx. 30 minutes when firing
up Toad again you will have to add it to the exclusion list again. For me and my
colleagues the trick of rolling back the datfile worked.
Kind regards / Met vriendelijke groet / Mit freundlichen Grüßen / Con respeto
bueno / avec de sincères amitiés / Pozdrawiam / hardik Shubhkamnaye / с
дружеским приветом / 드림,
Unfortunately, that didn’t work for me this morning, Jeff. I was in the middle
of using a Toad session that had been up for several days when my PC started
exhibiting this behavior. I had to fight with it–the task bar froze,
etc.–using Task Manager, slowly shutting things down to clear it up.
Pete J.
Jeff Smith wrote:
Or do what I do – don’t shutdown Toad.
When it’s time to shutdown my machine, I just hibernate/sleep the PC. It
will minimize the pain until McAfee get’s it act together.
McAfee has a work-around to the original issue experienced with Toad 10.5.1, but
I’m not sure if this fix would apply to this new issue. I think the best thing
to do at this point would be to contact McAfee. -Brad
I have asked McAfee to provide recommendations on the appropriate corrective
action.
As Brad says, they already provided Quest with a special Dat file for users on
10.5.1 experiencing startup performance issues which we will shortly be
providing via our Support portal together with a McAfee published Knowledge Base
article. (similar to the one on the McAfee website Christian referred to)
At this stage, it’s important we report this to McAfee, so if anyone else has
experienced these issues on Toad versions higher than 10.5.1, please let us know
and which McAfee product and version you are using.
I apologise for the inconvenience some of you may be experiencing.
Hi John–according to our admin, we are using McAfee 8.7i with Patch 3. She has
contacted McAfee and is waiting for that .dat file. Hope that fixes it; my whole
day has been basically shot.
Pete J.
John Pocknell wrote:
I have asked McAfee to provide recommendations on the appropriate corrective
action.
As Brad says, they already provided Quest with a special Dat file for users
on 10.5.1 experiencing startup performance issues which we will shortly be
providing via our Support portal together with a McAfee published Knowledge
Base article. (similar to the one on the McAfee website Christian referred
to)
At this stage, it’s important we report this to McAfee, so if anyone else
has experienced these issues on Toad versions higher than 10.5.1, please let
us know and which McAfee product and version you are using.
I apologise for the inconvenience some of you may be experiencing.
Thanks,
John
Strange, normally I’m one of the persons who finds problems with the
performance. But on the other hand, I’m mostly use the latest Toad beta and
I’m now running on Windows 7 64 bits, Virusscan Enterprice 8.7i (8.7.0.570)
with 4.5.0.1270. So maybe this combination doesn’t lead to problems.
Hi Pete, Below is the location of our Knowledge base article that discusses this
issue that occurred with Toad 10.5.1 and McAfee. This article contains the .dat
file that was provided to us by McAfee in Dec 2010 to fix the 10.5.1 issue. If
your admin is still waiting on McAfee for the .dat file, is there any way of
having your Admin test to see if this .dat file resolves your current issues?
SOL58403
Haven’t contacted our admin yet - looks like were on McAfee 8.7.0i. I been cursing McAfee all day periodically killing process but not connecting my crawling desktop to TOAD.
Then I remembered reading about the 10.5.1 issue (just upgraded to 10.6.1.3 from 9.7 over the holidays) and found this. Thanks for the posting.
