On my initial Lync 2013 project I encountered a problem with the Exchange 2010 UM server not finding a path to the Lync 2013 Edge pool. I was receiving the MSExchange Unified Messaging event 1438, as shown below.
I was able to resolve the issue by running the following PowerShell command on the Exchange UM server (replacing lync-edge.domain.local with your Lync Edge pool’s FQDN):
Get-UmServer | Set-UmServer -SIPAccessService lync-edge.domain.local:5062
Log Name: Application
Source: MSExchange Unified Messaging
Date: 11/14/2012 7:43:00 AM
Event ID: 1438
Task Category: UMCore
Level: Warning
Keywords: Classic
User: N/A
Description:
The UM server has been configured to automatically use the Communications Server Audio/Video Edge resources associated with ‘lync.domain.local:5061’. Inbound and outbound calls involving remote users (located outside the enterprise) might be failing using the current Communications Server Audio/Video Edge resources. To correct the issue, set the SIPAccessService property using the Set-UMServer cmdlet. The Microsoft Exchange Unified Messaging service will start using the Communications Server Audio/Video Edge resources corresponding to the new value.
On my initial deployment of Lync 2013 at a customer site last year I ran into a problem with the database creation not completing when Publishing the initial topology with the Topology Builder. This was a net new environment for Lync and initially everything seemed ok. I was able to build the Front End servers and Lync roles installed, but I soon found that the Front End service wouldn’t start.
I was finding LS Server event 12308 and LS User Services events 32171, 32134 and 32212 occurring (documented below). When I went back to check the databases existed on the SQL Server, I found that only the CS databases had been created. I had to rerun the Install Databases in the Topology Builder to rectify the situation.
Log Name: Lync Server
Source: LS Server
Date: 11/7/2012 1:14:13 PM
Event ID: 12308
Task Category: (1000)
Level: Error
Keywords: Classic
User: N/A
Description:
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!)
Log Name: Lync Server
Source: LS User Services
Date: 11/7/2012 1:14:13 PM
Event ID: 30941
Task Category: (1006)
Level: Error
Keywords: Classic
User: N/A
Description:
Initialize failure.
Error code: C3EE7A08
Log Name: Lync Server
Source: LS User Services
Date: 11/7/2012 1:14:13 PM
Event ID: 32171
Task Category: (1006)
Level: Error
Keywords: Classic
User: N/A
Description:
Local backend store could not be acquired.
Sql Instance: (local)\rtclocal Database: rtc could not be acquired.
Cause: Connectivity issues with the database or issues with SQL Server.
Resolution:
Check the health of the (local)\rtclocal instance and ensure that it is fully functional.
Log Name: Lync Server
Source: LS User Services
Date: 11/7/2012 1:14:12 PM
Event ID: 32134
Task Category: (1006)
Level: Error
Keywords: Classic
User: N/A
Description:
Failed to connect to back-end database. Lync Server will continuously attempt to reconnect to the back-end. While this condition persists, incoming messages will receive error responses.
Back-end Database: rtcab Connection string of: driver={SQL Server Native Client 11.0};Trusted_Connection=yes;AutoTranslate=no;server=sql.domain.local;database=rtcab;
Cause: Possible issues with back-end database.
Resolution:
Ensure the back-end is functioning correctly.
Log Name: Lync Server
Source: LS User Services
Date: 11/7/2012 1:13:33 PM
Event ID: 32212
Task Category: (1006)
Level: Error
Keywords: Classic
User: N/A
Description:
Lync Server Service Startup Pending as Backup Store BackEnd is not yet available.
Service Startup will be delayed until the Backup Store BackEnd becomes available.
Cause: Possible Issues with the Backup Store BackEnd.