<h2>SCOM Connector fails to pull the metrics due to the error - "Login failed for user 'domain\username'. ClientConnectionId:xxxx-xxxx-xxxx</h2><br/><div style="overflow-x:auto"><article><div ><h3 >Issue </h3><section><ul style="list-style-position: inside;"><li>The credentials used to connect to the SCOM Database have the required privileges.</li><li>Testing the SCOM Connector fails with the error - "Login failed for user 'domain\username'. ClientConnectionId:xxxx-xxxx-xxxx.</li></ul></section></div><div ><h3 >Release</h3><section><ul style="list-style-position: inside;"><li>Instance enabled with Event Management plugin.</li></ul></section></div><div ><h3 >Cause</h3><section><ul style="list-style-position: inside;"><li>Mid server service was not updated with the "Logon as user" with the Windows domain credentials having read access to the SCOM database<br /></li></ul></section></div><div ><h3 >Resolution</h3><section><ul style="list-style-position: inside;"><li>When Metric Collection is selected and the Database login with Windows authentication option is also selected.</li><li>Ensure the "Logon as the user" for the mid server service is updated with Windows domain credentials having read access to the SCOM database.</li><li> <ol id="ConfigureSCOMConnectorInstance__ol_xmf_bvd_lx" style="list-style-position: inside;"><li>In the local services, right-click the MID Server service and select Properties.</li><li>In the Log On tab, ensure that This account is selected with the details of the user in the Windows domain having read access to the SCOM database.<br /><br /></li></ol> </li><li>Test the Connector, the metric collection would be successful.<br /><br /><br /></li></ul></section></div></article></div>