Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Application Errors...linked to ePo??? 1

Status
Not open for further replies.

AuntieEPO

Technical User
Jul 3, 2002
61
GB
Since installing ePo 2.5.1 and deploying everything successfully, we have been experiencing application errors on numerous machines, from within numerous apps.

All errors are of the type "the instruction at 0x0123456 referenced memory at 0x123456. The memory could not be read."

Some of these errors are vshwin32.exe errors, and the majority of the others are in word, winword.exe errors, which result in people being kicked out of word and thus loosing any unsaved work.

Now, this may have nothing to do with ePo, its just that the time when these errors began to apear, coincides with the time when ePo was installed.

Is there any known issues with ePo and this type of memory error?
 
It might not be ePO. Check if you've installed SP1 for VirusScan 4.51. ePO has nothing to do with VSHWIN32.EXE errors. Only VirusScan does.

AVChap
 
yeah its vscan 4.5.1 sp1.

The more worrying thing is the word error, keeps happening on our company secretary (and director)'s machine, just seems odd that this has only begun to happen since installing epo and vscan 4.5.1. Before then we were all using vscan 4.5 and Management Edition.

Cheers

 
Hi

VSHWIN32.EXE is the control utility for the On-Access Scanner. It starts and stops the VShield scanner and controls the display status of the VirusScan System Tray icon.

I think you better report this to the McAfee support guys.



Cheers
AVDude
 
Hi,

Did you manage to find a solution to solve the problem with the crashing apps?

After installing ePO version 2.51 we are experiencing similair problems with services and apps that go down on several servers. Also about 20 dr.Watson's popup at logon.

EventID 5022
MCSCAN32 Engine Initialisation failed. Engine returned error : Memory allocation failed.

EventID 5019
Exception in McShield.Exe!
Exception details follow :
Build Feb 13 2000 14:57:40
Init 100:
Crash address 0x00408bf9
Code 0xc0000005
Flags 0x00000000
2 Parameters : 0x00000001 0x000005d4

EventID 4097
The application, , generated an application error The error occurred on 9/ 6/2002 @ 14:30:48.889 The exception generated was c0000005 at address 00408bf9 (<nosymbols>)

EventID 1004
Task Manager : McShield service couldn't be enabled

The domain consists of NT4sp6a machines with Netshield 4.5 on the servers and VirusScan 4.03 on the workstations.

If you did find a solution, could you please let me know.

TIA.

Regards,

Mark O.
 
We did manage to solve the problems in a round about kind of way, it was a combination of things.

The vshwin32.exe app errors we were experiencing were apparently due to the fact that we were using VScan 4.5.1 sp1 on NT4 machines and there is a known error with this combo. Theres either a registry hack you can perform to sort this (details are on mcafee's online Kbase) or simply revert back to Vscan 4.5 on all NT machines - which is what we did.

As you're using VScan 4.03, all i'd suggest is getting Vscan 4.5 from the dowloads site at Mcafee, then load it into the epo repository and push it out to your clients, i think if you were to speak to Mcafee then theyd definately tell you to move to the latest versions first, just dont use Vscan 4.5.1 with NT without performing the regedit.

Also theres a service pack for Netshield that is available for download.

This may clear up the errors you are getting.

HTH
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top