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

CDR logging problem with SQL Server7.0

Hi,

I've got a problem with CDR logging with my CallManager 3.1 publisher. When we try to see CDR table by doing:

Start->Programs->Microsoft SQL Server 7.0->Enterprise Manager

and select CDR table, we get an error message:

"The SQL Server <servername> is not known to be running. Are you sure you wish to connect?"

If we choose "OK" and force to select CDR table, we find no new calls are recorded to the table. If we check the SQL Service, however, the service is indeed running. We tried bunch of things like: start/stop SQL server, enable/disable CDR and update, restarting CCM server itself, etc. But nothing seems to work. After giving it up and started searching for a web for any solution, we end up with finding new calls are started being recorded. So it seems no solution is there but we need to wait enough time for CCM server to get happy to start cooperating with its SQL services.

Has anybody got any idea/solution for this problem???

cheers,

3 REPLIES
Cisco Employee

Re: CDR logging problem with SQL Server7.0

Do you have a publisher and a subscriber? If so which one is doing call processing? Look at the event log on both boxes at the application and system logs to see if you see any errors related to cdr.

Thank you,

-Mckee

Community Member

Re: CDR logging problem with SQL Server7.0

Hi,

We have 1xpublisher, 1xsubscriber(primary), 1xsubscriber(secondary). So a phone call should be processed by either primary or secondary, depending on which one was available when the phone was registered. And the CDR database exists on publisher. We have checked the eventlog on our primary CCM and found SQLServerAgent event: "The process could not connect to Distributor ''". So it looks like primary CCM failed to contact publisher. But why?

As for the error message on Enterprise Manager, we found a few posts on microsoft newsgroup:

1) see this message regulary

http://search.communities.microsoft.com/newsgroups/previewFrame.asp?ICP=SQL&sLCID=US&sgroupURL=microsoft.public.sqlserver.connect&sMessageID=%253C15be01c1c14e%24700af260%24a4e62ecf@tkmsftngxa06%253E

2) may have a name resolution problem

http://search.communities.microsoft.com/newsgroups/previewFrame.asp?ICP=SQL&sLCID=US&sgroupURL=microsoft.public.sqlserver.connect&sMessageID=%253C58j0VjHxBHA.2172@cpmsftngxa09%253E

3) basically you can ignore it

http://search.communities.microsoft.com/newsgroups/previewFrame.asp?ICP=SQL&sLCID=US&sgroupURL=microsoft.public.sqlserver.connect&sMessageID=%253CJjKfHi0wBHA.584@cpmsftngxa07%253E

We have taken the third option and decided to concentrate on troubleshooting CCM behavior. Do you have any further information/documentation?

Sorry about this longish post. But we, R&S experts, are now supposed to troubleshoot M$ products without enough information.

regards,

Cisco Employee

Re: CDR logging problem with SQL Server7.0

Usually when you get the cannot connect to distributor on the sub that means you may have a name resolution problem or the sqlsvc users password is different on the pub than on the sub. The password should be the same for all of the servers in a cluster. Did you ever mess with this users password?

Thank you,

-Mckee

107
Views
0
Helpful
3
Replies
CreatePlease to create content