Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

OPS Sync Problem

Status
Not open for further replies.

axeman91

MIS
Oct 4, 2006
3
GB
I'm having some problems when changing names against extensions in OPS manager. When trying to sync changes back out to the controllers I am getting errors saying 'Unable to translate the key data'. Anyone know what this relates to? I am assuming it is something to do with the programmable keys, however at least one of the extensions has no keys programmed, and others just have standard keys (DND, headset etc).
 
Have you done any upgrades recently to either the Eman, 3300 or Both?

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Both have been upgraded without problem. Matching versions on each.
 
I had an issue recently where tech support had to write a patch due to an issue with some security updates for Windows 2K SP4.

Try removing Java and then reloading JAVA from the client resources page.

If this doesn't help, call tech support.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Verify that the DN you're making the change on exists in the Remote Telephone Directory Assigment form of the node giving you the error.

Normally when I see the "Unable to translate key data" message, it's because Ops is trying to prop a MODKEY record for an entry that doesn't exist in the target node.

If it's missing, enter it manually or do a Full Propogate to the problem node.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top