Lync 2013 frontend – Event ID 32042

You might see the following 2 Event ID’s on your server if your have certificates in the wrong store:

  • Event ID 32042 LS User Services
    Invalid incoming HTTPS certificate
    cause: This can happen if the HTTPS certificate has expired or is untrusted

and

Solution:

Open up Lync Management Shell and run the following command:

  • Get-Childitem cert:\LocalMachine\root -Recurse | Where-Object {$_.Issuer -ne $_.Subject} | Format-List * | Out-File “c:\computer_filtered.txt”

If the text file lists certificates then you know which ones to remove/move. After you have cleaned up, reboot your server and all should be fine.

One thing to also take note of, your Lync client will show other users status as “Updating”. Once the server is rebooted it changes to there current status.

Hope it helps.

Advertisements

Full Lync 2013 Installation Guide – Coming Soon

Full Lync 2013 Installation Guide

I will be creating a step-by-step document on how to setup your Azure environment but also setup Lync 2013.

This test environment is built on Microsoft Azure, below are the outlined sections that will be covered in detail with screen shots.

______________________________________________________________

Software required:

  • Windows Server 2012 R2
  • Lync Server 2013
  • Office Web Application Server
  • Office 2013

Server Names & I.P’s used in this test environment:

 

Server Name I.P Role
Aetodc02 10.0.0.4 Primary Domain Controller
Aetodc03 10.0.0.5 Secondary Domain Controller
Aeteclyncapp1 10.0.0.10 Primary Lync Frontend 1
Aeteclyncapp2 10.0.0.11 Primary Lync Frontend 2
Aeteclyncapp3 10.0.0.12 Primary Lync Frontend 3
Aeteclyncapp4 10.0.0.13 Persistent Chat Server
Aeteclyncapp5 10.0.0.14 Web Access Server
Aeteclyncedge1 192.168.1.10 Lync Edge Server
Aetecsql1 10.0.0.15 Primary SQL Server
Aetecsql2 10.0.0.16 Secondary SQL Server
Aetecsql3 10.0.0.17 SQL Witness Server

 ______________________________________________________________

Section A: Azure Setup

Section A1

  • Azure Virtual Network Setup
    • P Address Setup
    • DNS Server

Section A2

  • Azure Storage Setup

Section A3

  • Server setup and Installation:
  • Windows Server 2012 R2 (Primary Domain Controller)
  • Windows Server 2012 R2 (Secondary Domain Controller)
  • Windows Server 2012 R2 (Primary Lync Frontend 1)
  • Windows Server 2012 R2 (Primary Lync Frontend 2)
  • Windows Server 2012 R2 (Primary Lync Frontend 3)
  • Windows Server 2012 R2 (Persistent Chat Server)
  • Windows Server 2012 R2 (Web Access)
  • Windows Server 2012 R2 (Lync Edge)
    • Edge Server setup with Multiple NICS – Azure PowerShell
  • Windows Server 2012 R2 (Primary SQL Server)
  • Windows Server 2012 R2 (Secondary SQL Server)
  • Windows Server 2012 R2 (SQL Witness Server)

_______________________________________________________________

Section B: Configuration of Domain Controllers

Section B1

  • Domain Controller Setup
  • Install AD Services on both Domain Controllers
  • Promote Primary Domain Controller
  • Promote Secondary Domain Controller

Section B2

  • Internal DNS Setup
  • External DNS Setup

Section B3

  • Certificate Authority Setup

Section B4

  • User Account Setup

Section C – Configuration of SQL Servers

Section C1

  • Joining SQL Servers to domain

Section C2

  • Installing SQL Server 2012 Enterprise

_______________________________________________________________

Section D – Configuration of Lync Servers (Excluding Edge in this section)

Section D1

  • Joining Lync Servers to domain

Section D2

  • Installing Lync Server Frontend Prerequisites

Section D3

  • Installing Lync Server 2013
  • Install Core Components
  • Install Administrative Tools
  • Create Topology (Topology Builder)
  • Prepare Active Directory
  • Publish Topology
  • Install Lync Server System
  • Adding additional Frontend Lync Servers to the Lync Pool

Section D4

  • Web Access Server Installation
  • PowerShell Execution Policy Setup
  • Installing Lync WAC Server Prerequisites
  • WAC Software Installation
  • WAC Server Language Pack Installation
  • Topology Builder – Add in Office Web Apps Server

Section D5

  • Archiving and Monitoring Setup
  • Topology Builder Loading
  • Archiving SQL Server Setup
  • Monitoring Server Setup
  • Publish Topology
  • Monitoring Report Installation

Section D6

  • Persistent Chat Setup
  • Server Prerequisites Setup
  • Topology Builder Loading
  • Create new Persistent Chat Pool
  • SQL Server Store Setup
  • Install Lync Server System
  • Persistent Chat Configuration – Lync Control Panel

_______________________________________________________________

Section E – Configuration of Lync Edge Server

