RButler
asked on
Error 2140 NT- Internet Mail Service
NT error "Could not start MS Exchange Internet Mail Server service on \\SERVER. Error 2140. An internal NT error occurred." Internet mail is not automatically starting on this Back Office Small Business Server installation. Seems that initialuization of the service fails. What would be the cause(s)?
How many other Exchange services do you have running?
Make sure that it has a valid account and use name for the service. Is this a new Internet Mail Connector or one that had been running for awhile and now has suddenly failed. Someone may have changed the service account password for the domain, and didn't change it on the service.
Is the Exchange Service account in the local of Domain Administrators group ?
Do you have other errors (e.g. 4143) in the Application Log ?
Frankie_Muccio's comment makes sense too.
Do you have other errors (e.g. 4143) in the Application Log ?
Frankie_Muccio's comment makes sense too.
I recommend you immediately check your Event Viewer. The Internet Mail Service is *one* of the few Services that provides *excellent* problem descriptions in the event log.
Some of the causes I have found for a refusal to start the IMC are:
1.Out of disk space on IMC spool drive
2.Messages already in queue could not have their domain names resolved (if you are using DNS to deliver your mail and not a forwarder, that is)
3.Incorrect account used to start service
So, check your event logs and all should be explained. If the error listed doesn't make sense, write back with the error.
Cheers
Some of the causes I have found for a refusal to start the IMC are:
1.Out of disk space on IMC spool drive
2.Messages already in queue could not have their domain names resolved (if you are using DNS to deliver your mail and not a forwarder, that is)
3.Incorrect account used to start service
So, check your event logs and all should be explained. If the error listed doesn't make sense, write back with the error.
Cheers
This may be a bit complicated to go into in this forum but if you have access to TechNet (and you should !) have a look at articles Q173496, Q163243 & Q193928. The most common cause appears to be that the Microsoft Exchange Service Account is not an Administrator or part of the Administrator group, but there are plenty of other causes all detailed in these articles.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.