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.

Similar Messages

Lync 2013 crashes on startup in Windows 8.1 on Dell latitude E6520 machines

Lync 2013 crashes on startup in Windows 8.1 on Dell latitude E6520 machines. Every E6520 with windows 8.1.
Error message is:
Log Name:      Application
Source:        Application Error
Date:          4/15/2014 3:54:06 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      ***
Description:
Faulting application name: lync.exe, version: 15.0.4420.1017, time stamp: 0x5067326f
Faulting module name: igdumd32.dll_unloaded, version: 9.17.10.3517, time stamp: 0x532b0b5b
Exception code: 0xc0000005
Fault offset: 0x00001040
Faulting process id: 0x10a0
Faulting application start time: 0x01cf58ecd02118cc
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
Faulting module path: igdumd32.dll
Report Id: 14b4ce16-c4e0-11e3-8255-8c705a44a074
Faulting package full name:
Faulting package-relative application ID:
Video driver in the image was originally out of date, changed the driver to the latest and greatest available straight from Intel for the Intel HD 3000 graphics card and this error still appears. Driver 9.17.10.3517 exceeds the minimum requirement
for Lync 2013. The faulting module is related to the graphics driver, but reinstalling does nothing, uninstalling and then reinstalling does nothing, it cannot further be upgraded. This same error affects all the Dell latitude e6520's. It
also only occurs in Windows 8.1. The windows 7 image using the exact same driver version (both the outdated driver and latest driver) works just fine with Lync 2013.
Running Lync with administrative permissions does nothing, disabling hardware acceleration did nothing. None of our laptops come with the bluetooth adapter, and also updated all other drivers such as chipset and soundcard. Error occurs on the
RTM version of Lync, and Lync with SP1 fully updated. The rest of Office 2013 works fine. I am currently at a loss here short of telling the help desk to not image E6520's with Windows 8.1 because Lync 2013 doesn't work on it. But there has
to be a reason for it. Calling out for some suggestions here.
Thanks!

