/mcpError Message %UC_CTI-3-kCtiProviderOpenInvalidUserNameSize: %[UserNameSize=Long][AppID=String] [ClusterID=String][NodeID=String]: Invalid userName size in ProviderOpen request.. Explanation User name length is invalid. Recommended Action Ask user of CTI application to use correct userName and to check the user name in configuration. It should not be more than 31 characters. Error Message %UC_DB-3-kDbConnectionFailed: %[AdditionalInfo=String][AppID=String][ClusterID=String] [NodeID=String]: Database connection failed.. Explanation An attempt to connect to database failed. Recommended Action Enable trace for the database layer monitor to get specific error information. Error Message %UC_DB-1-NoDbConnectionAvailable: %[AppID=String][ClusterID=String][NodeID=String]: No database connection available.. Explanation Database layer could not find any working database connection. Recommended Action In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for the Cisco Database Layer Monitor service. Check network connectivity and operation of SQL Server services. Error Message %UC_DB-2-ErrorChangeNotifyClientBlock: %[AppID=String][ClusterID=String][NodeID=String]: A change notification client is busy (blocked). If the change notification client continues to be blocked for 10 minutes, the system automatically clears the block and change notification should resume successfully.. Explanation Changes made to the database are not being consumed by one of the recipients. This does not always represent an issue. However, if the change notification client continues to be blocked for 10 minutes, the system automatically clears the block for all clients except the blocked one, which means that change notifications should resume successfully for all other clients. To clear the blocked client, you must restart the server. Recommended Action At the command line interface (CLI) on the database server, execute the following command: show tech notify. The CLI command output will provide information about the block. Use Cisco Unified Serviceability to restart the server that was indicated in the alarm. You may also want to gather traces to examine them for anomalous activity during the time that client was blocked. In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for the Cisco Database Layer Monitor service. Also, use RTMT to look for error messages that may have occurred around the time of the alarm. 5/24/26, 3:34 AM System Error Messages for Cisco Unified Communications Manager 15 - Cisco https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/err_msgs/15_x/ccmalarms15.html 27/343