Microsoft KB Archive/839929

= You may receive error message entries in log files after you install Message Queuing in Workgroup mode =

Article ID: 839929

Article Last Modified on 11/27/2007

-

APPLIES TO


 * Microsoft Message Queuing 2.0

-



Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
A problem may occur when you turn on error logging, and then you restart Microsoft Message Queuing Service 2.0. All the following conditions must be true for the problem to occur:
 * Message Queuing Service 2.0 is installed in Workgroup mode.
 * Message Queuing Service 2.0 is installed on a computer that is running Microsoft Windows 2000 Server.
 * Message Queuing is part of the domain.

You may receive the following error messages:

Error message 1

0xC00e0075: Message Queuing servers cannot be found on domain controllers.

You may receive the previous error message in the Msmq.log file.

Error messages 2, 3, and, 4

Event id - 2121

Unable to complete Message Queuing Setup. Hresult- c00e0075h

Event id - 2124

Message Queuing was unable to join the local Windows 2000 domain. Hresult- c00e0075h

Event id - 2068

The list of Message Queuing capable domain controllers in the Windows registry is empty

You may receive the previous error message Event id entries in the application log of Event Viewer.



CAUSE
When you install the Message Queuing Service in Workgroup mode, you can expect this problem to occur because the Message Queuing Service cannot connect to the Active Directory.



RESOLUTION
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To resolve this problem, add a DWORD registry value that is named AlwaysWithoutDS in the  registry key.

To add the registry value, follow these steps:
 * 1) Click Start, and then click Run.

The Run dialog box appears.
 * 1) In the Open box, type regedit.
 * 2) Click OK.
 * 3) In Registry Editor, locate the registry key that is named.
 * 4) In the left pane, right-click Setup, point to New, and then click DWORD Value.
 * 5) Name the new DWORD value AlwaysWithoutDS.
 * 6) Right-click AlwaysWithoutDS, and then click Modify.

The Edit DWORD Value dialog box appears.
 * 1) In the Value data box, type 1.
 * 2) Click OK.
 * 3) Close Registry Editor.

To restart the Message Queuing Service, follow these steps:
 * 1) Click Start, and then click Run.

The Run dialog box appears.
 * 1) Type cmd in the Open box, and then click OK.

The Command window appears.
 * 1) At the command prompt, type net stop msmq, and then press ENTER.

This stops the Message Queuing Service.

Note You may be prompted to stop a list of services that depend on Message Queuing, such as Message Queuing Triggers.
 * 1) Type y, and then press ENTER.
 * 2) At the command prompt, type net start msmq to restart the Message Queuing Service, and then press ENTER.



STATUS
This behavior is by design.



Steps to reproduce the problem

 * 1) Install Message Queuing 2.0 in Workgroup mode on a computer that is running Windows 2000 Server.

Note The computer must be part of a domain.
 * 1) Turn on Message Queuing error logging.
 * 2) Stop the Message Queuing Service. Restart the Message Queuing Service.

You may receive the error messages that are mentioned in the &quot;Symptoms&quot; section.

