Solved

Problem adding computers to group

Posted on 2008-06-11
1
269 Views
Last Modified: 2008-06-16
I have created some groups, and then wanted to add some servers to these groups. Most of them I had no problem adding, but some groups I get this error:

I dont really know what is causing this.

For some groups I tried renaming them, and suddenly I could add the servers, but for others this solution doesnt work
Note:  The following information was gathered when the operation was attempted.  The information may appear cryptic but provides context for the error.  The application will continue to run.
 
: Verification failed with [1] errors:
-------------------------------------------------------
Error 1:
: Failed to verify Discovery [UINameSpace140e4aac3df244f4ba437150a3d5b649.Group.DiscoveryRule]
Failed to verify referenced module : ID=GroupPopulationDataSourceInvalid configuration specified for Module [GroupPopulationDataSource]Incorrect expression : '$MPElement[Name="System.Mom.BackwardCompatibility.Library!System.Mom.BackwardCompatibility.Computer"]' specified. Unable to resolve this expression. Please check this expression for errors. (Hints:  Check for correct character casing (upper case/lower case), mismatched "$" signs, double quotes("), square brackets "[" or "]" ). Here is a sample expression: $MPElement[Name="Windows!Microsoft.Windows.Computer"]/NetworkName$
-------------------------------------------------------
 
Failed to verify Discovery [UINameSpace140e4aac3df244f4ba437150a3d5b649.Group.DiscoveryRule]Failed to verify referenced module : ID=GroupPopulationDataSourceInvalid configuration specified for Module [GroupPopulationDataSource]Incorrect expression : '$MPElement[Name="System.Mom.BackwardCompatibility.Library!System.Mom.BackwardCompatibility.Computer"]' specified. Unable to resolve this expression. Please check this expression for errors. (Hints:  Check for correct character casing (upper case/lower case), mismatched "$" signs, double quotes("), square brackets "[" or "]" ). Here is a sample expression: $MPElement[Name="Windows!Microsoft.Windows.Computer"]/NetworkName$
: Failed to verify Discovery [UINameSpace140e4aac3df244f4ba437150a3d5b649.Group.DiscoveryRule]
Failed to verify referenced module : ID=GroupPopulationDataSourceInvalid configuration specified for Module [GroupPopulationDataSource]Incorrect expression : '$MPElement[Name="System.Mom.BackwardCompatibility.Library!System.Mom.BackwardCompatibility.Computer"]' specified. Unable to resolve this expression. Please check this expression for errors. (Hints:  Check for correct character casing (upper case/lower case), mismatched "$" signs, double quotes("), square brackets "[" or "]" ). Here is a sample expression: $MPElement[Name="Windows!Microsoft.Windows.Computer"]/NetworkName$
: Failed to verify referenced module : ID=GroupPopulationDataSource
Invalid configuration specified for Module [GroupPopulationDataSource]Incorrect expression : '$MPElement[Name="System.Mom.BackwardCompatibility.Library!System.Mom.BackwardCompatibility.Computer"]' specified. Unable to resolve this expression. Please check this expression for errors. (Hints:  Check for correct character casing (upper case/lower case), mismatched "$" signs, double quotes("), square brackets "[" or "]" ). Here is a sample expression: $MPElement[Name="Windows!Microsoft.Windows.Computer"]/NetworkName$
: Invalid configuration specified for Module [GroupPopulationDataSource]
Incorrect expression : '$MPElement[Name="System.Mom.BackwardCompatibility.Library!System.Mom.BackwardCompatibility.Computer"]' specified. Unable to resolve this expression. Please check this expression for errors. (Hints:  Check for correct character casing (upper case/lower case), mismatched "$" signs, double quotes("), square brackets "[" or "]" ). Here is a sample expression: $MPElement[Name="Windows!Microsoft.Windows.Computer"]/NetworkName$
: Incorrect expression : '$MPElement[Name="System.Mom.BackwardCompatibility.Library!System.Mom.BackwardCompatibility.Computer"]' specified. Unable to resolve this expression. Please check this expression for errors. (Hints:  Check for correct character casing (upper case/lower case), mismatched "$" signs, double quotes("), square brackets "[" or "]" ). Here is a sample expression: $MPElement[Name="Windows!Microsoft.Windows.Computer"]/NetworkName$

Open in new window

0
Comment
Question by:mhjortby
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 5

Accepted Solution

by:
madhusk earned 500 total points
ID: 21759946
Does the account used for discovery have appropriate permissions on the target computer?


Open a command window with the "Run As" option using the account used for discovery, normally this is the MOM server action account.  
Use the command "net view ComputerName to verify that the account can connect using the API NetworkStationGetInfo.  This command may return the result, "There are no entries in the list."  This simply means that, the machine does not have any publicly visible shares.  
If the result is "Access denied.", then the account used does not have permission to contact the machine.
If the result is The command completed successfully. then the computer is properly configured for discovery.
0

Featured Post

Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Scenerio: You have a server running Server 2003 and have applied a retail pack of Terminal Server Licenses.  You want to change servers or your server has crashed and you need to reapply the Terminal Server Licenses. When you enter the 16-digit lic…
Setting up a Microsoft WSUS update system is free relatively speaking if you have hard disk space and processor capacity.   However, WSUS can be a blessing and a curse. For example, there is nothing worse than approving updates and they just have…
Nobody understands Phishing better than an anti-spam company. That’s why we are providing Phishing Awareness Training to our customers. According to a report by Verizon, only 3% of targeted users report malicious emails to management. With compan…
The Email Laundry PDF encryption service allows companies to send confidential encrypted  emails to anybody. The PDF document can also contain attachments that are embedded in the encrypted PDF. The password is randomly generated by The Email Laundr…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question