When restoring Service Applications of SharePoint 2010, the restore job can fail.

Article:TECH152382  |  Created: 2011-02-01  |  Updated: 2014-03-03  |  Article URL http://www.symantec.com/docs/TECH152382
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution

Product(s)

Subject

Issue



When restoring Service Applications of SharePoint 2010, the restore job can fail.


Error



Final error: 0xe000fefe - An error occurred while connecting the restored databases to the Microsoft SharePoint Portal Farm. The portal was not restored.

Final error category: Resource Errors.

 

For additional information regarding this error refer to link V-79-57344-65278.

 


Environment



Symantec Backup Exec 2010 R2 and R3.

Symantec Backup Exec Agent for Microsoft SharePoint.

Microsoft SharePoint Server 2010.

 


Cause



There are four reasons for the restore error.

 

A) An issue has been addressed.

Web Analytics Service Application, Word Automation Services and State Service fail to restore if Hotfix 148347 is not installed for Backup Exec 2010 R2.

www.symantec.com/docs/TECH148347

 

B) During Disaster Recovery

During Disaster Recovery, restore jobs fail because communication with the SharePoint server has not been fully established yet. This behavior is expected.

 

C) Timing issue of SharePoint Server

When restoring a Service Application, Backup Exec performs following operation to the SharePoint Server.

1) Backup Exec sends a request to delete existing Service Application to the SharePoint Server.

2) Backup Exec sends a request to create the Service Application to the SharePoint Server.

In the step 2 right after step 1 above, SharePoint Server is not ready to create the Service Application and can cause an error to create it. This behavior is also expected.

 

D) IIS is in an inconsistent state

Please refer to TECH153442 for this reason and solution.

www.symantec.com/docs/TECH153442 

 


Solution



A) An issue has been addressed

Install Hotfix 148347 for Backup Exec 2010 R2, or upgrade to Backup Exec 2010 R3 or Backup Exec 2012, and then get full backup of SharePoint farm.

 

B) During Disaster Recovery

When the restore error occurs during Disaster Recovery, proceed with the recovery process until all steps are complete.

 

C) Timing issue of SharePoint Server

Delete existing Service Application to be restored before performing the restore job.

Note1: If the restore job failed once, the Service Application might be being deleted already.

Note2: Even if this workaround is performed, the timing issue may be observed if insufficient memory or CPU resource is available.  For instance, a test system of a virtual machine.

Please refer Hardware and software requirements of SharePoint Server 2010.
http://technet.microsoft.com/en-us/library/cc262485.aspx

 

Cause C has been addressed in Backup Exec 2012.

 

D) IIS is in an inconsistent state

Please refer to TECH153442 for this reason and solution.

www.symantec.com/docs/TECH153442 

 


Supplemental Materials

SourceETrack
Value2152164
Description

SPS4: Two Shared Service entities are seeing restore failures - Web Analytics Service App and Word automation


SourceETrack
Value2250517
Description

StateService restore fails: V-79-57344-65278 - An error occurred while connecting the restored databases.


SourceETrack
Value2259703
Description

SPS4: Service Applications restore may fail by timing issue of SPS


SourceUMI
ValueV-79-57344-65278
Description

An error occurred while connecting the restored databases to the Microsoft SharePoint Portal Farm. The portal was not restored.


SourceError Code
Value0xe000fefe
Description

An error occurred while connecting the restored databases to the Microsoft SharePoint Portal Farm. The portal was not restored.




Article URL http://www.symantec.com/docs/TECH152382


Terms of use for this information are found in Legal Notices