ePO 3 SP2a Patch 3/4 - Naimserv.exe triggering event ID 4097

[simonjcook]

Hi there,

After upgrading to ePO 3 Patch 3 and 4 we have had issues with Naimserv.exe crashing periodically.

Dr Watson is generating an event ID 4097.

The application, , generated an application error The error occurred on 5/11/2004 @ 12:54:31.906 The exception generated was c0000005 at address 6041633f (naihttp_HttpServerWorkFunc)

Indications from

http://www.eventid.net

are that Naimserv.exe is accessing areas of memory it shouldn't be.

Please see:

http://www.eventid.net/display.asp?eventid=4097&eventno=265&source=DrWatson&phase=1

Anyone got any ideas?


Regards

Simon J Cook

< Keyboard Error - Press F1 to continue >

 

[Jump1ng]

We are running EPO version 2.1.2.257 (not sure which patch level that is). But I dont have naimserv.exe running on my machine.

Im not sure but it almost looks like this file is part of an old EPO and I think it was used with version 2.5.

Try to force and upgrade to the latest epo.

I usually do this.

FRAMEPKG.EXE /FORCEINSTALL /INSTALL=AGENT /SILENT
usually pushed out using LANGuard on pc's that show EPO problems like being stuck in old EPO version or start process that run at 100%

 

[simonjcook]

Hi Again,

Just to clarify, Naimserv.exe is the McAfee ePolicy Orchestrator 3.0.1 Server Service.

The affected server is running ePO 3 Service Pack 2a with Patch 3 installed.

I did previously patch the server to Patch 4. That was when the issue first became apparent and was more pronounced.
Consequently I rolled the server back to SP2a (using a Ghost Image).

In an effort to move forward (we had severe performance issues with SP2a). I recently upgraded the server to Patch 3.
The performance issues are solved by Patch 3 and above.

However, now the ePO server service is failing at seemingly random intervals.

Regards

Simon J Cook

< Keyboard Error - Press F1 to continue >

 

[simonjcook]

Hi everyone,

NAI have released ePO 3 SP2a Patch 5 to resolve this issue.
We are deploying it to affected servers today.
It seems to be backward compatible with Patch 4 unaffected servers need not be patched at present.

Regards

Simon J Cook

< Keyboard Error - Press F1 to continue >