[cisco-voip] CDRServerDown event log error

[Erick Bergquist]

This is all there is from time of a error.  It is a connect issue, I was just stating I have seen the "CDRServerDown" error before caused by bad formated data that could not be inserted due to commas or aprostrophes, etc (have bug id's) but the following is all that is there for this. 

Is the timeout 20 seconds?  DBL traces next step to get deeper or ?


|<CLID::StandAloneCluster><NID::172.16.1.1>
04/09/2006 20:44:46.468 CDR|-->CMonitor::ProcessDirectoryChange ()
|<CLID::StandAloneCluster><NID::172.16.1.1>
04/09/2006 20:44:46.468 CDR|   CMonitor::ProcessDirectoryChange () Get
connection|<CLID::StandAloneCluster><NID::172.16.1.1>
04/09/2006 20:45:04.047 CDR|   CMonitor::ProcessDirectoryChange ()
*ERROR* GetConnection ErrorCode [0] [Failed to connect to datasource:
[Microsoft][ODBC SQL Server Driver]Timeout
expired]|<CLID::StandAloneCluster><NID::172.16.1.1>
04/09/2006 20:45:04.047 CDR|kErrorCDRServerDown - Error connecting to
CDR Database. ODBC Error:Failed to connect to datasource:
[Microsoft][ODBC SQL Server Driver]Timeout expired App ID:Cisco CDR
Insert Cluster ID:StandAloneCluster Node

----- Original Message ----
From: Wes Sisk <wsisk at cisco.com>
To: Erick Bergquist <erickbe at yahoo.com>
Cc: ciscovoip <cisco-voip at puck.nether.net>
Sent: Wednesday, April 12, 2006 10:46:22 PM
Subject: Re: [cisco-voip] CDRServerDown event log error

set the cdrinsert logs to at least error if not detailed and wait for  
an event.  should shed some light.

I'd be leary of bad data causing SQL connectivity problems.  There  
have been a few CM fixes where records failed insert because of data  
in the file, but insert is a separate step from connect.

/Wes

On Apr 12, 2006, at 6:00 PM, Erick Bergquist wrote:

Ok. The enterprise parameters are set to publishers name (not IP) and  
it is inserting records fine, and they have hosts/lmhosts for the  
name to server IP, etc. I have seen this error in past when records  
were not inserted due to bad/corrupt data in the flat cdr files  
(bugs, etc) and either updates or changes to CCM descriptions, user  
names, etc so cdr could insert those records.

Not seeing anything here indicating a problem.


----- Original Message ----
From: Wes Sisk <wsisk at cisco.com>
To: Erick Bergquist <erickbe at yahoo.com>
Cc: ciscovoip <cisco-voip at puck.nether.net>
Sent: Wednesday, April 12, 2006 10:50:59 AM
Subject: Re: [cisco-voip] CDRServerDown event log error

i believe CDR insert generates that error when it cannot connect to the
server specified in the CDR DSN. defaults to the publisher or uses the
enterprise parameter Off Cluster CDR Connection String

/Wes

Erick Bergquist wrote:
> Hi,
>
> Anyone know cause why an occassional error for CDRServerDown will  
> occur in event log for no apparrent reason?  I have checked the  
> detailed traces and it works fine then out of blue fails to connect  
> to the database then works fine again for awhile. Getting error  
> once a day or once every 2 days on average at random times. Nothing  
> on server appears to be spiking, etc at those times and no other  
> apps besides CCM and CSA.
>
> No cdr flat files in the cdr folders either - all clean/empty (cdr/ 
> bad/cmr) and data is being inserted into CDR db fine.
>
> CCM 4.0(1)sr1a
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>