It’s possible my new Edge is jinxed. First I couldn’t RDP to it, and now I’ve installed SfB, CLS Logging isn’t working.
It might have something to do with the fact that Windows Updates put .NET 4.7 on it before I’d even had a chance to run Pat’s script to block it.
The quick way to check for it in Server 2016 is to look for the KB:
PS C:\Users\Administrator> get-hotfix Kb3186568
Anyway, despite having excised that, CLS logging wasn’t working. The service would start and appear to run fine, with no errors in the event log, but it wasn’t listening on the usual ports, and of course that was resulting in errors when I tried to start logging from the Front-End:
PS C:\Users\greig> Show-CsClsLogging -Computers sfb2015edge2.blah.local
WARNING: Failed on 1 agents
Agent - sfb2015edge2.blah.local, Reason - Error code - 20000, Message - Unknown error - Error calling agent
sfb2015edge2.blah.local; Could not connect to net.tcp://sfb2015edge2.blah.local:50002/. The connection attempt
lasted for a time span of 00:00:20.9811488. TCP error code 10060: A connection attempt failed because the connected
party did not properly respond after a period of time, or established connection failed because connected host has
failed to respond 192.168.19.89:50002. . Please refer CLS logs for details. PoolFqdn: sfb2015edge2.blah.local
MachineFqdn ResponseMessage AlwaysOn ScenarioName Remaining ProductVersion
Mins
----------- --------------- -------- ------------ --------- --------------
sfb2015edge2.blah.local Error code - 20000, Message - 0 6.0.9319.0
Unknown error - Error calling
agent
sfb2015edge2.blah.local;
Could not connect to net.tcp:/
/sfb2015edge2.blah.local:5
0002/. The connection attempt
lasted for a time span of
00:00:20.9811488. TCP error
code 10060: A connection
attempt failed because the
connected party did not
properly respond after a
period of time, or
established connection failed
because connected host has
failed to respond
192.168.19.89:50002. . Please
refer CLS logs for details.
PS C:\Users\greig>
Continue reading ‘SfB Server 2016 Edge CLS not listening’ »