Error Starting Lync Bandwidth Policy Service

This is a small one, and not too common, but it’s come up on the TechNet forums a few times so I thought I’d take a moment to write it up and make it easier on those searching for the fix.

Issue Overview

The issue is that upon a server restart, the Lync Server Bandwidth Policy Service (Authentication) and Lync Server Bandwidth Policy Service (Core) services fail to start.  A few errors are generated in the event logs, notably the LS Bandwidth Policy Service (Authentication) Event 29004 and LS Application Server Event ID 32014.

image1

Some examples of the logs are here:

Event ID 32014, source:LS Application Server

The application threw an exception while starting.

The application urn:application:testbot threw the following exception when starting: Exception: Microsoft.Rtc.Collaboration.ProvisioningFailureException
> FailureReason: ApplicationNotFound
> DetectionStackTrace:    at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
at System.Environment.get_StackTrace()
at Microsoft.Rtc.Collaboration.ProvisioningFailureException..ctor(String message, Exception innerException, ProvisioningFailureReason failureReason)
at Microsoft.Rtc.Collaboration.PlatformDataImpl.CreateInstance(String requiredCertificateUsage, UCSettings ucSettings, String applicationId, Boolean enableCMSLoadBalancing, Boolean useLocalRegistrar)
at Microsoft.Rtc.Collaboration.ProvisioningSourceImpl.GetInitialPlatformData()
at Microsoft.Rtc.Collaboration.ProvisioningSourceGetInitialPlatformDataAsyncResult.ProcessCoreHelper()
at Microsoft.Rtc.Collaboration.SipCollaborationAsyncResult.ProcessCore()
at Microsoft.Rtc.Signaling.AsyncWorkitemQueue.ProcessItems()
at Microsoft.Rtc.Signaling.SerializationQueue`1.ResumeProcessing()
at Microsoft.Rtc.Signaling.SerializationQueue`1.ResumeProcessingCallback(Object state)
at Microsoft.Rtc.Signaling.QueueWorkItemState.ExecuteWrappedMethod(WaitCallback method, Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
> Message: Application with id(urn:application:testbot) not found or a default port has not been configured for it.
> TargetSite: Exception: Exception has been thrown by the target of an invocation.
> StackTrace:    at Microsoft.Rtc.Internal.ServerSharedComponents.MachApplication.StartUp()
at Microsoft.Rtc.Internal.ServerSharedComponents.ServiceManager.Startup()
at Microsoft.Rtc.Internal.ServerSharedComponents.UCAS.MachUcasService.StartAsync()
at Microsoft.Rtc.ApplicationServerCore.ApplicationLoader.CallStartAsync()
> Source: Microsoft.Rtc.Collaboration
> HResult: -2146233088
.
Cause: Startup errors.
Resolution:
Check the events prior to this to resolve the service startup issue.

And

Event ID: 29004   Source: LS Bandwidth Policy Service (Authentication)

Error while trying to access local Settings. The LS Bandwidth Policy Service (Authentication) will stop.

Exception: System.Exception: MRAS port is not configured!
at Microsoft.Rtc.MRAS.Configuration..ctor(ConfigChangedHandler ConfigChangedEventHandler, RoleName roleName)
Cause: The current account may not have the necessary permissions to access these settings, or the LS Bandwidth Policy Service may not be installed correctly, or the settings are wrong.
Resolution:
Rerun LS Bandwidth Policy Service (Authentication) installation and activation.

Event ID: 29005   Source: LS Bandwidth Policy Service (Authentication)
LS Bandwidth Policy Service (Authentication) could not be started.

Exception: System.Exception: MRAS port is not configured!
at Microsoft.Rtc.MRAS.Configuration..ctor(ConfigChangedHandler ConfigChangedEventHandler, RoleName roleName)
at Microsoft.Rtc.MRAS.Core..ctor(ServiceStopHandler serviceStop, RoleName roleName)
at Microsoft.Rtc.MRAS.Server.OnStart(RoleName roleName)
Cause: Internal error.
Resolution:
Examine the details in the associated event log entry to determine the potential cause and report to Product Support Services.

Other errors seen are LS Bandwidth Policy Service (Authentication) Event 29005: “LS Bandwidth Policy Service (Authentication) could not be started”, LS Bandwidth Policy Service (Core) Event 36008: “LS Bandwidth Policy Service (Core) could not be started” and LS Bandwidth Policy Service (Core) Event 36058:” The LS topology is not configured to run the LS Bandwidth Policy Service (Core).  The PDP ports are not defined.”

Resolution

The events seem a little scary, but the answer is simple.  Someone likely disabled call admission control but did not finish the process.

When you uncheck Call Admission Control at the site level and publish your topology, you’re not done.

nocac

You need to remove the components after you’ve republished by running the bootstrapper or step 2 of the Lync deployment wizard.

RunStep2

Running this step will remove these services at this point.  If you need Call Admission Control enabled, rechecking the box, publishing the topology and confirming your configuration should allow you to get the services started once again.

 

 

 

2 thoughts on “Error Starting Lync Bandwidth Policy Service

  1. Pingback: NeWay Technologies – Weekly Newsletter #120 – November 7, 2014 | NeWay

  2. Pingback: NeWay Technologies – Weekly Newsletter #120 – November 6, 2014 | NeWay

Comments are closed.