I am having a problem with Skype for Business 2015 freezing as soon as i try to make or join an audio call. This is similar to the following problem.
https://social.technet.microsoft.com/Forums/office/en-US/b7c484af-d597-4f3e-9f1b-4b5a58c6e255/either-lync-2013-or-skype-for-business-crashed-right-after-making-audio-calljoin-meeting?forum=ocsclients
I am running a HP envy laptop, running windows 8.1. All other programs work fine.
My investigation tells me I am supposed to rollback drivers. Uh, I have lots of drivers, which ones? I assume audio and video, so I did. No luck. I then though the issue may be Office 365 itself so I completely removed all of O365 desktop software rebooted, then decided to try the 64 bit version. After a successful install, same problem with SfB. Crashes when trying to make a call.
My application log records the following.
The program lync.exe version 15.0.4737.1000 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.Process ID: 2508
Start Time: 01d0d0877ba856c8
Termination Time: 23
Application Path: C:\Program Files\Microsoft Office 15\root\office15\lync.exe
Report Id: 208a2e3b-3c7b-11e5-82bb-fcf8ae1a456d
Faulting package full name:
Faulting package-relative application ID:
I also enabled full logging within SfB and it does appear as though logs are being recorded to C:\Users\"myuser"\AppData\Local\Microsoft\Office\15.0\Lync\Tracing, but I am not sure who to send these to, nor can I read them myself? Seems like a silly logging system for MS, but that shouldn't shock anyone, least of which is me.
the problem started the same day that O365 forced an update on my laptop a few weeks back. I did not add any other hardware, nor did I install any hardware or driver updates that I know that could have caused any driver issues. My laptop works fine otherwise, and my sound system does work just fine with other competing products such as hangouts, gototmeeting, joinme, etc.
This appears to be squarely an issue that the SfB or O365 team caused with an update. Any ideas on who to send the logs to so that the ProdTeam can fix their bugs?
Thanks all.
Eric Overfield - PixelMill -ericoverfield.com - @EricOverfield