• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

MSMQ Triggers broken in Windows Server 2003

TakedownCA

Senior member
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?
 
Back
Top