Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Databases and Redis

pgAdmin says the utility file was not found and asks for a Binary Path

ErrorUtility file not found. Please configure the Binary Path in the Preferences dialog.

Short answer

Backup, Restore and similar tools in pgAdmin run pg_dump, pg_restore and psql from a folder you choose. If that folder is unset, wrong for the server's version, or the tools are not installed, pgAdmin shows this message. Install the PostgreSQL client tools, set the Binary Path for the version in Preferences, and use Validate path.

  • Applies to pgAdmin 4 9, PostgreSQL 16, PostgreSQL 17
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Find where the PostgreSQL client tools are installed. If this prints nothing, the tools are not installed and the third cause applies.

    which pg_dump pg_restore psql
    # Windows: where pg_dump
  2. 2Match what you see, then jump to its fix

    1. 1The Paths > Binary paths grid is empty, or its path has no pg_dump in itThe Binary Path is not set, or points to the wrong folderFix
    2. 2Works for one registered server but not anotherThe path is set for a different server versionFix
    3. 3which pg_dump prints nothingThe PostgreSQL client tools are not installed on this computerFix

What does the error look like?

  • Utility file not found. Please configure the Binary Path in the Preferences dialog.

Cause 1 of 3

The Binary Path is not set, or points to the wrong folder

1Check

pgAdmin's preferences describe the PostgreSQL Binary Path as the location of the utility programs. The directory must contain pg_dump, pg_dumpall, pg_restore and psql. If you set no path, pgAdmin searches standard install locations only.

ls "$(dirname "$(which pg_dump)")"

2Fix

Open Preferences, go to Paths > Binary paths, and enter the directory that holds those programs. Press Validate path; it checks that they exist and reports their versions.

# Example directory to enter in the PostgreSQL Binary Path row:
/usr/lib/postgresql/17/bin

3Verify

Press Validate path, then start the backup again.

# Validate path should list pg_dump, pg_dumpall, pg_restore and psql

Confirmed by pgadmin.org

Did this fix it?

Cause 2 of 3

The path is set for a different server version

1Check

The Binary paths grid is set per PostgreSQL server version. If no path is set for a version, pgAdmin falls back to the one marked as default.

psql -h HOST -U USER -d postgres -c "SHOW server_version;"

2Fix

Add a row for the server's major version, or mark the newest installed set of tools as the default, then validate the path.

# Preferences > Paths > Binary paths: set the row for the matching version

3Verify

Run Validate path and check the reported version.

# Validate path shows the version of pg_dump found

Confirmed by pgadmin.org

Did this fix it?

Cause 3 of 3

The PostgreSQL client tools are not installed on this computer

1Check

pgAdmin is only the interface. On a machine with pgAdmin alone, there are no pg_dump or pg_restore programs for it to call.

pg_dump --version

2Fix

Install the client package. On Ubuntu with the PostgreSQL apt repository, postgresql-client-VERSION holds the client binaries. Then set the Binary Path to where it installed them.

sudo apt update
sudo apt install postgresql-client-17

3Verify

Check that the tools respond.

pg_dump --version
psql --version

Confirmed by postgresql.org

Did this fix it?

How do I stop it coming back?

  • Install client tools of the same major version as your newest server and keep that version as the default row.
  • After upgrading PostgreSQL, revisit Binary paths: the old folder may no longer exist.
  • Press Validate path whenever you change a path.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Related fixes

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.