We also have the same issue with Dell E6420 running Windows 8.1. Lync application does not respond after start-up. Did you try looking for the error file under
C:\users\username\appdata\local\Microsoft\Windows\WER\Reportarchive
it should create file like AppHang_lync.exe_some numbers. search for the latest one.
Interesting, I don't have any 6420's handy but figured the issue would exist on those also. I looked up the location you mention and see many crash logs for Lync. Not really sure what the error is, just says it stopped working.
Version=1
EventType=BEX
EventTime=130420688460358806
ReportType=2
Consent=1
UploadTime=130420688461296414
ReportIdentifier=14b4ce17-c4e0-11e3-8255-8c705a44a074
IntegratorReportIdentifier=14b4ce16-c4e0-11e3-8255-8c705a44a074
WOW64=1
Response.BucketId=3a18275b4e359a3d32b33b327b07846b
Response.BucketTable=5
Response.LegacyBucketId=81648064370
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=lync.exe
Sig[1].Name=Application Version
Sig[1].Value=15.0.4420.1017
Sig[2].Name=Application Timestamp
Sig[2].Value=5067326f
Sig[3].Name=Fault Module Name
Sig[3].Value=igdumd32.dll_unloaded
Sig[4].Name=Fault Module Version
Sig[4].Value=9.17.10.3517
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=532b0b5b
Sig[6].Name=Exception Offset
Sig[6].Value=00001040
Sig[7].Name=Exception Code
Sig[7].Value=c0000005
Sig[8].Name=Exception Data
Sig[8].Value=00000008
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.3.9600.2.0.0.256.4
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
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.
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 (x86)\Microsoft Office\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\apphelp.dll
LoadedModule[5]=C:\windows\SYSTEM32\ADVAPI32.dll
LoadedModule[6]=C:\windows\SYSTEM32\ole32.dll
LoadedModule[7]=C:\windows\SYSTEM32\OLEAUT32.dll
LoadedModule[8]=C:\windows\SYSTEM32\MSVCR100.dll
LoadedModule[9]=C:\Program Files (x86)\Microsoft Office\Office15\LyncModelProxy.dll
LoadedModule[10]=C:\Program Files (x86)\Microsoft Office\Office15\LyncDesktopViewModel.dll
LoadedModule[11]=C:\Program Files (x86)\Microsoft Office\Office15\PropertyModel.dll
LoadedModule[12]=C:\Program Files (x86)\Microsoft Office\Office15\PropertyModelProxy.dll
LoadedModule[13]=C:\Program Files (x86)\Microsoft Office\Office15\RtmMvrAs.dll
LoadedModule[14]=C:\windows\SYSTEM32\MSVCP100.dll
LoadedModule[15]=C:\windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.9600.16384_none_dadf89385bc5c7d7\gdiplus.dll
LoadedModule[16]=C:\windows\SYSTEM32\IMM32.dll
LoadedModule[17]=C:\windows\SYSTEM32\MSIMG32.dll
LoadedModule[18]=C:\windows\SYSTEM32\DWrite.dll
LoadedModule[19]=C:\windows\SYSTEM32\msvcrt.dll
LoadedModule[20]=C:\windows\SYSTEM32\sechost.dll
LoadedModule[21]=C:\windows\SYSTEM32\RPCRT4.dll
LoadedModule[22]=C:\windows\SYSTEM32\combase.dll
LoadedModule[23]=C:\windows\SYSTEM32\GDI32.dll
LoadedModule[24]=C:\windows\SYSTEM32\USER32.dll
LoadedModule[25]=C:\windows\SYSTEM32\MSVCR110.dll
LoadedModule[26]=C:\Program Files (x86)\Microsoft Office\Office15\RtmPal.dll
LoadedModule[27]=C:\Program Files (x86)\Microsoft Office\Office15\RtmCodecs.dll
LoadedModule[28]=C:\windows\SYSTEM32\dxva2.dll
LoadedModule[29]=C:\windows\SYSTEM32\d3d9.dll
LoadedModule[30]=C:\windows\SYSTEM32\d3d11.dll
LoadedModule[31]=C:\windows\SYSTEM32\MSCTF.dll
LoadedModule[32]=C:\windows\SYSTEM32\SspiCli.dll
LoadedModule[33]=C:\windows\SYSTEM32\WINMM.dll
LoadedModule[34]=C:\windows\SYSTEM32\WS2_32.dll
LoadedModule[35]=C:\windows\SYSTEM32\PSAPI.DLL
LoadedModule[36]=C:\windows\SYSTEM32\POWRPROF.dll
LoadedModule[37]=C:\windows\SYSTEM32\pdh.dll
LoadedModule[38]=C:\windows\SYSTEM32\MSVCP110.dll
LoadedModule[39]=C:\windows\SYSTEM32\IPHLPAPI.DLL
LoadedModule[40]=C:\Program Files (x86)\Microsoft Office\Office15\dbghelp.dll
LoadedModule[41]=C:\windows\SYSTEM32\bcrypt.dll
LoadedModule[42]=C:\windows\SYSTEM32\SETUPAPI.dll
LoadedModule[43]=C:\windows\SYSTEM32\WTSAPI32.dll
LoadedModule[44]=C:\windows\SYSTEM32\PROPSYS.dll
LoadedModule[45]=C:\windows\SYSTEM32\VERSION.dll
LoadedModule[46]=C:\windows\SYSTEM32\dwmapi.dll
LoadedModule[47]=C:\windows\SYSTEM32\dxgi.dll
LoadedModule[48]=C:\windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[49]=C:\windows\SYSTEM32\WINMMBASE.dll
LoadedModule[50]=C:\windows\SYSTEM32\NSI.dll
LoadedModule[51]=C:\windows\SYSTEM32\WINNSI.DLL
LoadedModule[52]=C:\windows\SYSTEM32\CFGMGR32.dll
LoadedModule[53]=C:\windows\SYSTEM32\bcryptPrimitives.dll
LoadedModule[54]=C:\windows\SYSTEM32\DEVOBJ.dll
LoadedModule[55]=C:\windows\SYSTEM32\nvinit.dll
LoadedModule[56]=C:\PROGRA~2\Sophos\SOPHOS~1\SOPHOS~1.DLL
LoadedModule[57]=C:\Program Files (x86)\Common Files\Microsoft Shared\Office15\mso.dll
LoadedModule[58]=C:\windows\SYSTEM32\d2d1.dll
LoadedModule[59]=C:\windows\system32\uxtheme.dll
LoadedModule[60]=C:\windows\SYSTEM32\WINSTA.dll
LoadedModule[61]=C:\windows\SYSTEM32\SHELL32.dll
LoadedModule[62]=C:\windows\SYSTEM32\SHLWAPI.dll
LoadedModule[63]=C:\windows\SYSTEM32\shcore.dll
LoadedModule[64]=C:\windows\SYSTEM32\kernel.appcore.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.9600.16384_none_a9f4965301334e09\Comctl32.dll
LoadedModule[70]=C:\windows\SYSTEM32\msi.dll
LoadedModule[71]=C:\Program Files (x86)\Microsoft Office\Office15\1033\lyncDesktopResources.dll
LoadedModule[72]=C:\windows\SYSTEM32\DavClnt.DLL
LoadedModule[73]=C:\windows\SYSTEM32\DAVHLPR.dll
LoadedModule[74]=C:\windows\SYSTEM32\d3d10_1.dll
LoadedModule[75]=C:\windows\SYSTEM32\d3d10_1core.dll
LoadedModule[76]=C:\windows\SYSTEM32\D3D10Warp.dll
LoadedModule[77]=C:\windows\SYSTEM32\sppc.dll
LoadedModule[78]=C:\windows\SYSTEM32\Secur32.dll
LoadedModule[79]=C:\windows\SYSTEM32\clbcatq.dll
LoadedModule[80]=C:\Program Files (x86)\Microsoft Office\Office15\UccApi.dll
LoadedModule[81]=C:\Program Files (x86)\Microsoft Office\Office15\Win32MsgQueue.dll
LoadedModule[82]=C:\windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.9600.16384_none_7c55c866aa0c3ff0\Comctl32.dll
LoadedModule[83]=C:\Program Files (x86)\Microsoft Office\Office15\1033\ocapires.dll
LoadedModule[84]=C:\Program Files (x86)\Microsoft Office\Office15\Psom.dll
LoadedModule[85]=C:\Windows\SYSTEM32\msxml6.dll
LoadedModule[86]=C:\Program Files (x86)\Microsoft Office\Office15\OcImport.DLL
LoadedModule[87]=C:\Program Files (x86)\Microsoft Office\Office15\ocrec.dll
LoadedModule[88]=C:\windows\system32\mlang.dll
LoadedModule[89]=C:\windows\SYSTEM32\usp10.dll
LoadedModule[90]=C:\windows\system32\windowscodecs.dll
LoadedModule[91]=C:\Program Files (x86)\Microsoft Office\Office15\RtmMediaManager.dll
LoadedModule[92]=C:\windows\SYSTEM32\AVRT.DLL
LoadedModule[93]=C:\Program Files (x86)\Microsoft Office\Office15\AppSharingMediaProvider.dll
LoadedModule[94]=C:\Program Files (x86)\Microsoft Office\Office15\RTMPLTFM.dll
LoadedModule[95]=C:\windows\SYSTEM32\WINTRUST.dll
LoadedModule[96]=C:\windows\SYSTEM32\CRYPT32.dll
LoadedModule[97]=C:\windows\SYSTEM32\MSASN1.dll
LoadedModule[98]=C:\ProgramData\Sophos\Web Intelligence\swi_ifslsp.dll
LoadedModule[99]=C:\windows\system32\mswsock.dll
LoadedModule[100]=C:\windows\SYSTEM32\dhcpcsvc6.DLL
LoadedModule[101]=C:\windows\SYSTEM32\dhcpcsvc.DLL
LoadedModule[102]=C:\windows\SYSTEM32\wlanapi.dll
LoadedModule[103]=C:\windows\System32\MMDevApi.dll
LoadedModule[104]=C:\windows\SYSTEM32\MFPlat.dll
LoadedModule[105]=C:\windows\SYSTEM32\RTWorkQ.DLL
LoadedModule[106]=C:\Program Files (x86)\Intel\Media SDK\mfx_mft_h264ve_32.dll
LoadedModule[107]=C:\windows\SYSTEM32\EVR.dll
LoadedModule[108]=C:\windows\system32\NV\nvumdshim.dll
LoadedModule[109]=C:\windows\system32\nvd3dum.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=BEX
AppName=Microsoft Lync
AppPath=C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
ApplicationIdentity=00000000000000000000000000000000

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 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

