This content has been marked as final. Show 20 replies
Do your run the epo server in a virtual environment ?
Yes, it's running on an ESX Server 3.0.2 with Windows Server 2003 R2 Standard with latest patches installed. Is this a known issue with virtual environments?
imho it is not, but I realized in our last epo course (we use VMWare Player for the epo server OS) that after I installed patch 1 for ePO 4.0 no notifications where produced. As I was not running in a supported environment I have not raised a case (https://knowledge.mcafee.com/SupportSite/search.do?cmd=displayKC&docType=kc&exte rnalId=KB44248&sliceId=SAL_Public&dialogID=27802286&stateId=1%200%2027798838). But I immediately tested the ePO 4.0 patch 1 on our internal esx server 3.0.1 and the notifications there where working.
I also noticed the same log errors as you posted:
20080411111748 E #4544 McUpload Failed to send http request. Error=12029
20080411111748 W #4544 EventParser HTTPS POST returned error 0. Will retry.
But I have not found any further information. I have installed the latest VMWare tools, switch networking and so on but nothing worked. As your environment is supported please raise a call at McAfee and tell us the result - or someone else can shed some light on this wink
I know it didn't work, as I was there at your last epo course :-)
I already opened a call at McAfee but got no answer yet. I obviously followed the installation path that we took in the course so there might be an error. The other similarities are that we used virtual machines and that we used Win2003 R2 Standard Edition in German with all patches. What Windows Server version did you use on your ESX server? The same?
It´s a small world ;-)
We use ESX 3.0.1 and Windows 2003 R2 Standard - all notifications there are working properly.
Keep us informed about the McAfee call ...
I was finally able to reproduce the error on a test system:
When installing ePO Patch 1 you can change the sensor-to-server communication port. I did that and it messed up the notifications.
@ Tom: We also changed the port at the epo training. Did you change the port on your internal server too?
@ all: Now I'm looking for a way to change the port on a running system. Does anyone know how?
The port number is saved in the ServerInfo table. Changing the port there and restarting the server should change it. What do you mean with Patch 1 changed the port ? There is no initial sensor-communication port configuration in a new ePO 4 setup ...
Yes initially there is none defined, but when you install patch 1, there is a prompt for a port that defaults to port 8445 (see screenshot below).
I changed that to 9005 during patch 1 installation and notifications didn't work (like in the training). Then I reverted back to pre patch 1 VMWare snapshot and installed patch 1 again, now with port 8445, and notifications did work!
On our live system I did the following:
- in %programfiles%\McAfee\ePolicy Orchestrator\Server\conf\server.xml I changed the line
<Server port="9005" shutdown="SHUTDOWN"> to <Server port="8445" shutdown="SHUTDOWN">
ePO still shows port 9005 in the properties section but notifications are working again!
ok, thanks for the info - I will try this in my next course. Have you raised a call at McAfee for the issue ?