Lync Client Crashes on Inbound Calls

Hello,
We have a number of users (about half) complaining that Lync 2013 crashes when an inbound call comes in. We are running a fully patched Lync 2013 deployment with a fully patched Lync/Office 2013 deployment. Any suggestions would be helpful. It seems to especially
plague users connected to their CX700's, but this is not exclusively a problem they experience.

Hi,
Would you tell us which model of audio and video device do you use?
Please switch an audio device to test the issue.
Please also un-plug CX700 to test the issue.
If the issue persists, please check event viewer for further troubleshooting.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Similar Messages

Lync Client Crashes at Startup

I am having an issue with Lync 2013 32 bit. It crashes immediately at startup. The error code was referencing a fault with UCcapi.dll. I removed HP Skyroom but still have a problem, however it is now referencing a fault with kernelbase.dll.
I have uninstalled and reinstalled Office 2013. I tried logging on as another user but get the same results. Any help would be greatly appreciated.

It's probably the Lync update (KB2817465) that was released July 9. In my case I had a duplicate of it installed
on my HP laptop.
Other people are reporting that after the update they also needed to update a Bluetooth driver in order to get Lync to work again.
Here is a similar thread http://social.technet.microsoft.com/Forums/en-US/07a6ed04-afde-4ef8-8e38-aabf0d4782e2/lync-2013-client-crash-at-startup
Blog http://ucfoc.us | Twitter @georgathomas

Lync client crash

Hi
when i RDP my client PC my Lync client crahed and reopens automatically. please help me to resolve this issue.
client OC - win 7
Lync version - 4.0.7577.4103
we are getting event id 1000
Log Name:      Application
Source:        Application Error
Date:          12/3/2012 1:57:26 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:     computername
Description:
Faulting application name: communicator.exe, version: 4.0.7577.4103, time stamp: 0x4fd6bebb
Faulting module name: gdiplus.dll, version: 6.1.7601.17825, time stamp: 0x4f9235ab
Exception code: 0xc0000005
Fault offset: 0x000255fc
Faulting process id: 0x584
Faulting application start time: 0x01cdcfa14aa21281
Faulting application path: C:\Program Files (x86)\Microsoft Lync\communicator.exe
Faulting module path: C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17825_none_72d273598668a06b\gdiplus.dll
Report Id: 74fc00bb-3d27-11e2-b76a-005056af4b5d
Regards Mager

Hi,
Would you try to use another computer to logged into that PC through RDP?
Please also make sure all updates for Windows have been installed.
Kent Huang
TechNet Community Support

Calls not ending on the Lync Client

When Making a call through the Lync Client , you can talk as normal on the desk phone but when hanging up the lync client still shows the call window and after a short pause it says <person you tried to call> did not answer (an option
to retry appears).
We are using Lync Server with a Mitel based phone system. When hanging up on Lync the call hangs up on the Mitel phone.
Please let me know if you need any more information.
Thanks

Hi,
Did the issue also happen between two Lync desktop clients or just happen between one Lync desktop client and one Mitel phone?
If the issue just happen between Lync client and Mitel phones, it may be an inbound route issue.
Please also try to update to the latest version for Lync Server and then test again.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

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.

VVX handset initiated call will not connect to Lync client with simultaneous ring enabled