Lync 2013 Android Client - Intermittently unable to join conference

Hi
I've just finished installing Lync 2013 on our network (single Front End, Single Edge, Reverse Proxy Server and Office Web Apps Server).
Everything works fine currently, with one exception:
When a user tries to join a meeting from the Lync 2013 client on Android (Lollipop), the call generally sits there "connecting..." before it fails to connect with a message of "Can't connect the call".
Sometimes when rejoin is pressed it will connect, but most of the time it fails.
Testing on a Windows Phone client (and Full/Basic Lync 2013 desktop client and Windows 8.1 App) it works every time
Is it possible this is a Lollipop compatibility issue or does Android require something that the other devices and clients don't?
Thanks for any suggestions
Andy

Hi Zahoor
Thanks for the response
Although you suggest it's not a compatibility issue, other devices seem to connect fine on the same account and same wifi, so I'm still tending towards a hardware / os compatibility issue.
I have now tested on a (very old) Samsung Galaxy S (i9000) running Cyanogenmod 11 (KitKat). This works absolutely fine every time.
The device I'm currently seeing issues with is a Nexus 5 running Lollipop.
As I said they're both on the same account and same wifi. Wifi is strong (sitting by the router), internet is a decent speed (150Mbps) and they are external clients.
When I'm back in the office I'll try some other devices to see if they have any problems.I've had a quick look through the logs and couldn't see anything that stood out, but I'll investigate again after seeing if the other devices work.
Cheers
Andy

Lync 2013 basic client msi

Hi all,
Anyone knows where can I find .msi file for Lync 2013 basic client? Microsoft website only have .exe which doesn't work with GPO software deployment.
Thanks

The Basic client doesn't come in an MSI version, the following two links might help you work with the extracted exe:
http://unifiedme.co.uk/2013/04/silent-installation-of-lync-basic-2013-client/
http://community.spiceworks.com/how_to/show/1503-how-to-deploy-office-2010-using-gpo-and-oct
Please mark posts as answers/helpful if it answers your question.
Blog
Lync Validator - Used to assist in the validation and documentation of Lync Server 2013.

Lync 2013 Android Client and simultaneous ring problem

