Lync and Outlook 2010 appcrash UCMapi64.exe error RRS feed

  • Question

  • Hi All,

    I have 4 end-users who are experiencing the same appcrash errors.  When they open Lync and Outlook they first receive "Microsoft Lync 2010 has stopped working".  The details for this are:

    Problem Event Name: APPCRASH

    Application Name: UcMapi64.exe

    Application Timestamp: 5243366c

    Fault Module Name: MSVCR90.dll

    The second error generates in outlook stating "Microsoft Lync 2010 exited without properly closing your Outlook data file C:\Users\firstname.lastname\appdata\local\microsoft\outlook\firstname.lastname@domain.com.ost".  Microsoft outlook must be restarted." 

    Name and domain are omitted for confidentiality.  We've tried to restart outlook and lync and it still comes up with the same 2 errors.  Should we attempt to remove their outlook profile from Mail? Or try reinstalling Lync 2010?

    Tuesday, March 10, 2015 7:46 PM

All replies

  • Oligaf,

    We too have began to see this happen in the past few days with multiple individual across multiple divisions within our infrastructure. Myself and a colleague of mine believe that the issue is related to a specific update. Which one, not yet sure. We have split up the task to try and burn the candles at both ends. He is doing a restoration on a machine to a date before the issue occurred, and going to systematically work in the updates one at a time to find the faulted update (if there is one). We believe this is the culprit.  We have uninstalled, re installed, systematic Lync updates, re-registering DLL files, wiping dead Reg Keys....   I will report back what we have found. If you will do the same, maybe together we can get this figured out. I also found this--https://social.technet.microsoft.com/Forums/lync/en-US/47223a0a-217d-407e-b4d7-3cbbe825a726/microsoft-lync-has-stopped-working-please-close-the-program?forum=ocsmanagement

    I have yet to give this a try...

    sorry for the lack of a hyperlink.. still waiting Technet account verification.

    Hopefully I will report back soon...


    • Edited by DB0wden Thursday, March 12, 2015 2:51 PM
    Thursday, March 12, 2015 2:49 PM
  • I have at least 2 or 3 people with the error message. They're using Outlook 2010 and Lync 2013. I suspect it's related to a Windows update, but of course there were 1,000 this month. I haven't been able to find any other people having this issue besides you.
    Thursday, March 12, 2015 7:24 PM
  • Add my company to the list of people experiencing this issue.  I have about 8 Lync 2010 & 2013 users that are seeing this error.  As others have said, it seems to be related to a Windows update.

    Friday, March 13, 2015 1:50 PM
  • What we're attempting to do now is add a few Win7 machines we took off the network awhile ago that haven't been updated in months.  We'll run the updates in small batches to see which one is causing the error.
    Monday, March 16, 2015 1:49 PM
  • I've had this problem with a few client machines starting last week. This error began occurring on our machines on the 6th.  All clients experiencing the issue are running Office H&B 2010; Lync is 2010 or 2013.

    I tried scanpst, deleting the .ost and letting it rebuild, and uninstall/reinstall Lync.  The only thing that has worked so far was to completely uninstall Office and Lync and reinstall.  On the first reinstall, the behavior persisted.  I uninstalled again and then deleted any and all Microsoft Office files and folders from the hard drive.  Reinstalled both one last time.  I noticed that the 64-bit versions were installed previously, so I switched to the 32-bit versions.  No problems for 3 days on the machine that got the reinstall.

    Glad to find this thread - thought I was the only one.

    Tuesday, March 17, 2015 12:48 PM
  • So it looks like KB3020338 is the cause of the errors.  We have uninstalled this update for all of our users.  Lync and Outlook no longer have the appcrash or .ost errors for any of them.  The update doesn't look too important for end-users just going off the support.microsoft arcticles.
    • Proposed as answer by xXentropyXx Thursday, March 26, 2015 12:33 PM
    Friday, March 20, 2015 6:48 PM
  • I followed Oligaf's advice and removed KB3020338 from three machines experiencing the issue.  That was over 48 hours ago, and they have had no issues since.
    Thursday, March 26, 2015 12:36 PM