(CLSAgent,CommandProcessor.Initialize:commandprocessor.cs(247))Exception. He was seeing the following message in the ETL log (which us mere mortals don’t have the ability to read and the real reason I’m writing this blog article): 29 TL_ERROR(TF_COMPONENT) 14CC.1728::-16:53:00.193.00000010 After doing some traces and pulling the ETL logs, the Microsoft Engineer got back with and asked how we had generated the certificate. I went round and round with this and ultimately had to open a case with Microsoft on it. PS C:\Windows\system32> netstat -an | findstr 5000* I should have seen the system listening on ports 50001-50003. When I went to the server and did a netstat, I saw that CLS was not actively listening. No connection could be made because the target machine actively The connection attempt lasted forĪ time span of 00:00:02.0228175. I would start up CLSLogger and when I attempted to start the scenario, I would get an error like this: WARNING: Failed on 1 agentsĪgent -, Reason - Error code - 20000, Message - Unknown error -Įrror calling agent Could not connect to I turned to my favorite tool for this, the CLSLogger which takes advantage of the Centralized Logging Service (CLS). We were experiencing some issues that necessitated us to do some logging on the Front-end servers. That said, recently I had the opportunity to get back in to the game and start a deployment for a large organization. I have been focused more on evangelism and speaking with different organizations that are thinking about deploying Skype for Business. I haven’t written a new post in a while as I have not been doing as many deployments lately.
0 Comments
Leave a Reply. |