Section E1

  • Edge Server Installation
  • Add DNS Suffix (reboot required)
  • Install Server Prerequisites
  • DNS Setup
  • Topology Builder – New Edge Pool
  • Publish Topology
  • Export-CsConfiguration File
  • Permission Setup Lync Control Panel
  • Install Lync Server System

 

The Web Conferencing Server failed to send health notifications to the MCU factory at

After patching my Lync 2013 servers to November Updates I started getting flooded with the following errors:

  • LS MCU Infrastructure 61035

You can follow this KB to sort this out:

  • http://support.microsoft.com/kb/2901554/en-us
  • Click Start, type regedit in the Start search box, and then click regedit.exe in the results list.
  • Locate the following registry subkey: HKLM\System\CurrentControlSet\Control\SecurityProviders\Schannel
  • Right-click Schannel, and then click New DWORD (32-bit) value.
    Type EnableSessionTicket, then press Enter.
  • Right-click EnableSessionTicket, and then click Modify.
  • Change the existing value to 2, and then press Enter.
    Exit Registry editor.
  • Open the Lync Server Management Shell.
  • Run the following Lync Server PowerShell commands in the given order:
    Stop-CsWindowsService
    Start-CsWindowsService

After that the errors should be gone.

Hope it helps.

Lync Server 2013 Error – Lost Connection to all Web Conferencing Edge Services

Recently I started seeing the following event IDs 41026 and 41024 logged on my 3 front end servers every 15-30 min.

As this is a test environment I experienced a problem with one of my internal CA servers and created a new one.

I then re-issued certs for my front end from the new CA and the events stopped being logged.

Hope it helps.

Event ID 14584 – LS Protocol Stack – Connection attempt to at least one service in a pool failed.

I have seen the warning/error below logged on my Lync Servers:

  • “Connection attempts to the following services have failed. Another attempt will be made for each service every 10 minutes.
    Service Address: 192.168.1.10:444; Pool FQDN: LyncPool1.domain.com; Down Time: 0:15
    Service Address: 192.168.1.10:5061; Pool FQDN: LyncPool1.domain.com; Down Time: 0:14

    Cause: The specified service(s) are unavailable.
    Resolution:
    Check the servers in the pool(s) on which the service(s) are installed.”

From what I have seen these have no impact on the server. My servers are fully patched and up-to-date.

Hope it helps.

LS Server Error 12308 (1000)

Checking the CS-Replication status I noticed one of my servers was not replicating, upon investigation the Front-End service wasn’t started, after starting it the following error was thrown:

  • A component could not be started. The service has to stop.

    Component: Live Communications User Services Error code: C3EE7A08!_HRX! (ES_E_FAILED_TO_CONNECT_TO_LOCAL_BACKEND!_HRM!)

Looks like the CS-Database wasn’t installed correctly or not all at.

Solution:

Open up Topology builder and right click on your server or click the actions menu and then select “Install Database”

After this the front-end service should start.

Hope it helps.

LS File Transfer Agent Service – Error Event ID 1034

The following error is logged in event viewer:

  • “Microsoft Lync Server 2013, File Transfer Agent service encountered an error while accessing a file share and will continuously attempt to access this file share until this issue is resolved. While this condition persists, replication to replica machines might not occur. Access denied.”

Cause: Possible issues with file share permissions. This can occur if the computer hosting the file share has outdated cached credentials for the computer that is trying to access the file share.
Resolution:
For details about how to resolve file share permission issues, see the product documentation.

It doesn’t mention what has failed, just a general access denied error message. To see which servers are having a problem, open up the Lync Management Shell and run the following command:

  • Get-CSManagementStoreReplicationStatus

This will tell you if the replication is up-to-date, if it returns a false value then you know which server is the problem. You can invoke the replication by running the following command:

  • Invoke-CsManagementStoreReplication

After that check if there any cached credentials in Control Panel -> Credential Manager.

Hope it helps.

Lync Server Front End: Lost connection to the Web Conferencing Edge Server

Looking through the event log I stumbled across these 3 errors, logged at the same time every 5 min, after a reboot, every 15 min:

  • Event ID 41024 – Lost connection to all Web Conferencing Edge Services
  • Event ID 41024 – Lost connection to the Web Conferencing Edge Server
  • Event ID 41025 – Connection to the Web Conferencing Edge Server has been restored

Solution:

Disable IPv6 on the Front End server. You should disable it in the registry. Don’t forget to reboot after you make this change. Here is the MS KB article how to do this via the registry: http://support.microsoft.com/kb/929852

Hope it helps.

Error (An error occurred while applying SQL script for the feature RTCdatabaseStore) – Lync 2013 Edge Install

Playing around with my test lab, I decided to remove lync on my edge server and reinstall it. Upon running step 2 i encountered the following error:

Lync error

Looking at the log files listed it gave an “Operating System Error 5: Access Denied” error. I went to the CsData folder under the C:\ drive on my server, granted my account access and then ran the setup again. This time if installed successfully.

Hope it helps.