October 20, 2025

General Cloud Backup, Troubleshooting, Veeam

Veeam SSPI Authentication Failed for User When Updating

During an update or upgrade of Veeam Backup & Replication, you may encounter the error message: “SSPI authentication failed for user.” Even when running the installer or updater with administrative privileges, this issue can still occur. It’s most often related to a mismatch between the Windows account used for the original installation and the one currently running the update, or to a change in the system hostname after installation. Common Scenarios Case 1: Hostname Changed After Installation If the Veeam installation was performed under a local administrator account and the server’s hostname was later changed, the mapping in PostgreSQL’s authentication file (pg_ident.conf) no longer matches the current system identity. As a result, the SSPI handshake fails during authentication. Case 2: Different Administrator Account Used If the update is being run under a different administrator account than the one originally used for installation, the PostgreSQL service will reject authentication due to an unmatched user mapping. Resolutions Case 1: Edit the pg_ident.conf File 1. Open the file:C:\Program Files\PostgreSQL\15\data\pg_ident.conf(Note: The PostgreSQL version number may vary depending on your installation.) 2. Scroll to the bottom of the file and locate the section labeled:MAPNAME SYSTEM-USERNAME PG-USERNAME You can also add additional administrator accounts here if multiple users manage the environment. 3. Update the entries to reflect the current system username or hostname. Example: 4. Save the file and restart the PostgreSQL-Veeam service. 5. Rerun the installer or update process. Tip: Always create a backup of pg_ident.conf before making changes. Case 2: Run the Updater with the Original Admin Account 1. Log in using the same Windows administrator account that was used during the initial Veeam installation. 2. Re-run the updater or installer from that session. 3. Once the update completes successfully, verify that all Veeam services start normally and can access the configuration database. Additional Notes If the SSPI authentication error persists after applying these fixes, please contact Support@Managecast.com for further assistance.

Troubleshooting, Veeam

Veeam Backup & Replication Error: Failed to Expand Object

The “Failed to expand object” error in Veeam Backup & Replication typically occurs when Veeam attempts to enumerate or query a virtual infrastructure object (such as a VM, datastore, cluster, or host) but cannot retrieve its components. This issue is most often related to environment configuration or permission mismatches between Veeam and the underlying vCenter/ESXi infrastructure. Common Causes and Resolutions Cause 1: vCenter or ESXi Connectivity Issues When Veeam cannot communicate properly with vCenter or a managed host, it may fail to expand objects during job initialization or inventory enumeration. Resolution: Cause 2: Incorrect or Expired Credentials If the credentials used to connect to vCenter, ESXi, or a Windows repository have changed or expired, Veeam will be unable to access the associated objects. Resolution: Cause 3: Insufficient Privileges The account used to connect to the host or vCenter must have adequate privileges to query inventory objects and perform backup operations. Resolution: Additional Notes If you continue to experience this error or need further assistance, contact Support@Managecast.com for additional troubleshooting guidance.

Scroll to Top