Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Problem with SQL database

In event viewer are some error messages pointing at the sql server:

Error: kErrorCDRServerDown - Error connecting to CDR Database.

ODBC Error: Failed to connect to datasource: [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'CiscoCCMCDR'.

App ID: Cisco CDR Insert

Cluster ID: TrendServer-Cluster

Node ID: 172.16.60.25

Explanation: CDR database server is not responding. CDRs cannot be written.

Recommended Action: Either bring server back online or reconfigure CDRs to be written to a different server..

CallManager device unregistered.

All the devices in the system are registered and the auto-registration is disabled. Also, CDR insert is enabled but there are no reports in CDR table. Only 3 calls reported, but last week.

What the problem could be ?

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Problem with SQL database

There is no likelyhood that this problem is related to DC directory as CDR doesn't use it.

The error is SQL based, either your subscription is broken or you've a password problem. Check your replication agents on the publisher first and then ensure all the passwords for SQL accounts are the same on all boxes.

Make sure your host file is correct on both the pub and sub, and don't allow them to rely on DNS even to recognise themselves. Put them in their own Hosts files.

Paul

4 REPLIES
Blue

Re: Problem with SQL database

Dude, Prior to CM 3.2(3) CDR Insert had many issues. Upgrade to CM 3.2(3) or contact TAC and they have an engineering special that will correct your problem.

New Member

Re: Problem with SQL database

The problem is that CallManager cannot insert any records in database (cdr, art database). are there any posibility to be a problem with DC directory administration ?

Re: Problem with SQL database

There is no likelyhood that this problem is related to DC directory as CDR doesn't use it.

The error is SQL based, either your subscription is broken or you've a password problem. Check your replication agents on the publisher first and then ensure all the passwords for SQL accounts are the same on all boxes.

Make sure your host file is correct on both the pub and sub, and don't allow them to rely on DNS even to recognise themselves. Put them in their own Hosts files.

Paul

New Member

Re: Problem with SQL database

Thanks a lot !

119
Views
0
Helpful
4
Replies
CreatePlease to create content