Solved

Error when installing Exchange 2013

Posted on 2013-12-19
3
3,314 Views
Last Modified: 2013-12-19
I am getting this error when installing Exchange 2013 server

Error:
The following error was generated when "$error.Clear();
          if ($RoleStartTransportService)
          {
              start-SetupService -ServiceName FMS
          }
        " was run: "Service 'FMS' failed to reach status 'Running' on this server.".

Please advice.
THank you!
0
Comment
Question by:claudiamcse
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 

Author Comment

by:claudiamcse
ID: 39730210
[2] Will wait '25000' milliseconds for the service 'FMS' to reach status 'Running'.
[12/19/2013 19:10:20.0639] [2] Service 'FMS' failed to reach status 'Running' on this server after waiting for '25000' milliseconds.
[12/19/2013 19:10:20.0639] [2] [WARNING] Service checkpoint has not progressed. Previous checkpoint='0'- Current checkpoint='0'.
[12/19/2013 19:10:20.0639] [2] Previous service status query time is '12/19/2013 12:09:55 PM'.
[12/19/2013 19:10:20.0639] [2] Current service status query time is '12/19/2013 12:10:20 PM'.
[12/19/2013 19:10:20.0639] [2] Will wait '25000' milliseconds for the service 'FMS' to reach status 'Running'.
[12/19/2013 19:10:45.0675] [2] Service 'FMS' failed to reach status 'Running' on this server after waiting for '25000' milliseconds.
[12/19/2013 19:10:45.0675] [2] [WARNING] Service checkpoint has not progressed. Previous checkpoint='0'- Current checkpoint='0'.
[12/19/2013 19:10:45.0675] [2] Previous service status query time is '12/19/2013 12:10:20 PM'.
[12/19/2013 19:10:45.0675] [2] Current service status query time is '12/19/2013 12:10:45 PM'.
[12/19/2013 19:10:45.0675] [2] Will wait '25000' milliseconds for the service 'FMS' to reach status 'Running'.
[12/19/2013 19:11:10.0806] [2] Service 'FMS' failed to reach status 'Running' on this server after waiting for '25000' milliseconds.
[12/19/2013 19:11:12.0069] [2] Service Control Manager reports no process ID for service FMS.
[12/19/2013 19:11:12.0604] [2] Unable to get the process ID for service FMS because another similar process 0 was found
[12/19/2013 19:11:12.0698] [2] Service 'FMS' failed to reach status 'Running' on this server.
[12/19/2013 19:11:13.0057] [2] Service 'FMS' failed to reach status 'Running' on this server.
[12/19/2013 19:11:13.0805] [2] Ending processing start-SetupService
[12/19/2013 19:11:13.0914] [1] The following 1 error(s) occurred during task execution:
[12/19/2013 19:11:13.0914] [1] 0.  ErrorRecord: Service 'FMS' failed to reach status 'Running' on this server.
[12/19/2013 19:11:13.0914] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: Service 'FMS' failed to reach status 'Running' on this server.
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Tasks.ManageSetupService.WaitForServiceStatus(ServiceController serviceController, ServiceControllerStatus status, Unlimited`1 maximumWaitTime, Boolean ignoreFailures, Boolean sendWatsonReportForHungService)
   at Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(ServiceController serviceController, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
   at Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(String serviceName, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
   at Microsoft.Exchange.Management.Tasks.StartSetupService.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[12/19/2013 19:11:14.0235] [1] The following error was generated when "$error.Clear();
          if ($RoleStartTransportService)
          {
              start-SetupService -ServiceName FMS
          }
        " was run: "Service 'FMS' failed to reach status 'Running' on this server.".
[12/19/2013 19:11:14.0235] [1] Service 'FMS' failed to reach status 'Running' on this server.
[12/19/2013 19:11:14.0297] [1] [ERROR-REFERENCE] Id=BridgeheadServiceControl___7690585D-9B0C-4978-B0B5-1A9EB0E6CE33 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[12/19/2013 19:11:14.0344] [1] Setup is stopping now because of one or more critical errors.
[12/19/2013 19:11:14.0344] [1] Finished executing component tasks.
[12/19/2013 19:11:18.0326] [1] Ending processing Install-BridgeheadRole
0
 
LVL 53

Accepted Solution

by:
Will Szymkowski earned 500 total points
ID: 39730228
When installing Exchange 2013 you need to make sure that IPv6 is disabled from network connections and also from the registry.

Look here for details - http://vandropratama.wordpress.com/2013/08/22/error-was-run-service-fms-failed-to-reach-status-running-on-this-server/

Will.
0
 

Author Closing Comment

by:claudiamcse
ID: 39730774
Thanks!!!
0

Featured Post

Independent Software Vendors: 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!

Question has a verified solution.

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

Uncontrolled local administrators groups within any organization pose a huge security risk. Because these groups are locally managed it becomes difficult to audit and maintain them.
There are times when we need to generate a report on the inbox rules, where users have set up forwarding externally in their mailbox. In this article, I will be sharing a script I wrote to generate the report in CSV format.
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
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

718 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