Lync 2013 recording presentation

Hi all,
I enabled the lync conferencing and I still don't have the option record my presenation. Anything I'm missing? I can't click on publish and i don't see anything in the record settings. Any help with be greatly appreciated! Screenshots attached.

It wouldn't be in the recording manager, it would be in the ellipsis menu. This only works if it's actually a conference, meaning that you'd have more than 2 participants, or it was joined via a meet now or scheduled meet link.
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
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Similar Messages

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

Lync 2013 FE server certificate - different domain name

Hi,
I am implementing a small Lync infrastructure with the following components in a Resource Forest - Account Forest type implementation with a bi-directional Trust between the two forests:
1 x Lync 2013 FE Standard, 1 x Mediation server and 1 x Office Web App server
Both AD forests have their PKI CAs, the certificate on the FE server is signed by the CA from the Account domain. All servers and workstations have both Root certificates implemented.
User’s SIP domain name (account forest) is different from the FE server (resource forest) domain name.
Question: When internal users sign-in to Lync they get a warning prompt as follows:
“Lync cannot verify that the server is trusted for your sign-in address. Connect anyway?”
Users can select to connect and everything functions correctly, however, I would like to get rid of the warning message at the beginning.
Any idea what may be wrong, is something missing on the certificate ?
Thanks for your help,
Luca

You can try to edit the internal web services FQDN and ensure your other populated DNS records point to a FQDN that matches the sip domain, or use the TrustModelData workaround here:http://support.microsoft.com/kb/2833618
Here are a couple extra articles that dive in to what's happening: http://terenceluk.blogspot.com/2013/04/signing-into-lync-2013-client-presents.html?m=1
http://blogs.technet.com/b/jenstr/archive/2011/02/10/lync-cannot-verify-that-the-server-is-trusted-for-your-sign-in-address.aspx
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
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Audio and video not synchronized in recording made with Lync 2013

There appears to be no forum for the Lync 2013 client yet, so I am posting this in the Lync 2013 server forum.
Environment: Lync 2013 Server and Lync 2013 32-bit client. Only one Lync pool. Conference call was scheduled using "Lync Meeting" in Outlook about a week before the call. Call recorded on a laptop that was plugged into our LAN with an Ethernet
cable.
Problem: User scheduled a conference call with screen sharing (PowerPoint) and recorded the call. The audio and video are not synchronized in the recording. There is several minutes' delay, with the audio lagging behind the PowerPoint. The last slide
on the call was presented, the call ended, and the presenter ended the recording (I was present for all this and can confirm no user error in these steps); however, in the recording, the slides change before the speaker talks about it, and the last
couple of minutes are cut off.
Any ideas on why this happened? Web research has failed me. Thank you.

You may need to lower the recording quality as your PC might not be able to keep up the pace.
Go to Options in Lync client -> Recording -> Select 480p
Then test again
- Belgian Unified Communications Community : http://www.pro-lync.be - MCM/MVP/MCT

Error When Share PowerPoint Presentation. "This slide couldn't be downloaded. Error reason : name not resolved lync 2013"

Hi Partner,
I got an error as per title above when I'm sharing the powerpoint presentation within Internal.
Below are the detail of our new deployment :
- 3 SQL Servers, 3 Front End Servers, 2 Web App Servers.
- Lync 2013 Enterprise Edition
Below are the steps that i did for web app servers :
1. owapp01
- install pre-requisite
- install Microsoft Office Web Application
- install WAC Language Pack
- run command New-OfficeWebAppsFarm -InternalURL “https://LyncWAC.YourDomain.Local” -ExternalURL "https://WACsrv.domain.com" –CertificateName “My WAC Server” -EditingEnabled
2. owapp02
- installpre-requisite
- install Microsoft Office Web Application
- install WAC Language Pack
- run Command New-OfficeWebAppsMachine -MachineToJoin owapp01.yourdomain.local
3. Configure NLB follow http://blogs.technet.com/b/meamcs/archive/2013/03/27/office-web-apps-2013-multi-servers-nlb-installation-and-deployment-for-sharepoint-2013-step-by-step-guide.aspx
I can open the https://lyncwac.yourdomain.local/hosting/discovery from Web app server, Front end, Client Machines.
When I try to share the powerPoint Presentation, it shows below error on atendee
From Presenter side the error is : Some Presenting Features are unavailable due to server connectivity issues.
Below is what i got from event viewer log :
Log Name:      Lync Server
Source:        LS Data MCU
Date:          12/19/2013 4:04:26 PM
Event ID:      41033
Task Category: (1018)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      lyncfe01.domain.local
Description:
Office Web Apps Server (WAC) discovery failed, PowerPoint content is disabled.
Attempted Office Web Apps Server discovery Url: https://OfficeWebAppInt.domain.local/hosting/discovery/
Received error message: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
The number of retries: 29, since 12/19/2013 3:46:26 PM.
Cause: Office Web Apps Server may be unavailable or network connectivity may have been compromised.
Resolution:
Check HTTPS connectivity from this box to the Office Web Apps Server deployment using the discovery Url.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="LS Data MCU" />
    <EventID Qualifiers="50170">41033</EventID>
    <Level>2</Level>
    <Task>1018</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-12-19T09:04:26.000000000Z" />
    <EventRecordID>2013</EventRecordID>
    <Channel>Lync Server</Channel>
    <Computer> LYNCFE01.domain.local</Computer>
    <Security />
