Microsoft KB Archive/927362

From BetaArchive Wiki
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Knowledge Base


How to upgrade from Windows SharePoint Services 3.0 Beta 2 TR or SharePoint Server 2007 Beta 2 TR to the original release versions when you did not rename the DSN registry key to DSN2

Article ID: 927362

Article Last Modified on 10/17/2007



APPLIES TO

  • Microsoft Office SharePoint Server 2007
  • Microsoft Windows SharePoint Services 3.0



INTRODUCTION

You plan to perform one of the following upgrades:

  • Upgrade to the original release version of Microsoft Windows SharePoint Services (WSS) 3.0 from Microsoft Windows SharePoint Services 3.0 Beta 2 Technical Refresh (TR).
  • Upgrade to the original release version of Microsoft Office SharePoint Server 2007 from Microsoft Office SharePoint Server 2007 Beta 2 TR.

Before you upgrade, you must first rename the DSN registry key to DSN2. The DSN registry key is located in the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Secure\ConfigDB


Note You must rename the DSN registry key to DSN2 before you remove the WSS 3.0 Beta 2 TR version or before you remove the SharePoint Server 2007 Beta 2 TR version.

You must rename the DSN registry key for the following reasons:

  • If you do not rename the DSN registry key to DSN2 before you remove WSS 3.0 Beta 2 TR, the WSS 3.0 Beta 2 TR Web application and service configuration information is also removed.
  • When you install the original release version of WSS 3.0 or the original release version of SharePoint Server 2007, the Post Configuration Wizard detects the DSN2 registry key. Then, special upgrade steps are performed. If the DSN2 registry key is not detected, the Post Configuration Wizard performs a new installation.

Note The steps in this article assume one of the following:

  • You backed up the WSS 3.0 Beta 2 TR content database(s) before you removed WSS 3.0 Beta 2 TR.
  • The WSS 3.0 Beta 2 TR content database(s) are still present.

If you did not rename the registry key, you cannot use the original upgrade documentation to upgrade to the original release version of WSS 3.0 or to the original release version of SharePoint Server 2007. Instead, you must install the original release version of WSS 3.0 or the original release version of SharePoint Server 2007. Then, you must attach the Beta 2 TR content databases to the new Web applications in the original release version of WSS 3.0. When you attach the Beta 2 TR content database to the new Web applications, the database and its contents are upgraded to the original release version, and the data is preserved.

You should use the same deployment configuration in the original release version environment that you used in the Beta 2 TR environment. After you create the new Web application, you must remove the new content database for the new Web application. Then, you must use the Stsadm.exe command-line tool to attach the Beta 2 TR content database to the new Web application.

MORE INFORMATION

If the following conditions are true, follow the steps in this section to successfully re-create the Web applications and service configuration information:

  • You did not rename the DSN registry key in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Secure\ConfigDB registry subkey.
  • You have already removed WSS 3.0 Beta 2 TR.
  1. Remove the old SharePoint Configuration database, and then install the original release version of WSS 3.0. To do this, follow these steps:
    1. After you remove WSS 3.0 Beta 2 TR, remove the SharePoint Configuration database (SharePoint_Config) that is located in the following folder:

      \Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data

      Note In this case, the Beta 2 TR configuration database cannot be upgraded to the original release. You must create a new one.
    2. Perform a new installation of the original release version of WSS 3.0 or the original release version of SharePoint Server 2007. Then, use the same settings that you used in the first Beta 2 TR installation.
  2. Create a new Web application, remove the new content databases, and then use the STSADM command-line tool to attach the WSS 3.0 Beta 2 TR content database. To do this, follow these steps:
    1. Click Start, point to Administrative Tools, and then click SharePoint 3.0 Central Administration.
    2. On the Central Administration page, click Application Management, and then click Create or extend Web application.
    3. On the Create or Extend Web Application page, click Create a new Web Application.
    4. On the Create New Web Application page, enter the same settings that you used in the original Beta 2 TR installation, and then click OK.
    5. In SharePoint 3.0 Central Administration, click Application Management.
    6. On the Application Management page, click Content Databases.
    7. On the Content Databases page, click the content database that was created when you created the new Web application.
    8. On the Manage Content Databases page, click the Remove content database check box to remove the database, and then click OK.

      Note Because the database is no longer required, you can note the name of the database so that you can delete it from Microsoft SQL Server.
    9. Click Start, click Run, type cmd, and then click OK.
    10. At the command prompt, locate the following folder:

      \Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN

    11. At the command prompt, type the following command to attach the previous content database to the new Web application:

      stsadm -o addcontentdb -url URL -databasename database name -databaseserver database server name

      The parameters for the addcontentdb operation are as follows:
      • database name is the name of the database that you want to attach to the new Web application.
      • URL is the URL of the SharePoint Server 2007 site that hosts the content database.
      • Database server name is the name of the computer that hosts the content database.

        Note When you use the stsadm -o addcontentdb command, the databases are automatically upgraded, and the existing data is retained.

For more information about upgrading from Windows SharePoint Services 3.0 Beta 2 Technical Refresh to the release version, visit the following Microsoft Web site:


Additional query words: WSSv3 RTM

Keywords: kbhowto kbinfo kbexpertiseinter KB927362