Has anyone encountered a similar issue? And any advice on how to fix it please? (note - a case has been logged with Polycom, but weeks are passing by and they have not provided any useful response so far; hence reaching out in
the community for help) .... thanks in anticipation.
Here's the scenario:
A Lync 2010 user in the office (I'll call her Lisa) has setup her Sim Ring to an external number (her mobile number).
Another Lync 2010 user in the office (Mike) calls Lisa's extension from his VVX410.
Lisa answers the incoming call using her Lync client with a USB headset.
The call appears to connect according to Mike and his VVX screen starts the call timer.
Lisa's Lync client just says "Connecting Call ..." but never actually connects.
The line is silent for both Mike and Lisa. There is no audio in either direction.
Further testing reveals the following:
The same problem occurs if Lisa uses a VVX handset to answer and also happens if she uses a CX600 handset to answer. Hence the problem seems to relate specifically to the fact that Lisa has setup Sim Ring to an external number; rather than relating
to the answering device type.
If Lisa changes her Sim Ring so that it calls another internal extension, then the problem does not exist, i.e. calls connect fine. Hence it seems to be specific to sim ring to an external number.
The environment is Lync Server 2010 CU6, Lync client 2010 on Win 7 (although the same problem exists when tested with a Lync 2013 on Win 8.1 client); and with AudioCodes Mediant 2000 and 1000 gateways.

Please specify another external number for Simultaneously Ring.
You phone may not have permission to dial an external phone number.
Please check if you can call the external phone number directly.
Lisa Zheng
TechNet Community Support

T440P [20AN] - Lync 2013 Crashing When Sharing Desktop - Intel Driver

Hello,
After updating to the latest video drivers from the ThinkVantage Update Retriever, our Lync clients crash when sharing desktop on our T440P series and X240 series. I noticed when I uninstall the video driver I am able to screen share without incident. Also, if I update the driver from Windows Update I am able to share successfully. We use the update retriever and thininstaller to install our drivers in our environment. I have tried uninstalling the Lync updates all the way down to the base version and experience the same issue at every level. It crashes 100% of the time when sharing desktop. I have tested it on T440p machines in our environment that do not have the latest display driver, and no crashes occurred. Here are the specifics:
Thinkpad X240 [20AL]
Thinkpad T440p [20AN]
ThinkVantage Update Retriever 5.00.0007
Thinkvantage Thin Installer 1.2.0010
Intel HD Graphics Driver - gid634ww (10.18.10.3412)
Microsoft Lync 2013 SP1 32 Bit (15.0.4569.1503)
Error Message from Application Log:
Faulting application name: lync.exe, version: 15.0.4569.1503, time stamp: 0x52b0af33
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x53159a86
Exception code: 0x00000879
Fault offset: 0x0000c42d
Faulting process id: 0x220c
Faulting application start time: 0x01cf707ca316ae96
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
Faulting module path: C:\WINDOWS\syswow64\KERNELBASE.dll
Report Id: 9bb7c6e4-dc70-11e3-b695-5c514fb23d46
Any help or insight is greatly appreciated.
Thank you,
John
Solved!
Go to Solution.

Just as an updated to this:
I'm still waiting on updated drivers to fix the issue, however, there is a workaround. If you disable Desktop Composition screen sharing will work.
Control Panel -> Performance and Information Tools -> Adjust Visual Effects -> Uncheck “Enable desktop composition
John

Lync crashes on Video Call/Preview when I select MS VX-5000 Camera

Symptom: In Lync Settings I change the video device from the integrated webcam to the VX-5000. Preview looks good in the tools window. Then if I save it to use the VX-5000, and try to make any video call, Lync will instantly
crash. The integrated webcam works great.
I've made sure the drivers for the web cam show up and are working correctly in Device Manager. Any help/clues/workarounds would be great.
System info:
Computer is a Dell XPS 12, running Windows 8.1 x64 (latest patches), and Lync version: 2013 (15.0.4629.1000) MSO (15.0.4631.1002) 64 bit.
OS Name Microsoft Windows 8.1 Enterprise
Version 6.3.9600 Build 9600
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name NINJA
System Manufacturer Dell Inc.
System Model XPS 12 9Q23
System Type x64-based PC
System SKU XPS 12 9Q23
Processor Intel(R) Core(TM) i7-3687U CPU @ 2.10GHz, 2101 Mhz, 2 Core(s), 4 Logical Processor(s)
BIOS Version/Date Dell Inc. A08, 8/1/2013
SMBIOS Version 2.7
Embedded Controller Version 1.01
BIOS Mode UEFI
Windows Directory C:\windows
System Directory C:\windows\system32
Boot Device \Device\HarddiskVolume2
Locale United States
Hardware Abstraction Layer Version = "6.3.9600.17196"
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.88 GB
Available Physical Memory 2.07 GB
Total Virtual Memory 15.9 GB
Available Virtual Memory 6.99 GB
Page File Space 8.00 GB
Page File C:\pagefile.sys
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes

Hi,
Can you update the Lync client to the latest as well? and check whether you still have the problem. This one is 15.0.4629.1005
http://support.microsoft.com/kb/2825630
http://thamaraw.com

Lync Client 2013 64bit instantly crashes before sign-on || Office 2013 ProPlus 64bit & Windows 8.1 Enterprise 64bit

I have a problem with my Lync Client. It simply crashes before the sing-on with following error appearing in application log:
Faulting application name: lync.exe, version: 15.0.4623.1000, time stamp: 0x53728995
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17055, time stamp: 0x532954fb
Exception code: 0xe06d7363
Fault offset: 0x0000000000005bf8
Faulting process id: 0xc4c
Faulting application start time: 0x01cfa58adb7a455e
Faulting application path: C:\Program Files\Microsoft Office\Office15\lync.exe
Faulting module path: C:\WINDOWS\system32\KERNELBASE.dll
Report Id: 1a57ee5a-117e-11e4-825d-28d244607082
Faulting package full name:
Faulting package-relative application ID:
As the faulting module path is not pointing to a conflicting Bluetooth driver or anything, how to troubleshoot what software is conflicting this?
Needless to say I've done all basic steps; reinstalling the office, updating with all the latest Office & Windows patces, repairing it, tried it with another / empty user account, etc. This is a new machine with clean Windows installation without OEM
crippleware. Before I just uninstall everything but Office from this machine, how do I point a problem resulting a kernelbase.dll faulting?
Only clients "Starting..." screen is showing before the crash.

Please check if Word, Excel work correctly.
Check if Lync 2013 works on other computer installed using the same installation media.
Lisa Zheng
TechNet Community Support

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.

Custom Lync reporting to get inbound number list and call duration

Hi Guys,
I know this is going to be complex but surely a Lync SQL expert can assist here.
I would like to create a custom report of all inbound call received over a period of time with the call duration. The default reports does not have features to narrow down based on calling numbers. Is there any way that I can get a big extract for all the
calls received by the firm and later I can use vlook up etc to get what I want.
I am not good with sql but this I think
https://northernlync.wordpress.com/2014/03/10/lync-2013-creating-custom-lync-reports-within-monitoring/ will do the trick. Has any one tried it?
Any suggestions?
aman sahni

Hi,
Base on my knowledge, you can custom Lync Call Details Reports with the help of the link you provided above.
The first step to creating a custom call details report for use with the pre-existing Lync Server Monitoring Service Reports is to establish a secure connection to the SQL Server and LcsCdr database objects that will be used as data sources for any new reports.
Next, access will be provided to the user-defined database objects that reside in the LcsCDR database. Once the data is accessible, then it is time to present it by using the SQL Server Report tool.
More details, it is for Lync Server 2010, but similar for Lync Server 2013:
http://blogs.technet.com/b/nexthop/archive/2012/01/12/how-to-create-additional-lync-server-2010-call-details-reports-part-2.aspx
Best Regards,
Eason Huang
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Eason Huang
TechNet Community Support

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

Change the default one-click audio call option on Lync clients

I know that the Lync client looks to AD for the telephone number (of which I have the txt file normalizing the number there) and that is working properly. I would like to know how I can change the default to make a "Lync call" as oppose to dialing the
number from AD.Bob Ausmus

You need to set the client policy:
EnableVOIPCallDefault
Optional
Boolean
When set to True, a Lync 2010 call will be placed any time a user employs the click-to-call feature.
This policy setting only affects the initial state of the click-to-call feature. If the user modifies the value of the click-to-callsetting then the user-selected value will override this
policy setting. After a user has modified the click-to-call setting that setting will remain in use and will not be affected by the EnableVOIPCallDefault policy.
http://technet.microsoft.com/en-us/library/gg398300.aspx
Set-CsClientPolicy -Identity Global -EnableVOIPCallDefault $true
Regards,
Jamie Schwinn

Lync client show contact is adding audio and the "Call was not completed"

the incoming call show is adding audio, the call can't pick up.
User is using Lync certificated headset. Others incoming calls is able to pick up.
Any idea?
Thanks.

Hi,
To narrow down the issue, please test the issue with this issued Lync account on other computer Lync client (use the issued headset, then change to other well-worked headset), check if the issue still happen or not.
If the issue not happen on other Lync client, it can be the issue of Lync user profile, please try to delete the user profile with the following path:
%UserProfile%\AppData\Local\Microsoft\Office\15.0\Lync
Also delete the Lync user configuration information in registry with the following path:
HKCU\Software\Microsoft\Office\15.0\Lync\[email protected]
If the issue also happen on other Lync clients, it can be the issue of the Lync account itself, please try to disable it on Lync Server side, and then enable it again to test the issue.
Best Regards,
Eason Huang
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Eason Huang
TechNet Community Support

Lync 2013 I have a strange problem concerning group call pickup in lync 2013.the pickup calls on snom 710 having only a second delay, but in lync client it having about 5-7 second Anybody out there having similar problems with call pickup Groups?

HI
I have a strange problem concerning group call pickup in lync 2013.the pickup calls on snom 710 having only a second delay, but in lync client it having about 5-7 second
Anybody out there having similar problems with call pickup Groups?

Hi,
Did you meet any other call delay when you using Lync?
As the issue happen for Lync desktop client, it can be performance issue. Please check if there is any error message from FE Server when the issue happen.
Also please check if you have updated Lync Server to the latest version, if not, update it and then test again.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync Client Crashes on Inbound Calls

Similar Messages

Maybe you are looking for