This is how the Microsoft Message Queuing (MSMQ) error appears in the application log:
Event Type: Error Event Source: MSMQ Event Category: Kernel Event ID: 2124 Date: Time: User: N/A Computer: 503-UNITY Description: Message Queuing was unable to join the local Windows 2000 domain. Hresult- c00e0075h In some situations, the error message appears this way:
Event Type: Error Event Source: MSMQ Event Category: (1) Event ID: 2124 Date: Time: User: N/A Computer: 503-UNITY Description: The description for Event ID ( 2124 ) in Source ( MSMQ ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: c00e0075h.
The event logs may show that many CiscoUnity_DSGC entries failed to synchronize data for an object in the global catalog with the corresponding data for the object in the Cisco Unity Server Structured Query Language (SQL) Server/Microsoft SQL Desktop Edition (MSDE) database. The Cisco Unity service that monitors the global catalog (AvDSGlobalCatalog) may be listed among the entries.
Cisco Unity is not able to synchronize all changes for these objects until this issue is resolved. However, other objects continue to be synchronized.
This error appears with Event 2121 and Event 2124. For information on the error message related to Event 2121, refer to TAC Case Collection (TAC CC) solution K20025422.
For more information on Event 2124, refer to EventID.Net.
To resolve this problem, in both cases, perform these steps:
Add the AlwaysWithoutDS dword registry value under HKLM\SOFTWARE\Microsoft\MSMQ\Parameters\Setup, with a value of 1.
Note: This value is referenced in the W2K Resource Kit Registry Reference. This error occurs on W2K servers that have MSMQ configured in workgroup mode, but the server is actually in a domain. The value 1 tells MSMQ to remain in workgroup mode.
After the registry key is changed, restart the message queuing service.
Click Start > Run. The Run dialog box appears.
Type cmd in the Open box, then click OK.
The command window appears.
At the command prompt, type net stop msmq, then press Enter.
This stops the message queuing service.
Note: If prompted to stop services that depend on message queuing (such as message queuing triggers), type y andpress Enter.At the command prompt, type net start msmq to restart the message queuing service. Then, press Enter.
If this procedure does not work, try to un-install and re-install the message queuing service from Add/Remove Programs > Add/Remove Windows Components. Ensure the domain controller and global catalog are running MSMQ.