MOM 2005 Response Script Tracing

dszabo — Thu, 01 Mar 2007 13:22:21 GMT

I've been writing a MOM response script that stopped working at some point, so I had to debug or trace it. Of course, at the time I was able to check it, the problem already got solved. So, I decided to turn on tracing and give some time for the problem to re-occur.

The script was developed to write trace messages at different points using the ScriptContext.Echo(string) method, but I never tried this feature. I did a search on MSDN and found that I have to enable debugging on the *MOM AGENT* (my script runs on a remote agent box, so I have to do it there) in order to get these messages logged somewhere. The following article shows the registry keys: http://msdn2.microsoft.com/en-us/library/ms824564.aspx. Briefly, they are:

HKEY_LOCAL_MACHINE\SOFTWARE\Mission Critical Software\OnePoint\EnableActiveDebugging = 1
HKEY_LOCAL_MACHINE\SOFTWARE\Mission Critical Software\OnePoint\DebugEnabledScripts = <Your Response Script name>

Did that, restarted the MOM service on the agent box and found that a new log file created under C:\WINDOWS\Temp\Microsoft Operations Manager with a name of "AgentResponses-<Mgmt group name> MOM.log", containing the last trace result of my response script.

So far so good, but I want to let my script-friend here doing his job and I want MOM to log every run, so I could analyze it next week when I come back. Unfortunately, MOM doesn't provide this nice feature to you, so I had to write my own scheduled task that does it:

1. Created a batch script, called MomLogGatherer, with the following content (the current trace file is assigned to an existing file):

type "C:\WINDOWS\Temp\Microsoft Operations Manager\AgentResponses-<Mgmt group name> MOM.log" >> C:\dszabo_MS\MomLog\momlog.txt

2. Created a scheduled task to call the batch script in every 5 minutes (the response script in MOM is scheduled to run in every 5 mins)

I just have to take care to archive the file sometimes before it gets too big.

How .net stores dates/how to debug them

dszabo — Fri, 17 Nov 2006 01:38:00 GMT

I was debugging an application and had to check a DateTime variable’s actual value. I was expecting something like member variables holding year, month, day, hour, etc values on the object and it will be an easy one to debug, but that was not the case, so I had to find out how to check the actual date value of a DateTime variable and learn how dates are stored in the .net framework 2.0.

First of all, as you might already know, dumping out an object with SOS can be done with the !do (or !DumpObject) command. If you are not familiar with debugging .net, using WinDbg and using the SOS debugger extension, you can find a good starter at http://msdn.microsoft.com/msdnmag/issues/03/06/Bugslayer/default.aspx, you can check the reference of the SOS extension at http://msdn.microsoft.com/msdnmag/issues/03/06/Bugslayer/default.aspx, then if you are still interested, you'll find really good articles at Doug's (http://blogs.msdn.com/dougste) and Tess' (http://blogs.msdn.com/tess) blog. So, returning back to the subject, this is what you get when dumping out a DateTime variable:

0:000> !do 01481d74
Name: System.DateTime
MethodTable: 790ff4c4
EEClass: 790ff424
Size: 16(0x10) bytes
 (E:\Windows\assembly\GAC_32\mscorlib\2.0.0.0__b77a5c561934e089\mscorlib.dll)
Fields:
Field   Offset                 Type VT     Attr    Value Name
40000f4        4        System.UInt64  0 instance 630992916000000000 dateData
40000f0       30       System.Int32[]  0   shared   static DaysToMonth365
    >> Domain:Value  002401d8:01481cf4 <<
40000f1       34       System.Int32[]  0   shared   static DaysToMonth366
    >> Domain:Value  002401d8:01481d34 <<
40000f2       28      System.DateTime  1   shared   static MinValue
    >> Domain:Value  002401d8:01481cd4 <<
40000f3       2c      System.DateTime  1   shared   static MaxValue
    >> Domain:Value  002401d8:01481ce4 <<

The actual date value is stored in the UInt64 (long) member variable called dateData, which stores the ticks representing the date value. In my example, it is 630992916000000000. That's OK so far, but how can we get the date out from this? To convert it back without using your calculator or writing an expensive algorythm, you have to use the following DateTime constructor:

public DateTime(long ticks)

or the following static method on the DateTime class:

public static DateTime FromBinary(long dateData)

Code that does the job:

DateTime dateValue = new DateTime(630992916000000000);
Console.WriteLine(dateValue);

David Szabo's [MSFT] blog : debugging

MOM 2005 Response Script Tracing

How .net stores dates/how to debug them