If the web endpoint and the server endpoint are on different machines you should see an outbound queue on the web machine. You may see the messages there. This means that for some reason MSMQ couldn't complete the send to the other machine.
This typically means that there is a configuration issue on either machine related to MSMQ, MSDTC, or a firewall could be blocking it.
If the web endpoint and the server endpoint are on different machines you should see an outbound queue on the web machine. You may see the messages there. This means that for some reason MSMQ couldn't complete the send to the other machine.
This typically means that there is a configuration issue on either machine related to MSMQ, MSDTC, or a firewall could be blocking it. If it is all local its a bit harder to say since you won't see anything in the outbound queue. I would turn on journaling on the target queue to see if the message actually makes it there, if it does, then something is processing the message.
If not then it must be a config problem.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.