Loading...
Loading...
The PowerProtect Data Manager is used to protect the virtual machines (VM) with the Microsoft SQL Server application-aware solution. The initial configuration of the Microsoft SQL Server application-aware backup generates ABV0007 "unable to authenticate." ABV0007: VM Direct engine 'localhost' is unable to back up the virtual machine 'my-vm-name' on vCenter 'my-vcenter.my-domain.com' because of an SQL agent issue.The VM Direct engine cannot complete the backup of this virtual machine because the SQL agent operation was unsuccessful. If there is too much activity on the vSphere and the guest virtual machine, wait until some activities complete and then retry the operation. Read Less Unable to authenticate user 'testuser'. The user name or password is incorrect. The "PowerProtect Data Manager_*.log" export log shows: vmdm.log: YYYY-MM-DD HH:MM:SS INFO [] [vproxyMonitor] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:82ad56e103a61a50;JOB_ID:bce8e2cddeabcbcf][] [c.e.b.v.v.a.VPEProtectOp.statusChanged(226)] - MONITOR BackupJob: state changed BackupJobSession(state=Failure, id=f6f3c7e0-6b62-4f9b-87f6-0c01f0f6780c, error: code=500, text=Backup has FAILED. Backup of the application "MSSQLDM" on the virtual machine "my-vm-name" is unsuccessful. Unable to authenticate user 'testuser'. The user name or password is incorrect., target=my-vm-name): Queued -> Failure, progress=100 vmdm.log: YYYY-MM-DD HH:MM:SS INFO [] [vpe-completion-0] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:82ad56e103a61a50;JOB_ID:bce8e2cddeabcbcf][] [c.e.b.v.v.a.VPEProtectOp.resume(326)] - Resuming session for asset=my-vm-name -- BackupJobSession(state=Failure, id=f6f3c7e0-6b62-4f9b-87f6-0c01f0f6780c, clean, error: code=500, text=Backup has FAILED. Backup of the application "MSSQLDM" on the virtual machine "my-vm-name" is unsuccessful. Unable to authenticate user 'testuser'. The user name or password is incorrect., target=my-vm-name), isNew=true, taskId=346ca4b0-ae26-4937-864b-9a576685e4a5 vmdm.log: YYYY-MM-DD HH:MM:SS INFO [] [vpe-completion-0] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:82ad56e103a61a50;JOB_ID:bce8e2cddeabcbcf][] [c.e.b.v.v.a.VPEProtectOp.completeSessionFailure(921)] - Session complete with failure BackupJobSession(state=Failure, id=f6f3c7e0-6b62-4f9b-87f6-0c01f0f6780c, clean, error: code=500, text=Backup has FAILED. Backup of the application "MSSQLDM" on the virtual machine "my-vm-name" is unsuccessful. Unable to authenticate user 'testuser'. The user name or password is incorrect., target=my-vm-name) vmdm.log: YYYY-MM-DD HH:MM:SS INFO [] [vpe-completion-0] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:82ad56e103a61a50;JOB_ID:bce8e2cddeabcbcf][] [c.e.b.v.v.a.VPEProtectOp.shouldIndexBackup(1584)] - Backup type SYNTHETIC_FULL vmdm.log: YYYY-MM-DD HH:MM:SS INFO [] [vpe-completion-0] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:82ad56e103a61a50;JOB_ID:bce8e2cddeabcbcf][] [c.e.b.v.v.u.VMDMErrorHelper.getEEMI(269)] - Matched messageID=ABV0007, classificationKey=AGENT, keys=[vproxy, vmName, vCenterName] The "Vmdirect_*.log" export log shows: YYYY-MM-DD HH:MM:SS ERROR: [82ad56e103a61a50;bce8e2cddeabcbcf] MSSQLDM: MSSQLDM: connect: network: Unable to authenticate user 'testuser'. The user name or password is incorrect. YYYY-MM-DD HH:MM:SS ERROR: [82ad56e103a61a50;bce8e2cddeabcbcf] MSSQLDM: MSSQLDM: connect: network: Unable to receive message: io: read/write on closed pipe YYYY-MM-DD HH:MM:SS INFO: [82ad56e103a61a50;bce8e2cddeabcbcf] MSSQLDM: MSSQLDM: connect: Host agent lock released. YYYY-MM-DD HH:MM:SS ERROR: [82ad56e103a61a50;bce8e2cddeabcbcf] MSSQLDM: Backup of the application "MSSQLDM" on the virtual machine "my-vm-name" is unsuccessful. ... YYYY-MM-DD HH:MM:SS NOTICE: [82ad56e103a61a50;bce8e2cddeabcbcf] "Status": { YYYY-MM-DD HH:MM:SS NOTICE: [82ad56e103a61a50;bce8e2cddeabcbcf] "State": "Failure", YYYY-MM-DD HH:MM:SS NOTICE: [82ad56e103a61a50;bce8e2cddeabcbcf] "Description": "Backup of the application \"MSSQLDM\" on the virtual machine \"my-vm-name\" is unsuccessful. Unable to authenticate user 'testuser'. The user name or password is incorrect.", YYYY-MM-DD HH:MM:SS NOTICE: [82ad56e103a61a50;bce8e2cddeabcbcf] "Progress": 0, YYYY-MM-DD HH:MM:SS NOTICE: [82ad56e103a61a50;bce8e2cddeabcbcf] "Error": { YYYY-MM-DD HH:MM:SS NOTICE: [82ad56e103a61a50;bce8e2cddeabcbcf] "Text": "Backup has FAILED. Backup of the application \"MSSQLDM\" on the virtual machine \"my-vm-name\" is unsuccessful. Unable to authenticate user 'testuser'. The user name or password is incorrect.", YYYY-MM-DD HH:MM:SS NOTICE: [82ad56e103a61a50;bce8e2cddeabcbcf] "Code": 1007, YYYY-MM-DD HH:MM:SS NOTICE: [82ad56e103a61a50;bce8e2cddeabcbcf] "Classifications": [ YYYY-MM-DD HH:MM:SS NOTICE: [82ad56e103a61a50;bce8e2cddeabcbcf] "Authentication", YYYY-MM-DD HH:MM:SS NOTICE: [82ad56e103a61a50;bce8e2cddeabcbcf] "Agent", YYYY-MM-DD HH:MM:SS NOTICE: [82ad56e103a61a50;bce8e2cddeabcbcf] "Connection" YYYY-MM-DD HH:MM:SS NOTICE: [82ad56e103a61a50;bce8e2cddeabcbcf] ], YYYY-MM-DD HH:MM:SS NOTICE: [82ad56e103a61a50;bce8e2cddeabcbcf] "Retryable": false, YYYY-MM-DD HH:MM:SS NOTICE: [82ad56e103a61a50;bce8e2cddeabcbcf] "Remedy": null YYYY-MM-DD HH:MM:SS NOTICE: [82ad56e103a61a50;bce8e2cddeabcbcf] }, ...
The lockbox credentials configured for the Protection Policy are using an Active Directory Domain account. The credentials configuration does not include the Domain Name for the user account. The "User@Domain" format must be used for the Protection Policy credentials account.
Edit the stored authentication details for the Protection Policy credentials. From the left navigation pane, select "Administration > Credentials " to view the Credentials detail window. Locate the credential in the list of stored credentials. Use the filters and column sort options to organize the list of credentials. Select the credential from the list, and then click Edit . The Edit Credential dialog box opens. Modify the ' username ' field from "testuser" to "testuser@my-domain." Click Save to update the stored credentials. Test the Protection Policy with the updated credentials .
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.