The -21005 error is being thrown by the server and it indicates a language error (i.e. the characters in the server's DB do not match the language the client is asking for). This almost always means some bit of text corruption got in there. There was a bug in BAT and the LDAP import that did not properly handle Unicode characters in files for import and display and first/last names got some funky illegal characters in them.
There's nothing a client can do to talk the server side into skipping to the next record here - the ODBC side of things is stuck.
the output from CUDD is sorted by alias - you should be able to find the guy with the corruption in them by sorting by alias in the SA and looking at what the next guy after the last one output by CUDD is. I'll bet you see some funky looking characters in the names in the next few entries.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...