Good day Community,
I have a client that has about 250 users and they don't have SQL licenses. They want McAfee ePO deployed in their environment, so we thought we can run SQL Express that comes with ePO package.
During the installation we discovered that the SQL Server Agent Service cannot be started and found the below articles during my troubleshooting steps.
1. My question is has anyone come across the same issue and is McAfee aware of the problem (because they wouldn't include SQL Express in the ePO package knowing that SQL Agent Service is not supported).
2. Is there another work around since the customer does not have SQL licenses.
Customer is running Windows Server 2012 R2 with 8GB Ram, Intel Xeon 2.93GHz Processor.
Evans Dube (South Africa)
Have you cross checked the below ports, For SQL servers these ports are must be opened.
TCP port 1433 used to
communicate with the SQL server. This port is specified or determined
automatically during the setup process.
UDP port 1434 used to
request the TCP port that the SQL instance hosting the ePO database is using.
In this scenario and as per above screenshots, I am able to see there is a SQL UDP 1434 port issue. Due to that only, i think you are facing an issue.
If possible, Could you please try. I think it should work as we expected.
Is it necessary to check if the ports are blocked if SQL is going to be running on same Box?
Yes it is - the loopback interface is subject to the same rules as any other interface.
Evans - you don't necessarily need the SQL agent for ePO to run. All the SQL agent does is manage jobs/schedules/tasks/operaters/etc within SQL Server itself. It will not prevent ePO from running - you just won't be able to create jobs and such to perform tasks on your SQL DBs.
As for your port issue, SQL usually runs on 1433 or 1434, you will need those open for comm between ePO and SQL.