Microsoft KB Archive/307321

= Setting the SourceComputer Property in MOM Performance Data Scripts =

Article ID: 307321

Article Last Modified on 11/23/2006

-

APPLIES TO


 * Microsoft Operations Manager 2000 Service Pack 1

-



This article was previously published under Q307321



SYMPTOMS
When you set the SourceComputer property in Microsoft Operations Manager (MOM) 2000 Performance Data scripts, the CounterName property may be overwritten with the same data that is assigned to the SourceComputer property.



WORKAROUND
In the following script, the SourceComputer property is set last, and this causes the CounterName property to be overwritten with the computer name (strSrcComputer). Sub CreatePerformanceData(ByVal strObjectName,  _                          ByVal strCounterName,  _                          ByVal strInstanceName, _                          ByVal dblSampleValue,  _                          strSrcComputer) Dim oPerfData Set oPerfData = ScriptContext.CreatePerfData oPerfData.ObjectName  = strObjectName oPerfData.CounterName = strCounterName oPerfData.InstanceName = strInstanceName oPerfData.Value       = dblSampleValue If strSrcComputer <> &quot;&quot; Then oPerfData.SourceComputer = strSrcComputer End If  ScriptContext.Submit(oPerfData) Set oPerfData = Nothing End Sub To prevent this problem, modify the preceding script to set the SourceComputer property first: Sub CreatePerformanceData2(ByVal strObjectName,  _                           ByVal strCounterName,  _                           ByVal strInstanceName, _                           ByVal dblSampleValue,  _                           strSrcComputer) Dim oPerfData Set oPerfData = ScriptContext.CreatePerfData If strSrcComputer <> &quot;&quot; Then oPerfData.SourceComputer = strSrcComputer End If  oPerfData.ObjectName   = strObjectName oPerfData.CounterName = strCounterName oPerfData.InstanceName = strInstanceName oPerfData.Value       = dblSampleValue ScriptContext.Submit(oPerfData) Set oPerfData = Nothing End Sub Microsoft provides programming examples for illustration only, without warranty either expressed or implied, including, but not limited to, the implied warranties of merchantability and/or fitness for a particular purpose. This article assumes that you are familiar with the programming language being demonstrated and the tools used to create and debug procedures. Microsoft support professionals can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific needs. If you have limited programming experience, you may want to contact a Microsoft Certified Partner or the Microsoft fee-based consulting line at (800) 936-5200. For more information about Microsoft Certified Partners, please visit the following Microsoft Web site:

https://partner.microsoft.com/global/30000104

For more information about the support options that are available and about how to contact Microsoft, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Keywords: kbenv kbprb KB307321

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.