After Cisco CallManager is upgraded to 4.1 the SQL Monitor Disk Space Job fails to run and the application event log shows warnings about the Monitor Disk Space during the attempt to access the Database.

[TCC_2]

Core Issue

The SQL Monitor Disk Space Job fails and attempt to resync the subscriptions of the SQL db goes without success because the job points to the incorrect database. The application event log shows few instances of this warning :

Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: (3)
Event ID: 208
Date:
Time:
User: N/A
Computer:
Description: The description for Event ID ( 208 ) in Source ( SQLSERVERAGENT ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: Monitor Disk Space, 0xBAD845DCF1F70A4AB8416FEB1DD13B73, Failed, 2006-11-17 08:00:02, The job failed. The Job was invoked by Schedule 17 (Schedule 1). The last step to run was step 2 (TruncateCCMLog)..

Resolution

In order to resolve this issue, make sure that the job in fact points at the correct database (CMM030x) and that under the properties of the CCM030x database, the Options window shows the recovery Model as Full instead of simple.

If both steps are in place, then verify if Cisco CallManager and call detail record (CDR) databases have correct owners in SQL. Complete these steps in order to verify the owner:

1. Right-click on the Cisco CallManager and CDR in SQL Enterprise Manager and look at the Properties.
   
   If any of the databases have Unknown for the owner in Properties, change it in order to set the database owner in this way:
   
   
   1. Open SQL Query Analyzer and run this command on each database that is Unknown:
      
      sp_changedbowner 'hostname\Administrator'
      
      The hostname is the hostname of the Cisco CallManager server.
      
      
   2. If issue is still unresolved, then run this query from the Query Analyzer:
      
      SELECT name
      FROM master..sysdatabases
      WHERE SUSER_SNAME(sid) IS NULL
      
      The script shows if there is something wrong with the database owners. Set the owner on the original Cisco CallManager database and verify if the job executes correctly.

Problem Type

Call control software (CallManager, CallManager Express, ICS7750, SRST, SS7 call agents)

Call Control

CallManager

Common Software and Product Issues

Problems after an upgrade

Failure Type

Cannot start, stop, schedule, reset, power up, power down, run, initialize, open, close, activate, deactivate or load

Troubleshooting Tools

Application event viewer or other event log

CallManager Versions

CallManager 4.1

Operating System Components

SQL