/mcptbl_system_preferences table. 5. Check the number of records in tbl_billing_data, tbl_billing_error, and tbl_error_id_map tables. 6. Check if the scheduled job configuration is correct from CAR page. 7. Collect and check the CAR Scheduler traces for more details. Error Message %UC_CAR-3-CARSchedulerJobError: %[JobName=String][FailureCause=String][FailureDetail=String] [AppID=String][ClusterID=String][NodeID=String]: CAR scheduled job failed.. Explanation A normal CAR scheduled job failed for some reasons. Recommended Action 1. Check the status of Cisco CAR Scheduler service. 2. Check the Event Log from CAR page. 3. Check the contents in tbl_system_preferences table. 4. Check the number of records in tbl_billing_data, tbl_billing_error, and tbl_error_id_map tables. 5. Check if the scheduled job configuration is correct from CAR page. 6. Collect and check the CAR Scheduler traces for more details. Error Message %UC_CAR-3-CARSchedulerJobInterrupted: %[JobName=String][FailureCause=String] [FailureDetail=String][AppID=String][ClusterID=String][NodeID=String]: CAR scheduled job interrupted. Explanation A normal CAR scheduled job interrupted for some reasons. Recommended Action 1. Check the status of Cisco CAR Scheduler service. 2. Check the Event Log from CAR page. 3. Check the contents in tbl_system_preferences table. 4. Check the number of records in tbl_billing_data, tbl_billing_error, and tbl_error_id_map tables. 5. Check if the scheduled job configuration is correct from CAR page. 6. Collect and check the CAR Scheduler traces for more details. Error Message %UC_CAR-3-BadCDRFileFound: %[FileName=String][BadFileCause=String][BadFileSummary=String] [AppID=String][ClusterID=String][NodeID=String]: Bad CDR or CMR flat file found during CDR Load to CAR database.. Explanation A bad CDR or CMR flat file is found during loading to CAR database, the file could be corrupted for some reasons. However, CAR loader is able to skip the bad record(s) and load the good ones to CAR database. Recommended Action 1. Find the bad file from the cdr_repository folders, and check its problematic record(s) based on the information given by the cause and summary. 2. Collect the associated SDI and SDL traces for the bad record(s) found in this file as soon as possible. 3. Collect and check the CAR Scheduler traces for more details. Error Message %UC_CAR-7-CARIDSEngineDebug: %[Specific-Msg=String][ClassMsg=String][ClassID=String] [AppID=String][ClusterID=String][NodeID=String]: Indicates debug events from CAR IDS database engine.. Explanation This alarm provides low-level debugging information from CAR IDS database engine. System administrator can disregard this alarm. Recommended Action This is for debug information purposes only; no action is required. Error Message %UC_CAR-6-CARIDSEngineInformation: %[Specific-Msg=String][ClassMsg=String][ClassID=String] [AppID=String][ClusterID=String][NodeID=String]: No error has occurred but some routine event 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 104/343