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. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Error when viewing a DN in Callmanager 6.1

When i drill down into the DN one of my user phones on a subscriber i get the following error:

The item with key \'<key here>\' was not found in the database. Please select another item to view.

I tried removing the DN as well as the device itself, waited a couple minutes, then tried re-adding it. I tried this procedure on the publisher and it reported no error, however when i tried it on the subscriber i received the key error again. I only see this error on the subscriber. What gives?

4 REPLIES
Anonymous
N/A

Re: Error when viewing a DN in Callmanager 6.1

It appears to be a cosmetic error, in that the attempted operations do occur successfully. It only occurs if you access the ccmadmin webpages from a subscriber server instead of the publisher. Therefore, try to access ccmadmin from the publisher.

Cisco Employee

Re: Error when viewing a DN in Callmanager 6.1

you might be hitting this bug:

CSCsl46338 Bug Details

CM 6 - ccmadmin access from sub reads local database for some pages

HTH

javalenc

if this helps, please rate

HTH

java

if this helps, please rate

www.cisco.com/go/pdi
New Member

Re: Error when viewing a DN in Callmanager 6.1

Hi javalenc

i have saw the Debug but how can i resolve this isse, i have tried to restart the hall SUB server of the Call Manager and rerefresh it

but still the issue is there, could you advise me please.

thanks

Fadi

Silver

Re: Error when viewing a DN in Callmanager 6.1

Hi Fadi,

The bug is Fixed-In CUCM versions-
7.0(0.39000.3)
7.0(1.11000.2)
6.1(3.9901.139)
6.1(3.9999.1)
6.1(4.1000.10)

And was found in version 6.0. According to the title of your post i suppose you are running CUCM 6.1. Can you check whether your CUCM version is 6.1.3 or 6.1.4 because if its any of these then the bug must have been fixed in your CUCM version.

Regards

Nitesh

766
Views
0
Helpful
4
Replies