This week we came across the below error on in our project where we are using Windows Azure Service Bus Brokered Messaging.
Microsoft.ServiceBus.Messaging.MessagingCommunicationException: Error during communication with Service Bus. Check the connection information, then retry. ---> System.ServiceModel.CommunicationObjectFaultedException: Internal Server Error: The server did not provide a meaningful reply; this might be caused by a premature session shutdown..TrackingId:4990b52f-7588-4460-81eb-cbef7b103c11, Timestamp:4/22/2013 2:32:44 PM
We initially thought this was a networking issue, we had been having separate issues with our developer machines and networking and initially thought it was related to that. However on closer inspection you can see there is a tracking id in the error message which gives you a good clue you probably managed to make a call to the service bus.
We found the root cause of our problem was that we had put some logging in the code to log the message body before sending the message and when we had read the stream which contained the body and written it to the log file we hadnt set the position back to the start of the stream before sending the message.
Ive seen a few forum posts about this error which seemed to be related to other things but didnt see anyone have the above symptoms so sharing it incase it helps anyone else