Core Issue
In the Cisco CallManager 4.x application event log, this error appears at regular intervals:
Event ID: 208
SQL Server Scheduled Job 'Monitor Disk Space' (0x6D48E242DDF72F4DA8B8E7093AFC7AA9) - Status: Failed - Invoked on: 2007-01-03 05:00:00 - Message: The job failed. The Job was invoked by Schedule 17 (Schedule 1). The last step to run was step 2 (TruncateCCMLog).
Resolution
This issue is tracked in Cisco Bug ID CSCsc55053.
An upgrade of the Backup and Restore System (BARS) from version 4.0.7 to version 4.0.8 causes the Cisco CallManager and Call Detail Records (CDR) database owner to be changed to unknown. This causes the SQL Server Scheduled Job "Monitor Disk Space" to fail. One possible workaround for this issue is to run this command in the SQL analyzer in order to change the database owner:
use
sp_changedbowner '\Administrator'
and
"SELECT name FROM master..sysdatabases WHERE SUSER_SNAME(sid) IS NULL"
After the command is executed, complete these steps:
- Choose Enterprise Manager > Security, and right-click Logins. Choose New Login and add \SQLSvc as a user.
- Under the \SQLSvc properties on the Database Access tab, add these:
- Under the properties of each of those choose db_owner.
- Choose Management > Jobs > Monitor Disk Space, and choose \SQLSvc as the owner.
- Restart the SQLServerAgent and MSSQLServer services.
- If the Monitor Disk space turns blue, it indicates that the Replication Job fails. In this case, it is recommended to create a new subscription.
In this issue, after an upgrade from Cisco CallManager 3.3.3 to 4.1, a job failure error message appears at regular intervals in the subscriber application logs with Event Viewer. This is due to a changed representation of the MLA database in Cisco CallManager 4.1.
