• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3024
  • Last Modified:

Exchange Service Failing

Hi Experts,
I am in need of some urgent assistance!!! I have a Microsoft Exchange Server version 2007 Running on Server 2003 Standard Edition, that I just ran numerous current Microsoft Updates which include several updates to Microsoft .net framework plus many others. Like a moron I did not look at the updates really close as I have done this month after month for years with no issues at all except a occasional reboot. I have rebooted my primary domain controller, and mi Exchange server several times no no avail.
The Updates that I ran include the following:
Microsoft .NET Framework 3.0 Service Pack 2 - Update 'KB2756918
My Error message appears that this may be the root of the issue
Event Type:      Error
Event Source:      MSExchange TransportService
Event Category:      ProcessManager
Event ID:      1031
Date:            1/13/2013
Time:            6:13:37 PM
User:            N/A
Computer:      EXCHANGE-SERVER
The service configuration file could not be loaded for the following reason: System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize ---> System.Configuration.ConfigurationErrorsException: Unrecognized configuration section system.serviceModel. (C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Config\machine.config line 134)
   at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal)
   at System.Configuration.BaseConfigurationRecord.ThrowIfInitErrors()
   at System.Configuration.ClientConfigurationSystem.EnsureInit(String configKey)
   --- End of inner exception stack trace ---
   at System.Configuration.ConfigurationManager.GetSection(String sectionName)
   at System.Configuration.ConfigurationManager.get_AppSettings()
   at Microsoft.Exchange.ProcessManager.ServiceConfiguration.LoadAppSettingsConfigInt32(String configName, Int32& configvalue)
   at Microsoft.Exchange.ProcessManager.ServiceConfiguration.Load(ProcessManagerService processManagerService)
   at Microsoft.Exchange.ProcessManager.ProcessManagerService.Initialize()

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Plus others that I am having a difficult time trying to discover

The services that will not start are the following:
Microsoft Exchange IMAP
MicrosoftExchange Mail Submission
Microsoft Exchange Transport
Microsoft Exchange Momitoring
Any help will be greatly Appreciated
1 Solution
HarleyITGuyAuthor Commented:
OK Experts,
I never heard from anyone and thats OK as I went ahead and called Microsoft Support. The issue was a Windows Update KB2756918 which is a .NET Framework update that is nott supposed to be offered in an environment of Exchange 2007 running on a Server 2003. I uninstalled the update first and then had to got to c:\Windows\microsoft.net\framework\V2.0.50727 and rename the machine.config file to machineconfig.old. There was laready a older copy of machine.config and I now use that one rebooted and all services restarted.
I hope this assists someone else
THANKS! Exactly the same happened to me, wasted my whole day on this.
Thanks for posting this solution!

Also please not that the dir should be:
x86: c:\Windows\microsoft.net\framework\V2.0.50727\CONFIG
x64: c:\Windows\microsoft.net\framework64\V2.0.50727\CONFIG for x64

I didn't have a pre-KB2756918 machine.config file so I renamed it to machine.config.bad and renamed my machine.config.default to machine.config.  I did this in both the x86 and x64 folders but I probably just needed to do it in x64 for my environment.

Restarted and mail is flowing (although had to manually start services as the Microsoft Exchange Active Directory Topology service took quite some time to start)
Train for your Pen Testing Engineer Certification

Enroll today in this bundle of courses to gain experience in the logistics of pen testing, Linux fundamentals, vulnerability assessments, detecting live systems, and more! This series, valued at $3,000, is free for Premium members, Team Accounts, and Qualified Experts.

This resolved my issue also.  My server is Exchange 2007, SP2 with Update Rollup 5.
Just run into this myself. Many thanks for the information, proved to be a job saver!
Wow... The same thing happen to me after applying the Windows Updates...  I also did the x86 and x64.  Many Thanks...
This just happened again with KB2844285.  Mail flowed after uninstall and new machine.config.  I left KB2833940 installed as uninstalling 2844285 worked, but would also have uninstalled it had mail not flowed.  EdgeSych was failing for me this time, but others were failing too.  Interesting that both of these updates were for .NET 2.0.  I'm thinking of skipping any more 2.0 updates...
Well KB2836940 (.NET Framework 3.5 SP1) broke it tonight too.  I'm done with .NET updates!

Same remediation steps.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now