Almost always that happens when a backup was aborted without being able to clean up after itself. For example, waiting for tapes and then end-tasked. After that happens, you get that error because you can only have one backup in process at a time.
Now, I'm NOT guaranteeing this, but as long as you have one good backup and log files since then, you should just be able to bounce the store (restart the Information Store service) and the message go away... Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com -----Original Message----- From: JB [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 11:06 AM To: MS-Exchange Admin Issues Subject: NTBackup Issue-Exchange 2003 All, I'm having a weird issue with a customer of ours. They are using NTBackup run backups on a public folder server of theirs. The catch is that the OS is a W2K server with E2K3 installed on it. Here is the error we are constantly seeing when the backup attempts to kick off. Event Type: Error Event Source: NTBackup Event Category: None Event ID: 8012 Date: 3/18/2008 Time: 10:00:01 AM User: N/A Computer: SERVERNAME Description: The 'ESE API' returned 'Callback ' from a call to 'HrESEBackupRestoreNodes()' additional data 'SERVERNAME' Now I've researched this issue and have came across an article that pertains to Exchange 2000 and they say that the error is irrelevant and give no further explaination as to why it's irrelevant. Now how am I to ensure that the backups are working properly? Thank you, _____________ John Bowles ____________________________________________________________________________ ________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
