Skype Version 2 connectivity issues

%3CLINGO-SUB%20id%3D%22lingo-sub-183481%22%20slang%3D%22en-US%22%3ESkype%20Version%202%20connectivity%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-183481%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20SRSv2%20Logitech%20Smartdocks%2C.%26nbsp%3B%20Since%20last%20few%20days%20we%20are%20seeing%20a%20bug.%20I%20would%20like%20to%20know%20if%20any%20solution%20is%20available%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20a%20fairly%20regular%20experience%20where%20the%20units%20log%20out%20and%20won't%20log%20back%20in%20our%20one%20of%20the%20locations.%20%26nbsp%3BIt%20appears%20that%20if%20there%20is%20some%20problem%20in%20connectivity%20they%20don't%20try%20to%20reconnect.%20%26nbsp%3BA%20unit%20reboot%20always%20solves%20the%20problem%2C%20However%20we%20want%20to%20resolve%20this%20issue%20permanently%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBelow%20is%20what%20we%20find%20out%20in%20eventviewer%20logs%20on%20one%20of%20our%20system.%20Sometime%20we%20dont%20get%20the%20below%20logs%20and%20still%20system%20disconnects.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%7B%22Description%22%3A%22Network%20status%20%3A%20Healthy.%20Exchange%20status%20%3A%20Connected.%20Signin%20status%3A%20Unhealthy.%20We%20couldn't%20sign%20you%20in.%20There%20might%20be%20a%20problem%20with%20your%20credentials.%20Please%20contact%20your%20support%20team.%22%2C%22ResourceState%22%3A%22Unhealthy%22%2C%22OperationName%22%3A%22Heartbeat%22%2C%22OperationResult%22%3A%22Fail%22%2C%22OS%22%3A%22Windows%2010%22%2C%22OSVersion%22%3A%2210.0.15063.966%22%2C%22Alias%22%3A%22%22%2C%22DisplayName%22%3A%22%22%2C%22AppVersion%22%3A%223.1.100.0%22%2C%22IPv4Address%22%3A%2210.28.39.7%22%2C%22IPv6Address%22%3A%22%22%7D%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20description%20for%20Event%20ID%203001%20from%20source%20SRS-App%20cannot%20be%20found.%20Either%20the%20component%20that%20raises%20this%20event%20is%20not%20installed%20on%20your%20local%20computer%20or%20the%20installation%20is%20corrupted.%20You%20can%20install%20or%20repair%20the%20component%20on%20the%20local%20computer.%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20the%20event%20originated%20on%20another%20computer%2C%20the%20display%20information%20had%20to%20be%20saved%20with%20the%20event.%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20following%20information%20was%20included%20with%20the%20event%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%7B%22Description%22%3A%22Conference%20Microphone%20status%20%3A%20Healthy.%20Conference%20Speaker%20status%20%3A%20Healthy.%20Default%20Speaker%20status%20%3A%20Unhealthy.%20Camera%20status%20%3A%20Healthy.%20Front%20of%20Room%20Display%20status%20%3A%20Healthy.%20Motion%20Sensor%20status%20%3A%20Healthy.%20HDMI%20Ingest%20status%20%3A%20Healthy.%20%22%2C%22ResourceState%22%3A%22Unhealthy%22%2C%22OperationName%22%3A%22HardwareCheckEngine%22%2C%22OperationResult%22%3A%22Fail%22%2C%22OS%22%3A%22Windows%2010%22%2C%22OSVersion%22%3A%2210.0.15063.966%22%2C%22Alias%22%3A%22a.b%40domain.com%22%2C%22DisplayName%22%3A%22Conf%20room%22%2C%22AppVersion%22%3A%223.1.100.0%22%2C%22IPv4Address%22%3A%2210.28.39.7%22%2C%22IPv6Address%22%3A%22%22%7D%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-183481%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESkype%20for%20Business%20Adoption%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-217991%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Version%202%20connectivity%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-217991%22%20slang%3D%22en-US%22%3E%3CP%3EDid%20you%20ever%20find%20a%20fix%3F%20I%20still%20see%20this%20issue%20on%20the%20latest%20version%20of%20the%20app.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-190215%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Version%202%20connectivity%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-190215%22%20slang%3D%22en-US%22%3E%3CP%3ESkype%20room%20system%20logs%20show%20some%20errors.%20However%20from%20those%20errors%20we%20are%20not%20able%20to%20reach%20anywhere%20and%20find%20out%20if%20due%20to%20them%20the%20units%20disconnect%20from%20the%20network.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-190214%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Version%202%20connectivity%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-190214%22%20slang%3D%22en-US%22%3EStill%20we%20dont%20have%20a%20solution%20for%20this%20issue.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-190213%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Version%202%20connectivity%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-190213%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20logged%20a%20ticket%20with%20Microsoft%20to%20troubleshoot%20with%20them.%20It%20was%20closed%20after%20sometime%20due%20to%20some%20support%20issues.%20However%20the%20problem%20is%20still%20there%20and%20we%20are%20trying%20all%20different%20solutions%20as%20most%20of%20the%20units%20in%20my%20one%20location%20are%20only%20facing%20this%20problem.%20The%20second%20location%20doesnt%20show%20any%20issues%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-189061%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Version%202%20connectivity%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-189061%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20there%20been%20any%20solution%20to%20this%20issue%3F%20I%20am%20on%20the%20latest%20Windows%2C%20SfB%20app%2C%20and%20Logitech%20firmware%20updates%2C%20and%20I%20still%20have%20to%20reboot%20my%20devices%20to%20reconnect.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-184171%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Version%202%20connectivity%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-184171%22%20slang%3D%22en-US%22%3E%3CP%3EI%20see%20there%20are%20a%20small%20update.%20You%20have%26nbsp%3B%3CSPAN%3E3.1.100.0%3C%2FSPAN%3E%2C%20and%20the%20new%20version%20is%26nbsp%3B%3CSPAN%3E3.1.104.0.%20I%20would%20try%20updating%20first%2C%20but%20dont%20know%20whats%20fixed%20in%20this%20update.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAre%20these%20the%20eventviewer%20logs%3F%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EHave%20you%20taken%20a%20look%20at%20Skype%20Room%20System%20logs%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fskypeforbusiness%2Fmanage%2Fskype-room-systems-v2%2Fskype-room-systems-v2%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fskypeforbusiness%2Fmanage%2Fskype-room-systems-v2%2Fskype-room-systems-v2%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

