Message Queuing Downlevel Client Support failed to create the MSMQ Configuration (msmq) object with a given GUID for computer %1. Creating MSMQ Configuration objects with given GUIDs may be required for Message Queuing clients during the setup of Windows NT 4.0 or Windows 9x computers and when a Windows 2000 computer joins a Windows Server 2003 domain. By default, a windows Server 2003 forest does not support adding an object with a supplied GUID. You can solve this problem by upgrading Message Queuing on the client computer to a version that does not require creating an object with a given GUID. There are also alternative solutions.
Message Queuing detected a problem with the local domain controller. Until the problem is resolved, Message Queuing will ...
Message Queuing Downlevel Client Support cannot be added or removed in MSMQ 1.0 environment. This operation is not supported ...
Message Queuing Downlevel Client Support cannot operate in mixed mode. Mixed mode is a transient mode in which Message Queuing ...
Message Queuing Downlevel Client Support cannot start. This service can operate only on a domain controller. The service ...
Message Queuing Downlevel Client Support failed to create the MSMQ Configuration (msmq) object with a given GUID for computer ...
Message Queuing failed to bind to port 1801. The port may already be bound to another process. Make sure that the port is ...
Message Queuing found multiple IP addresses for the local computer. Message Queuing will use the default IP address determined ...
Message Queuing information cannot be read from Active Directory (Error: 1). This may be caused by replication delays or ...
Message Queuing is not supported on Windows XP Home Edition. Your earlier version of Message Queuing will be uninstalled ...