You receive a "WBEM_E_FAILED" error message when you try to run a query with a subselect query in the SMS Administrator console in SMS 2003 (886148)


The information in this article applies to:

  • Microsoft Systems Management Server 2003

SYMPTOMS

When you try to run a query with a subselect query in the SMS Administrator console, you may receive an error message that is similar to the following:
The following error was reported: WBEM_E_FAILED Running the query: select * from SMS_R_System inner join SMS_G_System_PROCESSOR as ProcessorName on ProcessorName.ResourceID = SMS_R_System.ResourceId where ProcessorName.Name in (select SMS_R_System.Name, SMS_R_System.SMSAssignedSites, SMS_R_System.IPAddresses, SMS_R_System.IPSubnets, SMS_R_System.OperatingSystemNameandVersion, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.LastLogonUserDomain, SMS_R_System.LastLogonUserName, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.NetbiosName, ProcessorName on ProcessorName on ProcessorName.ResourceID = SMS_R_System.ResourceId)

CAUSE

The problem occurs when the subselect query returns more than one column. The subselect query should return only one column. The data in this column should have the same data type as the field before the IN clause of the subselect query.

WORKAROUND

To work around this problem, modify the subselect query to return only one column. To do this, follow these steps.

Note The following steps are example steps. Modify your subselect query to fit your situation.
  1. Open the SMS Administrator console.
  2. Double-click Site Database (Site_code-Site_name).
  3. Click Queries, right-click All Systems, click All Tasks, and then click Properties.
  4. Click Edit Query Statement.
  5. On the General tab, click the button that has star icon to add a new property.
  6. Click Select.
  7. In the Attribute class list, click Processor.
  8. In the Alias as box, type ProcessorName.
  9. In the Attribute list, click Name, and then click OK.
  10. In the Sort list, click <Unsorted>, and then click OK three times.
  11. Right-click Queries, click New, and then click Query.
  12. In the Name box, type My Query.
  13. Click Edit Query Statement, and then click the Criteria tab.
  14. On the Criteria bar, click the button that has a star icon to create a new criterion.
  15. In the Criterion type list, click Subselected values.
  16. Click Select.
  17. In the Attribute class list, click Processor.
  18. In the Alias as box, type ProcessorName.
  19. In the Attribute list, click Name, and then click OK.
  20. In the Operator list, click is in.
  21. Click Browse.
  22. Click All Systems, and then remove all the columns until only the ProcessorName.Name column remains in the Subselect box.

    For example, the modified subselect query may look similar to the following query:

    select ProcessorName.Name from SMS_R_System inner join SMS_G_System_PROCESSOR as ProcessorName on ProcessorName.ResourceID = SMS_R_System. ResourceID

  23. Click OK three times.
  24. Right-click My Query, and then click Run Query.
The result window displays a result that includes the ProcessorName column.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

To reproduce this problem, follow steps 1 through 20 in the "Workaround" section. However, do not modify the subselect query as instructed in step 21. Instead, click OK four times, and go directly to step 23. When you complete step 23, you receive an error message that is similar to the message that is mentioned in the "Symptoms" section.
Modification Type:MinorLast Reviewed:6/14/2005
Keywords:kbtshoot kbSMS2003spfix kbSMS2003bug kbprb KB886148 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.