YYYY-MM-DDTHH:MM:SS+0000 DEBUG [vcf_om,698d06aa93f1a######85097eeb00f7b,f384] [c.v.v.p.v.u.CredentialsValidationTaskExecutor,om-exec-2] Updating expiration details for credentialId: fc56bea1-5c2a-4665-####-3f98####6175 in credential expiry cacheYYYY-MM-DDTHH:MM:SS+0000 DEBUG [vcf_om,698d06aa93f1a######85097eeb00f7b,f384] [c.v.v.p.s.PasswordExpirationService,om-exec-2] Validation checks size = 1YYYY-MM-DDTHH:MM:SS+0000 DEBUG [vcf_om,698d06aa93f1a######85097eeb00f7b,f384] [c.v.v.p.s.PasswordExpirationService,om-exec-2] expiry cache entity is available : trueYYYY-MM-DDTHH:MM:SS+0000 DEBUG [vcf_om,698d06aa93f1a######85097eeb00f7b,f384] [c.v.v.p.s.PasswordExpirationService,om-exec-2] Expiry retrieval status : SUCCEEDED , Diagnostic message : nullYYYY-MM-DDTHH:MM:SS+0000 WARN [vcf_om,698d06aa93f1a######85097eeb00f7b,f384] [o.h.e.jdbc.spi.SqlExceptionHelper,om-exec-2] SQL Error: 0, SQLState: 22008YYYY-MM-DDTHH:MM:SS+0000 ERROR [vcf_om,698d06aa93f1a######85097eeb00f7b,f384] [o.h.e.jdbc.spi.SqlExceptionHelper,om-exec-2] ERROR: timestamp out of range: "2739933-02-15 01:00:23.326876+00" Where: unnamed portal parameter $4 = '...'YYYY-MM-DDTHH:MM:SS+0000 ERROR [vcf_om,698d06aa93f1a######85097eeb00f7b,f384] [c.v.v.p.s.PasswordExpirationService,om-exec-2] could not execute statement [ERROR: timestamp out of range: "2739933-MM-DD HH:MM:SS+00" psql -h localhost -U postgres -d operationsmanager -c "SELECT credential_id, resource_fqdn, username, expiry_date, fetch_time, fetch_status FROM passwordmanager.credential_expiry WHERE resource_type = 'VCENTER' ORDER BY fetch_time DESC;"
VMware Cloud Foundation 9.x
VMware Cloud Foundation 5.x
This issue occurs when the vCenter Server SSO Password Policy is configured with an expiration value that calculates to an extremely far-future date (such as 0 for "never expires," or a very large number like 999999, which vCenter may translate to a year like 2739933).
When SDDC Manager attempts to fetch this password expiry date to update its internal PostgreSQL database, the value exceeds the database's maximum supported timestamp limit. This throws a timestamp out of range exception, causing the backend sync to fail and leaving the account permanently in a Disconnected state, regardless of password remediation success.
To resolve this issue, lower the vCenter SSO password expiration policy to a supported, finite value, and then remediate the password in SDDC Manager.
Step 1: Update vCenter SSO Password Policy
Log in to the vSphere Client (vCenter Server) as an administrator (e.g., [email protected]).
From the main menu, navigate to Administration.
Under Single Sign On, click on Configuration.
Select the Local Accounts tab.
Highlight the Password Policy row and click Edit.
Change the Maximum lifetime (Expiry) to 999 or 9999 days.
Click Save or OK.
Step 2: Retrieve the service accounts credentials from SDDC Manager for the Disconnected Account following KB: Retrieve the service accounts credentials from SDDC Manager
Step 3: Remediate Password in SDDC Manager
Log in to the SDDC Manager UI.
Navigate to Administration > Security > Password Management (or the relevant password management section for your VCF version).
Select the affected service account (e.g., svc-<fqdn_of_sddc>@vsphere.local) that is showing as Disconnected.
Click Remediate.
Provide the current valid password for the account and confirm.
Once the task completes successfully, SDDC Manager will fetch the newly supported expiration date, the database will update successfully, and the account status will reflect as Connected.
Setting the maximum lifetime password policy to zero (0) can cause prechecks to fail.
https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-5-2-and-earlier/4-5/vcf-release-notes/vmware-cloud-foundation-451-release-notes.html
Edit the vCenter Single Sign-On Password Policy
https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vsphere-authentication-8-0/vsphere-authentication-with-vcenter-single-sign-on-authentication/vmware-single-sign-on-polices-authentication.html