KnowledgeBase Event Repository

This site is the central interface to the Adiscon Event Repository

  • Details for this entry
  • Eventlog Type:
    Application
    Eventlog Source:
    MSMQ
    Event ID:
    2121
    Full Description:
    Unable to complete Message Queuing Setup. Hresult- c00e0075h
    Yoel Arnon [MSFT] posted in a Newsgroup:

    "On each boot, the MSMQ service checks whether the computer joined a domain. If it did, then MSMQ tries to do so as well, by creating an MSMQ Configuration object under the computer object in Active Directory. In order for joining a domain to succeed, you must have a domain controller in your computer's site that is running MSMQ, and you must also have a Global Catalog server running MSMQ in your computer's domain (a single Global
    Catalog in your site is enough). MSMQ cannot join an NT 4.0 MSMQ 1.0 enterprise. If you prefer that MSMQ remain in "workgroup" mode, then add
    the AlwaysWithoutDS dword registry value under
    HKLM\SOFTWARE\Microsoft\MSMQ\Parameters\Setup, with value 1."
    Search for this Event::
    Search in Knowledge Base  •  Search in this Forum  •  Search on Windows-Expert.com
  • Accessed: 4585

Discuss the Event

Discussion for KB Entry 6734 - Event ID 2121

by knowledgebase on Thu May 29, 2008 8:40 pm

This is the discussion thread for the Knowledge Base Entry 6734

Eventlog Type: Application
Eventlog Source: MSMQ
Event ID: 2121
Link to KB Entry

Short Description:
Unable to complete Message Queuing Setup. Hresult- c00e0075h
knowledgebase
Forum Bot
 
Posts: 165
Joined: Wed May 28, 2008 10:09 am


About the KnowledgeBase Event Repository

This is a repository of known Windows Events, hopefully together with a description of what it means, when it appears and how to troubleshoot it. The event repository was initially provided as a tool for parser creation but has since evolved. It is now part of the overall knowledgebase in the hope that it provides a useful service to the community. Please add your comments and questions (which we try to answer), as this increases the event repository usefulness for all of us.

Return to

cron