La configuración inicial de SQL de VM de PowerProtect falla ABV0025 "Los certificados SSL no están presentes"
Summary: El trabajo de configuración de la máquina virtual (VM) de Microsoft SQL Server falla con el estado de salida ABV0025 lo que indica que no se pudo registrar el servicio de agente de PowerProtect. ...
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
El dispositivo PowerProtect Data Manager se utiliza para proteger el entorno vSphere. Se está configurando una política de protección orientada a aplicaciones de VMware para proteger una máquina virtual (VM) de Microsoft SQL Server. El trabajo de configuración del sistema de VM de Microsoft SQL Server falla con el estado de salida ABV0025 lo que indica que no se pudo registrar el servicio de agente de PowerProtect.
ABV0025: VM Direct engine is unable to configure protection for the virtual machine 'my-sql-server.my-domain.com' on vCenter 'my-vcenter.my-domain.com'. The VM Direct engine cannot complete protection of this virtual machine because the protection configuration was unsuccessful. Review the error details and summary log in the Jobs window, or export the job logs and review the log files for more information. If the issue persists, contact Dell Customer Support. Read Less Unable to perform MSSQLDM Agent operation 'configure' on VM xxx.xxx.xxx.xxx (vm-##). Unsuccessful PowerProtect agent for Microsoft Applications operation 'configure'. Unable to update persisted settings for PowerProtect Data Manager host 'xxx.xxx.xxx.xxx': Unable to log in to PowerProtect Data Manager host 'xxx.xxx.xxx.xxx'. Received the HTTP code 400 and response 'Invalid FQDN'. Unable to register PowerProtect Agent Service. SSL certificates are not present.
Figura 1: Captura de pantalla del mensaje de error ABV0025 que indica que no se puede registrar el servicio de agente de PowerProtect.
La exportación del trabajo de configuración de la VM de Microsoft SQL Server muestra lo siguiente:
YYYY-MM-DD HH:MM:SS INFO: [a267c9eb8362b811;b45952b1439b3df9] MSSQLDM: MSSQLDM: PowerProtect agent for Microsoft Applications version 19.14.0.26 is present on VM xxx.xxx.xxx.xxx (vm-##)
YYYY-MM-DD HH:MM:SS INFO: [a267c9eb8362b811;b45952b1439b3df9] MSSQLDM: MSSQLDM: MSSQLDM Agent latest available version is '19.14.0.26' (19.14.0.26): emcmsappagent-19.14.0.26.exe
YYYY-MM-DD HH:MM:SS INFO: [a267c9eb8362b811;b45952b1439b3df9] MSSQLDM: MSSQLDM: connect: Connected to vProxy Agent on VM xxx.xxx.xxx.xxx (vm-##).
YYYY-MM-DD HH:MM:SS INFO: [a267c9eb8362b811;b45952b1439b3df9] MSSQLDM: MSSQLDM: connect: Host agent lock released.
YYYY-MM-DD HH:MM:SS [a267c9eb8362b811;b45952b1439b3df9]0 msagentcon PowerProtect Data Manager info Full diagnostic logs can be found in the file 'C:\Program Files\DPSAPPS\MSAPPAGENT\logs\msagentcon_cent_20230726181507_a267c9eb8362b811_b45952b1439b3df9_debug.log'.
YYYY-MM-DD HH:MM:SS [a267c9eb8362b811;b45952b1439b3df9]107091 msagentcon PowerProtect Data Manager notice Command line: C:\Program Files\DPSAPPS\MSAPPAGENT\bin\msagentcon.exe configure -D 3 -I -
YYYY-MM-DD HH:MM:SS [a267c9eb8362b811;b45952b1439b3df9]86738 msagentcon PowerProtect Data Manager notice System Version: 6.2 Build 9200
YYYY-MM-DD HH:MM:SS [a267c9eb8362b811;b45952b1439b3df9]86741 msagentcon PowerProtect Data Manager notice Computer Name: MY-SQL-NAME User Name: MY-SQL-NAME\Administrator (Administrator)
YYYY-MM-DD HH:MM:SS [a267c9eb8362b811;b45952b1439b3df9]107092 msagentcon PowerProtect Data Manager notice Version information for C:\Program Files\DPSAPPS\MSAPPAGENT\bin\msagentcon.exe: Original file name: msagentcon.exe Version: 19.14.0.26.Build.26 Comments:
YYYY-MM-DD HH:MM:SS [a267c9eb8362b811;b45952b1439b3df9]151790 msagentcon PowerProtect Data Manager notice A lockbox path was not specified, falling back to C:\Program Files\DPSAPPS\common\lockbox.
YYYY-MM-DD HH:MM:SS [a267c9eb8362b811;b45952b1439b3df9]199128 msagentcon PowerProtect Data Manager notice Parsed VM instance ID is '6abdd35e-1eac-5a7d-803d-a81dd54e3a0d'.
YYYY-MM-DD HH:MM:SS [a267c9eb8362b811;b45952b1439b3df9]187076 msagentcon PowerProtect Data Manager notice Configure the certificate authorization for PowerProtect Data Manager server 'xxx.xxx.xxx.xxx'.
YYYY-MM-DD HH:MM:SS [a267c9eb8362b811;b45952b1439b3df9]203449 msagentcon PowerProtect Data Manager notice vmDataSourceID: '6abdd35e-1eac-5a7d-803d-a81dd54e3a0d'
YYYY-MM-DD HH:MM:SS [a267c9eb8362b811;b45952b1439b3df9]3 msagentcon PowerProtect Data Manager notice hostname to register with Power Protect Data Manager: 'xxx.xxx.xxx.xxx'
YYYY-MM-DD HH:MM:SS [a267c9eb8362b811;b45952b1439b3df9]203451 msagentcon PowerProtect Data Manager notice Executing the registration script, parameters are hostname and VM DataSource ID.
YYYY-MM-DD HH:MM:SS [a267c9eb8362b811;b45952b1439b3df9]181389 msagentcon PowerProtect Data Manager error Unable to execute discovery command, error: 'Unable to update persisted settings for PowerProtect Data Manager host 'xxx.xxx.xxx.xxx': Unable to log in to PowerProtect Data Manager host 'xxx.xxx.xxx.xxx'. Received the HTTP code 400 and response 'Invalid FQDN'.
', 'Unable to register PowerProtect Agent Service. SSL certificates are not present.'
YYYY-MM-DD HH:MM:SS [a267c9eb8362b811;b45952b1439b3df9]181395 msagentcon PowerProtect Data Manager error The operation terminated with an error; details are in the status output file. El servicio de agente de PowerProtect (MSAPPAGENT) se puso en depuración mediante la creación del .ddbmcon.debug en el directorio C:\Program Files\DPSAPPS\MSAPPAGENT\tmp\ en Microsoft SQL Server. Los archivos de salida de depuración ddbmcon.*.log en C:\Program Files\DPSAPPS\MSAPPAGENT\logs\ muestran lo siguiente:
YYYY-MM-DD HH:MM:SS ddbmcon: libdd_getSVs: Setting the system stable values. YYYY-MM-DD HH:MM:SS ddbmcon: libdd_lockbox_open: Lockbox could not be opened in the directory 'C:\Program Files\DPSAPPS\common\lockbox\agents.clb'. Error code: -11. YYYY-MM-DD HH:MM:SS ddbmcon: libdd_lockbox_destroy: Freeing the context and releasing the lockbox application.
Cause
Hay una corrupción en el agents.clb lockbox que impide que el servicio MSAPPAGENT actualice los archivos de certificado.
Resolution
Elimine el archivo existente agents.clb lockbox, por lo que se vuelve a crear un nuevo lockbox en Microsoft SQL Server.
- Detenga el servicio de agente de PowerProtect desde
services.msco el símbolo del sistema:
net stop agentservice
- Mueva el contenido de C:\Program Files\DPSAPPS\common\lockbox a otro directorio.
- Inicie el servicio de agente de PowerProtect desde
services.msco el símbolo del sistema:
net start agentservice
Article Properties
Article Number: 000216374
Article Type: Solution
Last Modified: 03 Dec 2025
Version: 3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.