this is sort of a duplicate but since the other one was marked as answered when it was not I figured I'd start this topic up again.
I set up the Android mobile client on my phone and all seemed to work fine (apart from the know bu where it keeps saying "calls aren't setup to ring mobile device..." whether the are or not) but I've run into the super annoying issue where
even if you turn simultaneous ring off for the cell phone number it still rings through when I get a call on my Lync work phone (a bit delayed so it rings just before voice mail picks up). What stinks is that even if I completely sign out of the Lync mobile
app I still get these ring throughs. The only solution was to reinstall the app with a bogus cell number (which is a bad way to go as it might be calling a random number if I'm not careful). the other thread had a moderator give the answer to create a user
level voice policy to not allow simultaneous ringing. Yeah, thanks. I'd actually like to use the feature sometimes and so would all of my users.
So, is this a bug in the Android client? In the Mobile functionality on the server? What? When I run SEFAUtil on my account it doesn't show any simulring or forwarding (my full Lync 2013 client agrees with that) so what the heck is going on. I can't roll
this upgrade from 2010 out to users until this can be resolved.
Steve

I think I found the solution to the annoying ring to the phone even when your turn off your call forwarding/sim ring.
In Lync 2013 desktop client, when you first setup SIM ring, it asks you to enter the phone that you would like to have sim ring. In this case, most likely your cellphone number. Then when you are sick of SIM ring, you decide to turn this feature off, but
you still get SIM ring to your cellphone which is very annoying. If I remember correctly, in Lync 2010, when you switch from SIM ring ON to OFF, the cellphone number will be deleted automatically. In Lync 2013, however, doesn't do so. Therefore, your cellphone
number is still there even though your have call forwarding OFF. This is a bug. The work around to it is to go to Tools > Options > Call Forwarding, select SiM ring; then from the drop down list, instead of choosing your saved cellphone number, choose
WORK number. Then select "Turn Off Call Forwarding". Now, go back to SIM ring option again, you will see the saved cellphone number is now gone. It will only display your work number. Now, try to make a test call to your Lync phone, it shouldn't ring to your
cellphone anymore.
To me, this seems to have fixed it. You can try this and let me know if that fixes yours too.
A@RJC

Lync 2013 android client fails to login bug when ISP overrides DNS

Hello all,
I've noticed an issue occurring in the latest Android client (as of 3/9/2015) with internet networks where the provider resolves all DNS queries to an IP address (e.g. T-Mobile, Cox Cable, and lots of others).
Essentially, sometimes I have noticed my android client stuck on "Signing in". The diagnostic logs show that the client is attempting to resolve http://lyncdiscover.contoso.com (which is not resolvable
externally), but T-Mobile is sending it into a search engine. The app continues to try to connect despite not realizing that it really did not resolve properly. See below logs.
<html><head><meta http-equiv="refresh" content="0;url=http://lookup.t-mobile.com/index.php?origURL=http://lyncdiscoverinternal.contoso.com/"/></head><body><script type="text/javascript">window.location="http://lookup.t-mobile.com/index.php?origURL="+escape(window.location)+"&r="+escape(document.referrer);</script></body></html>
</ReceivedResponse>
Mar 9, 2015 8:26:50 AM ERROR LYNC: ERROR TRANSPORT /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/transport/common/private/TransportUtilityFunctions.cpp/1874:Accept-types (application/vnd.microsoft.rtc.autodiscover+xml;v=1) not found in Content-Type response from server (text/html). Not decoding.
Mar 9, 2015 8:26:50 AM INFO LYNC: INFO TRANSPORT /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/transport/requestprocessor/private/CHttpRequestProcessor.cpp/266:Sending event to main thread for request(0x9a306048)
Mar 9, 2015 8:26:50 AM INFO LYNC: INFO APPLICATION /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/applicationlayer/infrastructure/private/CTransportRequestRetrialQueue.cpp/822:Req. completed, Stopping timer.
Mar 9, 2015 8:26:50 AM INFO LYNC: INFO APPLICATION /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/applicationlayer/infrastructure/private/CUrlRedirectAndTrustResolver.cpp/610:UrlRedirectAndTrustResolver complete with url = http://lyncdiscoverinternal.contoso.com/, Hops = 1, status = E_ResponseUnknown (E2-1-5)
Mar 9, 2015 8:26:50 AM INFO LYNC: INFO APPLICATION /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/applicationlayer/infrastructure/private/CTransportRequestRetrialQueue.cpp/725:Response received for req. UrlTrustResolver(0x9a306048): E_ResponseUnknown (E2-1-5) (RemoteNetworkPermanentError); Done with req.; Stopping resend timer
Mar 9, 2015 8:26:50 AM INFO LYNC: INFO APPLICATION /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/applicationlayer/infrastructure/private/CUcwaAutoDiscoveryGetUserUrlOperation.cpp/393:CUcwaAutoDiscoverGetUserUrlOperation::onEvent received. Status = E_ResponseUnknown (E2-1-5), url = http://lyncdiscoverinternal.contoso.com/
Mar 9, 2015 8:26:50 AM INFO LYNC: INFO APPLICATION /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/applicationlayer/infrastructure/private/CUcwaAutoDiscoveryGetUserUrlOperation.cpp/224:UcwaAutoDiscoveryGetUserUrlOperation completed with url = http://lyncdiscoverinternal.contoso.com/?sipuri=sip:[email protected], userUrl = , status = E_ResponseUnknown (E2-1-5)
Mar 9, 2015 8:26:50 AM DEBUG SigningInActivity: onStop()
Mar 9, 2015 8:26:50 AM DEBUG SigninActivity: onStop()
Mar 9, 2015 8:27:20 AM DEBUG HubActivity: onPause()
Mar 9, 2015 8:27:20 AM DEBUG MyStatusFragment: onPause()
Mar 9, 2015 8:27:20 AM DEBUG ContactsFragment: onPause()
Mar 9, 2015 8:27:20 AM DEBUG HubActivity: onStop()
Mar 9, 2015 8:27:20 AM INFO LYNC: INFO APPLICATION /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/applicationlayer/objectmodel/private/CApplication.cpp/944:CApplication::serialize() called
Mar 9, 2015 8:27:20 AM VERBOSE LYNC: VERBOSE APPLICATION /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/applicationlayer/infrastructure/privateandroid/CCredentialStore.cpp/90:storing credentials for service:0
Mar 9, 2015 8:27:20 AM VERBOSE LYNC: VERBOSE APPLICATION /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/applicationlayer/infrastructure/privateandroid/CCredentialStore.cpp/90:storing credentials for service:1
Mar 9, 2015 8:27:20 AM INFO LYNC: INFO APPLICATION /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/applicationlayer/objectmodel/private/CBasePersistableEntity.cpp/179:Storing 1 out-of-sync Object Models took 32ms
Mar 9, 2015 8:27:20 AM INFO LYNC: INFO UTILITIES /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/platform/persistentstorage/private/CBasePersistableComponent.cpp/245:Storing 3 out-of-sync components took 1ms
Mar 9, 2015 8:27:20 AM INFO PreferencesManager: commit is called on
Mar 9, 2015 8:27:20 AM DEBUG MyStatusFragment: onStop()
Mar 9, 2015 8:27:20 AM DEBUG ContactsFragment: onStop()
Mar 9, 2015 8:27:27 AM ERROR HttpConnection: org.apache.http.conn.HttpHostConnectException: Connection to https://lyncdiscoverinternal.contoso.com refused
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:183)
at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:164)
at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:119)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:360)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:555)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:487)
at com.microsoft.office.lync.platform.http.HttpEngine.execute(HttpEngine.java:502)
at com.microsoft.office.lync.platform.http.HttpConnection$1.run(HttpConnection.java:219)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:422)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:818)
Caused by: java.net.ConnectException: failed to connect to /198.105.244.104 (port 443) after 180000ms: isConnected failed: ECONNREFUSED (Connection refused)
at libcore.io.IoBridge.isConnected(IoBridge.java:238)
at libcore.io.IoBridge.connectErrno(IoBridge.java:171)
at libcore.io.IoBridge.connect(IoBridge.java:122)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:183)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:456)
at java.net.Socket.connect(Socket.java:882)
at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:144)
... 12 more
Caused by: android.system.ErrnoException: isConnected failed: ECONNREFUSED (Connection refused)
at libcore.io.IoBridge.isConnected(IoBridge.java:223)
... 19 more
Since DNS overrides by ISPs are a common occurance, I believe the app should properly handle this situation. I installed an app to override my DNS and use Google's DNS servers, and the client connects fine.

