Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Cannot add WMI node - Test failed

Cannot add WMI node - Test failed

Created by Zoltán Jalsovszky, last modified by MindTouch on Jun 23, 2016

Views: 3,410 Votes: 2 Revisions: 6

Overview

You are trying to add a Windows machine using WMI polling method. When you click on Test - you receive a Test failed error message. You are sure that you are using the correct username/password and when you test the connection using wbemtest.exe, it is successful.

Environment

  • All SAM versions
  • All NPM versions

Cause 

If you are using a domain account, a missing domain name can cause the test to fail.

Resolution

  1. Edit the credentials that you are trying to use (Settings > Manage Windows Credentials).
  2. Enter the username in the DOMAIN\username format.

 

Last modified

Tags

Classifications

Public