PowerProtect: El registro del agente falla con el error ABV0025 cuando el FQDN del host contiene guion bajo.
Summary: El agente de PowerProtect Data Manager no se puede registrar debido a un problema de firma de certificado.
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 registro del agente de PowerProtect Data Manager (PPDM) falla con el error "ABV0025: El motor de VM Direct no puede configurar la protección para la máquina virtual 'hostname.company_name.com' en vCenter 'xxxxxxxx.xxxxxxx.xxx'".
Los registros del servicio de agente tendrían mensajes de error similares a los siguientes:
xxxx-xx-xxTxx:xx:xx.xxxZ WARN [] [vpe-thread-13] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:xxxxxxxxxxxxxxx;JOB_ID:xxxxxxxxxxxxxxx][] [c.e.b.v.v.a.VPEConfigureOp.logErrorStack(64)] - Unable to configure hostname.domain_name.com
com.emc.brs.vmdm.error.InternalServerErrorException: Unable to perform MSSQLDM Agent operation 'configure' on VM xxx.xxx.xxx.xxx (vm-1137): 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. error: 'Timeout: Register was not performed by ADM in 180 seconds'
at com.emc.brs.vmdm.vpe.util.VPEProtectionUtils.setupAppAgent(VPEProtectionUtils.java:489)
at com.emc.brs.vmdm.vpe.util.VPEProtectionUtils.configureAppAgent(VPEProtectionUtils.java:388)
at com.emc.brs.vmdm.vpe.actions.VPEConfigureOp.createConfig(VPEConfigureOp.java:158)
at com.emc.brs.vmdm.vpe.actions.VPEConfigureOp.execute(VPEConfigureOp.java:100)
at com.emc.brs.vmdm.vpe.service.VPEActionDispatcher.execute(VPEActionDispatcher.java:406)
at com.emc.brs.vmdm.vpe.service.VPEActionDispatcher.lambda$executeOp$1(VPEActionDispatcher.java:360)
at com.emc.brs.vmdm.vpe.util.ResourceUtils$JobExecutorImpl.lambda$createWorkflowTask$0(ResourceUtils.java:177)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:840)
xxxx-xx-xxTxx:xx:xx.xxxZ ERROR [] [vpe-thread-13] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:xxxxxxxxxxxxxxx;JOB_ID:xxxxxxxxxxxxxxx][] [c.e.b.v.v.a.VPEConfigureOp.buildWorkflowException(362)] - Unable to create configuration -- Unable to perform MSSQLDM Agent operation 'configure' on VM xxx.xxx.xxx.xxx (vm-1137): 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. error: 'Timeout: Register was not performed by ADM in 180 seconds'
Parameters: {
"asset" : "hostname.domain_name.com",
"taskId" : "7d665915-b1c2-4295-b9ed-75791cccf53a",
"vcenter" : "xxxxxxxx.xxxxxxx.xxx"
}
Result: {
"status" : "Failure",
"error" : "Unable to perform MSSQLDM Agent operation 'configure' on VM xxx.xxx.xxx.xxx (vm-1137): 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'.\n\nUnable to register PowerProtect Agent Service. error: 'Timeout: Register was not performed by ADM in 180 seconds'"
}
En el servidor de PowerProtect Data Manager, los registros del servicio adm tendrían entradas similares a las siguientes:
HTTP: 400: Bad Request: "{\"Code\"400,\"reason\":\"Invalid FQDN\",\"remediation\":\"Please provide valid FQDN.\"}"
Failed to signing the CSR for FQDNs= [hostname.domain_name.com]
Failed to generate tls certs, aborting agent registration for hostname.domain_name.com
Cause
El nombre de dominio calificado (FQDN) para el host del cliente contiene un guion bajo. El guion bajo no se permite en el nombre de dominio calificado para las solicitudes de firma de certificado.
Resolution
El producto funciona según el diseño.
La firma y emisión de certificados para un nombre de dominio con guion bajo va en contra de las prácticas de seguridad.
La firma y emisión de certificados para un nombre de dominio con guion bajo va en contra de las prácticas de seguridad.
Affected Products
PowerProtect Data Manager Appliance, PowerProtect Data Manager, PowerProtect Data Manager Essentials, PowerProtect Data Manager Software, PowerProtect DM5500Article Properties
Article Number: 000227247
Article Type: Solution
Last Modified: 02 Sept 2025
Version: 3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.