Hi,
Did you login Lync 2013 mobile client internal or external the company?
Did the issue also happen for IOS/Windows Phones or just happen for Android Phones?
Please try to check if the issue only happen for your mobile Lync client or also happen for other Android mobile clients.
If the issue only happen for your Android mobile, please try to uninstall Lync client and install the latest version from Android Market and test the issue again.
If the issue happen for multiple mobile clients, please double check the Reverse Proxy settings, if you use IIS ARR for Reverse Proxy, you can troubleshooting with the help of the link below:
http://blogs.technet.com/b/nexthop/archive/2013/02/19/using-iis-arr-as-a-reverse-proxy-for-lync-server-2013.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
Ok, I figured out that I had a partial misconfiguration, but the existing client behavior still leads to long delays on a variety of networks. I had the reverse proxy forwarding into port 80 instead of 8080, which seemingly caused problems
during the second autodiscovery phase after the first timed out. I have since confirmed that it's not just T-Mobile, but any such provider (e.g. Cox Cable, see below) that resolves all DNS entries.
Essentially, the following is happening:
1) Client attempts to resolve lyncdiscoverinternal first.
2) DNS record resolves to ISP's website, because they resolve everything and will return their own page if the entry really doesn't exist.
3) Lync client continues to try to connect to the ISP's address, and sits for at least a minute until it eventually falls to the lyncdiscover record.
From the below log entries, you can see that the login process is delayed a full minute due to the client being stuck on the lyncdiscoverinternal record! Again, this does not occur on ISPs that do not catch all DNS resolution
attempts, regardless of validity.
Mar 9, 2015 8:10:04 PM INFO HttpConnection: originalurl is
https://lyncdiscoverinternal.contoso.com/?sipuri=sip:[email protected] method Get
Mar 9, 2015 8:10:04 PM INFO HttpConnection: decodedurl is
https://lyncdiscoverinternal.contoso.com/?sipuri=sip:[email protected]
Mar 9, 2015 8:10:04 PM INFO LYNC: INFO TRANSPORT /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/transport/common/private/TransportUtilityFunctions.cpp/689:<SentRequest>
GET
https://lyncdiscoverinternal.contoso.com/?sipuri=sip:[email protected] 9, 2015 8:10:05 PM INFO LYNC: INFO APPLICATION /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/applicationlayer/infrastructure/private/CUcwaAutoDiscoveryGetUserUrlOperation.cpp/224:UcwaAutoDiscoveryGetUserUrlOperation
completed with url =
http://lyncdiscoverinternal.contoso.com/?sipuri=sip:[email protected], userUrl = , status = E_ResponseUnknown (E2-1-5)
GET http://lyncdiscoverinternal.contoso.com/
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "<html><head><meta">http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html><head><meta
http-equiv="refresh" content="0;url=http://finder.cox.net/main?InterceptSource=0&ClientLocation=us&ParticipantID=96e687opkbv4scrood8k84drs6gw5duf&FailureMode=1&SearchQuery=&FailedURI=http%3A%2F%2Flyncdiscoverinternal.contoso.com%2F&AddInType=4&Version=2.1.8-1.90base&Referer=&Implementation=0&method=GET"/><script
type="text/javascript">url="http://finder.cox.net/main?InterceptSource=0&ClientLocation=us&ParticipantID=96e687opkbv4scrood8k84drs6gw5duf&FailureMode=1&SearchQuery=&FailedURI=http%3A%2F%2Flyncdiscoverinternal.contoso.com%2F&AddInType=4&Version=2.1.8-1.90base&Referer=&Implementation=0&method=GET";if(top.location!=location){var
w=window,d=document,e=d.documentElement,b=d.body,x=w.innerWidth||e.clientWidth||b.clientWidth,y=w.innerHeight||e.clientHeight||b.clientHeight;url+="&w="+x+"&h="+y;}window.location.replace(url);</script></head><body></body></html>
</ReceivedResponse>
Mar 9, 2015 8:10:21 PM INFO LYNC: INFO APPLICATION /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/applicationlayer/infrastructure/private/CUcwaDataSynchronizer.cpp/799:Mode 0
timed out
Mar 9, 2015 8:11:08 PM ERROR HttpConnection: org.apache.http.conn.HttpHostConnectException:
Connection to https://lyncdiscoverinternal.contoso.com refused
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:183)
Mar 9, 2015 8:11:08 PM INFO LYNC: INFO TRANSPORT /Volumes/ServerHD2/buildagent/workspace/200604/tps/ucmp/ucmp/transport/common/private/TransportUtilityFunctions.cpp/1032:<ReceivedResponse>
GET http://lyncdiscover.contoso.com/

