MSMQ Triggers broken in Windows Server 2003

[TakedownCA]

I'm trying to migrate a homebrewed msmq triggers based application from Win2000 to Win2003, but I can't seem to make it work. At first I thought it was a problem with my program, but now it looks like nonfunctional triggers are at fault.

I've got a private test queue "A" with a trigger "B" that uses a rule "C". All C does is start a Test.exe file that pops up a message box so I know it ran. If I run Test.exe manually it works fine. I can send a msmq message to queue A just fine. But the trigger never kicks in.

I've tried using rule C without any conditions and with a "Label contains" condition with no success. Is there something I'm missing that's new in Windows Server 2003?

 

[spyordie007]

I dont deal much with MSMQ, however I do know that in MSMQ 3.0 (xp and 2003 server) triggers are a component of MSMQ as opposed to an add-in module like it was in 2.0 and earlier (2000 and below). See the MSMQ 3.0 Feature List. I dont know if/what effect this has on how MSMQ handles the triggers but that is probably where I would start looking.

Good luck,

 

[TakedownCA]

Triggers are included in 2003, but they are not part of MSMQ. It's still a separate program, but now you can install it from the Add/Remove Windows Components wizard.