Microsoft KB Archive/300281

= &quot;(Null)&quot; Appears Instead of the Script Name in the History of a Script-Generated Alert =

Article ID: 300281

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Operations Manager 2000 Service Pack 1

-



This article was previously published under Q300281



SYMPTOMS
When you view the history of an alert that is generated when a script runs (for example, for a timed event), you may see the text &quot;(null)&quot; instead of the script name. The properties of the alert display a history that is similar to the following statements:

Started executing script (null) (ID {4DAD34E5-281E-48C8-813F-4EAF4E30641D})

12/28/2000 12:10:29
Finished running script (null) (ID {4DAD34E5-281E-48C8-813F-4EAF4E30641D}). Exit code: The operation completed successfully.



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



MORE INFORMATION
To list the name of the script, based on its GUID, run the following query in Microsoft SQL Server Query Analyzer:

SELECT * FROM Script WHERE idScript='4DAD34E5-281E-48C8-813F-4EAF4E30641D'

Make sure that you point to the OnePoint database, and substitute the GUID from the alert's history. The name of the script is stored in the Name column of the Script table.

Keywords: kbbug kbenv kbpending KB300281

-

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

© Microsoft Corporation. All rights reserved.