cancel
Showing results for 
Search instead for 
Did you mean: 

Error EC8F1C25: bad allocation

Scott_Douglass
Level 3

Does anyone know what this error is referring to?

 

 

Date: 4/12/2007 9:48:01 AM

Notification Type: Error

Priority: High

Description: Error EC8F1780: Cannot successfully reconcile changes since last session. Error EC8F1771: Cannot enumerate the current drives on this system. Error EC8F1C25: bad allocation

Details: Unspecified error

 

 

8 REPLIES 8

Scott_Douglass
Level 3
Date: 5/12/2007 8:48:18 AM Notification Type: Error Priority: High Description: Error EC8F1780: Cannot successfully reconcile changes since last session. Error EC8F1771: Cannot enumerate the current drives on this system. Error EC8F1C25: bad allocation Details: Unspecified error

Rich_L
Level 6
Employee
Hi Scott,
 
This error indicates the drive has drive errors.  I would recommend doing a CHKDSK /R from a CMD Prompt.  CHKDSK should be able to find the bad allocation and fix or mark them.

KMD77
Not applicable
Hi Scott
 
I had the same problem on one of my servers.
 
Stopping and restarting the BESR service corrected the problem for me.
 
CHKDSK found no problem with the drives.
 
Ken

Scott_Douglass
Level 3
Ken,
 
Error EC8F1C25: bad allocation again today.
 
As I look after these servers, it's rather annoying to say the least to have to reboot them to fix this issue.
 
Anyone else experiencing this issue?

Scott_Douglass
Level 3
Firstly: chkdsk all volumes, no errors wait for this patch which will endup being a new version.
7.0.3 for anyone having the issue
EC8F1C25: Bad allocation

Serious fault in Backup Exec System Recovery until this patch.
Intermittent Complete failure of backup software.

From: enterprise_support@symantec.com [mailto:enterprise_support@symantec.com]
Sent: Friday, 4 January 2008 4:13 PM
To: brett.douglass@evit.com.au
Subject: Case 311-799-554 (EC8F1C25: Bad allocation...)

 Dear Brett,

 Thanks for your reply.

 I had a look at the BESR logs but couldn't find anything wrong. 

Partition information and all other settings on the IBM server are correct.

In addition, I've consulted with backline support and I was told that it is related to BESR memory leak problem since the issue is fixed if you reboot the machine.  Actually, the issue is fixed in the next version of BESR (7.03) which will be available end of this month. 

I'll let you know when the version is available.

If you have any questions, please let me know.

Thanks, 

Dawson


Rich_L
Level 6
Employee
Scott,
 
BESR 7.0.3 is available for download.  I see that the download information was sent to you via an email thru your case.
 
Thanks,
RichL


Message Edited by Rich L on 01-17-2008 11:41 AM

voyager152
Level 2
Hello,
 
I have a Dell Server running Windows 2003 Standard SP1. This server is dedicated to running MSFT Exchange 2003 Server.
 
BESR version is 7.0.3.24709
 
I am getting this error regularly (every couple of weeks) Any suggestions?

Deano
Level 2

I was able to resolve the error, just like KMD77 suggested.

I restarted the Backup Exec System Recovery service and then I was able to run a "catchup" LSR image.

The server is using v7.0.4.26323 BSR.