1

I have an rather unpleasant error with MSMQ, one that following the information available on-line isn't fixing. It's resulting in emails (.EML files) going into C:\inetpub\mailroot\Queue and just sitting there not being sent.

Environment Information: The server in question is Windows Server 2012 R2. My Active Directory domain controllers are 2012 R2 and domain and forest levels are at 2012 R2. I recently upgraded from Exchange 2010, by creating a 2012 R2 server and installing Exchange 2013 SP1 on it which was then patched to CU 19 and is functioning normally and accepts relayed mail (tested via telnet) from the server running MSMQ.

The error that shows in the event log is this Source: 

    MSMQ
    Event ID: 2164
    "The Message Queuing service will not join the MyDomainName domain. An MSMQ Configuration (msmq) object exists in the new domain with an ID differing from the service ID. Please delete the MSMQ Configuration object in the new domain, restart the Message Queuing service, and log on again."

The available information I have suggestions two actions. 1. Deleting the msmq from Active Directory for the server in question. 2. Make sure Network Service on that server is had the specific permission of ' Create MSMQ configuration Objects.

I have removed the msmq object via AD on the server running MSMQ and waited for it to replicate around my domain controllers. (and double checked, by confirming it was gone on each DC).

For the next stage I've tried both rebooting and restarting services, both have the same effect. I restart the Messaging Queuing service (doing this also restarts Messaging Queuing Triggers and Net.Msmq Listener Adapter services).

I get two new event log errors for MSMQ.

    MSMQ
    Event ID: 2116
    "Message Queuing was unable to create the msmq (MSMQ Configuration) object in Active Directory Domain Services. Error c00e0025h"

Directly followed with this error...

    MSMQ
    Event ID: 2164
    "The Message Queuing service failed to join the computer's domain 'MyDomainName'. Error 0xc00e0025"

If I restart the services again, I end up back with this error in the event log "The Message Queuing service will not join the MyDomainName domain. An MSMQ Configuration (msmq) object exists in the new domain with an ID differing from the service ID. Please delete the MSMQ Configuration object in the new domain, restart the Message Queuing service, and log on again."

Now... in Active Directory my server has had the msmq recreated against it.

I've gone round in a circle. I have considered reinstalling MSMQ, this requires removing App server functionality and .Net 4.5. This is a production server that runs some RDP and IIS functions and I'm concerned it would wipe out settings and potentially break the software running on the server.

In the short term, I've written a C# program to manually process the email queue to keep things going, but it doesn't resolve the issue. :(

Anyone got any thoughts or ideas on what to try or where else to look?

Improve this question

3 Answers 3

Reset to default
1

Are you logged in as domain admin when you install MSMQ?

Error 0xC00E0033 when you try and install MSMQ with Active Directory Integration https://blogs.msdn.microsoft.com/johnbreakwell/2009/10/21/error-0xc00e0033-when-you-try-and-install-msmq-with-active-directory-integration/

Deleting Stale MSMQ Active Directory Objects https://blogs.msdn.microsoft.com/johnbreakwell/2009/12/16/deleting-stale-msmq-active-directory-objects/

Watch out when re-installing MSMQ 4.0 in a domain https://blogs.msdn.microsoft.com/johnbreakwell/2007/05/15/watch-out-when-re-installing-msmq-4-0-in-a-domain/

Improve this answer
5
  • Hi, when I installed MSMQ originally I was logged in as a domain admin user.
    – FridgeMagnet
    Apr 19, 2018 at 11:35
  • Did you select "Routing Services"? (I assume that's an MSMQ option on 2012; I don't have a server handy)
    – John Breakwell
    Apr 19, 2018 at 12:30
  • I can't remember, this was setup back in October 2017, it only stopped working last week. (about 6 months later).
    – FridgeMagnet
    Apr 21, 2018 at 19:29
  • Anyway, do you need MSMQ in Active Directory Integrated mode? Are you using public queues?
    – John Breakwell
    Apr 23, 2018 at 12:02
  • It is a third party piece of software that uses MSMQ, Unfortunately I'm responsible for the server and MSMQ working, their software uses it and they haven't encountered any issues like this. I don't know why they don't directly send email through the mail server.
    – FridgeMagnet
    Apr 24, 2018 at 8:01
0

I had the same issue, uninstalling and reinstalling MSMQ in Windows Features fixed it for me.

Improve this answer
0

Turns out it was linked to Group Policy, I'd wanted some users to be able to log on as a service without going round each PC and setting it up. So I'd added them to a group policy to include certain users that they had permission to log on as a service, this had the effect of allowing ONLY those ones and to stop the existing users of background services from working properly.

Lesson learned.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .