DX Infrastructure Manager

Expand all | Collapse all

help with ntperf probe

  • 1.  help with ntperf probe

    Posted 11-15-2011 08:04 PM

    Needing any community help with the following:

     

    we are using MSMQ heavily in our environment, and currently need a way to monitor the queue size and alert.  We have two variants of MSMQ servers.  One being a x32 2003 server for our legacy queues, and our newer x64 2008 for most production.  we are able to use ntperf on the x32 server with no problems at all...the x64 server we havent had luck.  Been working with support, but they are leaning towards a problem with our MSMQs all together.  We have been running this way for well over a years with no issues, so i dont beleive its our queues.  When i click ctrl+P on the ntperf64 probe, and the probe utility comes up, when i select list_objects from the drop down...it doesnt even list MSMQ in the output list, which means i wouldnt even be able to add this as a profile.  log file for ntperf gets loaded with things like:

     

    Nov 14 14:17:28:842 ntperf64: *** Index out of range -1 (5049 items in internal list)
    Nov 14 14:17:28:842 ntperf64: *** Index out of range -1 (5049 items in internal list)
    Nov 14 14:17:28:842 ntperf64: *** Index out of range -1 (5049 items in internal list)
    Nov 14 14:17:28:842 ntperf64: *** Index out of range -1 (5049 items in internal list)

     

    has anyone else had any success with MSMQ monitoring  though ntperf, or shed some light on what could the issue be. 



  • 2.  Re: help with ntperf probe

    Posted 11-15-2011 08:24 PM

    Check out this thread, I think it explains what you're seeing:

     

    http://forum.nimsoft.com/t5/General/NTPerf-and-NotFound-messages/m-p/6365/highlight/true#M2986

     

    This thread is older but may have some options for you:

     

    http://forum.nimsoft.com/t5/General/MQ-Series-Probes/m-p/1384/highlight/true#M908

     

    Dustin



  • 3.  Re: help with ntperf probe

    Posted 11-16-2011 06:26 PM

    What happens when you try that callback on the ntperf probe rather than the ntperf64 probe? This might be a long shot, but perhaps that performance object is only available as a 32-bit object for some reason? If that were the case, you should be able to see it in the ntperf probe but not the ntperf64 probe.