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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Error in callmanager server

Hi all,

I keep seeing this in my server (CCM 4.1(3)sr2) all debug server is set to default.

the files and directory seems exist.

Any idea? Is it related to CSA?

Event Type: Error

Event Source: Cisco CallManager

Event Category: None

Event ID: 3

Date: 2/17/2006

Time: 3:02:05 PM

User: N/A

Computer: CCM3

Description:

Error: GetNewFileName-fopen in wb mode failed to update existing file. szFileNumberName = c:\Program Files\Cisco\Trace\DBL\DBL_DLLHOST~num.bin.

4 REPLIES
Silver

Re: Error in callmanager server

Seems to be related to CSA indeed

CSCeg57610 Bug Details

Headline CSA issues with DBL num.bin when DBL trace change default location

Product ccm-csa

Symptom:

Application event logs are getting flooded with the following errors:

Event Type: Error

Event Source: Cisco CallManager

Event Category: None

Event ID: 3

Date: 12/16/2004

Time: 10:40:13 AM

User: N/A

Computer: xxxxxxx

Description:

Error: GetNewFileName-fopen in wb mode failed to update new file.

szFileNumberName = c:\dbltest7\DBL_xxxxx~num.bin.

Event Type: Error

Event Source: Cisco CallManager

Event Category: None

Event ID: 3

Date: 12/16/2004

Time: 10:40:13 AM

User: N/A

Computer: xxxxxxxx

Description:

Error: szNumber = 3e5.

Condition:

This has been observed with CSA-CCM policy 1.1(9) when the default path location

for Database Layer Monitoring traces has been changed from the default location.

Workaround:

None. To stop the error messages the following must be done:

1. Disable the CSA service on all nodes

2. Set DBL traces to default path location of c:\program files\cisco\trace\dbl\aupair.txt

Re: Error in callmanager server

I've also seen this when a client installed the Unity CSA version on a CCM server, so check the call manager version is installed on CCM.

Re: Error in callmanager server

CSCin57059

Description:

Lot of "GetNewFileName-fopen in wb mode failed to update existing file"

Error Alarm is getting generated

which is flooding the Event viewer. Here are the details of the Alarm

Error: GetNewFileName-fopen in wb mode failed to update existing file.

szFileNumberName = c:\Program Files\Cisco\Trace\DBL\dbl~num.bin.

Every minute 7 alarms are getting generated for the same error with same

time stamp.

After running CCM for one day Event viewer is flooded with this Alarm

making it difficult to analyze other important Alarms.

Condition : When Trace configuration is enabled to detailed Database

Tracing

workaround : Turn off tracing.

or

Grant Read, write and modify access for IWAM_Guest account on trace\dbl

and trace\ris directory.

New Member

Re: Error in callmanager server

Hello guy's!

Where can I found more info about this king of issues that appears on Event Viewer??

Thanks

151
Views
0
Helpful
4
Replies