PowerProtect: Agentregistratie mislukt met fout ABV0025 wanneer FQDN voor de host een underscore bevat.

Summary: PowerProtect Data Manager agent kan niet worden geregistreerd vanwege een probleem met het ondertekenen van certificaten.

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.
Check out other resources

Symptoms

PowerProtect Data Manager (PPDM)-agentregistratie mislukt met fout "ABV0025: VM Direct Engine kan bescherming voor de virtuele machine 'hostname.company_name.com' op vCenter 'xxxxxxxx.xxxxxxx.xxx' niet configureren."


Servicelogboeken van agenten bevatten foutmeldingen die vergelijkbaar zijn met de volgende:

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'"
}


Op de PowerProtect Data Manager-server bevatten adm-servicelogboeken vermeldingen die vergelijkbaar zijn met de volgende:

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

De volledig gekwalificeerde domeinnaam (FQDN) van de clienthost bevat een underscore. Underscore is niet toegestaan in de volledig gekwalificeerde domeinnaam voor certificaatondertekeningsverzoeken.

Resolution

Het product werkt volgens het ontwerp.
Het ondertekenen en uitgeven van certificaten voor een domeinnaam met een onderstrepingsteken is in strijd met beveiligingspraktijken.

Affected Products

PowerProtect Data Manager Appliance, PowerProtect Data Manager, PowerProtect Data Manager Essentials, PowerProtect Data Manager Software, PowerProtect DM5500
Article 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.