cancel
Showing results for 
Search instead for 
Did you mean: 

Windows couldn't start the McAfee ePolicy Orchestartor 5.10.0 application server

Jump to solution

Hi,

 

We updated remote 2016 SQL this morning.  Restarted epo services  services fail to start  with Error 1053:  The service didn't respond to the start or... request in timely fashion.   epolicy  5.10.0 Build 893.

 

Thanks

2 Solutions

Accepted Solutions
McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 2 of 4

Re: Windows couldn't start the McAfee ePolicy Orchestartor 5.10.0 application server

Jump to solution

Please open a ticket with McAfee and provide a mer from epo, sql error logs and an nmap output from sql and epo servers.  Refer to kb91115 for running nmap.  This isn't something we can easily guess at with out specific data.

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

Re: Windows couldn't start the McAfee ePolicy Orchestartor 5.10.0 application server

Jump to solution

Issue was related to a change I made in SQL server Dynamic port.   I am using same SQL server for RDSweb farm.   I made SQL server  to  only listen on  ports "1433-1434"   once I logged in to https://<servername>:8443/core/config.  and changeed the SQL port from 55090  to 1433. the problem was fixed

Thanks   

3 Replies
McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 2 of 4

Re: Windows couldn't start the McAfee ePolicy Orchestartor 5.10.0 application server

Jump to solution

Please open a ticket with McAfee and provide a mer from epo, sql error logs and an nmap output from sql and epo servers.  Refer to kb91115 for running nmap.  This isn't something we can easily guess at with out specific data.

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

Re: Windows couldn't start the McAfee ePolicy Orchestartor 5.10.0 application server

Jump to solution

Issue was related to a change I made in SQL server Dynamic port.   I am using same SQL server for RDSweb farm.   I made SQL server  to  only listen on  ports "1433-1434"   once I logged in to https://<servername>:8443/core/config.  and changeed the SQL port from 55090  to 1433. the problem was fixed

Thanks   

McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 4 of 4

Re: Windows couldn't start the McAfee ePolicy Orchestartor 5.10.0 application server

Jump to solution

Good deal - we have had some cases with an sql upgrade that didn't go so well, which is why I requested a case open, but your situation is better 🙂

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

More McAfee Tools to Help You

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community