Solving Event ID 32134


Whilst working through a patching session I noticed a standard edition front end server throwing Event ID 32134 every 10 minutes.

That’s new to me, so how do we resolve this?

Error Details

Event ID 32134

Event ID 32134
Source: LS User Services
Error

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=(local)\rtc;database=rtcab;

Cause: Possible issues with back-end database.

Resolution:
Ensure the back-end is functioning correctly.

 Cause

The error message does give a good clue as to where to start looking. The server cant connect to the backend database rtcab on the local server.

My weapon of choice is SQL Management Studio as it will allow me to take a peek at the suspect database.

Connecting to the local server and expanding the databases folder I notice the rtcab database stating that access is set to Restricted User).

SQL Restricted User

Solution

Not sure why this rtcab access has been locked, perhaps part of the update process that didn’t quite finish.

An easy fix, simply right click the database rtcab and select Properties. Navigate to Options.

Scroll down to the State section and change the Restrict Access to MULTI_USER.

Lync Backend Database

Even on a good day, error messages from SQL make me uncomfortable, BUT this particular issue has been comfortably sorted.

 

Advertisements

About Paul B

My name is Paul Bloem and I am employed at Lexel Systems in New Zealand as a Principal Consultant for Unified Communications. I have been working on enterprise voice solutions for over 20 years. My first 10 years were spent working for a Telco in South Africa (Telcom SA). This is where all the groundwork happened as I was exposed to just about every aspect of telecommunication you could imagine. I develop an interest in PBX technologies and eventually became the go-to guy. Next, I had a 10 year run at Siemens South Africa, most of my time there was as a Technical Trainer. During this time VoIP hit the world stage, I had the privilege of introducing VoIP both as H.323 and later SIP across the Siemens HiPath 4000 solution stack. In 2008 I immigrated to New Zealand with my newly attained MCSE, I was ready to go where no PBX Techie had gone before. I was employed to explore OCS 2007 and that was pretty much the beginning of the end for me. I have been working on OCS and Lync ever since. My current role focuses exclusively on Lync and associated technologies.. That includes pre-sales, consulting, architecture and design, training and support. I even get to play in the development space from time to time - focus on play ;-) I was nominated as a Microsoft VTSP for Lync early in 2013 and also awarded Microsoft's MVP award for Lync in 2014.
This entry was posted in event id, RTC Database, RTCAB, SQL, Uncategorized and tagged . Bookmark the permalink.

One Response to Solving Event ID 32134

  1. Pingback: Weekly IT Newsletter – December 28-January 1st, 2016 | Just a Lync Guy

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s