Background: I'm an MSMQ novice and am having to support some legacy VB6 windows services; one on MachineA which sends SQL insert statements to a transactional public queue on MachineB, and another service on MachineB which consumes the messages.
We had one queue set up and working just fine, then I was asked to create another queue to handle different messages. The service on MachineA has run-time config options to specify the queue to send to, so this was set up in the config and the service created the outgoing queue.
At this point the public queue did not exist on MachineB, but once this was manually created I was expecting to see messages to start appearing in it, but none have.
I thought it might be permission but the code below is used to instantiate the queue object in code:
Set oMSMQueue = oMSMQQueueInfo.Open(MQ_SEND_ACCESS, MQ_DENY_NONE)
...MQ_DENY_NONE meaning that the queue is available to anyone.
From perfmon counters on MAchineB IO can see that under the MSMQ session the number of messages is building up, but nothing in the queue itself.
Also there is nothing in any of the dead-letter queues.
Is it as simple as I should have created the receiving queue first?