Skype for Business crashes

I am using office 365 for business on a Windows 8.1 64 bit laptop (Lenovo Yoga).

Skype for Business is crashing. It starts up OK but then crashes soon after whilst I am using it to join/create a meeting. I am getting the following Application Error. I also from time to time get a Side by Side error. I have copied the details from the event viewer. I have run sxstrace for the side by side error and attached the logfile from that too. Can anyone suggestion what I can do to fix these errors? I don't really know what to do next.

The application error suggests a problem with MSVCR110.dll. The side by side error suggests a problem with UccApi.dll

The Application error is:

Faulting application name: lync.exe, version: 15.0.4711.1002, time stamp: 0x551a0d44

Faulting module name: MSVCR110.dll, version: 11.0.50727.1, time stamp: 0x5011aa2a

Exception code: 0xc0000409

Fault offset: 0x0009e1bf

Faulting process id: 0x15e8

Faulting application start time: 0x01d08f04f825d05e

Faulting application path: C:\Program Files\Microsoft Office 15\root\office15\lync.exe

Faulting module path: C:\Program Files\Microsoft Office 15\root\office15\MSVCR110.dll

Report Id: 7af39866-faf8-11e4-bedf-fd68fef01223

Faulting package full name:

Faulting package-relative application ID:

The  details of the side by side error are:

Activation context generation failed for "C:\Program Files\Microsoft Office 15\root\office15\lync.exe.Manifest".Error in manifest or policy file "C:\Program Files\Microsoft Office 15\root\office15\UccApi.DLL" on line 1. Component identity found in manifest does not match the identity of the component requested. Reference is UccApi,processorArchitecture="AMD64",type="win32",version="15.0.0.0". Definition is UccApi,processorArchitecture="x86",type="win32",version="15.0.0.0". Please use sxstrace.exe for detailed diagnosis.

An extract from the sxs trace is below:

=================
Begin Activation Context Generation.
Input Parameter:
 Flags = 0
 ProcessorArchitecture = AMD64
 CultureFallBacks = en-US;en
 ManifestPath = C:\Program Files\Microsoft Office 15\root\office15\lync.exe.Manifest
 AssemblyDirectory = C:\Program Files\Microsoft Office 15\root\office15\
 Application Config File =
-----------------
INFO: Parsing Manifest File C:\Program Files\Microsoft Office 15\root\office15\lync.exe.Manifest.
 INFO: Manifest Definition Identity is Lync,processorArchitecture="*",type="win32",version="15.0.0.0".
 INFO: Reference: UccApi,processorArchitecture="*",type="win32",version="15.0.0.0"
INFO: Resolving reference UccApi,processorArchitecture="*",type="win32",version="15.0.0.0".
 INFO: Resolving reference for ProcessorArchitecture AMD64.
  INFO: Resolving reference for culture Neutral.
   INFO: Applying Binding Policy.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:\Program Files\Microsoft Office 15\root\office15\UccApi.DLL.
    INFO: Manifest found at C:\Program Files\Microsoft Office 15\root\office15\UccApi.DLL.
   INFO: End assembly probing.
INFO: Resolving reference UccApi.mui,language="*",processorArchitecture="AMD64",type="win32",version="15.0.0.0".
 INFO: Resolving reference for ProcessorArchitecture AMD64.
  INFO: Resolving reference for culture en-US.
   INFO: Applying Binding Policy.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Did not find manifest for culture en-US.
   INFO: End assembly probing.
  INFO: Resolving reference for culture en.
   INFO: Applying Binding Policy.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Did not find manifest for culture en.
   INFO: End assembly probing.
INFO: Parsing Manifest File C:\Program Files\Microsoft Office 15\root\office15\UccApi.DLL.
 INFO: Manifest Definition Identity is UccApi,processorArchitecture="x86",type="win32",version="15.0.0.0".
 ERROR: Component identity found in manifest does not match the identity of the component requested. Reference is UccApi,processorArchitecture="AMD64",type="win32",version="15.0.0.0". Definition is UccApi,processorArchitecture="x86",type="win32",version="15.0.0.0".
ERROR: Activation Context generation failed.
End Activation Context Generation.

May 15th, 2015 11:52am

have you installaed all required updates? Not only the skype updates?

https://greiginsydney.com/lync-2013-client-update-to-skype-for-business-april-2015/

Free Windows Admin Tool Kit Click here and download it now
May 15th, 2015 4:08pm

Hi,

1. Rollback the Sound Card, VGA Device/Video Card, Graphic Card to which Windows applied. Then restart SFB.

2. Make sure SFB update to the latest version.

Best Regards,
Eason Huang

May 18th, 2015 3:31am

Thanks for both of the suggestions above.

I am on Office 365 and updates install automatically so I cannot see any SFB updates. I have carried out a manual update of Office which has taken me from version 15.0.4711.1003 to 15.0.4719.1002.

I installed Windows update KB3022345 which I discovered had been failing. I ran DISM to fix the failure. I have rolled back the sound/video and graphic cards.

I have started up a meeting and it seems to be running OK so far. I would like to wait until I use SFB for real to properly check that it is working OK. I will keep this thread open another day or two and if all seems ok close it.

Thanks for the help

Ian

Free Windows Admin Tool Kit Click here and download it now
May 18th, 2015 5:30am

It seems to be working now, no more crashes. Not sure which of the changes above fixed it but all OK.
  • Marked as answer by ISB100 17 hours 10 minutes ago
May 22nd, 2015 10:16am

It seems to be working now, no more crashes. Not sure which of the changes above fixed it but all OK.
  • Marked as answer by ISB100 Friday, May 22, 2015 2:16 PM
Free Windows Admin Tool Kit Click here and download it now
May 22nd, 2015 2:15pm

It seems to be working now, no more crashes. Not sure which of the changes above fixed it but all OK.
  • Marked as answer by ISB100 Friday, May 22, 2015 2:16 PM
May 22nd, 2015 2:15pm

It seems to be working now, no more crashes. Not sure which of the changes above fixed it but all OK.
  • Marked as answer by ISB100 Friday, May 22, 2015 2:16 PM
Free Windows Admin Tool Kit Click here and download it now
May 22nd, 2015 2:15pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics