Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

After upgrade to 4.13sr2, getting many 9415 events on CM

Problem Details: After upgrading from 4.12 to 4.13 and applying 4.13 SR1 and SR2 we are getting many of the events below in the Call Manager Application Event log. Also, users cannot access the Corporate Directory from their phones. They get HTTP Error [500]!. Also, found similar issue in bug report CSCeg48952 but for version 4.02 of Call Manager.

Event Type: Warning

Event Source: DCDirectory

Event Category: Configuration

Event Type: Warning

Event Source: DCDirectory

Event Category: Configuration

Event ID: 9415

Date: 1/30/2006

Time: 9:11:47 AM

User: N/A

Computer: SYSENG-CM1

Description:

(BASE IL NEW CONNECT(49) Proc 88, Sev 14)

No free connection control blocks - connection refused. This

indicates that the maximum number of simultaneous TCP/IP connections has been reached, and further connection

attempts will fail until one of the existing connections has been closed.

Socket ID A4156708

Component LDAP

Number of CBs configured 504

Anyone have any ideas??

tcekada@syseng.com

2 REPLIES
Green

Re: After upgrade to 4.13sr2, getting many 9415 events on CM

Hi!

Seems to be you are hitting:

CSCsc59352

Externally found enhancement defect: Duplicate (D)

CallManager 4.1.3 DCD No free connection control blocks

Release-note:

Symptom:

DC Directory stops accepting new connections

Conditions:

CallManager 4.1.3

PA 1.4.5

Also seen with CallManager 3.3.x

Workaround:

Restart DC Directory

Let us know

New Member

Re: After upgrade to 4.13sr2, getting many 9415 events on CM

Yep. You nailed it!! I wish you would have replied earlier so I wouldn't have had to burn an incident with Cisco to find this out, but that's the breaks. Thanks anyhow. BTW in the interim I scheduled winat to restart the DC directory every six hours until we get a fix for CSCsc59352.

Thanks again.

123
Views
5
Helpful
2
Replies
CreatePlease login to create content