?
Solved

Microsoft Exchange (2010) Forefront Protection Eventing Service Wont Start.

Posted on 2014-12-02
22
Medium Priority
?
654 Views
Last Modified: 2014-12-12
Microsoft Exchange (2010) Forefront Protection Eventing Service Wont Start. Installed Microsoft Hotfix Rollup3 for forefront protection for exchange. But still the FPE Service wont start.
0
Comment
Question by:Maricel Lepana
  • 13
  • 6
  • 3
22 Comments
 
LVL 5

Expert Comment

by:A Karelin
ID: 40477898
Check Event viewer.
0
 

Author Comment

by:Maricel Lepana
ID: 40477911
Already done... N

System Log
Event : 7001
Level  : Error
Source : Service Control Manager
Description : The Microsoft Forefront Server Protection Controller service depends on the Microsoft Forefront Server Protection Eventing Service service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

Application Log
Event : 2063
Level : Error
Source : FSC Controller
Description : An error occured. Failed to initialize document.

And other App events are event ID 205 and 210.
0
 

Author Comment

by:Maricel Lepana
ID: 40477915
If we try to start the service by manually, getting the error like this
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 5

Expert Comment

by:A Karelin
ID: 40477958
Look for more events, for more errors or warnings.
Check dependent services. Why your Microsoft Exchange Transport didnt start but have Automatic Startup type?
0
 

Author Comment

by:Maricel Lepana
ID: 40477964
Now The exchange Transport Service has started, but the Forefront Protection is not integrated with the exchange.
0
 
LVL 5

Expert Comment

by:A Karelin
ID: 40477969
Check other services with Automatic Startup type.
And checj event viewer for more error. Something like http://kb.prismmicrosys.com/evtpass/evtpages/EventId_465_ESE_50146.asp
0
 

Author Comment

by:Maricel Lepana
ID: 40478020
There is no other events ratherthan the 7001 in the system log and Event ID 1076 in App Log which says "The forefront Protection Eventing Service Has Stopped"
0
 
LVL 24

Expert Comment

by:VB ITS
ID: 40478094
Stop all Forefront services then delete the configuration.xml and configuration.bak files in C:\Program Files (x86)\Microsoft Forefront Protection for Exchange Server\data then try starting the services again.

If that doesn't work look at installing Hotfix Update Rollup 4.
0
 

Author Comment

by:Maricel Lepana
ID: 40478172
I tried what you said with the configuration file, but no luck. If we install Rollup4 then that would be help us to resolve this issue. Because here I have two servers, and the second server is working without having the Rollup3 and there were no issues with any services.
0
 
LVL 24

Expert Comment

by:VB ITS
ID: 40478206
Anything change recently that would have caused the services to stop on one server and not another? Windows Updates, A/V patches, etc?
0
 

Author Comment

by:Maricel Lepana
ID: 40478241
No other changes, Only windows updates for both servers.
0
 
LVL 24

Expert Comment

by:VB ITS
ID: 40478246
I would see how you go with Update Rollup 4 anyway as it's best practice to have the latest updates installed, especially when something stops working.

If all else fails you may need to do a reinstall on the problematic server.
0
 

Author Comment

by:Maricel Lepana
ID: 40478257
I noticed one thing regarding the updates installed on both servers, The first server does't install the udpate for Microsoft Visual C++ 2010 x64 but the second server have installed that update with the same updation.

Any idea..?
0
 

Author Comment

by:Maricel Lepana
ID: 40478417
Anyway I am going to try with Rollup 4 and lets see what will happen.
0
 
LVL 24

Expert Comment

by:VB ITS
ID: 40478454
Not too sure if Visual C++ would have an effect on Forefront Protection but see how you go with Update Rollup 4 first.
0
 

Author Comment

by:Maricel Lepana
ID: 40480114
I have done with Rollup4, but the issue is still there.

Any other solutions?
0
 
LVL 24

Expert Comment

by:VB ITS
ID: 40480176
Check the dependencies for the service, are they started? What about in the Application and System logs? Look at all logs and not just for warnings/errors
0
 

Author Comment

by:Maricel Lepana
ID: 40480182
No other dependencies for this service....
0
 

Author Comment

by:Maricel Lepana
ID: 40480241
System Log
Error      12/3/2014 22:56      Service Control Manager      7001      None      "The Microsoft Exchange Transport service depends on the Microsoft Forefront Server Protection for Exchange Registration Service service which failed to start because of the following error:
The dependency service or group failed to start."

Error      12/3/2014 22:56      Service Control Manager      7001      None      "The Microsoft Forefront Server Protection for Exchange Registration Service service depends on the Microsoft Forefront Server Protection Controller service which failed to start because of the following error:
The dependency service or group failed to start."

Error      12/3/2014 22:56      Service Control Manager      7001      None      "The Microsoft Forefront Server Protection Controller service depends on the Microsoft Forefront Server Protection Eventing Service service which failed to start because of the following error:
The operation completed successfully."

Information      12/3/2014 22:58      Service Control Manager      7036      None      The Microsoft Forefront Server Protection Monitor service entered the stopped state.

Information      12/3/2014 22:56      Service Control Manager      7036      None      The Microsoft Exchange Transport service entered the running state.

Information      12/3/2014 22:56      Service Control Manager      7036      None      The Microsoft Forefront Server Protection Eventing Service service entered the stopped state.
0
 
LVL 24

Expert Comment

by:VB ITS
ID: 40480702
Only thing left I can think of is to do a reinstall/repair on Forefront or alternatively restore the server from a backup to its last known working configuration. It's possible a Windows Update has broken Forefront but you'll need to use the process of elimination and uninstall the most recent updates one by one while restarting the server each time to see if it fixes the problem.
0
 

Accepted Solution

by:
Maricel Lepana earned 0 total points
ID: 40486345
Thank you for your information.

The issue was resolved by replacing "configuration.xml" file in the problematic server with "confiuration.xml" file from the Working Server. Before doing this I stopped all the Forefront protection Services and Disabled "Symantec Private Branch Exchange service".

Thank you again and Regards...
0
 

Author Closing Comment

by:Maricel Lepana
ID: 40495787
The issue is resolved
0

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Eseutil Hard Recovery is part of exchange tool and ensures Exchange mailbox data recovery when mailbox gets corrupt due to some problem on Exchange server.
Among the most obnoxious of Exchange errors is error 1216 – Attached Database Mismatch error of the Jet Database Engine. When faced with this error, users may have to suffer from mailbox inaccessibility and in worst situations, permanent data loss.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
how to add IIS SMTP to handle application/Scanner relays into office 365.
Suggested Courses
Course of the Month8 days, 7 hours left to enroll

616 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question