Backup of SharePoint 2003 server fails with error " 0xe000fe30 - Communication has failed."

Article:TECH74310  |  Created: 2009-01-08  |  Updated: 2013-03-05  |  Article URL
Article Type
Technical Solution


Backup of SharePoint 2003 server fails with error " 0xe000fe30 - Communication has failed."


Backup - http://server\ Index DB 1 (SERVER)  - The connection to target system has been lost. The backup has been canceled.

Backup - http://server\ Index DB 1 (SERVER) WARNING: the file http://server \ Index DB 1 (SERVER) \ http://server\ Index DB 1 (SERVER) is damaged.


Backup Exec Job Engine crashes during SPS backup of SQL databases on same server.
Able to backup SQL databases. The above error occurs backing up the Index DB.
Backup using SharePoint utility also fails on the same Index DB.

Corruption in the SPS Index database.

Application Log Error:

Event Type: Error
Event Source: Backup Exec
Event Category: None
User: N / A
Computer: <computer name>
Backup Exec Alert: Job Failed
(Server: "server name") (Job: "job name")<Job Name> - The job failed with the following error: The Backup Exec job engine system service is not responding.
Event Type:      Error
Event Source:      Application Error
Event Category:      (100)
Event ID:      1000
User:            N/A
Computer:    <computer name>
Description: Faulting application bengine.exe, version 12.5.2213.133, faulting module msvcr80.dll, version 8.0.50727.3053, fault address 0x000000000001e385.
End State: Failed 


1) Continue the backups without Index DB.

2) Re-index using SharePoint Utilities and retry backup job.
Contact Microsoft Technical Support for assistance in rebuilding the indexes, or if SharePoint backup utility returns an error while backing up the index database.
For more information on SharePoint's in-built backup utility, refer to the following Microsoft documents:

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices