cancel
Showing results for 
Search instead for 
Did you mean: 
Nick_B
Level 10
Report Inappropriate Content
Message 1 of 5

ePO is unable to connect to the SQL Database after updating the db.properties on AH

Jump to solution

Dear ePO Fans,

We have an issue at the moment whereby the account used to connect ePO to the SQL Server backend DB is unable to connect due to the account it uses getting locked out.

I was going to give this post the title of: Updating the db.properties file on Agent Handler causes the Windows Service Account to Lockout

Background

The customer in question has around 7,500 endpoints running Win7/10/2008/2012.

Products deployed include MA 5.5.1.388, VSE 8.8.0.2024, HIPS 8.0.0.4605 & DLP 11.0.200.1002.

ePO version is 5.3.2.156. SQL is on separate server running SQL 2016 on a Windows 2012R2 VM.

Agent Handler running same version of ePO but not in DMZ.

The work last week involved migrating the ePO SQL DB to a shiny new MS SQL 2016 Std VM on a Windows Server 2012R2 VM from SQL Server 2008R2. This went OK.

The issue made itself known when the account used to connect ePO-SQL (epo-02) repeatedly locked itself out time and time again. So we created a fresh service account (epo-04) and assigned it the Log On Locally right as per instructions.

The Event Parser is not running on the Agent Handler at the moment, as when we modified the db.properties file to update it with the new SQL Server DB info, instance, port and username used to connect, the account (the Windows service account listed above, epo-04) got locked out - so this of course caused ePO to fail to connect to the database! Source of the lockout was the AH!

It may be trying to use cached credentials from an older account that was previously being used - epo-02.

Anyway, to resolve the issue with ePO failing to connect to the database, we stopped the Event Parser service on the AH and unlocked the Windows service account (epo-04)..

Any ideas would be gratefully received.

Thanks,

Nick

1 Solution

Accepted Solutions
McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 3 of 5

Re: ePO is unable to connect to the SQL Database after updating the db.properties on AH

Jump to solution

Please follow KB75333 to properly reset the password on the agent handler rather than directly modifying the db.properties file.

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?

4 Replies
Reliable Contributor vnaidu
Reliable Contributor
Report Inappropriate Content
Message 2 of 5

Re: ePO is unable to connect to the SQL Database after updating the db.properties on AH

Jump to solution

Dear @Nick_B 

I hope you already have this KB tried KB69850. This issue may occur for several reasons so we need to makesure what is causing the issue.

However, I wish you go through the KB articles KB51465 and KB81146 also try to perform an UDL test. I hope your issue will be resolved soon.

Venu
McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 3 of 5

Re: ePO is unable to connect to the SQL Database after updating the db.properties on AH

Jump to solution

Please follow KB75333 to properly reset the password on the agent handler rather than directly modifying the db.properties file.

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?

Nick_B
Level 10
Report Inappropriate Content
Message 4 of 5

Re: ePO is unable to connect to the SQL Database after updating the db.properties on AH

Jump to solution

Hi cdinet,

Thanks for your help - the information contained in KB75333 resolved the issue (Solution 1 at the top) - so we basically re-ran the Agent Handler installation.

Many thanks,

Nick

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

Re: ePO is unable to connect to the SQL Database after updating the db.properties on AH

Jump to solution

Glad it helped!

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