Lync 2013 aborts (crashes) after call is terminated

Computer is on a network. Desktop is running Win 7 64 bit with lync 2013. When the user terminates a call lync aborts and asks if user wants to restart Lync. I believe this is profile related as I logged on as myself with my credentials and could not
make the same issue happen.  The user also logged into a different computer and worked fine. Did not crash after ending a call. This issue just started as the user has been with this computer for quite some time with no issues before now.
Is there a fix for the user profile?
Thanks

You can enable log on phone device, then check if the phone got the BYE signal in log file.
The log files are stored on the Lync filestore associated with the pool where the user logged into the phone hosted. Should be something like 
\\fileserver\LyncShare\*WebServices*\DeviceUpdateLogs\...
Lisa Zheng
TechNet Community Support

Similar Messages

  • Lync 2013 Mobility Client - Video Call Issue (Everything Else works).

    Hey Technet’ies,
    I have been struggling for a couple of weeks now to resolve one of the final issues with a Migration/Upgrade Project on Lync Server 2013.
    I have nearly every Lync Client Scenario working well except the Mobility Client (outside of the domain) which cannot successfully complete a Video
    Call to a Windows Desktop Client (inside the domain) – the toast pops up, but when we click accept - it just times out after 15 seconds
    K
    The strange thing is every other Video Call scenario works;
    Mobility Client (Outside Domain)
    àWindows Desktop Client (Inside Domain)
    = Unsuccessful
    Mobility Client (Inside Domain)
    à Windows Desktop Client (Inside Domain) = Successful
    Mobility Client (Inside Domain)
    à Windows Desktop Client (Outside Domain) = Successful
    Mobility Client (Outside Domain)
    à Windows Desktop Client (Outside Domain) = Successful
    Mobility Client (Inside Domain)
    à Mac Desktop Client (Inside Domain) = Successful
    Mobility Client (Inside Domain)
    à Mac Desktop Client (Outside Domain) = Successful
    Mobility Client (Outside Domain)
    à Mac Desktop Client (Outside Domain) = Successful
    Mobility Client (Outside Domain)
    à Mac Desktop Client (Inside Domain) = Successful
    Mobility Client (All Scenarios)
    à Mobility Client (All Scenarios) = Successful
    Our setup is pretty standard;
    All OS servers are Win Server 2012 R2
    Lync 2013 Standard FE Server
    Lync 2013 Edge Server
    Reverse Proxy IIS AAR (Also Win Server 20012 R2)
    Lync 2013 Desktop Clients, Lync 2011 Mac Clients, IOS and Android Mobility Clients – all latest versions.
    External NAT (via Cisco Routers ACL’s)
    Internal Windows Firewall Currently off on all Servers
    All Certs / DNS Configured as per Technet Recommendation
    I have reviewed / analysed a number of log/trace files – looking for some/any information on the problem;
    Mobility Client (cmlogX.log)
    Windows Desktop Client (*.etl) / Microsoft Message Analyzer
    Lync 2013 Server (CSController)
    With all my looking I could not make out an error except a timeout (15 seconds) on the Mobility Client log (which I currently can’t find).
    Clearly we are missing something and I have gone up and down our implementation a number of times, the only semi-unknown is our old 2010 Pool / Central Management Server (which is currently pretty much redundant but the majority of users still on).
    I would really appreciate any feedback anyone can provide or any insight anyone may have on this challenge.
    Thanks in advance, Alex.
    Alex

    Hi Andrew,
    Thanks for the quick contact!!
    Sorry - typo in my post, I have now corrected it;
    Mobility
    Client (Outside Domain) àWindows
    Desktop Client (Inside Domain) = Unsuccessful
    So I completely missed that blog post of yours (out of the 100's I have read) and you are the first person to clearly say (in simple terms) to point the lyncweb.contso.com to the public IP address on my internal DNS, I have just made that change and see
    if it will correct the issue - will wait for replication. 
    Also I am running IIS / AAR as Reverse Proxy (not ISA) and had the Internal DNS Host A of lyncweb.contso.com and lyncdiscover.contso.com point back to my Reverse Proxy Internal NIC (i.e. 10.1.1.32) as the External NIC is isolated on in the Perimeter Network,
    is this correct?
    So it now goes like this
    *Inside Domain*
    lyncdiscover.contson.com --> 10.1.1.32 (Reverse Proxy Internal Nic) --> 10.1.1.26 (Front End Server)
    lyncweb.contson.com --> 201.183.0.1 (Reverse Proxy External Nic - Public IP) --> 10.1.2.16 (Reverse Proxy External Nic) --> 10.1.1.26 (Front End Server)
    Does this make any sense, I know ISA and IIS/AAR are pretty much interchangeable.
    Thanks again Andrew and look forward to any feedback,
    Alex.
    Alex

  • How do I enable users to attend on Lync 2013 meeting on Windows 2008 R2 Terminal Services/XenApp 6?

    Hi,
    We are not using Lync internally. But some of my users need to attend Lync 2013 meetings. We run a Windows 2008 R2 Terminal Services/XenApp environment. Users are not allowed to install applications.
    In the past, I was able to install administratively a Lync 2010 attendee client.
    How do I enable my users to attend a Lync 2013 meeting?
    Thanks.

    This is not viable. I don't know which user is going to be attending Lync meetings from suppliers or customers ahead of time and have no contacts to request a test meeting. This is a loop. How does Microsoft expect sysadmins to support their products if
    the client software is not easily available.
    At this point if I have a user who needs this, I will only know about it after the meeting has failed. At that point the user is not very receptive to the idea of involving his contact in troubleshooting and setting up test meetings. It's even worse if it's
    an executive.
    Is there any way of pre-installing the pre-requisites for attending Lync 2013 meetings?
    My only choice is to inform my user community that we have no way of supporting Lync and request that they use GotoMeeting or WebEx with their contacts who try to do a Lync meeting.
    I am very disappointed in Microsoft's approach with Lync 2013.
    Thanks for your time.

  • Lync 2013 updating databases after updating Front End servers

    We have a front-end server pool consisting of 3 Lync 2013 servers and a back end of 2 SQL servers using SQL mirroring.  All servers are Windows 2008 R2.
    Following the instructions in
    http://support2.microsoft.com/kb/2809243 , I verified that the servers were all ready for updates, then I ran the
    Stop-CsWindowsService -Graceful cmdlet to stop the Lync services on the first FE server, then I ran LyncServerUpdateInstaller.exe to install the updates.  After the updates were installed, I restarted the server, waited for Lync services
    to all start, then repeated the process on the next 2 servers in turn.  This was all successful.
    I am now looking at step 2 in this document, applying the back-end database updates, and I have a problem and some questions.  The problem is that all the databases had the principal copy on the mirrored SQL server.  I ran the recommended Invoke-CsDatabaseFailover
    -NewPrincipal Primary cmdlet repeatedly, using all the database types I could find, but I still have two databases (database names
    xds and lis) on the mirrored server.  Since the cmdlet requires a database type, what type of databases are the xds and the lis databases?
    Once I get that done, I an still unsure of exactly what to run to update the databases.  The KB article states to run Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn FEBE.FQDN -Verbose .  Do I type this in exactly
    as stated, or is FEBE.FQDN a variable for our SQL server or some other entity in our environment?  If I do use the actual SQL Server name in that, do I run it twice, using the name of the mirrored SQL server the second time?  
    Thank you very much for your help.

    Hi Logan Burt,
    Central Management store database files
    Data file or log purpose
                    Xds.ldf
    Transaction log file for the Central Management store
                    Xds.mdf
    Maintains the configuration of the current Lync Server 2013 topology, as defined and published by Topology Builder
                    Lis.mdf
    Location Information service data file
                    Lis.ldf
    Transaction log for the Location Information service data file
    And you could verify if Lync Server 2013 database updates have completed successfully.
    How to Verify if Lync Server 2013 Database Updates Completed Successfully
    http://blogs.technet.com/b/dodeitte/archive/2013/07/02/how-to-verify-if-lync-server-2013-database-updates-completed-successfully.aspx
    Best regards,
    Eric

  • Lync 2013 Client crashes

    Eventlog message:
    Faulting application name: lync.exe, version: 15.0.4420.1017, time stamp: 0x5067326f
    Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time stamp: 0x51fb1116
    Exception code: 0xc0000017
    Fault offset: 0x0000c41f
    Faulting process id: 0x2918
    Faulting application start time: 0x01cecb1ab5a8cccf
    Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
    Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
    Report Id: 5806ca39-372c-11e3-af61-002618927526
    We are having this on a few lync clients.  The crashes are at random, a few times per day.  Generally happens when the client is idle.  Windows 7 systems, with the latest version of the client. (15.0.4517.1504)Any ideas?

    Hi Everett.Chris,
    Did you solve the issue with the suggestion Waqas105 provided?
    Did you install Bluetooth on your computer? If yes, please remove it and test the issue again.
    Please also make sure you remove all instances of the Lync 2013 Security Update KB2817465.
    If the issue persists, please past the entire log or message when Lync client crashes so that we know which file cause the issue.
    Best Regards,
    Eason Huang
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Lync 2013 SQL Permission after install

    We have started to install Lync 2013 Enterprise to replace our Lync 2010 Standard servers.  Since we are moving to enterprise I've had to ask the SQL dba to get envolved with the installation.  We followed the recommended permission document here..
    http://technet.microsoft.com/en-us/library/gg398375.aspx
    we gave the install account Sysadmin and local admin on the SQL server.
    Now that the install is complete our dba wants to remove sysadmin from the account and remove it from SQL. 
    Can we do that or does it need to stay in place?
    Thanks,
    Matt

    Hi Matt,
    You should be able to remove it now that the databases have been created as it should only be required for installation. You just need to make sure that your users accounts for management are part of the appropriate RBAC groups.
    The only caveat I can think of is if you need to do some SQL configuration tasks like deploy mirroring or run an update that may need to drop and rebuild the database. In those scenario you would need to have it reapplied.
    If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer"
    Georg Thomas | Lync MVP
    Blog www.lynced.com.au | Twitter
    @georgathomas
    Lync Edge Port Check (Beta)

  • Lync 2013 meet now dropping calls

    Hello,
    We have migrated from Lync 2010 to Lync 2013 and all the users are using Lync 2010 clients. We have tested meet now between external and federated users and seems to work fine. However internal users o federated users keep on getting dropped off and are
    requested to rejoin,when they try rejoining it doesn't work.
    Thanks

    Did decommission the Lync 2010 pool?
    Please check if you have the same problem in internal conferencing.
    Check if you have the same problem in a conferencing with internal users and externals without federated users.
    Please check the certificates on Lync Front End and Edge Server are configuration correctly.
    Lisa Zheng
    TechNet Community Support

  • Lync 2013 stopped working after update

    Lync starts up fine, but when I click a contact or receive a message, Lync crashes
    I already updated and repaired office.
    I do have office 2010 and 2013 installed, but 2010 doesn't have Lync so there shouldn't be a conflict there.
    Event logs:
    Log Name:      Application
    Source:        Application Error
    Date:          16/10/2014 11:40:51
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      TSS-DXCSJX1.teu.tomra.corp
    Description:
    Faulting application name: lync.exe, version: 15.0.4659.1001, time stamp: 0x5423b435
    Faulting module name: lync.exe, version: 15.0.4659.1001, time stamp: 0x5423b435
    Exception code: 0xc0000005
    Fault offset: 0x00e70000
    Faulting process id: 0x1740
    Faulting application start time: 0x01cfe9254143f6df
    Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
    Faulting module path: C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
    Report Id: 83b07477-5518-11e4-bdc0-005056c00008
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-16T09:40:51.000000000Z" />
        <EventRecordID>104534</EventRecordID>
        <Channel>Application</Channel>
        <Computer>TSS-DXCSJX1.teu.tomra.corp</Computer>
        <Security />
      </System>
      <EventData>
        <Data>lync.exe</Data>
        <Data>15.0.4659.1001</Data>
        <Data>5423b435</Data>
        <Data>lync.exe</Data>
        <Data>15.0.4659.1001</Data>
        <Data>5423b435</Data>
        <Data>c0000005</Data>
        <Data>00e70000</Data>
        <Data>1740</Data>
        <Data>01cfe9254143f6df</Data>
        <Data>C:\Program Files (x86)\Microsoft Office\Office15\lync.exe</Data>
        <Data>C:\Program Files (x86)\Microsoft Office\Office15\lync.exe</Data>
        <Data>83b07477-5518-11e4-bdc0-005056c00008</Data>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        SideBySide
    Date:          16/10/2014 11:40:43
    Event ID:      35
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      TSS-DXCSJX1.teu.tomra.corp
    Description:
    Activation context generation failed for "C:\Program Files (x86)\Microsoft Office\Office15\lync.exe.Manifest".Error in manifest or policy file "C:\Program Files (x86)\Microsoft Office\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.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="SideBySide" />
        <EventID Qualifiers="49409">35</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-16T09:40:43.000000000Z" />
        <EventRecordID>104515</EventRecordID>
        <Channel>Application</Channel>
        <Computer>TSS-DXCSJX1.teu.tomra.corp</Computer>
        <Security />
      </System>
      <EventData>
        <Data>UccApi,processorArchitecture="AMD64",type="win32",version="15.0.0.0"</Data>
        <Data>UccApi,processorArchitecture="x86",type="win32",version="15.0.0.0"</Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>C:\Program Files (x86)\Microsoft Office\Office15\lync.exe.Manifest</Data>
        <Data>C:\Program Files (x86)\Microsoft Office\Office15\UccApi.DLL</Data>
        <Data>1</Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    Same error here. I just had to re-install windows so it installed a good 300+ updates and no way to know which one could have been the culprit. 
    Alexander, do you know what update (KBXXXXXXX) you recently installed? 
    Here is my error:
    Activation context generation failed for "C:\Program Files (x86)\Microsoft Office\Office15\lync.exe.Manifest".Error in manifest or policy file "C:\Program Files (x86)\Microsoft Office\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.
    System
    Provider
    [ Name]
    SideBySide
    EventID
    35
    [ Qualifiers]
    49409
    Level
    2
    Task
    0
    Keywords
    0x80000000000000
    TimeCreated
    [ SystemTime]
    2014-10-17T13:55:56.000000000Z
    EventRecordID
    3786
    Channel
    Application
    Computer
    SERVECIG
    Security
    EventData
    UccApi,processorArchitecture="AMD64",type="win32",version="15.0.0.0"
    UccApi,processorArchitecture="x86",type="win32",version="15.0.0.0"
    C:\Program Files (x86)\Microsoft Office\Office15\lync.exe.Manifest
    C:\Program Files (x86)\Microsoft Office\Office15\UccApi.DLL
    1

  • Lync 2013 Client crashes when searching for a specific user

     We are using Lync client version 15.0.4569.1503
    When typing "Singh" into the search field, Lync crashes with the error message:
    Microsoft Lync has stopped working. Windows is checking for a solution to the problem.
    This is happening for all users in the enterprise who search for Singh.
    In Event Viewer, Application Error 1000 is logged:
    Faulting application name: lync.exe, version: 15.0.4569.1503, time stamp: 0x52b0af33Faulting module name: Uc.dll, version: 15.0.4569.1503, time stamp: 0x52b0b5c4Exception code: 0xc0000005Fault offset: 0x00007c3aFaulting process id: 0x3dcFaulting application start time: 0x01cfa5ae6c1d6266Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\lync.exeFaulting module path: C:\Program Files (x86)\Microsoft Office\Office15\Uc.dllReport Id: aba6fa46-11a1-11e4-9f53-18037341ac8d
    The WER file contains the following:
    Version=1
    EventType=APPCRASH
    EventTime=130505075954941334
    ReportType=2
    Consent=1
    UploadTime=130505075956121334
    ReportIdentifier=135567f7-11a0-11e4-9f53-18037341ac8d
    IntegratorReportIdentifier=135567f6-11a0-11e4-9f53-18037341ac8d
    WOW64=1
    Response.BucketId=106444627
    Response.BucketTable=17
    Response.type=4
    Sig[0].Name=Application Name
    Sig[0].Value=lync.exe
    Sig[1].Name=Application Version
    Sig[1].Value=15.0.4569.1503
    Sig[2].Name=Application Timestamp
    Sig[2].Value=52b0af33
    Sig[3].Name=Fault Module Name
    Sig[3].Value=Uc.dll
    Sig[4].Name=Fault Module Version
    Sig[4].Value=15.0.4569.1503
    Sig[5].Name=Fault Module Timestamp
    Sig[5].Value=52b0b5c4
    Sig[6].Name=Exception Code
    Sig[6].Value=c0000005
    Sig[7].Name=Exception Offset
    Sig[7].Value=00007c3a
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=6.1.7601.2.1.0.256.4
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=2057
    UI[2]=C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
    UI[3]=Microsoft Lync has stopped working
    UI[4]=Windows can check online for a solution to the problem and try to restart the program.
    UI[5]=Check online for a solution and restart the program
    UI[6]=Check online for a solution later and close the program
    UI[7]=Close the program
    LoadedModule[0]=C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
    LoadedModule[1]=C:\windows\SysWOW64\ntdll.dll
    LoadedModule[2]=C:\windows\syswow64\kernel32.dll
    LoadedModule[3]=C:\windows\syswow64\KERNELBASE.dll
    LoadedModule[4]=C:\windows\syswow64\ADVAPI32.dll
    LoadedModule[5]=C:\windows\syswow64\msvcrt.dll
    LoadedModule[6]=C:\windows\SysWOW64\sechost.dll
    LoadedModule[7]=C:\windows\syswow64\RPCRT4.dll
    LoadedModule[8]=C:\windows\syswow64\SspiCli.dll
    LoadedModule[9]=C:\windows\syswow64\CRYPTBASE.dll
    LoadedModule[10]=C:\windows\syswow64\ole32.dll
    LoadedModule[11]=C:\windows\syswow64\GDI32.dll
    LoadedModule[12]=C:\windows\syswow64\USER32.dll
    LoadedModule[13]=C:\windows\syswow64\LPK.dll
    LoadedModule[14]=C:\windows\syswow64\USP10.dll
    LoadedModule[15]=C:\windows\syswow64\OLEAUT32.dll
    LoadedModule[16]=C:\windows\system32\MSVCR100.dll
    LoadedModule[17]=C:\Program Files (x86)\Microsoft Office\Office15\LyncModelProxy.dll
    LoadedModule[18]=C:\Program Files (x86)\Microsoft Office\Office15\PropertyModel.dll
    LoadedModule[19]=C:\windows\system32\MSVCP100.dll
    LoadedModule[20]=C:\Program Files (x86)\Microsoft Office\Office15\PropertyModelProxy.dll
    LoadedModule[21]=C:\Program Files (x86)\Microsoft Office\Office15\LyncDesktopViewModel.dll
    LoadedModule[22]=C:\windows\system32\MSIMG32.dll
    LoadedModule[23]=C:\windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18455_none_72d576ad8665e853\gdiplus.dll
    LoadedModule[24]=C:\windows\system32\DWrite.dll
    LoadedModule[25]=C:\Program Files (x86)\Microsoft Office\Office15\RtmMvrAs.dll
    LoadedModule[26]=C:\windows\system32\MSVCR110.dll
    LoadedModule[27]=C:\Program Files (x86)\Microsoft Office\Office15\RtmPal.dll
    LoadedModule[28]=C:\windows\system32\WINMM.dll
    LoadedModule[29]=C:\windows\syswow64\WS2_32.dll
    LoadedModule[30]=C:\windows\syswow64\NSI.dll
    LoadedModule[31]=C:\windows\syswow64\PSAPI.DLL
    LoadedModule[32]=C:\windows\system32\POWRPROF.dll
    LoadedModule[33]=C:\windows\syswow64\SETUPAPI.dll
    LoadedModule[34]=C:\windows\syswow64\CFGMGR32.dll
    LoadedModule[35]=C:\windows\syswow64\DEVOBJ.dll
    LoadedModule[36]=C:\windows\system32\pdh.dll
    LoadedModule[37]=C:\windows\system32\MSVCP110.dll
    LoadedModule[38]=C:\windows\system32\IPHLPAPI.DLL
    LoadedModule[39]=C:\windows\system32\WINNSI.DLL
    LoadedModule[40]=C:\Program Files (x86)\Microsoft Office\Office15\dbghelp.dll
    LoadedModule[41]=C:\windows\system32\bcrypt.dll
    LoadedModule[42]=C:\windows\system32\WTSAPI32.dll
    LoadedModule[43]=C:\windows\system32\PROPSYS.dll
    LoadedModule[44]=C:\Program Files (x86)\Microsoft Office\Office15\RtmCodecs.dll
    LoadedModule[45]=C:\windows\system32\d3d11.dll
    LoadedModule[46]=C:\windows\system32\dxgi.dll
    LoadedModule[47]=C:\windows\system32\VERSION.dll
    LoadedModule[48]=C:\windows\system32\dwmapi.dll
    LoadedModule[49]=C:\windows\system32\d3d9.dll
    LoadedModule[50]=C:\windows\system32\d3d8thk.dll
    LoadedModule[51]=C:\windows\system32\dxva2.dll
    LoadedModule[52]=C:\windows\syswow64\IMM32.dll
    LoadedModule[53]=C:\windows\syswow64\MSCTF.dll
    LoadedModule[54]=C:\windows\system32\UIAutomationCore.DLL
    LoadedModule[55]=C:\windows\system32\OLEACC.dll
    LoadedModule[56]=C:\Program Files (x86)\Common Files\Microsoft Shared\Office15\mso.dll
    LoadedModule[57]=C:\windows\system32\d2d1.dll
    LoadedModule[58]=C:\windows\system32\uxtheme.dll
    LoadedModule[59]=C:\windows\system32\WINSTA.dll
    LoadedModule[60]=C:\windows\syswow64\WINTRUST.dll
    LoadedModule[61]=C:\windows\syswow64\CRYPT32.dll
    LoadedModule[62]=C:\windows\syswow64\MSASN1.dll
    LoadedModule[63]=C:\windows\syswow64\SHELL32.dll
    LoadedModule[64]=C:\windows\syswow64\SHLWAPI.dll
    LoadedModule[65]=C:\Program Files (x86)\Microsoft Office\Office15\Uc.dll
    LoadedModule[66]=C:\Program Files (x86)\Microsoft Office\Office15\RtmMvrCs.dll
    LoadedModule[67]=C:\windows\system32\WINSPOOL.DRV
    LoadedModule[68]=C:\windows\system32\HID.DLL
    LoadedModule[69]=C:\windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\Comctl32.dll
    LoadedModule[70]=C:\windows\syswow64\CLBCatQ.DLL
    LoadedModule[71]=C:\windows\system32\msi.dll
    LoadedModule[72]=C:\Program Files (x86)\Microsoft Office\Office15\1033\lyncDesktopResources.dll
    LoadedModule[73]=C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE15\adal.dll
    LoadedModule[74]=C:\windows\system32\WINHTTP.dll
    LoadedModule[75]=C:\windows\system32\webio.dll
    LoadedModule[76]=C:\windows\syswow64\WININET.dll
    LoadedModule[77]=C:\windows\syswow64\Normaliz.dll
    LoadedModule[78]=C:\windows\syswow64\iertutil.dll
    LoadedModule[79]=C:\windows\syswow64\urlmon.dll
    LoadedModule[80]=C:\windows\system32\Secur32.dll
    LoadedModule[81]=C:\windows\system32\DavClnt.DLL
    LoadedModule[82]=C:\windows\system32\DAVHLPR.dll
    LoadedModule[83]=C:\windows\System32\netprofm.dll
    LoadedModule[84]=C:\windows\System32\nlaapi.dll
    LoadedModule[85]=C:\windows\system32\CRYPTSP.dll
    LoadedModule[86]=C:\windows\system32\rsaenh.dll
    LoadedModule[87]=C:\windows\system32\RpcRtRemote.dll
    LoadedModule[88]=C:\windows\System32\npmproxy.dll
    LoadedModule[89]=C:\windows\system32\webservices.dll
    LoadedModule[90]=C:\windows\system32\d3d10_1.dll
    LoadedModule[91]=C:\windows\system32\d3d10_1core.dll
    LoadedModule[92]=C:\windows\system32\D3D10Warp.dll
    LoadedModule[93]=C:\windows\system32\dhcpcsvc6.DLL
    LoadedModule[94]=C:\windows\system32\dhcpcsvc.DLL
    LoadedModule[95]=C:\windows\system32\credssp.dll
    LoadedModule[96]=C:\windows\system32\mswsock.dll
    LoadedModule[97]=C:\windows\System32\wshtcpip.dll
    LoadedModule[98]=C:\windows\System32\wship6.dll
    LoadedModule[99]=C:\windows\system32\DNSAPI.dll
    LoadedModule[100]=C:\windows\system32\rasadhlp.dll
    LoadedModule[101]=C:\windows\System32\fwpuclnt.dll
    LoadedModule[102]=C:\windows\SysWOW64\msv1_0.DLL
    LoadedModule[103]=C:\windows\system32\cryptdll.dll
    LoadedModule[104]=C:\windows\SysWOW64\schannel.dll
    LoadedModule[105]=C:\windows\system32\ncrypt.dll
    LoadedModule[106]=C:\windows\SysWOW64\bcryptprimitives.dll
    LoadedModule[107]=C:\windows\system32\USERENV.dll
    LoadedModule[108]=C:\windows\system32\profapi.dll
    LoadedModule[109]=C:\windows\system32\GPAPI.dll
    LoadedModule[110]=C:\Program Files (x86)\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\osppc.dll
    LoadedModule[111]=C:\windows\system32\ntmarta.dll
    LoadedModule[112]=C:\windows\syswow64\WLDAP32.dll
    LoadedModule[113]=C:\Program Files (x86)\Microsoft Office\Office15\UccApi.dll
    LoadedModule[114]=C:\Program Files (x86)\Microsoft Office\Office15\Win32MsgQueue.dll
    LoadedModule[115]=C:\windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_ec80f00e8593ece5\Comctl32.dll
    LoadedModule[116]=C:\Program Files (x86)\Microsoft Office\Office15\1033\ocapires.dll
    LoadedModule[117]=C:\Program Files (x86)\Microsoft Office\Office15\Psom.dll
    LoadedModule[118]=C:\windows\System32\msxml6.dll
    LoadedModule[119]=C:\Program Files (x86)\Microsoft Office\Office15\OcImport.DLL
    LoadedModule[120]=C:\Program Files (x86)\Microsoft Office\Office15\ocrec.dll
    LoadedModule[121]=C:\windows\system32\mlang.dll
    LoadedModule[122]=C:\windows\system32\windowscodecs.dll
    LoadedModule[123]=C:\Program Files (x86)\Microsoft Office\Office15\RtmMediaManager.dll
    LoadedModule[124]=C:\windows\system32\AVRT.DLL
    LoadedModule[125]=C:\Program Files (x86)\Microsoft Office\Office15\AppSharingMediaProvider.dll
    LoadedModule[126]=C:\Program Files (x86)\Microsoft Office\Office15\RTMPLTFM.dll
    LoadedModule[127]=C:\windows\system32\wlanapi.dll
    LoadedModule[128]=C:\windows\system32\wlanutil.dll
    LoadedModule[129]=C:\windows\System32\MMDevApi.dll
    LoadedModule[130]=C:\windows\system32\MFPlat.dll
    LoadedModule[131]=C:\Windows\SysWOW64\devenum.dll
    LoadedModule[132]=C:\windows\system32\msdmo.dll
    LoadedModule[133]=C:\Program Files (x86)\Common Files\Intel\Media SDK\i2\3.0\mfx_mft_h264ve_32.dll
    LoadedModule[134]=C:\windows\system32\EVR.dll
    LoadedModule[135]=C:\windows\system32\MF.dll
    LoadedModule[136]=C:\windows\system32\ATL.DLL
    LoadedModule[137]=C:\windows\system32\ksuser.dll
    LoadedModule[138]=C:\windows\system32\WinSATAPI.dll
    LoadedModule[139]=C:\windows\system32\AUDIOSES.DLL
    LoadedModule[140]=C:\Program Files (x86)\Microsoft Office\Office15\RdpQoEMetrics.dll
    LoadedModule[141]=C:\windows\system32\XmlLite.dll
    LoadedModule[142]=C:\windows\SysWOW64\SFC.DLL
    LoadedModule[143]=C:\windows\system32\sfc_os.DLL
    LoadedModule[144]=C:\windows\SysWOW64\SXS.DLL
    LoadedModule[145]=C:\Program Files (x86)\Microsoft Office\Office15\sqmapi.dll
    LoadedModule[146]=C:\Program Files (x86)\Microsoft Office\Office15\lynchtmlconvpxy.dll
    LoadedModule[147]=C:\windows\system32\explorerframe.dll
    LoadedModule[148]=C:\windows\system32\DUser.dll
    LoadedModule[149]=C:\windows\system32\DUI70.dll
    LoadedModule[150]=C:\Program Files (x86)\Common Files\Microsoft Shared\Office15\riched20.dll
    LoadedModule[151]=C:\windows\system32\RASAPI32.dll
    LoadedModule[152]=C:\windows\system32\rasman.dll
    LoadedModule[153]=C:\windows\system32\rtutils.dll
    LoadedModule[154]=C:\windows\system32\sensapi.dll
    LoadedModule[155]=C:\windows\system32\apphelp.dll
    LoadedModule[156]=C:\windows\system32\cryptnet.dll
    LoadedModule[157]=C:\windows\SysWOW64\Kerberos.DLL
    LoadedModule[158]=C:\windows\system32\LOGONCLI.DLL
    LoadedModule[159]=C:\windows\system32\DSROLE.DLL
    LoadedModule[160]=C:\windows\system32\NETUTILS.DLL
    LoadedModule[161]=C:\windows\system32\NTDSAPI.DLL
    LoadedModule[162]=C:\windows\system32\inetcomm.dll
    LoadedModule[163]=C:\windows\system32\MSOERT2.dll
    LoadedModule[164]=C:\windows\system32\inetres.dll
    LoadedModule[165]=C:\windows\system32\igd10umd32.dll
    LoadedModule[166]=C:\Users\b6600\AppData\Local\LogMeIn Rescue Applet\LMIR0001.tmp\rahook.dll
    LoadedModule[167]=C:\windows\system32\wsock32.dll
    LoadedModule[168]=C:\windows\system32\netapi32.dll
    LoadedModule[169]=C:\windows\system32\srvcli.dll
    LoadedModule[170]=C:\windows\system32\wkscli.dll
    LoadedModule[171]=C:\windows\system32\BROWCLI.DLL
    LoadedModule[172]=C:\windows\system32\DFSCLI.DLL
    LoadedModule[173]=C:\windows\system32\SAMCLI.DLL
    LoadedModule[174]=C:\windows\system32\SCHEDCLI.DLL
    LoadedModule[175]=C:\windows\system32\snmpapi.dll
    LoadedModule[176]=C:\windows\system32\inetmib1.dll
    LoadedModule[177]=C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE15\MSPTLS.DLL
    Sec[0].Key=LCID
    Sec[0].Value=1033
    State[0].Key=Transport.DoneStage1
    State[0].Value=1
    FriendlyEventName=Stopped working
    ConsentKey=APPCRASH
    AppName=Microsoft Lync
    AppPath=C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
    Thanks in advance,

    If you update your client to the most recent version, does the issue reoccur?
    How many Singh's do you have at your company?  I'm curious if there's an active directory attribute that is returned with that user that the client really just doesn't like.  Can you go into Active Directory Users and Computers, select View->Advanced
    then manually find Singh (don't search) and go to the Attribute Editor tab.  Do you see any attribute in there (not just Lync attributes) that seems to have any odd or escape characters? 
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
    SWC Unified Communications

  • Lync 2013 basic crashing on T520 and T530?

    We use SCCM to deploy our machines and with the Thinkpad's T520 and T530 having the Intel HD 3000 or 4000 graphical card the application is crashing without reason
    When we use Teamviewer in a remote session Lync is working fine. How come and how can we solve this?

    Peer to peer or 1-on-1 chatting send the audio peer to peer (not through the server).  When you add another participant, the audio then flows through an A/V Conferencing Server (assuming you're running 2010 server per the forum you posed in, this is
    often the same as your front end pool).  This sounds like a port restriction or connectivity issue. 
    http://technet.microsoft.com/en-us/library/gg398833(v=ocs.14).aspx
    http://technet.microsoft.com/en-us/library/gg425891.aspx
    If not that, then check your conferencing configuration (are you hosting?), ensure you're not muted, try from a different machine. 
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
    SWC Unified Communications

  • Lync 2013 x64 Crashes on Windows 7 Pro x64

    Version=1
    EventType=APPCRASH
    EventTime=130571930358088832
    ReportType=2
    Consent=1
    UploadTime=130571930358712834
    ReportIdentifier=d4494ca1-4e6d-11e4-b4ac-001cc4ae67d4
    IntegratorReportIdentifier=d4494ca0-4e6d-11e4-b4ac-001cc4ae67d4
    Response.type=4
    Sig[0].Name=Application Name
    Sig[0].Value=lync.exe
    Sig[1].Name=Application Version
    Sig[1].Value=15.0.4649.1000
    Sig[2].Name=Application Timestamp
    Sig[2].Value=53e9ae69
    Sig[3].Name=Fault Module Name
    Sig[3].Value=KERNELBASE.dll
    Sig[4].Name=Fault Module Version
    Sig[4].Value=6.1.7601.18409
    Sig[5].Name=Fault Module Timestamp
    Sig[5].Value=5315a05a
    Sig[6].Name=Exception Code
    Sig[6].Value=e06d7363
    Sig[7].Name=Exception Offset
    Sig[7].Value=000000000000940d
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=6.1.7601.2.1.0.256.48
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1033
    UI[2]=C:\Program Files\Microsoft Office 15\root\office15\lync.exe
    UI[3]=Microsoft Lync has stopped working
    UI[4]=Windows can check online for a solution to the problem.
    UI[5]=Check online for a solution and close the program
    UI[6]=Check online for a solution later and close the program
    UI[7]=Close the program
    LoadedModule[0]=C:\Program Files\Microsoft Office 15\root\office15\lync.exe
    LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
    LoadedModule[2]=C:\Windows\system32\kernel32.dll
    LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
    LoadedModule[4]=C:\Windows\System32\SYSFER.DLL
    LoadedModule[5]=C:\Program Files\Microsoft Office 15\root\office15\AppVIsvSubsystems64.dll
    LoadedModule[6]=C:\Program Files\Microsoft Office 15\root\office15\AppVIsvStream64.dll
    LoadedModule[7]=C:\Program Files\Microsoft Office 15\root\office15\c2r64.dll
    LoadedModule[8]=C:\Windows\system32\ADVAPI32.dll
    LoadedModule[9]=C:\Windows\system32\msvcrt.dll
    LoadedModule[10]=C:\Windows\SYSTEM32\sechost.dll
    LoadedModule[11]=C:\Windows\system32\RPCRT4.dll
    LoadedModule[12]=C:\Windows\system32\USER32.dll
    LoadedModule[13]=C:\Windows\system32\GDI32.dll
    LoadedModule[14]=C:\Windows\system32\LPK.dll
    LoadedModule[15]=C:\Windows\system32\USP10.dll
    LoadedModule[16]=C:\Windows\system32\USERENV.dll
    LoadedModule[17]=C:\Windows\system32\profapi.dll
    LoadedModule[18]=C:\Windows\system32\SHELL32.dll
    LoadedModule[19]=C:\Windows\system32\SHLWAPI.dll
    LoadedModule[20]=C:\Windows\system32\ole32.dll
    LoadedModule[21]=C:\Windows\system32\OLEAUT32.dll
    LoadedModule[22]=C:\Program Files\Microsoft Office 15\root\office15\MSVCR100.dll
    LoadedModule[23]=C:\Program Files\Microsoft Office 15\root\office15\LyncModelProxy.dll
    LoadedModule[24]=C:\Program Files\Microsoft Office 15\root\office15\PropertyModel.dll
    LoadedModule[25]=C:\Program Files\Microsoft Office 15\root\office15\MSVCP100.dll
    LoadedModule[26]=C:\Program Files\Microsoft Office 15\root\office15\PropertyModelProxy.dll
    LoadedModule[27]=C:\Program Files\Microsoft Office 15\root\office15\LyncDesktopViewModel.dll
    LoadedModule[28]=C:\Windows\system32\MSIMG32.dll
    LoadedModule[29]=C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18455_none_2b283fd671e9bf4d\gdiplus.dll
    LoadedModule[30]=C:\Windows\system32\DWrite.dll
    LoadedModule[31]=C:\Program Files\Microsoft Office 15\root\office15\RtmMvrAs.dll
    LoadedModule[32]=C:\Program Files\Microsoft Office 15\root\office15\MSVCR110.dll
    LoadedModule[33]=C:\Program Files\Microsoft Office 15\root\office15\RtmPal.dll
    LoadedModule[34]=C:\Windows\system32\WINMM.dll
    LoadedModule[35]=C:\Windows\system32\WS2_32.dll
    LoadedModule[36]=C:\Windows\system32\NSI.dll
    LoadedModule[37]=C:\Windows\system32\PSAPI.DLL
    LoadedModule[38]=C:\Windows\system32\POWRPROF.dll
    LoadedModule[39]=C:\Windows\system32\SETUPAPI.dll
    LoadedModule[40]=C:\Windows\system32\CFGMGR32.dll
    LoadedModule[41]=C:\Windows\system32\DEVOBJ.dll
    LoadedModule[42]=C:\Windows\system32\pdh.dll
    LoadedModule[43]=C:\Program Files\Microsoft Office 15\root\office15\MSVCP110.dll
    LoadedModule[44]=C:\Windows\system32\IPHLPAPI.DLL
    LoadedModule[45]=C:\Windows\system32\WINNSI.DLL
    LoadedModule[46]=C:\Program Files\Microsoft Office 15\root\office15\dbghelp.dll
    LoadedModule[47]=C:\Windows\system32\bcrypt.dll
    LoadedModule[48]=C:\Windows\system32\WTSAPI32.dll
    LoadedModule[49]=C:\Windows\system32\PROPSYS.dll
    LoadedModule[50]=C:\Program Files\Microsoft Office 15\root\office15\RtmCodecs.dll
    LoadedModule[51]=C:\Windows\system32\d3d11.dll
    LoadedModule[52]=C:\Windows\system32\dxgi.dll
    LoadedModule[53]=C:\Windows\system32\VERSION.dll
    LoadedModule[54]=C:\Windows\system32\dwmapi.dll
    LoadedModule[55]=C:\Windows\system32\d3d9.dll
    LoadedModule[56]=C:\Windows\system32\d3d8thk.dll
    LoadedModule[57]=C:\Windows\system32\dxva2.dll
    LoadedModule[58]=C:\Windows\system32\IMM32.dll
    LoadedModule[59]=C:\Windows\system32\MSCTF.dll
    LoadedModule[60]=C:\Windows\system32\UIAutomationCore.DLL
    LoadedModule[61]=C:\Windows\system32\OLEACC.dll
    LoadedModule[62]=C:\Program Files\Common Files\Microsoft Shared\Office15\mso.dll
    LoadedModule[63]=C:\Windows\system32\d2d1.dll
    LoadedModule[64]=C:\Windows\system32\uxtheme.dll
    LoadedModule[65]=C:\Windows\system32\WINSTA.dll
    LoadedModule[66]=C:\Windows\system32\WINTRUST.dll
    LoadedModule[67]=C:\Windows\system32\CRYPT32.dll
    LoadedModule[68]=C:\Windows\system32\MSASN1.dll
    LoadedModule[69]=C:\Windows\system32\CRYPTBASE.dll
    LoadedModule[70]=C:\Program Files\Microsoft Office 15\root\office15\Uc.dll
    LoadedModule[71]=C:\Program Files\Microsoft Office 15\root\office15\RtmMvrCs.dll
    LoadedModule[72]=C:\Windows\system32\WINSPOOL.DRV
    LoadedModule[73]=C:\Windows\system32\HID.DLL
    LoadedModule[74]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac\Comctl32.dll
    LoadedModule[75]=C:\Windows\system32\CLBCatQ.DLL
    LoadedModule[76]=C:\Windows\system32\msi.dll
    LoadedModule[77]=C:\Program Files\Microsoft Office 15\root\office15\1033\lyncDesktopResources.dll
    LoadedModule[78]=C:\Windows\system32\DavClnt.DLL
    LoadedModule[79]=C:\Windows\system32\DAVHLPR.dll
    LoadedModule[80]=C:\Windows\System32\netprofm.dll
    LoadedModule[81]=C:\Windows\System32\nlaapi.dll
    LoadedModule[82]=C:\Windows\system32\CRYPTSP.dll
    LoadedModule[83]=C:\Windows\system32\rsaenh.dll
    LoadedModule[84]=C:\Windows\system32\RpcRtRemote.dll
    LoadedModule[85]=C:\Windows\system32\d3d10_1.dll
    LoadedModule[86]=C:\Windows\system32\d3d10_1core.dll
    LoadedModule[87]=C:\Windows\System32\npmproxy.dll
    LoadedModule[88]=C:\Windows\system32\D3D10Warp.dll
    LoadedModule[89]=C:\Windows\system32\webservices.dll
    LoadedModule[90]=C:\Program Files\Microsoft Office 15\root\office15\OLMAPI32.DLL
    LoadedModule[91]=C:\Program Files\Microsoft Office 15\root\office15\1033\mapir.dll
    LoadedModule[92]=C:\Windows\system32\ntmarta.dll
    LoadedModule[93]=C:\Windows\system32\WLDAP32.dll
    LoadedModule[94]=C:\Program Files\Common Files\Microsoft Shared\Office15\riched20.dll
    LoadedModule[95]=C:\Windows\system32\nvwgf2umx.dll
    LoadedModule[96]=C:\Program Files\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\osppc.dll
    LoadedModule[97]=C:\Windows\system32\Secur32.dll
    LoadedModule[98]=C:\Windows\system32\SSPICLI.DLL
    LoadedModule[99]=C:\Program Files\Microsoft Office 15\root\office15\UccApi.dll
    LoadedModule[100]=C:\Program Files\Microsoft Office 15\root\office15\Win32MsgQueue.dll
    LoadedModule[101]=C:\Program Files\Microsoft Office 15\root\office15\1033\ocapires.dll
    LoadedModule[102]=C:\Program Files\Microsoft Office 15\root\office15\Psom.dll
    LoadedModule[103]=C:\Windows\System32\msxml6.dll
    LoadedModule[104]=C:\Program Files\Microsoft Office 15\root\office15\OcImport.DLL
    LoadedModule[105]=C:\Program Files\Microsoft Office 15\root\office15\ocrec.dll
    LoadedModule[106]=C:\Windows\system32\mlang.dll
    LoadedModule[107]=C:\Windows\system32\windowscodecs.dll
    LoadedModule[108]=C:\Program Files\Microsoft Office 15\root\office15\RtmMediaManager.dll
    LoadedModule[109]=C:\Windows\system32\AVRT.DLL
    LoadedModule[110]=C:\Program Files\Microsoft Office 15\root\office15\AppSharingMediaProvider.dll
    LoadedModule[111]=C:\Program Files\Microsoft Office 15\root\office15\RTMPLTFM.dll
    LoadedModule[112]=C:\Windows\system32\bcryptprimitives.dll
    LoadedModule[113]=C:\Windows\system32\credssp.dll
    LoadedModule[114]=C:\Windows\system32\mswsock.dll
    LoadedModule[115]=C:\Windows\System32\wshtcpip.dll
    LoadedModule[116]=C:\Windows\System32\wship6.dll
    LoadedModule[117]=C:\Windows\system32\dhcpcsvc6.DLL
    LoadedModule[118]=C:\Windows\system32\dhcpcsvc.DLL
    LoadedModule[119]=C:\Windows\system32\wlanapi.dll
    LoadedModule[120]=C:\Windows\system32\wlanutil.dll
    LoadedModule[121]=C:\Windows\System32\MMDevApi.dll
    LoadedModule[122]=C:\Windows\system32\MFPlat.dll
    LoadedModule[123]=C:\Windows\system32\devenum.dll
    LoadedModule[124]=C:\Windows\system32\msdmo.dll
    LoadedModule[125]=C:\Windows\system32\MF.dll
    LoadedModule[126]=C:\Windows\system32\ATL.DLL
    LoadedModule[127]=C:\Windows\system32\ksuser.dll
    LoadedModule[128]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI64.dll
    LoadedModule[129]=C:\Windows\system32\WinSATAPI.dll
    LoadedModule[130]=C:\Windows\system32\urlmon.dll
    LoadedModule[131]=C:\Windows\system32\api-ms-win-downlevel-ole32-l1-1-0.dll
    LoadedModule[132]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l1-1-0.dll
    LoadedModule[133]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l1-1-0.dll
    LoadedModule[134]=C:\Windows\system32\api-ms-win-downlevel-user32-l1-1-0.dll
    LoadedModule[135]=C:\Windows\system32\api-ms-win-downlevel-version-l1-1-0.dll
    LoadedModule[136]=C:\Windows\system32\api-ms-win-downlevel-normaliz-l1-1-0.dll
    LoadedModule[137]=C:\Windows\system32\normaliz.DLL
    LoadedModule[138]=C:\Windows\system32\iertutil.dll
    LoadedModule[139]=C:\Windows\system32\WININET.dll
    LoadedModule[140]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll
    LoadedModule[141]=C:\Program Files\Common Files\Microsoft Shared\OFFICE15\MSOXMLMF.DLL
    LoadedModule[142]=C:\Program Files\Microsoft Office 15\root\office15\RdpQoEMetrics.dll
    LoadedModule[143]=C:\Windows\system32\dnsapi.dll
    LoadedModule[144]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll
    LoadedModule[145]=C:\Windows\system32\apphelp.dll
    LoadedModule[146]=C:\Windows\system32\AUDIOSES.DLL
    Sec[0].Key=LCID
    Sec[0].Value=1033
    State[0].Key=Transport.DoneStage1
    State[0].Value=1
    FriendlyEventName=Stopped working
    ConsentKey=APPCRASH
    AppName=Microsoft Lync
    AppPath=C:\Program Files\Microsoft Office 15\root\office15\lync.exe

    Go to your computer manufacturer’s website and update all driver packages for your computer, especially:
    Audio drivers
    Bluetooth drivers
    System chipset drivers
    webcam drivers
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
    Mai Ali | My blog: Technical | Twitter:
    Mai Ali

  • Lync 2013 SP1 64 bit crashes on Windows 7 Enterprise 64bit SP1

    Systems Involved:
    Dell OptiPlex 9020 All in One (080) –Crashes Lync 2013 64bit SP1
    Dell OptiPlex 9020 All in One (081) –Crashes with Lync 2013 64bit SP1   -Working okay with 2010 so far 
    Dell OptiPlex 9020 All in One (083) –Clean install Seems to be working okay 
    Details of the problems
    I have a put in place 2 Dell OptiPlex 9020 All in One’s both with network card Intel I217-LM. 
    The first system (080) I put place crashed several times before, I put a different new 9020AIO (083) that I created a new with clean install from disk of Windows 7 and Office 2013 64 bit with Lync 2013 64 bit upgraded to SP1.    After having this
    system side by side with the system that was crashing all the time and network capturing software installed on the new system this issue appeared to disappear.  The user has not reported an issue with Lync 2013 in three to 4 weeks.  
    After thinking this was an issue with Office 2013-upgraded SP1. I decided to create a new image Windows 7 and Office 2013 64 bit SP1 intergraded .iso from web store. (Not upgraded) thinking there was something wrong with the SP 1 upgrade the way I intended
    it to work.   I reimaged the other 9020’s I have including the one (080) that was having the crashing issues. 
    The second system (081) is a new image I created, the system got some office updates from the WSUS it should not have been updated with and Lync 2013 was also crashing. I decided to reimage (080) a clean format with the new image.  I put this system in
    place for the user knowing it was clean install and not have any issue but for the last 2 weeks Lync 2013 has crashed.
    I did take their old system back to my desk and was able to get it to crash as well.  I decided to see if this problem was with Lync so I installed Lync 2010 I have not seen issue with 2010 yet.
    I have also rolled out 2 Dell OptiPlex 7010 towers   with the same image as above with no issues so it seems like this issue is only related to the 9020AIO.
    Issue:
    The computer will operate fine for most of the time but Lync 2013 will crash with not responding, please sign into Lync on the phone  (Plantronics D540m).  I get windows circle thing spinning and Lync is not responding    if you close the
    program it will try to run solution finder but there is not anything that will help.   The only way to fix this issue is to reboot at this time.   At first I thought it was the network driver issue for Intel I217-LM but after installing the usb network
    adapter I believe the issue is something related to Lync 2013 SP1 
    Things I have tried
    1. System Event : Application Log pulled  I will include below in this message 
    2. 9020 with Intel I217-LM
    3. Update driver version = to current version
    4. Change power management settings as outlined http://en.community.dell.com/support-forums/desktop/f/3514/p/19523337/20460673.aspx 
    5. Disable Wireless and  Bluetooth 
    6. Reset users Lync account 
    7. USB Network Adapter.
    Event Logs:
    1.The program lync.exe version 15.0.4569.1503 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: 1be4
      Start Time: 01cf5a40e5452e63
      Termination Time: 60000
      Application Path: C:\Program Files\Microsoft Office\Office15\lync.exe
      Report Id: 11c8f99b-c65d-11e3-b675-c4d98743ad3b
    2.  Fault bucket, type 0
     Event Name: AppTermFailureEvent
     Response: Not available
     Cab Id: 0
     Problem signature:
     P1: 
     P2: 
     P3: 
     P4: 
     P5: 
     P6: 
     P7: 
     P8: 
     P9: 
     P10: 
     Attached files:
     C:\Windows\Temp\WER3076.tmpatk.kdmp
     C:\Windows\Temp\WER3077.tmp.appcompat.txt
     C:\Windows\Temp\WER30A7.tmp.xml
     C:\Windows\Temp\WER3125.tmp.WERInternalMetadata.xml
     C:\Windows\Temp\WER3126.tmp.hdmp
     C:\Windows\Temp\WER4208.tmp.mdmp
     These files may be available here:
     C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0a244260
     Analysis symbol: 
     Rechecking for solution: 0
     Report Id: f6cda468-d60a-11e3-a941-c4d98743ad3b
    3. Fault bucket 24029667, type 22
     Event Name: AppHangB1
     Response: Not available
     Cab Id: 0
     Problem signature:
     P1: lync.exe
     P2: 15.0.4569.1503
     P3: 52b0bd5c
     P4: ac33
     P5: 1
     P6: 
     P7: 
     P8: 
     P9: 
     P10: 
     Attached files:
     C:\Users\netid\AppData\Local\Temp\WERFA2A.tmp.appcompat.txt
     C:\Users\netid\AppData\Local\Temp\WERFE21.tmp.WERInternalMetadata.xml
     These files may be available here:
     C:\Users\netid\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppHang_lync.exe_fe2cd4e98d389da9ae67bda6ac81af366f458bb6_11cc0947
     Analysis symbol: 
     Rechecking for solution: 0
     Report Id: ec8f9268-d60a-11e3-a941-c4d98743ad3b
    Then I get about 10 Office Software Protection Platform before the above error logs occur.

    Does the issue disappear when you uninstall the update?
    If so, it seems that the Lync update is incompatible with your computer.
    Please try to uninstall Lync 2013 SP1.
    Lisa Zheng
    TechNet Community Support

  • Lync 2013 crashes when double-clicking on contact to send IM...

    I have a 64 bit Windows 7 machine. I have Office 2010 and 2013 installed. I am able to successfully run Lync 2013 and login to the Lync Server and see my contacts and their statuses online.  However, every time I double-click on a contact name to send
    them an IM i get a message saying "Microsoft Lync has stopped working" and Lync shuts down and restarts. When I debug the error using Visual Studio 2010 I get an "Unhandled exception... Access violation" error.
    Here is what I know so far... It has to do with some incompatibility with Office 2010, because when I uninstall Office 2010, Lync 2013 starts working properly.  (However, I need Office 2010 installed for supporting my clients. <sigh>)
    Here's is what I've done so far...
    1. Uninstalled Office 2013 = Lync 2013 still crashes.
    2. Uninstalled Office 2010 = Lync 2013 works fine now.
    3. Reinstalled Office 2013 w/out Office 2010 present = Lync 2013 works fine.
    4. Reinstalled Office 2010 followed by Office 2013 = Lync 2013 still crashes.
    5. I've also delete the sip_ folder to have Lync recreate it = that doesn't work either.
    I have also updated Lync 2013 to the latest version update provided by Microsoft, but nothing seems to help.
    My Event Viewer says the following:
    Faulting application name: lync.exe, version: 15.0.4675.1000, time stamp: 0x54629b57
    Faulting module name: lync.exe, version: 15.0.4675.1000, time stamp: 0x54629b57
    Exception code: 0xc0000005
    Fault offset: 0x00f50000
    Faulting process id: 0x1564
    Faulting application start time: 0x01d024b896c56e36
    Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
    Faulting module path: C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
    Report Id: 282d47fc-90ac-11e4-8ed2-14feb598d143
    Any help will be greatly appreciated!!!

    Hi bihtime3,
    I understand the inconvenience caused by this issue. I would like to confirm if you have tried the following scenarios.
    1. Repairing Office 2013 after installing Office 2010.
    2. Installing Office 2010 before installing Office 2013.
    Best regards,
    Eric

  • Lync 2013 RTM client crashing on startup in Windows 8 RTM

    Lync 2013 client crashes during startup with the following event:
    Faulting application name: lync.exe, version: 15.0.4420.1017, time stamp: 0x5067326f
    Faulting module name: KERNELBASE.dll, version: 6.2.9200.16384, time stamp: 0x5010ac2f
    Exception code: 0xe06d7363
    Fault offset: 0x00014b32
    Faulting process id: 0x15bc
    Faulting application start time: 0x01cdc372c8b81886
    Faulting application path: C:\Program Files (x86)\Office 2013\Office15\lync.exe
    Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
    Report Id: 06d225ad-2f66-11e2-be7f-000ffedc7546
    I'm running Windows 8 64-bit, but Office 32-bit for compatibility reasons. Office 2010 and Lync 2010 worked beautifully. Other Office 2013 applications work fine. Lync 2010 client works fine as well. Only see this problem with Lync 2013.
    Any ideas how to troubleshoot or correct?

    Hi,
    Have you tried to remove Lync 2010 client and test it again?
    How about the other machines? Please also log on the problem machine with another account and test it.
    Please try to disable any local antivirus software to see if that fixes the issue.
    Please remove Silverlight and reinstall it:
    http://www.microsoft.com/silverlight/
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Cisco Call Manager 8.5 and Lync 2013

    Dear all,
    Our customer wants to integrate their Lync 2013 to the Cisco Call Manager 8.5.
    Out of some not so recent information i thought that if u want to use the enterprise voice of lync you'll have to make a sip trunk between Cisco Call Manager & Lync 2013.
    I think that this still counts, i've also heard that there have been a moderate amount of changes between cucm 8.5 and cucm 8.6 on matters of sip.
    I'm unable to find them though, also what does CUCI - Lync do?
    Kr,
    Yannick Vranckx

    Hi Yannick,
    There can be three types of integrations between Lync and Cisco Systems
    1)      Direct SIP Trunk between Lync Server and Call Manager - In this, we can setup shared line between Cisco extensions and Lync extensions, and Sip trunk between the servers. Any Cisco phone / Lync client  can call each other vice-versa. Initial setup needs planning, but later it does not need much configurations in client side. The following document explains the configurations needed.
    http://www.cisco.com/en/US/docs/voice_ip_comm/cucilync/9/CUCI_BK_C0B36AC1_00_cisco-uc-integration-for-microsoft.pdf
    2) CUCILYNC, which is like Cisco Jabber client but connects with Lync and Call Manager: Lync Client <----> CUCILYNC <-----> CUCM
    In this option, a plug-in is installed in each client side. Although initial configurations is easier, each user needs to install the client and operate it. The below document explains the configuration and setup.
    http://www.cisco.com/en/US/docs/voice_ip_comm/cucilync/9/CUCI_BK_C0545A41_00_cisco-uc-integration-for-microsoft.html
    3) RCC (Remote Call Plugin) which just provides basic call control feature but for that you need Cisco Unified Presence Server: Lync Client <----> CUPS <-----> CUCM
    HTH
    Manish

Maybe you are looking for