Loading...
Loading...
PPDM VMware application-aware backup failed with following error messages in vmdm.log: vmdm.log: 2024-11-20T07:38:19.049Z ERROR [] [vpe-thread-38] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:a5315ff07f0bb74a;JOB_ID:9959173e0c09b0ff][] [c.e.d.v.c.VProxyManager.error(1102)] - Session waitFor READY failed InstallClientSession(state=Failure, id=76c8ed37-66d5-4710-a030-eb768a239b36, clean, error: code=0, text=Unable to perform MSSQLDM Agent operation 'configure' on VM 10.2.1.69 (vm-70). Unsuccessful PowerProtect agent for Microsoft Applications operation 'configure'. Unable to update persisted settings for PowerProtect Data Manager host '10.0.0.1': Unable to log in to PowerProtect Data Manager host '10.0.0.1'. Received the HTTP code 400 and response 'Invalid FQDN'.)
This error could occur when: The computer name of the SQL server does not match with the DNS name it resolves to, differentiate between long and short name.The reverse IP lookup does not work for the SQL server.
To resolve the issue with VMware application-aware backup failing to configure MSSQLDM Agent due to the 'Invalid FQDN' error, follow these steps: Step 1: Configure the computer name to ensure it matches with the DNS name it resolves to. Step 2: Verify the name resolution and reverse IP lookup works for the SQL Server client. Step 3: Rename the lockbox folder in C:\Program Files\DPSAPPS\common on the Microsoft SQL Server client. Step 4: Retry the virtual machine backup job. For detailed instructions, refer to the PPDM Microsoft SQL Server User Guide -> Application-aware backup failure with persisted settings message part. CAUTION: If you are unsure about any of these steps or if the issue persists after attempting the resolution, contact Dell Support for further assistance.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.