</System>
<EventData>
    <Data>https://OfficeWebAppInt.domain.local/hosting/discovery/</Data>
    <Data>Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.</Data>
    <Data>29</Data>
    <Data>12/19/2013 3:46:26 PM</Data>
</EventData>
</Event>
Thank you.
Assraf Kamaruddin Suria Business Solutions Sdn. Bhd.

Hi Lisa,
the Office Web Apps Server discovery URL defined in Lync Topology is https://officewebappint.domain.local/hosting/discovery.
the issue still persist. I hope there is any other solutions.
THank you for your feedback.
Assraf Kamaruddin Suria Business Solutions Sdn. Bhd.

Lync 2013 actual size of shared presentation does not fit to window

In Lync 2013 with Win 8 - I am unable to click the actual size (fit to window) icon and see a change on screen so data being presented is hard to read. I click the icon and nothing happens.
How can I resolve this?

Hi,
Please try following registry key to change IM window size.
HKCU:\Software\Microsoft\Office\15.0\Lync
IMGCNoExtensionTabbedFrameWidth
IMLargeExtensionTabbedFrameWidth
IMMediumExtensionTabbedFrameWidth
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync 2013 DNS records

Hello,
Have been working on my Lync 2013 deployment for a while and until today I am still not quite sure about some DNS entries, especially confused by MS planning tool DNS Report. Here is my setup:
2013 enterprise, 3 FE servers in a pool (lyncpool01.domain.local), 3 BE SQL servers, 1 WAC server in a farm (wacfarm.domain.local) , Kemp HLB (cswebint.domain.local and wacfarm.domain.local), TMG server as reverse proxy and 1 edge server ( lyncedge01.domain.local)
in a pool ( lyncedgepool.domain.local)
sip domain name: domain.com
Please help to clarify, in "domain.com" zone on my internal DNS server
1) lyncdiscoverinternal.domain.com:
MS planning tool does not have it in DNS report. Should I point it to lyncpool.domain.local as a CNAME record, or 3 A records pointing to the FE servers, or point to the reverse proxy server external DMZ address?
2) _sipinternaltls._tcp.domain.com
MS planning tool says pointing to lyncpool01.domain.local, should I point it to sip.domain.com?
3) cswebint.domain.local and cswebext.domain.com
Should I point both to the VIP of the kemp HLB?
4) lyncdiscover.domain.com
Should I create 3 A records pointing to the FE servers, or one CNAME record pointing to lyncpool01.domain.local?
Thanks in advance.

Let me see if I can help you make sense of what you have:
1. LyncDiscoverInternal
You don't really need this record as lyncdiscoverinternal just will re-direct you back to lyncdiscover.
2. _sipinternalts
This should be in your internal DNS SRV records point to lyncpool.
3. Are you using your Kemps for HLB for all Lync services and/or Lync Web Services?
I'm going to guess below without knowing:
cswebext = your external DNS A record for Lync Web Services connectivity point to your reverse proxy solution. If that is the Kemp in this case, then the DMZ VIP.
cswebint = you internal DNS A record for Lync Web Services. This would point to you internal VIP.
4. LyncDiscover
This should be an external DNS A record pointing to your reverse proxy, which is the same external VIP as cswebext.
Hope this helps,
Please “Vote As Helpful” and/or “Mark As Answer” if this post helped you. Thanks!
Adam Curry, UC Consultant, Unify Square Inc. (Blog,
Twitter)
Looking for Lync Users Groups in your area? Check out
Lync Users Group

Lync 2013 to CUPS RCC - Record-Route signature is invalid

Hi all,
             I have a Lync 2013 environment and I'm trying to implement RCC with a CUPS 10 environment.
On the Lync side, I have run the following commands:
$tcpRoute = New-CsStaticRoute -TCPRoute -Destination 10.10.120.54 -Port 5060 -MatchUri cups.domain.com -ReplaceHostInRequestUri $true
Set-CsStaticRoutingConfiguration -Route @{Add=$tcpRoute}
CsTrustedApplicationpool -Identity 10.10.120.54 -Registrar LyncFE.domain.com–Site 1 –TreatAsAuthenticated $True –ThrottleAsServer $True –RequiresReplication $False
New-CsTrustedApplication -ApplicationID RCCGateway-1 –TrustedApplicationPoolFqdn 10.10.120.54 -Port 5060 -EnableTcp
Set-CsRegistrar registrar:LyncFE.domain.com -SipServerTcpPort 5060
on the test user I have set
Set “Telephony” to:
Remote call control
Set Line uri to:
tel:<ext>;phone-context=dialstring
Set Line server uri to:
sip:<username>@cups.domain.com
In the SIP logs I get the following (I have bolded the bits I think are important)
TL_INFO(TF_PROTOCOL) [0]1FDC.1670::02/19/2015-05:35:53.687.001b274e (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(265))[1932678887] $$begin_record
Trace-Correlation-Id: 1932678887
Instance-Id: 45F
Direction: incoming
Peer: 10.10.120.54:5060
Message-Type: response
Start-Line: SIP/2.0 200 OK
From: "Test ADL"<sip:[email protected]>;tag=224a04a9f9;epid=fa015fbbdb
To: <sip:[email protected]>;tag=29e9c078-ce4a5e7
Call-ID: 669e8717f0a0487fb09aed392d84f589
CSeq: 1 INVITE
Contact: <sip:[email protected]:5060;transport=TCP>
Via: SIP/2.0/TCP 10.70.11.70:52575;received=10.70.11.70;branch=z9hG4bKE005ADB2.742BA66DD49B1869;branched=FALSE;ms-internal-info="aaweLh0WVLdGLzdpabeIHETcyFKD5xJlVJz_tnBJ0l-7ptpit0RW23IQAA", SIP/2.0/TLS 10.70.20.36:52402;ms-received-port=52402;ms-received-cid=1A00
Record-Route: <sip:[email protected]:5060;maddr=10.10.120.54;transport=tcp;lr>,<sip:LyncFE.domain.com;transport=tcp;opaque=state:T;lr;ms-route-sig=aaF2AA9BciRLZcYZPN0XasMmn8g4LiFd4j7Fdcxg6R6uRtpit0mCXPOAAA>;tag=7E7648A7380D372597F42EAEAECC07A2
Content-Length: 190
Content-Type: application/csta+xml
Message-Body: <?xml version="1.0"?>?<RequestSystemStatusResponse xmlns="??<systemStatus>normal</systemStatus>?</RequestSystemStatusResponse">http://www.ecma-international.org/standards/ecma-323/csta/ed3">??<systemStatus>normal</systemStatus>?</RequestSystemStatusResponse>?
$$end_record
TL_ERROR(TF_SECURITY) [0]1FDC.1670::02/19/2015-05:35:53.687.001b2b66 (SIPStack,SIPAdminLog::WriteSecurityEvent:SIPAdminLog.cpp(319))[1932678887] $$begin_record
Text: Record-Route signature is invalid
Result-Code: 0xc3e93f1e SIPPROXY_E_INVALID_RECORD_ROUTE
Connection-ID: 0x1300
Peer-IP: 10.10.120.54:5060
Peer: 10.10.120.54:5060
SIP-Start-Line: SIP/2.0 200 OK
SIP-Call-ID: 669e8717f0a0487fb09aed392d84f589
SIP-CSeq: 1 INVITE
$$end_record
TL_WARN(TF_DIAG) [0]1FDC.1670::02/19/2015-05:35:53.687.001b2b74 (SIPStack,SIPAdminLog::WriteDiagnosticEvent:SIPAdminLog.cpp(805))[1932678887] $$begin_record
Severity: warning
Text: Routing error occurred; check Result-Code field for more information
Result-Code: 0xc3e93f1e SIPPROXY_E_INVALID_RECORD_ROUTE
SIP-Start-Line: SIP/2.0 200 OK
SIP-Call-ID: 669e8717f0a0487fb09aed392d84f589
SIP-CSeq: 1 INVITE
Peer: 10.10.120.54:5060
$$end_record
I have not had any luck finding the solution to this as yet - and any suggestions as to what I have done wrong would be appreciated.
Edit - apparently bold doesn't work.... sorry - it works in the editor, but not when I save the post! Please look at the ":record-route" line in the first log and the result code in the next two entries.

Hi Ben, thank you for your update.
To clarify, the
device=SEP0123456789F is an example, you have to change it with the correct Cisco IP-Phone serial number used by your user.
I've checked every step of your procedure and I've not found any issue, I've used the same procedure with a Cisco CUPS 10 and everything works fine.
Please be sure to check this on Cisco:
- the MatchURI need to be equal to the Cisco Unified Presence Domain
- on the CUCM the CTI Account (default is CtiGw) nned to have CTI controll of every phone (Standard CTI Allow Control of Phone supporting Connected Xfer and conf) and Supporting Rollover Mode
- it's important that the "Standard CTI Secure Connection" group is NOT associated to the CtiGw account (if it's associated it force the connection to TLS).
Let me know.
Regards
Luca
Luca Vitali | MCITP Lync/Exchange | snom Certified Engineer | Sonus SBC1000 Engineer

Lync 2013 : two problems 1) quicked off from meeting when presenter change 2) Freeze when leaving first call of day

Hello,
I have two problems with Microsoft Lync 2013 (see level in screenshot). The first one appeared after May Windows updates and is so annoying that I decided myself to open a post in this forum, with the second one. The first problem is the most important for
me (see why when reading) and the second one is the cherry on the cake if solved, but is minor.
1) I'm kicked off from meetings when presenters change
In an online meeting, when presenters change, I'm kick off since last May updates (very clear since it didn't happen before). I'm unable to specify if it occurs when I'm presenter or just attendee, but that could influence. I will try to report if/when I
notice a difference.
THIS IS REALLY IMPORTANT, Please help me solve this !
2) Lync freezes for approx. 30' to 1min. when leaving first call of day
I reboot my PC every day. I always notice that after leaving voice call from my first meeting of the day, Lync freezes (doesn't respond message) for 30' to 1min. This is when I leave audio, not meeting window. This never occurs again in the course of the
day. Windows goes into hourglass, then it works again.
Does anyone know about this ? Any action to help diagnose or solve this ?
Again this is less important than first problem
Thanks for help
-Pierre

The steps to remove the update:
Open Control Panel, click Programs, and then, under Programs and Features, clicking View installed updates.
Click the update that you want to remove, and then click Uninstall.
For Lync 2013 May 2014 update, it is KB2880980.
You can check the following website about the drivers:
http://www.driverscape.com/download/plantronics-c320-m
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Lisa Zheng
TechNet Community Support

No audio device detected - Lync 2013 Client

I have a brand new Dell Latitude E6430 laptop running Windows 7 x64 SP1. I installed Office 2013, including the Lync 2013 client. We are running Lync 2013 server as well. I have connected three different audio devices.
Polycom CX600 phone.
Plantronics Bluetooth headset.
Logitech Video Camera (The video on this works with Lync but no audio)
I cannot get Lync to recognize either of them. I can see them as devices in Windows but within Lync I only get a screen that says "We didn't find an audio device, which you need for calling". Does anyone have any idea on how to resolve this issue?
It is driving me crazy. Especially since it worked perfectly on my old laptop that had the same OS and patches, etc...
Thanks for your help in advance.
Jamie

Had the same issue. For me it required uninstalling the Intel Widi device from device manager. I think it was titled "wiusb" or something similar. It was in its own group in device manager. After uninstalling that, Lync would then
recognize my mic/speakers again.
I had the exact same problem as everyone else. I purchased two Dell Latitude E6530 laptops with Windows 7 Pro 64-bit. Both laptops had the issue. I uninstalled the WIUSB devices, restarted Lync, and Lync suddenly is able to detect devices...
I refreshed device manager to see if the devices would auto-install again... but there weren't detected again.
William Christenson
This worked for me as well. Uninstalled the WIUSB and WIUSB Host Controller which was present under its own group, Exit Lync process and started again, it detected the Sound Devices again. Definitely a driver conflict but it was quick resolution to uninstall
and get it working. No other issues with user as far as another device stopped working due to uninstallation of the devices.
It does not look like any driver conflicts, all other software detects audio device perfectly (Skype, Recorder,softphone, Lync 2010 etc.), but only Lync 2013 client keeps saying ""we didn't find an audio device". it appears the faulty in Lync 2013 client

EWS not deployed anymore to Lync 2013 Desktop Clients, Mobile Clients still working fine

Hello dear community,
the subject of EWS in conjunction with Lync 2013 has been discussed a lot here .
However, I could not find here any solution for my problem and I'm (almost) at my end.
Following scenario - 1 x Lync 2013 BE server, 1 x Lync 2013 Edge server, 1 x reverse proxy (IIS ARR). This Lync 2013 deployment
was installed about two months ago and integrated into existing IT landscape. Everything worked wonderfully - desktop and mobile clients were able to connect from inside and outside our organization, EMS was deployed to both desktop and mobile clients.
After that there are no any configuration changes made on Lync server, and yesterday, shortly before an important presentation
I've found, that EWS is not deployed anymore on all desktop clients. Mobile clients, however, continue to function smoothly.
I have tried the following: restart Lync and reverse proxy servers - without success, Lync Connectivity Analyzer shows all
green (internal and external), all relevant tests with Microsoft Remote Connectivity Analyzer were passed, also analysis using Wireshark brought nothing.
I must to say that a week ago I installed SP3 for Exchange 2010 - can it may be because? Also appears more
times a day the following error message in Event Viewer on the back-end server (language of operation system is German):
Protokollname: Lync Server
Quelle:        LS Storage Service
Datum:         05.12.2013 19:23:14
Ereignis-ID:   32054
Aufgabenkategorie:(4006)
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:      SERVER-11.Speedpoint.local
Beschreibung:
EWS-AutoErmittlungsfehler im Speicherdienst.
ExchangeAutodiscoverException: code=ErrorEwsAutodiscover, reason=GetUserSettings
failed, smtpAddress = xxx, Autodiscover Uri=https://autodiscover.xxx.de/autodiscover/autodiscover.svc, Autodiscover WebProxy=<NULL> ---> Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed.
Das Stammelement ist nicht vorhanden. ---> System.Xml.XmlException: Das Stammelement ist nicht vorhanden.
   bei System.Xml.XmlTextReaderImpl.ThrowWithoutLineInfo(String res)
   bei System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   bei System.Xml.XmlCharCheckingReader.Read()
   bei Microsoft.Exchange.WebServices.Data.EwsXmlReader.Read()
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverRequest.InternalExecute()
   --- Ende der internen Ausnahmestapelüberwachung ---
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverRequest.InternalExecute()
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.InternalGetUserSettings(List`1 smtpAddresses, List`1 settings, Nullable`1 requestedVersion, Uri& autodiscoverUrl)
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetSettings[TGetSettingsResponseCollection,TSettingName](List`1 identities, List`1 settings, Nullable`1 requestedVersion, GetSettingsMethod`2 getSettingsMethod, Func`1 getDomainMethod)
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetUserSettings(List`1 smtpAddresses, List`1 settings)
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.InternalGetSoapUserSettings(String smtpAddress, List`1 requestedSettings)
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetUserSettings(String userSmtpAddress, UserSettingName[] userSettingNames)
   bei Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.SendGetUserSettingsRequest(StoreContext ctx, String smtpAddress)
   --- End of inner exception stack trace ---
   bei Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.SendGetUserSettingsRequest(StoreContext ctx, String smtpAddress)
   bei Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.GetUserEwsSettings(StoreContext ctx, String smtpAddress, CacheMode cacheMode)
Ursache: Der AutoErmittlungs-URI war nicht richtig konfiguriert oder nicht erreichbar. Eventuell besteht ein Problem mit dem Proxy, oder andere Fehler liegen
vor.
Lösung:
Überprüfen Sie die Ereignisdetails. Überprüfen Sie, ob der URI des AutoErmittlungsdiensts ordnungsgemäß konfiguriert und erreichbar ist. Prüfen Sie, ob die Proxyeinstellungen ordnungsgemäß konfiguriert sind und der Proxy erreichbar ist. Prüfen Sie die Konfiguration
der AutoErmittlung zwischen Lync und Exchange Autodiscovery anhand des Handbuchs zur Problembehandlung. Wenn das Problem weiterhin besteht, wenden Sie sich mit den Ereignisdetails an das Supportteam Ihrer Organisation.
Ereignis-XML:
< Event xmlns="">
<System>
    <Provider Name="LS Storage Service" />
    <EventID Qualifiers="53158">32054</EventID>
    <Level>2</Level>
    <Task>4006</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-12-05T18:23:14.000000000Z" />
    <EventRecordID>19949</EventRecordID>
    <Channel>Lync Server</Channel>
    <Computer>SERVER-11.Speedpoint.local</Computer>
    <Security />
</System>
<EventData>
    <Data>ExchangeAutodiscoverException: code=ErrorEwsAutodiscover, reason=GetUserSettings failed, smtpAddress=xxx, Autodiscover Uri=https://autodiscover.xxx.de/autodiscover/autodiscover.svc, Autodiscover WebProxy=<NULL> --->
Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed.
Das Stammelement ist nicht vorhanden. ---> System.Xml.XmlException: Das Stammelement ist nicht vorhanden.
   bei System.Xml.XmlTextReaderImpl.ThrowWithoutLineInfo(String res)
   bei System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   bei System.Xml.XmlCharCheckingReader.Read()
   bei Microsoft.Exchange.WebServices.Data.EwsXmlReader.Read()
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverRequest.InternalExecute()
   --- Ende der internen Ausnahmestapelüberwachung ---
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverRequest.InternalExecute()
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.InternalGetUserSettings(List`1 smtpAddresses, List`1 settings, Nullable`1 requestedVersion, Uri& autodiscoverUrl)
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetSettings[TGetSettingsResponseCollection,TSettingName](List`1 identities, List`1 settings, Nullable`1 requestedVersion, GetSettingsMethod`2 getSettingsMethod, Func`1 getDomainMethod)
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetUserSettings(List`1 smtpAddresses, List`1 settings)
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.InternalGetSoapUserSettings(String smtpAddress, List`1 requestedSettings)
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetUserSettings(String userSmtpAddress, UserSettingName[] userSettingNames)
   bei Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.SendGetUserSettingsRequest(StoreContext ctx, String smtpAddress)
   --- End of inner exception stack trace ---
   bei Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.SendGetUserSettingsRequest(StoreContext ctx, String smtpAddress)
   bei Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.GetUserEwsSettings(StoreContext ctx, String smtpAddress, CacheMode cacheMode)
< /Data>
</EventData>
< /Event>
However Event ID
32054
was actually
always there
– even
when everything
worked fine -
but with
some another content.
That's why I
don't know
if I
should take it seriously.
Thanks a lot in advance for your help!

Hi MiF,
The issue may cause by the Network Service account that the Lync Storage Service uses does not have access to the private key in used by the oAuth certificate. Please do with the following steps:
Open MMC and add the “Certificates” Snap-in (Local Computer)
Open Personal | Certificates and find the the Certificate being used for OAuth (use the Lync “Get-CsCertificate -Type OAuthTokenIssuer” cmdlet to find the serial number of the OAuth certificate).
Right-click | “All Tasks” | “Manage Private Keys”
Add Permissions for “Network Service” account (the defaults Full control and Read).
Please also check registry key on client computer.
If the HKCU\Software\Microsoft\ Office\15.0\Lync \[User SMTP Address]\Autodiscovery registry key does not exist on the user’s workstation, then it likely means that one of the following failures
have occurred:
Lync was unable to locate a valid DNS A record or SRV record for the Autodiscover site
Certificate assigned to Autodiscover site is not trusted by the Lync workstation
More details:
http://www.microsoft.com/en-in/download/confirmation.aspx?id=15668
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync 2013 Server / Roles & Components

Lync
2013 Server / Roles & Components
Front End
User authentication and registration
Presence information and contact card exchange
Address book services and distribution list expansion
IM functionality, including multiparty IM conferences
Web conferencing, PSTN Dial-in conferencing and A/V conferencing (if deployed)
Application hosting, for both applications included with Lync Server (for example, Conferencing Attendant and Response Group application), and third-party applications
Primary store for user and conference data. Information about each user is replicated among Front End Servers in the pool
Optionally, Monitoring, to collect usage information in the form of call detail records (CDRs) and call error records (CERs). This information provides metrics about the quality of the media (audio and video) traversing your network for both Enterprise
Voice calls and A/V conferences.
Web components to supported web-based tasks such as web scheduler and join launcher.
One Front End pool runs the Central Management Server DB, which manages and deploys basic configuration data to all servers running Lync
Optionally, Archiving, to archive IM communications and meeting content for compliance reasons.
Optionally, if Persistent chat is enabled, Persistent Chat Web Services for Chat Room Management and Persistent Chat Web Services for File Upload/Download.
Back End
Database server running Microsoft SQL Server
Provide the DB services for the Front End pool
Acts as backup store for the pool’s user and conference data
Primary stores for other DB’s like Response Group
High Availability for the BE DB is provided via SQL Mirroring
Optional Witness to enable automatic failover for BE
SQL Sever 2008 R2 or higher required for SQL Mirroring
Edge Server
Enable users to communicate and collaborate with users outside the organization’s firewall
Comprises four separate server roles
Access Edge – Acts as a secure proxy for all remote Lync signaling traffic
Remote Access
Federation
Public IM Connectivity (PIC)
Web Conferencing Edge – Enable remote users to participate in Web conferences with internal or remote workers
A/V Edge – Responsible for secure relay of A/V media among internal, external, and federated contacts
XMPP Gateway – Allows IM/P with XMPP federated contacts
Reverse Proxy
Simple URL Publishing – Required for users to join Lync meetings
Web Conferencing Content – Users download meeting content (PowerPoint, Whiteboard, and Poll data) via Lync Web Services when in meeting
Address Book & Distribution List Expansion – Required for users to download Lync Address Book and perform DL expansion
User Certificates – Provides client certificate authentication via Lync Web Services
Device Updates – Provides software updates to Lync IP endpoints
Mobility – Provides connectivity for mobile clients via Lync Web Services
Mediation Server
Translates signaling and media between Lync Server and PSTN, IP-PBX, or SIP Trunk
Can be co-located on Front End or separated as stand-alone Server dependent on call volume
Role facilitates dial-in conferencing
Capacity
Co-located = 150 Concurrent Calls
Standalone = 1100 Concurrent Calls
Persistent Chat
Enable users to participate in multiparty, topic-based conversations that persist over time
Pchat Front End server role runs persistent chat service
Pchat Back End server stores chat content and compliance events
Geographic DR is provided via stretched pool and SQL log shipping to replicate DB info
150k provisioned users / 80k concurrent users
Archiving
Uses SQL Server 2008 R2 or SQL Server 2012 for DB
Capable of archiving the following:
Peer-to-peer IM
Multiparty IM
Web Conferences, including uploaded content and events
A/V for peer-to-peer IM and web conferences
Web conferencing annotations and polls
Monitoring
Agent that runs on each Front End Server that collects and manages information from the Front End and Mediation Servers
Stored on SQL Server DB
Leverages SQL Server Reporting Services for creation of reports related to call quality and metrics
Office Web Apps Server
External server leveraged for rendering PowerPoint slides within the Lync client and Lync Web App
Typically leveraged within SharePoint deployments to deliver browser-based versions of Microsoft Office applications
System Center Ops Mgr
Health configuration in Lync Server 2013 is built around System Center Operations Manager and the use of Lync Server Management Packs. These Management Packs include a number of new features and enhancements, including:
Feature
Description
Synthetic Transactions
Windows PowerShell cmdlets that can be run from various locations to ensure that end user scenarios such as sign-in, presence, IM, and conferencing are readily available to end users.
Call Reliability Alerts
Database queries for Call Detail Records (CDR). These records are written by Front End Servers to reflect whether end users were able to connect to a call or why a call was terminated. These queries result in alerts that indicate when a wide range of end
users are experiencing connectivity issues for peer-to-peer calls or basic conferencing functionality.
Media Quality Alerts
Database queries that look at Quality of Experience (QoE) reports published by clients at the end of each call. These queries result in alerts that pinpoint scenarios where users are likely to be experiencing poor media quality during calls and conferences.
The data is built upon key metrics such as packet latency and loss, metrics that are known to directly contribute to call quality.
Component Health
Individual server components raise alerts by using event logs and performance counters. These alerts indicate failure conditions that can severely impact one or more end user scenarios. These alerts can also indicate a variety of other failure conditions,
including services not running, high failure rates, high message latency, or connectivity issues.
Dependency Health
Failures can occur for a variety of external reasons. The management packs now monitor and collect data for some of the critical external dependencies that might indicate severe issues, including IIS availability, CPU and memory usage of servers and processes,
and disk metrics.
Exchange UM
http://www.contactcenterarchitects.com/lync-2013-server-roles-components/

Hi,
Thank you for sharing the information. It is useful for others who not understand Lync Server Roles and Components. You time and effort are appreciated.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync 2013 Enterprise load balancing on the front end and edge pool

Hi,
I am setting up a Lync 2013 Enterprise deployment consisting of a Front End pool (x2 FE servers) and an Edge pool (x2 Edge servers). I'm seeing some conflicting advice regarding load balancing using hardware or DNS for the front end and the edge.
On the front end I have 2 internal DNS records 'lyncfepool1.contoso.local' each of which map to one of the IPs of the FE servers. I've used my details to populate the Detailed Design Planner excel spreadsheet and am told that I require a HLB to load
balance my front end pool. I'm aware of the need to load balance HTTPS traffic internally (which will be done by TMG) however other traffic to the front end (SIP, etc) can be balanced by DNS only, and not require a HLB?
Can someone clarify the front end requirement?
Also - looking now at the edge pool - this site again have two edge servers in a pool. We are using a total of six private IP addresses, two per edge service (2 x av.contoso.com, 2 x sip.contoso.com and 2 x webcon.contoso.com). These will be
NAT'ed by the external firewall and directed to the respective external (DMZ) IP addresses on the Edge servers on port 443. I know this isn't true roundrobin due to the intelligence of the Lync client when connecting (in that the Lync client will connect
to one of the public IPs and if it can't connect, it will know to connect to the other service IP), however I want to clarify this set up, particularly the need to direct the external public IP traffic at the DMZ Edge IP specified in the topology builder.
I've attached a basic diagram of the external/DMZ/Edge side which hopefully helps with this question
Persevere, Persevere, Per..

That is because you will always need HLB for a front-end server since it hosts the Lync webservices which use HTTP/HTTPS traffic.
The description on the calculation tool also describes this correctly:
Supports Standard and Enterprise pools (up to 12 nodes), with pure device-based load balancing or a combination of DNS load balancing and device-based load balancing (for
Lync web services)
You can use either Hardware or DNS loadbalancing for SIP traffic only, but you will always need a HLB for the webservices. Both are applicable for the Front-End so you have either
full HLB for both SIP and HTTP(S) traffic
DNS LB for SIP traffic and HLB for HTTP(S) traffic
Hope this is more clear :-)
Lync Server MVP | MCITP Lync Server 2010 | If you think my post is the answer to your question, please mark it as answer so future visitors can easily find it.

Iphone and ipad Lync Client Randomly cannot sign in to Lync 2013 Server

I have a Lync 2013 environment that will allow all clients to connect from inside and outside of the network except for ios devices. iOS devices are sometimes able to connect and sometimes not. When they are not able to sign in they receive a message stating,
"An Error Occurred in Lync. Please retry. If the problem persists, contact your support department"
I have run tests using the Microsoft Remote Connectivity Analyzer and all tests come back green. I have also used the Lync Connectivity Analyzer and get the results below:
Starting Lync server autodiscovery
Starting automatic discovery for secure (HTTPS) internal channel
Server discovery failed for secured internal channel against
https://lyncdiscoverinternal.earenfroe.com/
Starting automatic discovery for unsecure (HTTP) internal channel
Server discovery failed for unsecured internal channel against
http://lyncdiscoverinternal.earenfroe.com/
Starting automatic discovery for secure (HTTPS) external channel
Server discovery succeeded for secure (HTTPS) external channel against URL
https://lyncdiscover.earenfroe.com/
Starting automatic discovery for unsecure (HTTP) external channel
Server discovery failed for unsecured external channel against
http://lyncdiscover.earenfroe.com/
Starting the requirement tests for Lync Mobile 2013 App
Starting tests for Mobility (UCWA) service
Completed tests for Mobility (UCWA) service
Your deployment meets the minimum requirements for Lync Mobile 2013 App.
Anyone have any suggestions on where to go next? Troubleshooting an intermittent connection issue that only affects one mobile platform is tough...especially when all the testing tools say everything is configured correctly :)
Thanks in advance!
Tom

I have the same problem, and we have netscaller as revrse proxy solution and we have the required records created for mobility.
with lync2010 mobility it is working fine, but with lync 2013 mobiltity we have intermittent issue with error e2-3-33 error
raghu
I had the same problem (e2-3-33 on mobile devices at random times) and it turns out it was McAfee antivirus causing the UCWA service to crash repeatedly. The workaround for it is outlined in the below blog entry I found as well as the below Microsoft document.
Long story short you want to run follow the steps outlined in the workaround section below (I copied it from the linked MSFT document)
http://support.microsoft.com/kb/2997513
http://lynclounge.blogspot.com/2014/07/lync-mobility-issues-event-ids-1309.html
WORKAROUND
he following procedures must be performed on all Lync Server 2013 FE server and Director Lync 2013 server roles. To
perform these procedures, first open a command prompt as an administrator.
Windows Server 2008 R2
On the Start menu, type cmd.exe in the Windows search feature, and then press Enter.
Right-click cmd.exe, and then click Run as administrator.
Windows Server 2012
Press the Windows key to access the Start page.
Use the Windows search feature to locate cmd.exe.
Right-click cmd.exe, and then click Run as administrator.
In the Command Prompt window, follow these steps:
Navigate to the %install drive%:\Windows\System32\inetsrv> directory prompt.
Enter the following command, and then press Enter:
appcmd set config /section:applicationPools /[name='LyncUcwa'].recycling.disallowOverlappingRotation:true
Enter the following command, and then press Enter:
appcmd set config /section:applicationPools /[name='LyncUcwa'].processModel.shutdownTimeLimit:0.00:00:30
To confirm the changes from steps 2–3, enter the following command, and then press Enter:
appcmd list apppools lyncucwa /config
The following information should be returned to the console to confirm the update to the LyncUcwa application pool
settings:
<add name="LyncUcwa" autoStart="true" managedRuntimeVersion="v4.0" managedPipelneMode="Integrated" startMode="AlwaysRunning">
<processModel identityType="NetworkService" idleTimeout="00:00:00" shutdownTieLimit="00:00:30" />
<recycling disallowOverlappingRotation="true">
<periodicRestart time="00:00:00">
<schedule>
</schedule>
</periodicRestart>
</recycling>
<failure />
<cpu />
</add>

Voice problems with Lync 2013 Mobile

Hi
I have a situation where Lync 2013 on both iPhone & Android has started giving problems with making and receiving voice calls. There are no problems with Windows, Mac or Phone Edition clients that I'm aware of. I have not tested anything over the VPN,
but this should not be a factor.
For receiving calls - If the user is connected to the LAN via Wi-Fi AND the call is from an internal user, all works fine. If the call is from an external user OR the user is connected via 3G, then the call just shows "Connecting" indefinitely.
This includes transferred calls.
For making calls - If the user is connected to the LAN via Wi-FI and calls either an internal or external users, all works fine. If the user is connected via 3G and calls either an internal or external user, the phone rings, but when it's answered it shows
call ended.
I have ran RUCT on a computer outside the network, with the following findings:
DNS:
Record
Type
Hostname
IP Address
Port
Weight
Priority
_sip._tls.domain.com
SRV
sip.domain.com
Edge External IP
443
100
0
sip.domain.com
A
sip.domain.com
Edge External IP
sipexternal.domain.com
A
sipexternal.domain.com
Edge External IP
meet.domain.com
A
meet.domain.com
<null>
_ntp._udp.domain.com
SRV
pool.ntp.org
NTP Server IP
123
100
0
_sipfederationtls._tcp.domain.com
SRV
sip.domain.com
Edge External IP
5061
100
0
lyncdiscover.domain.com
A
sip.domain.com
Edge External IP
lyncdiscover.domain.com
CNAME
sip.domain.com
I have ran Test Port on each entry where there is a port with successful results. Ping works on all entries.
If I query Certificate Information on sip.domain.com with port 5061 or 444, it succeeds and returns the certificate with subject sip.domain.com. If I query 443, it fails with error "An error occurred while retrieving the certificate. Unable to read
data from the transport connection: An existing connection was forcibly closed by the remote host."
On Microsoft Remote Connectivity Analyzer, all tests pass except for the certificate test:
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server sip.domain.com on port 443
The Microsoft Connectivity Analyzer wasn't able to obtain the remote SSL certificate.
Running netstat on Lync Edge gives me the following with regards to port 443:
TCP <Internal IP>:443 Lync2:0 LISTENING
TCP <External IP>:443 Lync2:0 LISTENING
Firewall allows connections on port 443 and I've tried disabling the firewall as well. Trying to open https://sip.domain.com in the browser on the Lync Edge fails also, telnet succeeds, but no data is returned.
I've restarted the AV service and also rebooted the Lync Edge server, no change. In the topology builder, I can see that AV is configured to listen on port 443.
Any ideas would be most welcome.
Regards
Lionel
MCP Windows Server MCTS .NET