We have SRSv2 Logitech Smartdocks,.  Since last few days we are seeing a bug. I would like to know if any solution is available

 

We have a fairly regular experience where the units log out and won't log back in our one of the locations.  It appears that if there is some problem in connectivity they don't try to reconnect.  A unit reboot always solves the problem, However we want to resolve this issue permanently

 

Below is what we find out in eventviewer logs on one of our system. Sometime we dont get the below logs and still system disconnects.

 

{"Description":"Network status : Healthy. Exchange status : Connected. Signin status: Unhealthy. We couldn't sign you in. There might be a problem with your credentials. Please contact your support team.","ResourceState":"Unhealthy","OperationName":"Heartbeat","OperationResult":"Fail","OS":"Windows 10","OSVersion":"10.0.15063.966","Alias":"","DisplayName":"","AppVersion":"3.1.100.0","IPv4Address":"10.28.39.7","IPv6Address":""}

 

The description for Event ID 3001 from source SRS-App cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

{"Description":"Conference Microphone status : Healthy. Conference Speaker status : Healthy. Default Speaker status : Unhealthy. Camera status : Healthy. Front of Room Display status : Healthy. Motion Sensor status : Healthy. HDMI Ingest status : Healthy. ","ResourceState":"Unhealthy","OperationName":"HardwareCheckEngine","OperationResult":"Fail","OS":"Windows 10","OSVersion":"10.0.15063.966","Alias":"a.b@domain.com","DisplayName":"Conf room","AppVersion":"3.1.100.0","IPv4Address":"10.28.39.7","IPv6Address":""}

6 Replies

I see there are a small update. You have 3.1.100.0, and the new version is 3.1.104.0. I would try updating first, but dont know whats fixed in this update. 

 

Are these the eventviewer logs? 

Have you taken a look at Skype Room System logs?

https://docs.microsoft.com/en-us/skypeforbusiness/manage/skype-room-systems-v2/skype-room-systems-v2

Has there been any solution to this issue? I am on the latest Windows, SfB app, and Logitech firmware updates, and I still have to reboot my devices to reconnect.

We logged a ticket with Microsoft to troubleshoot with them. It was closed after sometime due to some support issues. However the problem is still there and we are trying all different solutions as most of the units in my one location are only facing this problem. The second location doesnt show any issues

Still we dont have a solution for this issue.

Skype room system logs show some errors. However from those errors we are not able to reach anywhere and find out if due to them the units disconnect from the network.

Did you ever find a fix? I still see this issue on the latest version of the app.