Another problem I now have after upgrading to 5.1.
Reboot seems to fix it for a short time, then it comes back again.
ePO was updated from 4.6.6 to 5.1.0. Latest agent and viruscan installed and SQL database on another server.
McAfee REALLY need to test this stuff out before releasing.
Thanks in advance.on 05/12/13 13:52:13 GMT
It works fine after a reboot or restart of services. I've already gone to that page and re-entered the same info again and left the 'Database server instance' field empty. The connection seems to break after an hour or so, will see how it goes on.
I had a similar issue with same version of EPO with one of my customer and the issue resolved after changing the authentication from windows to sql user.
Moreover, my customer also confirmed reboot the server resolves the issue.
So, I suggest to follow the steps as the document attached with screenshots to create create sql user and monitor for one day to confirm issue resolves.
RGCMessage was edited by: rgc on 12/6/13 4:36:49 AM CST
It's great, then from your environment from the sql configuration manager for the epo instance the name pipes option is disabed.
Hence it working after removing the instance name.
But even after this, if you find the issue re-produced, I suggest to go for sql user with mixed mode.
Getting the error again this morning, seems to have been alright for 4 days.
I've seen other users facing the same problem but still not seen any fix from McAfee...
The main problem I have with this error is that when it happens the ePO server effectively stops working, no replication occurs and no downloading of new dat files. Come on McAfee you're putting your customers at risk here!
If it helps, ePO is running on 2008 R2 VM with 8GB RAM and SQL database on another server. It's been this way for 2 years without problem. As soon as upgraded to 5.1.0 the license errors started.on 27/12/13 12:10:36 GMT