Operational Defect Database

BugZero found this defect 115 days ago.

Veeam | kb4542

"SSPI authentication failed for user"

Last update date:

1/26/2024

Affected products:

Veeam Backup & Replication

Affected releases:

12.1

Fixed releases:

No fixed releases provided.

Description:

Challenge

When the Veeam Backup & Replication Configuration Database is using PostgreSQL, direct interaction with the database may fail with the error: SSPI authentication failed for user Interactions where this may occur include: Installing an update to Veeam Backup & Replication. Performing a configuration restore. Attempting to interact directly with the database (e.g., using pgAdmin or pgsql commands).

Cause

This error occurs when the account being used to perform the interaction is not authorized to access the Veeam Backup & Replication configuration database within the PostgreSQL instance. When PostgreSQL is deployed by the Veeam Backup & Replication installer, that PostgreSQL database engine is configured to use SSPI Authentication, which allows for access authentication using Windows accounts. The pg_ident.conf  file, which maps Windows accounts to the postgres root user account, is updated to add Windows accounts that should have access to the configuration database. By default, the following Windows accounts are added as authorized to access the database directly: The Windows account was used during the initial install. The NT AUTHORITY\SYSTEM account, which is the default account used by the Veeam Backup & Replication services.

Solution

Option 1: Use an Existing Authorized Windows Account To identify which accounts are currently authorized to access the Veeam Backup & Replication configuration database, open the following file in a text editor: C:\Program Files\PostgreSQL\15\data\pg_ident.conf At the bottom of the file, you will find at least two uncommented lines with a format similar to this example: veeam   User@Domain   postgress

Additional Resources / Links

Share:

BugZero® Risk Score

What's this?

Coming soon

Status

Solved

Learn More

Search:

...