Cisco Unity Fails to Start After Changing the Maximum Concurrent Connections in SQL [Cisco Unity]

Document ID: 109367

Updated: Jan 16, 2009

Download PDF

Problem

Introduction

This document describes how to troubleshoot the issue of Cisco Unity system not getting started due to maximum concurrent connections running out in SQL.

Before You Begin

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on these hardware and software versions:

Unity 4.x and later
Windows 2000 or 2003 Server Operating System
Microsoft SQL 2000

Conventions

For more information on document conventions, refer to Cisco Technical TipsConventions.

Problem

Cisco Unity does not start, and there are a large number of SQL errors in the application logs, similarto this error:

Event ID: 17052
Source: MSSQLSERVER
Description:
Error: 17809 
Severity: 20 
State: 1  
Could not connect. 
The maximum number of '5' configured user connections are already connected. 
The system administrator can change the maximum to a higher value using sp_configure.

Also, if you go to the SQL Enterprise Manager, you can not connect to the SQL server instance for your Unity server.

Solution

Complete these steps in order to resolve this issue:

Go to Start > Programs > Administrative Tools > Services, and restart the MSSQLSERVER service (even if it states that it has started).

Once you complete this step, the connection to the SQL server instance of your Unity server will be allowed from SQL Enterprise Manager.
Go to Start > Programs > Microsoft SQL Server > Enterprise Manager, and navigate to the SQL server instance of your unity server.
Right-click your SQL server Instance, and choose Properties.
Click the Connections tab, and set the Maximum concurrent user connections to be 0.

Note: 0 is the default value on install and should never change.
Click OK.
Reboot the server.

Unity should start successfully.