External Meetings using Lync Web App vs Lync 2013 Desktop client

We have LYNC Server 2013 deployed on premise. Our clients are LYNC 2013. When someone external to our organization sends us a Lync meeting request we are able to connect with our Lync 2012 desktop client but only Audio is available. We cannot share
the desktop. If however we connect to the external meeting using the Lync Web App (by specifying
?sl=1 at the end of the meeting url) we are able to use all the services like audio, desktop sharing etc.
I've found the following articles that suggest that the desktop clients are not the preferred choice to connect to external meetings.
http://blog.schertz.name/2011/11/forcing-lync-web-app/
http://www.computer-talk.com/en/blog/item/attendees-cannot-join-your-lync-web-conference
Can anyone advise as to why the desktop clients are restrictive and if there is a fix and if not how can we force users to use the Lync Web App to connect to external meetings?
Our lync 2013 desktop clients use the following ports:
PS C:\Users\am03744ad> Get-CsConferencingConfiguration
Identity                           : Global
MaxContentStorageMb                : 500
MaxUploadFileSizeMb                : 500
MaxBandwidthPerAppSharingServiceMb : 375
ContentGracePeriod                 : 15.00:00:00
ClientMediaPortRangeEnabled        : True
ClientMediaPort                    : 5350
ClientMediaPortRange               : 40
ClientAudioPort                    : 50020
ClientAudioPortRange               : 20
ClientVideoPort                    : 58000
ClientVideoPortRange               : 20
ClientAppSharingPort               : 42000
ClientAppSharingPortRange          : 20
ClientFileTransferPort             : 42020
ClientFileTransferPortRange        : 20
ClientSipDynamicPort               : 7100
ClientSipDynamicPortRange          : 3
Organization                       :
HelpdeskInternalUrl                :
HelpdeskExternalUrl                :
ConsoleDownloadInternalUrl         :
ConsoleDownloadExternalUrl         :

