I am very curious to know about VSE 8.7.1
When is it supposedly releasing ? What will be the major changes or updates ?
Also, I have been hearing about the version 9.0. What happened to that ?
April 19, 2010 and engineserver.exe is STILL a SERIOUS problem. We just installed Total Protection on the server and workstations and they all exist just for the purpose of running engineserver.exe because nothing else is getting done. The workstations are continuously locking up and occassionally, the server locks up too. When can we expect some relief from this? Is there anything we can do short of uninstalling McAfee to get our computers back again? We really need to get some work done. Thanks.
For what its worth to those still having problems, creating the RunAtNormalPriority key as advised a few posts ago resolved my issue. Maybe we'll get an update on when the patch will be coming out to resolve this permanently.
There is a HF available for engineserver + outlook scan memory issue:
Microsoft Internet Explorer 7 x
Mozilla FireFox 3 x
For details of all supported operating systems, see KB51109
The OutlookScan feature can fail to release an instance of the scan engine that was loaded via EngineServer.exe. This can lead to symptoms of EngineServer.exe using large amounts of memory, until the service was restarted.
Memory usage is higher than expected
Because of the present (March 2010) size of virus definition files, it is reasonable to expect to use 50 MB of memory for a single instance of the Engine and DAT files.
If you find that the EngineServer service is using more than 150 MB of memory (in other words, more than three instances of the Engine and DAT files), and this memory is not released after being idle for more than 30 seconds, you should install the hotfix attached to this article.
Install the hotfix attached to this article.
The hotfix will be included in Patch 4 for VirusScan Enterprise 8.7i (expected to be released for general availability in July 2010).
To receive email notification when this article is updated, click Subscribe at the top of the page. (You must be logged in at https://mysupport.mcafee.com to subscribe.)
This issue has been resolved with hotfix HF539488 for VirusScan Enterprise 8.7i.
The Outlook UI library will now properly release the Engine instance on exit of Outlook.
When EngineServer.exe's memory usage is high, restarting the service will reset the amount used.
Thank you for using McAfee® VirusScan® Enterprise 8.7i. This document contains important information about this HotFix. We strongly recommend that you read the entire document.
Resolved issues in this release of the software are described below:
I have several machines (WinXP Sp3) that are having this issue in our environment. I have noticed most of them are the older laptops that are still in use. We do not notice any issue with the dual core and higher laptops.
We are running
VSE 8.7i Patch 3
I looked at the KB article that was posted this week. I downloaded the zip file and ran the EXE on my computer, to test and see what it does, before I release to production. I received an error, Product(s) already running the latest version of engine and DAT files. So i clicked OK and then that was it, the window closed.
I will run this on one of the computers that is having this issue and test it, but has anyone else seen a positive outcome from this?
What is the file actually updating. If I am already using the latest engine version, everyone else is as well, so not sure what value it will have to resolve this issue.
Which KB article that was posted this week? could you provide a link?
As far as I know an engine update isn't going to fix this, which it sounds like you downloaded. I still haven't seen patch 4 come out. But on single core machine I've used (which is all of mine unfortunately), that registry hack mentioned above and that I posted about also has stopped the headaches for me so far. The reason you don't see it on the multi-core machines is because it only ties up one core, leaving the other for normal work causing users not to notice it.
Hmmm, what's different between the 60% it worked for and 40% it didn't work for? Different hardware? Different software load? Different VirusScan upgrade paths to 8.7p3? That registry hack puts VirusScan on an even keel with other programs so it shouldn't be spiking the processor after that reg hack is applied and the VirusScan stuff is restarted.