When you edit those scenarios, you will notice a warning about the components Somehow this triggers an internal failure on the IISLogManager component and damaged it. The reason is that the two scenario contain invalid trace components called ‘Internal’ and ‘External’. You find yourself without any logging capability on your servers! CAUSE Worst, the service will crash every time you try to start it with the same error. Resolution: Examine error details to determine resolution. Log Type – IISLogManager, Error – Object reference not set to an instance of an object. “ Centralized Logging Service Agent Error starting background thread to process traces. Please refer CLS logs for details.”īy this time you will notice that the (Skype for Business Server Centralized Logging Service Agent) RTCCLSAGT service has crashed on all the servers you initiated the trace, with the following event error id 33040: TCP error code 10061: No connection could be made because the target machine actively refused it 10.101.128.20:50002.

The connection attempt lasted for a time span of 00:00:02.0071248. ISSUEġ) You start the Skype for Business logging toolĢ) Pick one of the following builtin scenarios (CmdletDebug or IISLog)ģ) As soon as you start this scenarios on the selected servers you will notice the following error message on the logging tool output window: “ResponseMessage: Error code – 20000, Message – Unknown error – Error calling agent Could not connect to net.tcp://:50002/. Another quest with an issue that appears to be there since some time of Skype for Business 2015 server (if not even Lync server.

Skype call internal error