CopyPastehas never been so tasty!

SharePoint Recovery After Receiving File Damaged

by anonymous

  • 1
  • 0
  • 0

SharePoint Server, a portal collaboration software is one of the many offerings of Microsoft that enhances sharing and working in large organisations. Knitting the various segments of an organization together, it includes site templates for collaborating, offers tagging news feeds, and helps employees search business critical data. However, due to different reasons like virus attacks, bad sectors in storage media, software malfunctioning etc, MDF file may get corrupted or damaged. Owing to this the website becomes inaccessible and people are unable to access critical documents from the database, thereby calling for extensive SharePoint recovery using updated backup. But, in case the same is unavailable, then there is a need to recover SharePoint using repair software.


Consider, that you are unable to access either the workspace dashboard site or the SharePoint Portal Server Administrator Console. Such a situation may be accompanied by the following error message, when you try to restart the Server service:


Could not start the Sharepoint Portal Server service on Local Computer.

The service did not return an error. This could be an internal windows error or an internal service error. If the problem persists, contact your system administrator.


Not only that, following event ID messages might also be logged in the event log of the Application:


Event ID: 482

Source: ESE98

Description: Information Store (1008) An attempt to write to the file "F:\Program Files\SharePoint Portal Server\Data\Web Storage System\Wss.mdb" at offset 25174016 (0x0000000001802000) for 1048576 (0x00100000) bytes failed with system error 112 (0x00000070): "There is not enough space on the disk.". The write operation will fail with error -1808 (0xfffff8f0). If this error persists then the file may be damaged and may need to be restored from a previous backup.

Event ID: 9539

Source: MSExchangeISPublic Store

Description: The Microsoft Exchange Information Store database "SharePoint Portal Server Group\SharePoint Portal Server Store" was stopped.

Event ID: 103

Source: ESE98

Description: Information Store (1008) The database engine stopped an instance (0).

Event ID: 101

Source: ESE98

Description: Information Store (1008) The database engine stopped.

Event ID: 1004

Source: MSExchangeIS

Description: Unable to start the Microsoft Exchange Information Store. Disk is full.

Event ID: 24578

Source: Sharepoint Portal Server

Description: Upgrade to version 10.145.3914.0003 failed. The error code returned was 0x80150804.


Reason: There could be two possible reasons behind such an error message:


  • If Microsoft Exchange Information Store (MSExchangeIS) service has exited as the server ran out of disk space. Since, SharePoint Portal Server (Msdmserv) service counts on MSExchangeIS to begin; it cannot restart, if MSExchangeIS doesn't run.

  • Another reason could be that database file may be damaged and may need to be restored from a previous backup.



  • In case the error has occurred due to the first reason, i.e., server running out of disk space, then

    • Free up disk space on the SharePoint Portal Server drive.

    • After this, stop and restart MSExchangeIS service.

    • Now the Msdmserv service should start normally.


  • In case the error has occurred due to database file being damaged, then you will need recover SharePoint database file from an updated backup. But, in case the backup is outdated, or doesn't work, then a powerful third-party SharePoint Recovery tool is the best option. These are used to repair the damaged and inaccessible database file.

Stellar Phoenix SharePoint Server Recovery is one of the most reliant tool that is used to recover MDF database files that have been created for MS SQL Server 2000, 2005, and 2008. Compatible with various versions of Windows, including Vista, XP, 2000, NT, and 9x, this SharePoint repair tool supports MS SharePoint Server 2007 and 2010.

Add A Comment: