We have upgraded our installation to v8 (and it is great!). We have about 400 custom queue depth sensors using a small powershell script to monitor depths on our expansive number of MSMQ queues. I saw that you had a queue depth monitor now so I wanted to try it out on some new queues we need. However, no matter how I define the queue name, I have tried using just the queue name "eventexpansion_error" and the fully qualified name "jtcstgquexis01\eventexpansion_error" but all I get is the error message - " 0:Queuename not found on specified machine" back. I even downloaded the PTG listqueue utility and it pulled the queues correctly from the server.
Based on how the sensor parameters are defined, I am guessing it would have to have the fully qualifed name because I don't know how else it would work correctly though I have the sensor in a device with the queue server name. Any ideas on this. I really want to be able to use this as the custom sensor is more involved to setup.
Richard Finnigan
Article Comments
We have MSMQ installed and running on those servers that are hosting the probes (and it is running on our actual MSMQ servers as well obviously). If it was not, then our existing sensors using PowerShell scripts would not function as they still require MSMQ. This is quite vexing.
Sep, 2011 - Permalink
Seems to me as a rights issue.
Can you please try running the PTF listqueue utility from your PRTG server (probe) and explicitly supply credentials in the utility. If this works, use the same credentials with the sensor.
Sep, 2011 - Permalink
Hello,
to get the MSMQ sensor to work the Message Queuing Windows Service (mqsvc.exe) must be started on the computer running the PRTG Probe as well as on the target system and then the normal queue name should work (the fully qualified should not be necessary).
Sep, 2011 - Permalink