Event ID 2068 — Message Queuing Active Directory Operation

Event ID 2068 — Message Queuing Active Directory Operation

Updated: January 31, 2008

Applies To: Windows Server 2008

Message Queuing must integrate successfully with Active Directory Domain Services (AD DS) to function properly in domain mode. The integration of the Active Directory interface, configuration, and other related issues can affect Message Queuing.

Event Details

Product: Windows Operating System
ID: 2068
Source: MSMQ
Version: 6.0
Symbolic Name: EVENT_ERROR_DS_SERVER_LIST_EMPTY
Message: The list of Message Queuing servers with directory service functionality in the Windows registry is empty.

Resolve
Contact Microsoft

There may be several reasons why the server list is empty.

If you continue to receive this error, note any details in the event message, and then contact Microsoft Customer Service and Support (CSS). For information about how to contact CSS, see Enterprise Support (http://go.microsoft.com/fwlink/?LinkId=52267).

Verify

You can confirm the presence of the Directory Service Integration feature by doing the following:

  • Verify the registry key setting
  • Verify that the computer is joined to the correct domain
  • Verify Active Directory operation

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.

Verify the registry key setting

To verify the registry key setting:

  1. Open Registry Editor. To open Registry Editor, click Start. In the search box, type regedit, and then press ENTER.
  2. In Registry Editor, expand HKEY_LOCAL_MACHINE, expand SOFTWARE, expand Microsoft, expand MSMQ, and then click Setup.
  3. In the details pane, double-click msmq_ADIntegrated.
  4. Confirm that Value data is set to 1.
  5. Under MSMQ, expand Parameters.
  6. In the details pane, double-click Workgroup.
  7. Confirm that Value data is not set to 1.

Verify that the computer is joined to the correct domain

To verify that the computer is joined to the correct domain:

  1. Open Server Manager. To open Server Manager, click Start, point to Administrative Tools, and then click Server Manager.
  2. Confirm that the domain that is listed in Computer Information is the correct domain.

Verify Active Directory operation

You can confirm that Active Directory is operating correctly by verifying that the Public Queue feature is enabled in Message Queuing.

To verify that the Public Queue feature is enabled:

  1. Open the Computer Management snap-in. To open Computer Management, click Start. In the search box, type compmgmt.msc, and then press ENTER.
  2. Navigate to MSMQ.
  3. If the Public Queues folder exists and you can right-click the folder, Message Queuing is operating correctly in domain mode with Active Directory Integration.
  4. For further confirmation, run a test application that uses the Active Directory features that you require.

Related Management Information

Message Queuing Active Directory Operation

Message Queuing

Related:

Process %1 (PID=%2). DSAccess initialized successfully.

Details
Product: Exchange
Event ID: 2068
Source: MSExchange ADAccess
Version: 8.0
Symbolic Name: DSC_EVENT_INITIALIZED
Message: Process %1 (PID=%2). DSAccess initialized successfully.
   
Explanation

This event indicates that DSAccess initialized successfully. This is an informational message.

   
User Action

No user action is required.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

Unable to move a log file from the inspector directory to the log directory for storage group %1. Old path: %2. New path: %3.

Details
Product: Exchange
Event ID: 2068
Source: MSExchangeRepl
Version: 8.0
Symbolic Name: CouldNotMoveLogFile
Message: Unable to move a log file from the inspector directory to the log directory for storage group %1. Old path: %2. New path: %3.
   
Explanation

This Error event indicates that the Microsoft® Exchange Replication (MSExchangeRepl) service could not move a log file from the old path to the new path. The failure could be caused by an I/O or permission failure. The failure could also be caused by any other failure that prevents moving the log file between the two locations.

Note   The old log file path and the new log file path should be in the same volume.

   
User Action

To resolve the error, try one or more of these steps:

  • Check the file system for issues that could prevent moving any files. Make sure that the correct volume is mounted at the correct location. For example, you might encounter these problems if your log drive should be on <D:> and your database drive on <E:>. But you accidentally put the database drive on <D:> and log drive on <E:>.

  • Check file permissions. The Microsoft Exchange Replication service runs under local system rights. These rights may have different permissions than the administrator level rights.

  • Try to move the file manually.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related: