D(one) IT

IT Tips, Tricks & Such

Monthly Archives: April 2013

Event ID: 41029 No connectivity with Lync Web App

On each Lync 2013 Front End the Data MCU will attempt to connect to the Lync Web App Reach URL over TCP/8061 every thirty minutes, this poke event uses the server FQDN. If the External Lync Web Services is using a certificate that doesn’t contain the server FQDN, a 41029 will be recorded to the Event Log every poke.


Server FQDN is not included by default when requesting a separate certificate for the Lync External Web Services.


During testing I have found this is a noise event and has no impact.


Product Group – as by design


Applying Lync Server Cumulative Updates, don’t forget to update Monitoring Server Reports

When applying Lync Server (2010/2013) Cumulative Updates, one step that is often overlooked is updating the Monitoring Server Reports hosted on SQL Server Reporting Services (SSRS).

Looking at TechNet for both 2010/2013 there is no reference to update Lync Monitoring Server Reports:

Lync Server 2013 Monitoring Reports RTM Version: 5.0.8308.0:

To install the Monitoring Reports re-run the Deploy Monitoring Server Reports, this will overwrite the current reports with the latest version:

  1. As a member of the DomainAdmins group, log on to any server in the domain that has the cumulative update installed.
  2. Run the Lync Server Deployment Wizard.
  3. In the Deployment Wizard, click Deploy Monitoring Server Reports.
  4. On the Specify Monitoring Server page, specify the Monitoring server that will collect and store the CDR and QoE data if not already shown.
  5. On the Specify Monitoring Server wizard page, specify the instance of SQL Server Reporting Services that will publish the reports if not already shown.
  6. On the Specify Credential page, specify the user credentials that will be used to access the Monitoring Server store (QoEMetrics and LcsCDR databases).
  7. On the Specify Read-Only group page, specify the domain group that will be granted read-only access to the Monitoring reports.

Upgrade Monitoring Server Report:

Updated Lync Server 2013 Monitoring Reports CU1 Version: 5.0.8308.291:

Test-CsDatabase –LocalService Expected and Installed version mismatch

After applying the Lync 2013 CU1 update, I noticed some oddities with the Test-CsDatabase –LocalService. All databases showed Expected Version and Installed Version matching, except for:

  • Local\rtclocal: rtcdyn – Expected Version 125.6.2 / Installed Version 0.0.0
  • Local\rtclocal: xds – Expected Version BLANK / Installed Version 10.13.2



Known issue and can be safely ignored.

Unable to Lync Device Update Snom 7XX series phones via Edge

With the recent announcement: Snom IP Phones Deliver Out-of-the-Box Provisioning Speeds and Simplify Microsoft Lync Voice Deployments. I decided to setup Lync Device Update service for my Snom 760.

A quick check on the Lync Interop Programs shows the Snom 760 as compatible with Lync 2013 and Managed Updates supported:

Downloaded the snom760- firmware, imported and approved the update:

I found the 760 registered to our Lync 2013 environment via the Edge server but refused to attempt the firmware update, where as my Lync phone edition devices (Polycom cx600 and Aastra 6735) had no issue.

Reviewing the logs of the Snom 760 I found that the device detected “not registered locally, thus skipping update attempt”:

3/4/2013 08:45:31 [NOTICE] PHN: ProvUtils::UcSendFirmwareUpdateAvailableRequest: enabled: 1; url: >https://webext1.iluminaritech.com:443/RequestHandlerExt/ucdevice.upx<; id: >camt@ILUMINARITECH.COM<
3/4/2013 08:45:31 [NOTICE] PHN: ProvUtils::UcSendFirmwareUpdateAvailableRequest: not registered locally, thus skipping update attempt!

A bug was opened with Snom support. Internal Tracking ID is SCPP-4825, This is for Snom use, yet will be referenced in the Release Notes to indicate the solution.


UC Edition Developer is speaking with Microsoft about the apparent requirement for authentication to retrieve the firmware file. Unfortunately, this means that external updates are not yet supported. However, the Development Team is pursuing the fix as a high priority

No Free/Busy information could be retrieved when Scheduling a Meeting from the Lync Client

When using the Lync Client to “Schedule a Meeting” with an internal contact the Scheduling Assistant page doesn’t provide Free/Busy information for the invited contact, unless the invite window sits open for over 5 minutes.

Reproduced this issue in:

  • Lync Client 2010, Lync Server 2010, Exchange 2010
  • Lync Client 2010/2013, Lync Server 2013, Exchange 2007
  • Lync Client 2013, Lync Server 2013, Exchange 2013
  • Lync Client 2013 CU1, Lync Server 2010 CU1, Exchange 2013 CU1


Workarounds to bring up Free/Busy immediately:

  1. Uncheck and Check the Attendee
  2. Check Name button
  3. free_busy

  4. Ctrl + K (Check Name hotkey)
  5. Clicking in the “To” Field then another location on the “Appointment” page, then switch back to “Scheduling Assistant” page
  6. Book Lync Meeting directly from Outlook

In contrast using the “Send An Email Message” from the Lync Client, does a check name automatically within a few seconds.