How to test SQL database connectivity using a test.udl file

Technical Articles ID: KB70929
Last Modified: 2/10/2020

Environment

McAfee ePolicy Orchestrator (ePO) 5.x

All supported Microsoft SQL servers

For details of ePO and SQL supported environments, see KB51569.

Summary

If you are experiencing a database connection issue, use a test.udl file to confirm the database credentials outside of ePO.

Problem

The ePO server and any additional Agent Handlers, must connect to the ePO database to function. If they can't, several symptoms are displayed, including:

Connection errors in the log files
Inability to log on to the ePO console

Solution

Prerequisite checks:

If you are trying to verify connectivity to an SQL Server, from a system where ePO is not currently installed, you need to install the Microsoft SQL Native Client before performing this test:
1. Browse to https://www.microsoft.com/en-us/download/details.aspx?id=50402
2. Click Download to obtain x64 or x86 version as needed.
3. To install the SQL Native Client, Run the downloaded installer
The Data Link connection test does not allow you to specify a Windows account, and can only use the credentials of the logged-on user.
If you are trying to verify connectivity for a Windows account, make sure that you have logged on to the system using that account before proceeding.

To verify SQL connectivity using a UDL file:

Create a text file on the ePO server.
Rename it to test.udl.
Double-click the test.udl file.
Click the Provider tab.
Select SQL Server Native Client 11.0.
Click Next.
On the Connection tab, enter the same information entered in the ePO core/config page for the database connection.
In the Select or Enter a Server Name field, type the SQL Server name in the following format:

<server_
name>,<port>

NOTE: If you are verifying connectivity to a named instance of SQL, use the following format:

<server_name>\<instance_name>

Examples:

EPO53SVR,1433
EPO53SVR\EPOSERVER
To verify connectivity for the logged-on Windows account, click Use Windows NT Integrated security, and leave the Server SPN box empty.
To verify connectivity for an SQL account, click Use a specific user name and password, and enter the user name and password.
To verify connectivity to an existing ePO database, click Select the database, and enter the name of the ePO database.
To verify connectivity to the SQL Server, click Select the database, and enter primary as the database name.
Click Test Connection.

Affected Products

ePolicy Orchestrator 5.9
ePolicy Orchestrator 5.10.x

Languages:

This article is available in the following languages:

German
English United States
Spanish Spain
French
Italian
Japanese
Korean
Dutch
Portuguese Brasileiro
Chinese Simplified
Chinese Traditional

Glossary of Technical Terms

Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.

How to test SQL database connectivity using a test.udl file

Environment

Summary

Problem

Solution

Affected Products

Languages:

Glossary of Technical Terms

Title

Title

Featured Solutions

Explore Our Portfolio

Security Outcomes

Industries

Products

Featured Solutions

Explore Our Portfolio

MVISION Products

Services & Training

Threat Research

Our Researchers

Threat Landscape Dashboard

Tools

Contact Us

Resources

Downloads

Product Help

Connect with Us

Explore

Our Company

Our Efforts

Other Resources

Careers

Partnerships

How to test SQL database connectivity using a test.udl file

Environment

Summary

Problem

Solution

Affected Products

Languages:

Glossary of Technical Terms

Choose your region

Title

Title