I have ran a large amount of additional tests. On my latest round of testing, I have obtained the following results:
Call received via PSTN gateway on user DID, answered by desktop client inside LAN - works.
Call received via PSTN gateway on response group, answered by desktop client inside LAN - works.
Call received via PSTN gateway on user DID, answered by desktop client outside LAN (behind NAT, DSL router) - works.
Call received via PSTN gateway on response group, answered by desktop client outside LAN (behind NAT, DSL router) - works.
Call received via PSTN gateway on user DID, answered by mobile client inside LAN - does not work.
Call received via PSTN gateway on response group, answered by mobile client inside LAN - does not work.
Call received via PSTN gateway on user DID, answered by mobile client outside LAN (behind NAT, DSL router) - works.
Call received via PSTN gateway on response group, answered by mobile client outside LAN (behind NAT, DSL router) - works.
Call received via PSTN gateway on user DID, answered by mobile client outside LAN (3G) - does not work.
Call received via PSTN gateway on response group, answered by mobile client outside LAN (3G) - does not work.
Call received via PSTN gateway on user DID, answered by desktop client inside LAN and transferred to mobile client inside LAN - does not work.
Call received via PSTN gateway on response group, answered by desktop client inside LAN and transferred to mobile client inside LAN - does not work.
Call received via PSTN gateway on user DID, answered by desktop client inside LAN and transferred to mobile client outside LAN (behind NAT, DSL router) - works.
Call received via PSTN gateway on response group, answered by desktop client inside LAN and transferred to mobile client outside LAN (behind NAT, DSL router) - works.
Call received via PSTN gateway on user DID, answered by desktop client inside LAN and transferred to mobile client outside LAN (3G) - does not work.
Call received via PSTN gateway on response group, answered by desktop client inside LAN and transferred to mobile client outside LAN (3G) - does not work.
Call made through PSTN gateway from desktop client inside LAN - works.
Call made through PSTN gateway from desktop client outside LAN (behind NAT, DSL router) - works.
Call made through PSTN gateway from mobile client inside LAN - does not work.
Call made through PSTN gateway from mobile client outside LAN (behind NAT, DSL router) - works.
Call made through PSTN gateway from mobile client outside LAN (3G) - does not work.
Call from desktop client inside LAN to desktop or mobile client (regardless of location) - works.
Call from desktop or mobile client (regardless of location) to desktop client inside LAN - works.
Call from desktop or mobile client (regardless of location) to desktop or mobile client (regardless of location) - works.
There is no difference in behaviour between normal calls and conference calls. Reproducing the problem seems to require the following:
1. PSTN gateway needs to be involved
2. One party needs to be on mobile client
3. The mobile client needs to be inside the LAN or on a 3G connection, but not behind NAT on a DSL connection
The only conclusion I can make is that somehow NAT makes the problem go away, but it does not affect desktop clients (on the LAN or Wi-Fi at least, I do not have a way to test them on 3G).
The PSTN gateway (Cisco UCM) could also be the problem, but it works fine in all other cases. It has 4 trunks and makes all kinds of routing decisions, but once a call is routed to/from Lync, it should not make a difference on what type of device it is answered.
I'm really baffled by this one. Perhaps the 3G thing is a service provider issue and the issue on the LAN has something to do with the internal DNS combined with the behaviour of the mobile client. Just not sure exactly what.
MCP Windows Server MCTS .NET

Lync 2013 recording presentation

Similar Messages

Maybe you are looking for