Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
The purpose of this KB is to understand the groups the SRM & VR solution users must be a part of.dr.log YYYY-MM-DDTHH:MM:SS.527+05:30 warning vmware-dr[04864] [SRM@6876 sub=LocalHms] Failed to connect: --> (vim.fault.InvalidLogin) {--> faultCause = (vmodl.MethodFault) null,--> faultMessage = <unset>--> msg = "Received SOAP response fault from [<cs p:00000055d2bffea0, TCP:10.14.124.206:8043>]: login--> Cannot complete login due to an incorrect user name or password."--> }--> [context]zKq7AVMEAAgAAFaTwQAMdm13YXJlLWRyAAAqPwJ2bWFjb3JlLmRsbAABtM4CdmltLXR5cGVzLmRsbAAB/X8yAqXCBXZtb21pLmRsbAACz+AFAOt+GwBLjhsAyYghA39PAk1TVkNSMTIwLmRsbAADJlECBNITAEtFUk5FTDMyLkRMTAAF9FQBbnRkbGwuZGxsAA==[/context]--> [backtrace begin] product: VMware vCenter Site Recovery Manager, version: 8.1.2, build: build-12686166, tag: vmware-dr, cpu: x86_64, os: windows, buildType: release--> backtrace[03] vmacore.dll[0x00023F2A]--> backtrace[04] vim-types.dll[0x0002CEB4]--> backtrace[05] vim-types.dll[0x00327FFD]--> backtrace[06] vmomi.dll[0x0005C2A5]--> backtrace[07] vmomi.dll[0x0005E0CF]--> backtrace[08] vmacore.dll[0x001B7EEB]--> backtrace[09] vmacore.dll[0x001B8E4B]--> backtrace[10] vmacore.dll[0x002188C9]--> backtrace[11] MSVCR120.dll[0x00024F7F]--> backtrace[12] MSVCR120.dll[0x00025126]--> backtrace[13] KERNEL32.DLL[0x000013D2]--> backtrace[14] ntdll.dll[0x000154F4]--> [backtrace end] /opt/vmware/hms/logs/hms.log YYYY-MM-DDTHH:MM:SS.246 ERROR com.vmware.vim.sso.client.impl.SoapBindingImpl [tcweb-11] (..client.impl.SoapBindingImpl) operationID=lro-2-71e1a81-37ab-HMS-201468 | SOAP fault com.sun.xml.internal.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: Access not authorized! Please see the server log to find more detail regarding exact cause of the failure.YYYY-MM-DDTHH:MM:SS.247 ERROR jvsl.security.authentication.sm [tcweb-11](..security.authentication.SessionManagerInternal) operationID=lro-2-71e1a81-37ab-HMS-201468 | Invalid token com.vmware.vim.sso.client.exception.InvalidTokenRequestException: Request is invalid: ns0:InvalidRequest: Access not authorized!YYYY-MM-DDTHH:MM:SS.248 INFO hms.i18n.class com.vmware.hms.response.filter.I18nActivationResponseFilter [tcweb-11] (..response.filter.I18nActivationResponseFilter) operationID=lro-2-71e1a81-37ab-HMS-201468 | The localized message is: Cannot complete login due to an incorrect username or password.
The issue is identified to be caused when one or more SolutionUsers get removed from the groups they should be a part off.Following are the 4 SRM & VR SolutionUsers that one would have in their environment. SRM-SRM-remote-h5-dr-com.vmware.vr- The following are the groups these SolutionUsers should be a part of: SolutionUsers SRM-SRM-remote-h5-dr-com.vmware.vr- ActAsUsers CN=h5-dr-com.vmware.vr- Administrators SRM- LicenseService.Administrators SRM- SRM Remote Users SRM-remote- HmsRemoteUsers SRM-remote- To resolve this issue: Login to the vCenter Server using vSphere Flex client.Navigate to Administration -> Single Sign-On -> Users and Groups -> Groups -> Add Group members.Manually add the SolutionUsers to these groups.Re-register SRM/VR.