Trying to set up agent handler in DMZ, keep getting error message for SQL connection

[markgarza]

Hi, trying to install an agent handler in FIPS mode in our DMZ to handle management of machines outside of our network. I keep running into a problem while connecting to our SQL database. The agent handler is in a workgroup and we're trying to connect to our domain-joined SQL server/domain joined EPO server. The error I keep seeing in the AH5100-ahsetupdll_handle log is:

20200723075730 I #06040 AHSETUP Trying to connect to database server dbms.company.pri,1433, instance ePO_EPOSVR256 as user svchandler

20200723075730 E #06040 AHSETUP dbfunctions.cpp(933): COM Error 0x80040E4D, source=Microsoft SQL Server Native Client 11.0, desc=Login failed for user 'svchandler'., msg=IDispatch error #3149

Anyone know what that dispatch error is about?

EDIT: Our primary server is EPO 5.10, and I am trying to use the agent handler files from that installation. 

[Hem]

If Agent handler is in work group environment then would suggest to use SQL Authentication than Windows Auth.

Make sure that we are successfully able to complete UDL test from AH to SQl server (KB70929)

[markgarza]

We are using a local SQL account instead of a domain account to connect to the database, yes.

I tried the test in KB70929 and it tested successfully with the exact same information I'm putting in the installer, but installer still fails saying it cannot log in with that credential.

[Hem]

so user #: svchandler is SQL user. UDL test is completing with this user only for ePO DB.

[markgarza]

Yes. I should also note that the SQL server is separate from our EPO server, they are not together on one server.

[Hem]

Would suggest to open case with support.

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?

[markgarza · Accepted solution]

I think we figured it out, there was a backslash in the password which according to KB66286 is not allowed: https://kc.mcafee.com/corporate/index?page=content&id=KB66286

We reset the password and made sure it followed those rules and it worked immediately. 

[Hem]

Excellent, Glad that it's working.