You should be fine using the full Lync client, it's not restricted by default. If there's an issue, it's typically in the networking related to your edge, or the edge of the organization you're federating with.
The reason the web client is preferred by many (not all, and that's not an official Microsoft stance), is simply that if everyone uses the web client, it's a consistent experience for the attendees and you don't have to worry about the status of attendee's Lync
environment or federation.
Can your external users share a desktop with internal users? Can they do it externally in a conference hosted by you? Can the remote organization share desktops with you when connected to your conferences? And in these conferences,
have the marked you as presenter so you can present your desktop?
There's no good way to automatically force users to use the web app each time unfortunately. The other organization would need to hardcode that ?sl=1 into each meeting invite sent.
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

InDesign CS6 crashes at startup after windows 7 update

InDesign crashes at startup after windows 7 update: Faulting module path: C:\Windows\system32\MSVCR100.dll (Microsoft Visual C runtime and update KB2538243 and KB2565063)
Reinstalling did not help
Also Adobe Encore CS6 seems to be affected

I looked at the recovery files in:
C:\Users\MyName\AppData\Local\Adobe\InDesign\Version 8.0\en_US\Caches\InDesign
I deleted all the files and Indesign started up fine. feeling good I closed Indesign and restarted.
Indesign Crashed again.
Deleted all files again and reloaded.
I went to "Edit:Preferences:File Handling:Document Recovery Data" to:
G:\Adobe\Indesign\Cache\Recovery
Interestingly, the Indesign application recovery files still reside in the user directory above. But the document recovery data moves to the G drive above.
There is no clear reason why Indesign quit loading today. It worked fine since initial installation last year. But separating the document recovery data from the application recovery data seems to fix the problem for now.

Lync 2013 Recording Manager Crashes

Environment Background:
1. Lync 2010 Front-End Pool
2. Workstation running Windows 8 and Lync 2013 Client
I am able to record meetings with my Lync client but when I click stop and go to launch recording manager, the application opens and then hangs. Below is the Error from the event log
Faulting application name: OcPubMgr.exe, version: 15.0.4481.1000, time stamp: 0x50ee68d6
Faulting module name: MFReadWrite.dll, version: 12.0.9200.16384, time stamp: 0x50108233
Exception code: 0xc0000005
Fault offset: 0x0001ddc9
Faulting process id: 0x11a4
Faulting application start time: 0x01ce7f2b93c36813
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\OcPubMgr.exe
Faulting module path: C:\Windows\SYSTEM32\MFReadWrite.dll
Report Id: d20fec8a-eb1e-11e2-be72-70f3957a2ef1
Faulting package full name:
Faulting package-relative application ID:
I am able to use recording manager on a Windows 7 workstation with the Lync 2013 client without any issues. I have tried a clean boot into windows 8 to clear third party start applications, Uninstalled the lync component of Office, rebooted, reinstalled
component without success.
Any help is appreciated. Thanks in advance.
Jason Apt, Microsoft Certified Master | Exchange 2010
My Blog

My problem was with Lync Recording Manager crashing with details in the OP's first post. LRM would crash as soon as it started to process the .mp4 file. Uninstalling Citrix Receiver fixed my crash issue completely.
LRM starts to process the files in
%UserProfile%\AppData\Local\Microsoft\Communicator\Recording Manager\Temporary Recording Files
and would save them elsewhere when process is complete.
Another issue was that LRM would not for some reason process the files in one of the recording-folders in the above 'Temporary Recording Files' folder. You can get around this by creating a new Lync meeting with yourself, start recording, then stop recording
& exit LRM at about the same time. This will create a new temp folder to be processed by LRM. Delete files in that new folder, and copy files from your old meeting to the newly created folder to kickstart processing for the old files
Lync 2013 client, Win7

How can I manually verify autodiscovery configuration for on premise environment from Lync 2013 desktop client?

I have very limited access to an environment (basically just user access). I am documenting the Lync 2013 cilent for this environment. I was provisioned a limited SIP enabled account for testing. Autodiscovery from the Lync 2010 client works, but not from
the 2013 client. I can connect (with some issues) from either 2010 client (autodiscovery) and 2013 client (manually configuring the server). So I want to verify if the Autodiscover is configured correctly to work with the 2013 client or not and if the reason
it fails for me is due to something wrong with my account or if this will happen with other users?
I have checked the lyncdiscoverinternal.domain.com and it resolves and is reachable. I can navigate to https :// lyncdiscoverinternal.domain.com/Autodiscover/AutodiscoverService.svc/root/domain and it returns the information I would think it should
including hrefs to Internal/Autodiscover, Internal/AuthBroker, External/Autodiscover, External/AuthBroker, Internal/Mcx & External/Mcx as well as fqdns for SipClientExternalAccess, SipClientInternalAccess, SipServerExternalAccess & SipServerInternalAccess.
The AuthBrokers urls return what I believe is the expected RemoteService Service pages. The Mcx urls return what I believe is the expected McxService2 Service pages. The SipClientInternalAccess & SipServerInternalAccess fqdns are both resolvable and
reachable. The Autodiscover urls return hrefs for Domain and User. Those Domain urls return the same information as the initial root/domain url and the user url (which I believe is the one that is actually opened by lync during the autodiscover process) returns
what I believe is an expected 401 - Unauthorized: Access is denied due to invalid credentials page.
If I explicitly configure the Lync 2013 client to use the fqdn listed for SipClientInternalAccess, the client will log me in. However on Automatic configuration, it fails to log me in.
One other note is that when I watch with Wireshark, I observed that it is getting another internal server fqdn from somewhere. We'll just say that the SipClientInternalAccess fqdn is lyncABC.domain.internal. When looking at Wireshark and the DNS requests,
I'm also seeing a lync2013ABC.domain.internal that does resolve and is reachable and can also be used as the explicitly listed server in the Lync 2013 client and it will log in. However, that fqdn is not listed in any of the root or domain url replies. So
I'm not sure where it is coming from or how to check that.
Is there any additional information anywhere that can tell me exactly what the behavior of the 2013 client is when trying to find the server to authenticate to and how I can reproduce any missing steps manually to determine what it is identifying as the
login server (if any) since it is obviously not the trying the one listed as SipClientInternalAccess?
Thanks,
Richard

Hi Richard,
To narrow down the issue, you could refer to the following steps first.
1. Delete the Lync client 2013 user profile and registry key.
User profile:
%userprofile%\AppData\Local\Microsoft\Office\15.0\Lync\[email protected]
Registry Key:
HKCU\Software\Microsoft\Office\15.0\Lync\[email protected]
Certificate:
a. Open Windows Certificate Manager. To do this, press Windows + R, type certmgr.msc, and then click OK.
b. Expand Personal, and then expand Certificates.
c. Look for a certificate that's issued by Communications Server and delete it.
2. Upgrade Lync client to the latest update.
3. Check the DNS records(A records and SRV records) again.
Best regards,
Eric

Lync 2013 mobile client can't see all fields in contact card

We have deployed Lync 2013 infra in our organization, now we observed, mobile Lync client users are not able to see other users mobile number on contact card rest all information is visible.
Is there any workaround or fix to resolve this issue. Appreciate quick help.

That's effectively by design (but a popular complaint). The workaround is to put the users who's mobile numbers you need in your Outlook contact list. There's another workaround related to setting the privacy relationship, but you have to coordinate
it with many people which is not too feasible.
Here are others upset about it:
http://ammarhasayen.com/2013/09/25/lync-2013-mobile-contact-card-not-showing-mobile-number/
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 Mobile client on Windows phone

Hello All,
I am configuring Lync 2013 client and lync 2013 server.
When i try to sign in on Windows Mobile, it does not sign in. Log file also empty.
I uses IIS ARR as RP. Is there any way to see logs on IIS ARR ?
regards

Hi,
Did the issue happen only for you or for multiple users?
You can login manually in your Windows Lync client:
https://<ExtPoolFQDN>/Autodiscover/autodiscoverservice.svc/Root for external access
https://<IntPoolFQDN>/AutoDiscover/AutoDiscover.svc/Root for internal access
You can check Reverse Proxy (IIS ARR) with the help of the link below:
http://blogs.technet.com/b/nexthop/archive/2013/02/19/using-iis-arr-as-a-reverse-proxy-for-lync-server-2013.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync 2013 Mobile Client

have a test Lync 2013 onprem installation, everything works fine both from inside and outside, however the Lync Client for iphone does not function as supposed. I checked debug logs on all servers and see nothing that could cause the behaviour. The strange
thing is that for example IM is actually working, the problem is that it disconnects on every action.
So, the test scenario is as following
- User 1 is logged on Lync Client on Windows 7 - LAN
- User 2 is logged on on Lync Mobile on Iphone - public internet
User 1 sees presence of User 2
User 1 sends IM message to User 2 - no errors
User 2 successfully recieves the message - gets an error "Failed to process the server respons" and appears offline
User 2 signs out of Lync Mobile and signs back In- no errors
User 2 sends IM message back to User 1 - gets an error "Failed to process the server respons" and appears offline
User 1 recieves the IM message - no error
Any glues anyone? Where to look? I used debugging tools (S4 and SIPStack) both on Edge and FE and found nothing strange
Thanks in advance
Emin

Hi,
Which kind of Reverse Proxy did you use (TMG or IIS ARR)?
Did the issue only happen to you or for multiple users?
Did the issue only happen for IPhone or for all kind of mobile clients (IOS, Android, Windows Phone)?
If the issue happen only for you, please try to use another mobile and test the issue again.
If the issue happen for multiple users, and only happen for IOS client, try to update to the latest version for Lync IOS client and test again.
If the issue happen for multiple users, and happen for all kind of mobile platforms, double check the configuration of Reverse Proxy ( certificate, port).
For WP8 root certificates need to have HTTP URLs in the CRL (Certificate Revocation List). If root certs doesn’t contain these CRL attributes than the certificate won’t be accepted by WP8 and sign in would fail.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync 2013 RTM client crashing on startup in Windows 8 RTM

Similar Messages

Maybe you are looking for