Message Queuing could not establish connection to %1, because connection was refused by the recipient computer. It is possible that Client Access Licenses (CALs) are exhausted (if the recipient is a Windows Server), or connection limit has been reached (if the recipient is a Windows workstation). This event is logged at most once per %2 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2187 registry value to desired time in seconds.
Message Queuing cannot establish new connections to this computer because connection limit was reached. There are too many ...
Message Queuing could not access Active Directory Domain Services and failed to compute routing path for messages sent to ...
Message Queuing could not authenticate a message sent to queue %1. The message was rejected because the queue only accepts ...
Message Queuing could not complete SSL negotiation with the remote computer. It is possible that the server certificate is ...
Message Queuing could not establish connection to %1, because connection was refused by the recipient computer. It is possible ...
Message Queuing could not establish connection to %1, because the connection limit for this computer was reached. There too ...
Message Queuing could not establish SSL connection with the recipient computer because a trust chain from the server certificate ...
Message Queuing could not establish SSL connection with the recipient computer because the computer name specified in the ...
Message Queuing could not resolve the name '%1' to an IP address. Try to ping the recipient computer, and check this computer's ...