BizTalk/MQ - DCOM was unable to communicate with the computer xxx using any of the configured protocols

Posted by NealWalters on Server Fault See other posts from Server Fault or by NealWalters
Published on 2013-10-30T20:13:30Z Indexed on 2013/10/30 21:59 UTC
Read the original article Hit count: 275

Filed under:
|
|
|
|

I've read the other questions on this same error, but don't see a close match to this scenario.

We got 18 of these last night between 12:17:13 and 12:39:37 on Win 2008/R2. It caused us to lose connectivity between BizTalk 2010 and WebSphere MQ machine. All our BizTalk machines (Prod, QA, Train, etc...) got the messages at the roughly same time and in the same quantity (about 18 of them).

Computer xxx is the WebSphere MQ machine.

What could cause this in the middle of the night? The servers are configured and running in Prod for a couple of years. There is no Win Firewall running, and servers are practically on the same rack.

Could a run-away or 100% utilized CPU on the WebSphere MQ cause this issue? What else could cause it?

BizTalk did NOT auto-recover from this situation.

The above was followed by thousands of this message in the BizTalk event logs: The adapter "MQSeries" raised an error message. Details "Error encountered on Queue.Get Queue name = MyQManager/MyQueueName Reason code = 2354.".

We restated BizTalk host instances, and it did not come back right away. It seemed we had to stop host instances for about two minutes, then start them.

© Server Fault or respective owner

Related posts about dcom

Related posts about BizTalk