Solved

Error when installing Exchange 2013

Posted on 2013-12-19
3
3,200 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
  • 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

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

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

This article runs through the process of deploying a single EXE application selectively to a group of user.
This article explains how to install and use the NTBackup utility that comes with Windows Server.
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…

840 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