MQSeries Trigger Monitor Service vs runmqtrm on Win2K

[embern]

We currently have set up all of the queues & processes for triggering on a Win2K machine with MQSeries vs 5.
If we run the trigger with runmqtrm... then the trigger works great with our executable. However, if we use the Trigger Monitor in MQServices, the trigger does not work.
We also tried to create a custom service, with the exact same runmqtrm... statement that worked in the cmd window. This also does not work.

Our executable was written in VB6. It works on its own and it works when the trigger monitor is started from the command line.

Has anyone else had this issue? How did you solve it? Do we need a fix? Is there something else we need to do?
Is there some way to have the trigger started when the queue manager starts other than an MQSeries Service?

Thank you,
Embern

 

[embern]

Here's an update.
For our early development, we're using the 60-day trial version for testing.
We moved everything to our licensed copy of MQSeries and the trigger monitor service worked fine.
We're still not sure why it doesn't work with the 60-day trial version.
If anyone can shed light on that, I would still appreciate it.
Thank you.
Embern