Loading...
Loading...
The vCenter Asset Source is configured with an Active Directory (AD) Domain account. The discovery fails to complete with the error code ADS0006 . The discovery job details show: Discovery job failed before discovery is started Discovery Job Error: 400 : "{"code":400,"reason":"Cannot complete login due to an incorrect user name or password.","remediation":null,"timestamp":1684956496435,"path":"/api/v2/vmwareservice/vcenters/validate-connection","extendedInfo":null}" The vCenter Asset Discovery System Job output shows: vmware-service.log: YYYY-MM-DD HH:MM:SS ERROR [] [https-jsse-nio-0.0.0.0-8469-exec-4] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:bd365dbfcdca07fd;JOB_ID:a37ad63dcacbc13f][] [c.e.b.v.a.f.RestErrorHandler.logErrorAndDebug(201)] - Cannot complete login due to an incorrect user name or password. vmware-service.log: YYYY-MM-DD HH:MM:SS ERROR [] [https-jsse-nio-0.0.0.0-8469-exec-4] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:bd365dbfcdca07fd;JOB_ID:a37ad63dcacbc13f][] [c.e.b.v.a.f.RestErrorHandler.handleError(173)] - Cannot complete login due to an incorrect user name or password. vmware-service-rest-call.log: YYYY-MM-DD HH:MM:SS INFO [https-jsse-nio-0.0.0.0-8469-exec-4] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:bd365dbfcdca07fd;JOB_ID:a37ad63dcacbc13f][] [c.e.b.t.api.RestLogFilter.doFilter(56)] - Exit RESTful Msg - Status: 400 , ContentType: application/json vmdm-discovery.log: YYYY-MM-DD HH:MM:SS ERROR [https-jsse-nio-0.0.0.0-8447-exec-8] [][][][TRACE_ID:bd365dbfcdca07fd;JOB_ID:a37ad63dcacbc13f][] [c.e.b.v.d.v.s.VmdmDiscoveryService.start(154)] - 400 : "{"code":400,"reason":"Cannot complete login due to an incorrect user name or password.","remediation":null,"timestamp":1684956496435,"path":"/api/v2/vmwareservice/vcenters/validate-connection","extendedInfo":null}" vmdm-discovery.log: YYYY-MM-DD HH:MM:SS INFO [https-jsse-nio-0.0.0.0-8447-exec-8] [][][][TRACE_ID:bd365dbfcdca07fd;JOB_ID:a37ad63dcacbc13f][] [c.e.b.v.d.a.VmdmDiscoveryAlertService.addAlertToMap(77)] - Alert was generated but not yet thrown for inventorySource: 7bf3dc75-d230-54a0-ad7a-4e7be020f1a8 during Full discovery. Eemi message ID is: ADS0006 and alert message is: Failed to connect. vmdm.log: YYYY-MM-DD HH:MM:SS INFO [https-jsse-nio-0.0.0.0-8447-exec-8] [][][][TRACE_ID:bd365dbfcdca07fd;JOB_ID:a37ad63dcacbc13f][] [c.e.b.v.a.ActivityBuilder.complete(617)] - Completed activity. Activity resource id 45c4299f-2eff-41b1-a949-e4aaf28969a8 State COMPLETED Progress null Stats:Result: { "status" : "FAILED", "summaries" : [ "Discovery job failed before discovery is started", "Discovery Job Error: 400 : \"{\"code\":400,\"reason\":\"Cannot complete login due to an incorrect user name or password.\",\"remediation\":null,\"timestamp\":1684956496435,\"path\":\"/api/v2/vmwareservice/vcenters/validate-connection\",\"extendedInfo\":null}\"." ], "error" : { "code" : null, "reason" : null, "detailedDescription" : null, "remediation" : null, "extendedReason" : "Discovery Job Error: 400 : \"{\"code\":400,\"reason\":\"Cannot complete login due to an incorrect user name or password.\",\"remediation\":null,\"timestamp\":1684956496435,\"path\":\"/api/v2/vmwareservice/vcenters/validate-connection\",\"extendedInfo\":null}\".", "messageID" : "ADS0006", "arguments" : [ { "name" : "discoveryType", "value" : "Full" }, { "name" : "vCenterName", "value" : "efvvctr-ho-01p (Hillsboro VxRail vCenter)" } ] }, "bytesTransferred" : null } Steps: vmdm-discovery.log: YYYY-MM-DD HH:MM:SS ERROR [https-jsse-nio-0.0.0.0-8447-exec-8] [][][][TRACE_ID:bd365dbfcdca07fd;JOB_ID:a37ad63dcacbc13f][] [c.e.b.v.d.c.VmdmDiscoveryController.postDiscovery_aroundBody0(82)] - VMDM Discovery Failed. Discovery Job Error: 400 : "{"code":400,"reason":"Cannot complete login due to an incorrect user name or password.","remediation":null,"timestamp":1684956496435,"path":"/api/v2/vmwareservice/vcenters/validate-connection","extendedInfo":null}".. com.emc.brs.vmdm.discovery.vm_discovery.exceptions.VmdmDiscoveryException: Discovery Job Error: 400 : "{"code":400,"reason":"Cannot complete login due to an incorrect user name or password.","remediation":null,"timestamp":1684956496435,"path":"/api/v2/vmwareservice/vcenters/validate-connection","extendedInfo":null}". at com.emc.brs.vmdm.discovery.vm_discovery.services.VmdmDiscoveryService.start(VmdmDiscoveryService.java:155) at com.emc.brs.vmdm.discovery.controller.VmdmDiscoveryController.postDiscovery_aroundBody0(VmdmDiscoveryController.java:79) ... Caused by: org.springframework.web.client.HttpClientErrorException$BadRequest: 400 : "{"code":400,"reason":"Cannot complete login due to an incorrect user name or password.","remediation":null,"timestamp":1684956496435,"path":"/api/v2/vmwareservice/vcenters/validate-connection","extendedInfo":null}" at org.springframework.web.client.HttpClientErrorException.create(HttpClientErrorException.java:101) at org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:168) ... vmdm.log: YYYY-MM-DD HH:MM:SS INFO [https-jsse-nio-0.0.0.0-8447-exec-8] [][][][TRACE_ID:bd365dbfcdca07fd;JOB_ID:a37ad63dcacbc13f][] [c.e.b.v.f.RestLogFilter.doFilter(58)] - Exit RESTful Msg - POST https://localhost:8447/api/v2/vmdm/discoveries, Status: 500, ContentType: application/json The vSphere Support Bundle vCenter vpxd*.log shows an authentication failure for the configured AD account configured for the vCenter Asset Discovery: $ grep -ri 'my-aduser-name' vpxd*.log | grep 'YYYY-MM-DD HH:MM:SS' ./vpxd-1119.log:YYYY-MM-DD HH:MM:SS error vpxd[03714] [Originator@6876 sub=User opID=47d66a7f] Failed to authenticate user my-aduser-name@my-domainame.com ./vpxd-1119.log:YYYY-MM-DD HH:MM:SS error vpxd[04245] [Originator@6876 sub=User opID=14a99c5b] Failed to authenticate user my-aduser-nam Searching for the operation identifier (opID), in the vSphere Support Bundle vCenter vpxd*.log , shows an exception while acquiring the token: $ grep -ri 'opID=14a99c5b' vpxd*.log ./vpxd-1119.log:YYYY-MM-DD HH:MM:SS info vpxd[03743] [Originator@6876 sub=vpxLro opID=14a99c5b] [VpxLRO] -- BEGIN lro-67645031 -- SessionManager -- vim.SessionManager.login -- 52832f9e-3358-7e03-5998-019cd1b050a0 ./vpxd-1119.log:YYYY-MM-DD HH:MM:SS error vpxd[03743] [Originator@6876 sub=UserDirectorySso opID=14a99c5b] AcquireToken exception: N9SsoClient27InvalidCredentialsExceptionE(Authentication failed: Invalid credentials) ./vpxd-1119.log:YYYY-MM-DD HH:MM:SS error vpxd[03743] [Originator@6876 sub=User opID=14a99c5b] Failed to authenticate user <cable\my-aduser-name> ./vpxd-1119.log:YYYY-MM-DD HH:MM:SS warning vpxd[03743] [Originator@6876 sub=Vmomi opID=14a99c5b] VMOMI activation LRO failed; <<52832f9e-3358-7e03-5998-019cd1b050a0, <TCP '127.0.0.1 : 8085'>, <TCP '127.0.0.1 : 51302'>>, SessionManager, vim.SessionManager.login>, N3Vim5Fault12InvalidLogin9ExceptionE(Fault cause: vim.fault.InvalidLogin ./vpxd-1119.log:YYYY-MM-DD HH:MM:SS info vpxd[03743] [Originator@6876 sub=vpxLro opID=14a99c5b] [VpxLRO] -- FINISH lro-67645031 ./vpxd-1119.log:YYYY-MM-DD HH:MM:SS info vpxd[03743] [Originator@6876 sub=Default opID=14a99c5b] [VpxLRO] -- ERROR lro-67645031 -- SessionManager -- vim.SessionManager.login: vim.fault.InvalidLogin: If the vCenter Asset credentials are changed from an AD account to a local vSphere account, the vCenter asset discovery completes as expected.
The N9SsoClient27InvalidCredentialsExceptionE exception can be generated when there are issues between the vCenter Identity Manager and the local domain controller.
The PowerProtect components should be configured with the same Network Time Protocol (NTP) servers as the vSphere components (vCenter and ESXi hosts). Review the remainder of the causes in the Broadcom knowledge Article https://knowledge.broadcom.com/external/article?legacyId=2147174 If required, engage Broadcom Support to better understand the exception when acquiring the token for the Active Directory user.
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.