LS Bandwidth Policy Service (Core) log stopped because of unexpected errors when writing log files. LS Bandwidth Policy Service (Core) log failed after retrying the log operation[%1] for %2 times. Log file name: %3 Exception: %4 Cause: An unexpected error has occurred, possibly because of a network outage. Resolution: Make sure the CS File Store can be accessed by Bandwidth Policy Service (Core)and re-enable PDP logging via CS power-shell cmdlet.
LS Bandwidth Policy Service (Core) definition was removed from the topology configuration. The service continue to run; however, ...
LS Bandwidth Policy Service (Core) failed to listen on %1:%2 Cause: Another service may be listening on the same port. Resolution: ...
LS Bandwidth Policy Service (Core) has successfully synchronized with other LS Bandwidth Policy services in the deployment. ...
LS Bandwidth Policy Service (Core) is synchronizing with other LS Bandwidth Policy services in the deployment to obtain the ...
LS Bandwidth Policy Service (Core) log stopped because of unexpected errors when writing log files. LS Bandwidth Policy Service ...
LS Bandwidth Policy Service (Core) startup is pending. The configuration database is not yet available. Cause: There may ...
Lync Online Provisioning Service definition is removed from topology configuration. The service will be running using the ...
Lync Online Provisioning Service startup is pending because the Central Management database is not yet available. Cause: ...
Lync Online Provisioning Service successfully registered with the rtcprov database, but a schema or sproc version mismatch ...