"A service failed to start due to the following error" ???

  • Thread starter Thread starter Bob Perez
  • Start date Start date
B

Bob Perez

Exchange 2000 Server just stopped delivering mail in my domain and I tried
to figure out why. The Outlook clients just hung without ever accessing the
server and eventually gave me a Retry/Offline/Cancel option. Upon viewing
the Event Viewer I noticed a lot of NNTP informational messages that seemed
superfluous since I'm not running an NNTP server, so I tried to uninstall
IIS (I'm not running OWA, a local web server or anything else that appears
to require IIS). This seemed to cause havoc to the system, so I re-installed
IIS and on system boot up I'm getting a message that "A service failed to
start". Examination of the Event viewer reveals these error messages:


Event ID 7000. "The Microsoft Exchange IMAP4 Service failed to start due to
the following error:
"The executable program that this service is configured to run in does not
implement the service"

Event ID 7000. "The Microsoft Exchange Routing Service failed to start due
to the following error:
"The executable program that this service is configured to run in does not
implement the service"

Event ID 7000. "The Microsoft Exchange POP3 Service failed to start due to
the following error:
"The executable program that this service is configured to run in does not
implement the service"

The Outlook clients are now able to access the mail store and display mail
that had existed on the server prior to my changes. But it's evident that no
new mail is coming in.

Can anyone help me decipher these error codes above? I've searched the KB
and I don't see anything helpful. What exactly do these errors mean, what
causes this to happen?

Help! Thanks in advance for your suggestions and advice!

Bob
 
Check your services (Control Panel / Administrative Tasks / Services)
and examine those services that are on "Automatic" start but have
not started. You can try and start them manually.
 
Bob said:
Exchange 2000 Server just stopped delivering mail in my domain and I
tried to figure out why. The Outlook clients just hung without ever
accessing the server and eventually gave me a Retry/Offline/Cancel
option. Upon viewing the Event Viewer I noticed a lot of NNTP
informational messages that seemed superfluous since I'm not running
an NNTP server, so I tried to uninstall IIS (I'm not running OWA, a
local web server or anything else that appears to require IIS). This
seemed to cause havoc to the system, so I re-installed IIS and on
system boot up I'm getting a message that "A service failed to
start". Examination of the Event viewer reveals these error messages:


Event ID 7000. "The Microsoft Exchange IMAP4 Service failed to start
due to the following error:
"The executable program that this service is configured to run in
does not implement the service"

Event ID 7000. "The Microsoft Exchange Routing Service failed to
start due to the following error:
"The executable program that this service is configured to run in
does not implement the service"

Event ID 7000. "The Microsoft Exchange POP3 Service failed to start
due to the following error:
"The executable program that this service is configured to run in
does not implement the service"

The Outlook clients are now able to access the mail store and display
mail that had existed on the server prior to my changes. But it's
evident that no new mail is coming in.

Can anyone help me decipher these error codes above? I've searched
the KB and I don't see anything helpful. What exactly do these errors
mean, what causes this to happen?
Click to expand...

Oh boy. Your current problem is related to the fact that you removed IIS.
Exchange uses IIS components for a heck of a lot of the things that it does
and I'm not surprised it doesn't like you removing it.

You need to look at the exchange "disaster recovery" section in Technet for
details on what to do next - you'll want to re-install Exchange files
without altering your database or AD information.


--
 
Thanks for all the responses, I tried every one of them. Turns out that I
was able to get everything in good condition again by re-installing
Exchange, re-applying SP3 and then the rollup hotfix. All is working now.

Thanks!

Bob
 
Back
Top