Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Skype for Business 2015 cannot start services

Status
Not open for further replies.

alex1002

Technical User
Jan 15, 2014
29
0
0
CA
An exception caused the process to stop.

Exception Details. System.ApplicationException: Failed to start Fabric Pool Manager. ---> System.ApplicationException: Failed to start Fabric Pool Manager
at Microsoft.Rtc.Server.FabricConfigurator.StartRuntime()
at Microsoft.Rtc.Server.FabricConfigurator.Start()
at Microsoft.Rtc.AppDomainHost.Launcher.BootstrapFabric(String roleName)
at Microsoft.Rtc.AppDomainHost.Launcher.Initialize(String[] args)
--- End of inner exception stack trace ---
at Microsoft.Rtc.AppDomainHost.Launcher.Initialize(String[] args)
at Microsoft.Rtc.AppDomainHost.Launcher.Main(String[] args)
Cause: Check the eventlog description.
Resolution:
Examine prior event log entries to find and resolve the problem. If the problem persists contact product support.

Faulting application name: FabricHost.exe, version: 3.0.8549.9492, time stamp: 0x550aaac2
Faulting module name: FabricHost.exe, version: 3.0.8549.9492, time stamp: 0x550aaac2
Exception code: 0xc0000602
Fault offset: 0x000000000006ea09
Faulting process id: 0x16c
Faulting application start time: 0x01d138e2e6e3a4fb
Faulting application path: C:\Program Files\Windows Fabric\bin\FabricHost.exe
Faulting module path: C:\Program Files\Windows Fabric\bin\FabricHost.exe
Report Id: d8be053a-a4d6-11e5-80e5-005056a72bb8
Faulting package full name:
Faulting package-relative application ID:

start-cspool –poolfqdn SFB-1.I.LOCAL

Progress at 2015-12-17T13:19:33:

Status of the Servers:
Server Status Stage
Details
------- ------- ------
--------
SFB-1.I.LOCAL N/A N/A
Failed to get status data!

PS C:\Users\sfpadministrator>
PS C:\Users\sfpadministrator> Start-CsWindowsService
Start-CsWindowsService : Service RTCSRV failed to start. Check to make sure
the service is not disabled. Failure to start could also be because this front
end was previously failed over(using computer fail over), in which case please
invoke fail back(using computer failback). Consult event logs for further
details.
At line:1 char:1
+ Start-CsWindowsService
+ ~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationTimeout: :)SourceCollection) [Start-CsW
indowsService], InvalidOperationException
+ FullyQualifiedErrorId : ServiceStartFailed,Microsoft.Rtc.Management.Depl
oyment.StartServicesCmdlet
WARNING: Start-CsWindowsService encountered errors. Consult the log file for a
detailed analysis, and ensure all errors (2) and warnings (0) are addressed
before continuing.
WARNING: Detailed results can be found at
"C:\Users\sfpadministrator\AppData\Local\Temp\2\Start-CsWindowsService-5d6bb2e8
-9606-41cd-8722-a889f63f0113.html".
PS C:\Users\sfpadministrator>

ServiceStartFailed: Failed to start service. 12/17/2015 9:13:43 AM Error

Error: Service RTCSRV entered into an unexpected state while waiting. Expected State: Running. Actual State:Stopped.
▼ Details
└ Type: InvalidOperationException
└ ▼ Stack Trace
└ at Microsoft.Rtc.Management.Deployment.Core.NTService.WaitForStatus(ServiceControllerStatus expectedStatus, ServiceControllerStatus unexpectedStatus, TimeSpan TotalWaitTime)
at Microsoft.Rtc.Management.Deployment.Core.NTService.Start(Boolean wait) 12/17/2015 9:13:43 AM Error
└ ServiceStartFailed: Service RTCSRV failed to start. Check to make sure the service is not disabled. Failure to start could also be because this front end was previously failed over(using computer fail over), in which case please invoke fail back(using computer failback). Consult event logs for further details. 12/17/2015 9:13:43 AM
└ ServiceStartFailedResolution: If starting the service failed because of a timeout, wait to see if the service eventually starts. Check eventlog for errors. Re-run the cmdlet or start the service manually. 12/17/2015 9:13:43 AM
I also noticed that Windows Fabric Service fails to start
 
ServiceStartFailed: Failed to start service. 12/17/2015 2:46:27 PM Error
└ Error: Service RTCSRV entered into an unexpected state while waiting. Expected State: Running. Actual State:Stopped.
▼ Details
└ Type: InvalidOperationException
└ ▼ Stack Trace
└ at Microsoft.Rtc.Management.Deployment.Core.NTService.WaitForStatus(ServiceControllerStatus expectedStatus, ServiceControllerStatus unexpectedStatus, TimeSpan TotalWaitTime)
at Microsoft.Rtc.Management.Deployment.Core.NTService.Start(Boolean wait)


12/17/2015 2:46:27 PM Error
└ ServiceStartFailed: Service RTCSRV failed to start. Check to make sure the service is not disabled. Failure to start could also be because this front end was previously failed over(using computer fail over), in which case please invoke fail back(using computer failback). Consult event logs for further details. 12/17/2015 2:46:27 PM
└ ServiceStartFailedResolution: If starting the service failed because of a timeout, wait to see if the service eventually starts. Check eventlog for errors. Re-run the cmdlet or start the service manually. 12/17/2015 2:46:27 PM
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top