THX TO KELLO!

SYMPTOMS

When you connect to your Microsoft Windows SharePoint Services Web site after you install a Microsoft Windows SharePoint Service service pack on the server, you may receive an error message that is similar to one of the following:
Exception from HRESULT: 0x80040E14.
Troubleshoot issues with Windows SharePoint Services.

HTTP 500 - Internal server error

CAUSE

This issue may occur if the content databases in Windows SharePoint Services are not updated correctly during the installation of the Windows SharePoint Services service pack. The content databases still have the same version numbers that were present before you installed the Windows SharePoint Services service pack. This issue may occur if one of the following conditions is true:
  • You install Microsoft Windows SharePoint Services Service Pack 1 (SP1) on the server when the virtual server is unextended, and then you extend the virtual server by mapping the virtual server to an existing Windows SharePoint Services Web site.
  • You install Windows SharePoint Services Service Pack 1 (SP1) on the server when the MSSQLSERVER service is stopped. In this situation, Windows SharePoint Services SP1 is installed successfully, but the content databases are not updated.
  • You install Windows SharePoint Services Service Pack 1 (SP1) on the server and a process has the virtual servers content directory files \_vti_pvt\service.cnf or \web.config locked for write access.
This issue may also occur if you follow these steps:
  1. Install Windows SharePoint Services .
  2. Install Windows SharePoint Services SP 1.
  3. Remove Windows SharePoint Services SP 1.
  4. Reinstall Windows SharePoint Services release to the manufacturing build.
  5. Connect back to the upgraded databases.
In this scenario, Windows SharePoint Services SP 1 is in a bad state because the databases are upgraded but Windows SharePoint Services SP 1 is running the release to manufacturing release build. You must reinstall Windows SharePoint Services SP 1 for the program and the databases to be functional.

RESOLUTION

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:
  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 quit Command Prompt.