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

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.
Maricel LepanaTechnical CoordinatorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

A KarelinCommented:
Check Event viewer.
0
Maricel LepanaTechnical CoordinatorAuthor Commented:
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
Maricel LepanaTechnical CoordinatorAuthor Commented:
If we try to start the service by manually, getting the error like this
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

A KarelinCommented:
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
Maricel LepanaTechnical CoordinatorAuthor Commented:
Now The exchange Transport Service has started, but the Forefront Protection is not integrated with the exchange.
0
A KarelinCommented:
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
Maricel LepanaTechnical CoordinatorAuthor Commented:
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
VB ITSSpecialist ConsultantCommented:
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
Maricel LepanaTechnical CoordinatorAuthor Commented:
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
VB ITSSpecialist ConsultantCommented:
Anything change recently that would have caused the services to stop on one server and not another? Windows Updates, A/V patches, etc?
0
Maricel LepanaTechnical CoordinatorAuthor Commented:
No other changes, Only windows updates for both servers.
0
VB ITSSpecialist ConsultantCommented:
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
Maricel LepanaTechnical CoordinatorAuthor Commented:
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
Maricel LepanaTechnical CoordinatorAuthor Commented:
Anyway I am going to try with Rollup 4 and lets see what will happen.
0
VB ITSSpecialist ConsultantCommented:
Not too sure if Visual C++ would have an effect on Forefront Protection but see how you go with Update Rollup 4 first.
0
Maricel LepanaTechnical CoordinatorAuthor Commented:
I have done with Rollup4, but the issue is still there.

Any other solutions?
0
VB ITSSpecialist ConsultantCommented:
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
Maricel LepanaTechnical CoordinatorAuthor Commented:
No other dependencies for this service....
0
Maricel LepanaTechnical CoordinatorAuthor Commented:
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
VB ITSSpecialist ConsultantCommented:
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
Maricel LepanaTechnical CoordinatorAuthor Commented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Maricel LepanaTechnical CoordinatorAuthor Commented:
The issue is resolved
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

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.