Friday, March 18, 2011

How to fix Error: Exception from HRESULT: 0x80040E14

Have you got this error message when you connect to your Windows SharePoint Services Web site:

Exception from HRESULT: 0x80040E14.
Troubleshoot issues with Windows SharePoint Services.

If this error occurs you are not able to perform these actions:

  • Edit columns on a list
  • Import a spreadsheet
  • Add choices to a choice field

To resolve this issue, use the Stsadm.exe command-line tool to force an upgrade of the content databases. To do this, follow these steps:

Windows SharePoint Services 2.0


  1. Click Start, click Run, type cmd in the Open box, and then click OK.
  2. At the command prompt, type the following lines, and then press ENTER after each line: cd /d %commonprogramfiles%\Microsoft Shared\Web Server Extensions\60\Bin
    stsadm -o upgrade -forceupgrade
  3. Type exit to exit Command Prompt.

Windows SharePoint Services 3.0


  1. Click Start, click Run, type cmd in the Open box, and then click OK.
  2. At the command prompt, type the following lines, and then press ENTER after each line: cd /d %commonprogramfiles%\Microsoft Shared\web server extensions\12\BIN
    stsadm -o upgrade -forceupgrade
  3. Type exit to exit Command Prompt.

After applying these steps if you still get same error message then you should try SharePoint Recovery Software to resolve this issue.

Stellar Phoenix SharePoint Server Recovery Software is very easy to use & you can check its all functionality by its demo version. It provides recovery for SharePoint server 2010 & 2007. It recover SharePoint database as well inaccessible SharePoint site content.

Wednesday, March 9, 2011

How to fix Windows SharePoint Services: "Server Error in '/_vti_bin'

Have you get this error “Server Error in '/_vti_bin” when you try to open a WSS site. Do you know the cause & solution of this error. Here I am explaining cause & solution of this error. 
 
Cause:

This error occurs when the virtual server on which Windows SharePoint Services is extended does not have Business Portal 3.0 installed. Therefore, if the virtual server on which Windows SharePoint Services is extended does not have Business Portal 3.0 installed, SharePoint Web services cannot be accessed on that virtual server. This condition occurs because the Web.config file in the Isapi subfolder was modified.
 
Resolution:

To fix this issue, remove the following lines from the Web.config file that is located in the Drive:\Program Files\Common Files\Microsoft Shared\Web server extensions\60\Isapi folder:

To do this action, follow below steps:

1.Start Notepad, and then open the Web.config file that is located in the following folder:
Drive:\Program Files\Common Files\Microsoft Shared\Web server extensions\60\Isapi
2.Remove the following lines from the Web.config file:
<httpModules>
<remove name="EnterpriseInitializationModule"></remove>
<remove name="BPAdminRedirectModule">
</remove> </httpModules>
3.Save and then close the Web.config file.

After taking above step may be this error does not resolve. In this case you can try SharePoint Database Recovery to resolved this error. These software are very easy to use & recover all lost data in few minutes.
 
Stellar SharePoint Server Recovery Software is one of the best recovery tool to recover corrupt SharePoint database as well as inaccessible SharePoint site content. The Software recover SharePoint 2007 & 2010.