Microsoft KB Archive/924000

From BetaArchive Wiki

Article ID: 924000

Article Last Modified on 8/23/2006


APPLIES TO

  • Microsoft Windows Small Business Server 2003 R2 Premium Edition



SUMMARY

This article describes the steps that you must take to upgrade the initial release media of Microsoft Windows Small Business Server 2003 R2 (Windows SBS 2003 R2) to include the final release version of Microsoft SQL Server 2005 Workgroup Edition.


INTRODUCTION

The initial release media for Windows Small Business Server 2003 R2 does not contain the final release version of SQL Server 2005 Workgroup Edition. This article describes the steps that you must take to upgrade Windows SBS 2003 R2 to include the final release version of SQL Server 2005 Workgroup Edition.

Does this article apply to me?

This article applies only to a limited number of international customers who used the initial release media of Windows SBS 2003 R2 Premium Edition to install SQL Server 2005 Workgroup Edition. This article applies only if the following conditions are true:

  • You are running one of the following language versions of Windows SBS 2003 R2 Premium Edition:
    • Chinese (Simplified)
    • Chinese (Traditional)
    • French
    • German
    • Italian
    • Japanese
    • Korean
    • Spanish
  • You used the initial release media of Windows SBS 2003 R2 Premium Edition to install SQL Server 2005 Workgroup Edition.
  • You migrated Microsoft Windows SharePoint Services to SQL Server 2005 Workgroup Edition.

Notes

  • This article does not apply to you if you are running an English version or any other language version of Windows SBS 2003 R2 Premium Edition that is not listed in this section.
  • If you are running applications other than Windows SharePoint Services that require SQL Server 2005, contact the application vendor or Microsoft before you continue.


MORE INFORMATION

Step One: Obtain the latest release media

Before you can update Windows SBS 2003 R2, you must obtain the latest release media. To obtain the latest release media, contact the person or the company from which you purchased Windows SBS 2003 R2.

Step Two: Back up the SQL Server databases including the master database

For information about how to back up SQL Server databases, see online Help for SQL Server 2005. For more information, visit the following Microsoft Web site:

http://msdn2.microsoft.com/en-us/library/ms203721.aspx


Step Three: Stop Windows SharePoint Services, and then back up the Window SharePoint Services databases

Note If you did not migrate the http://companyweb Web site to SQL Server 2005, go to step c in the following procedure.

  1. Stop the http://companyweb Web site. To do this, follow these steps:
    1. Click Start, and then click Server Management.
    2. In Server Management, expand Advanced Management, expand Internet Information Services, expand ServerName (local computer), and then expand Websites.

      Note ServerName is the name of the Windows SharePoint Services server.
    3. Right-click companyweb, and then click Stop.
  2. Stop the Windows SharePoint Timer service. To do this, follow these steps:
    1. Click Start, click Run, type Control admintools, and then click Services.
    2. Double-click SharePoint Timer Service to open the Properties dialog box.
    3. On the General tab, click Stop.
    4. Click Manual for the Startup Type.
    5. Click OK to apply the changes and to close the SharePoint Timer Services Properties dialog box.
  3. In the Services dialog box, right-click SQL Server (SHAREPOINT), and then click Stop.
  4. Back up the Windows SharePoint Services database files in the %systemdrive%\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\data folder, and then copy the following files to a backup location:
    • STS_ServerName_1.mdf
    • STS_Config.mdf
    • STS_ServerName_1.mdf_log.ldf
    • STS_Config_log.ldf

    Notes

    • By default, the Windows SharePoint Services instances of the SQL Server Desktop Engine database files are installed in the %systemdrive%\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\data folder. However, you may have installed the database files in a different location.
    • If the original copies of these database files become corrupted or are overwritten, you must use the backup copies to reattach to the Windows SharePoint Services instance of SQL Server 2005. (See the "Step Seven: Reattach database files to the Windows SharePoint Services instance of SQL Server 2005" section.) To successfully reattach the backup copies to the database, you must copy the backup copies of these database files back to the %systemdrive%\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\data folder.
  5. Start the SQL Server (SHAREPOINT) service.
    1. Click Start, click Run, type Control admintools, and then click Services.
    2. Double-click SQL Server (SHAREPOINT) to open the Properties dialog box.
    3. On the General tab, click Start.
    4. Click Automatic for the Startup Type.
    5. Click OK to apply the changes.

Step Four: Detach the Windows SharePoint Services database from SQL Server 2005

When you detach a database, you remove it from the instance of the SQL Server Database Engine. However, you leave the database intact together with the data files and with the transaction log files. To detach the Windows SharePoint Services database, follow these steps:

  1. In SQL Server Management Studio Object Explorer, connect to the Windows SharePoint Services instance of the SQL Server Database Engine, and then expand the instance.
  2. To detach a database, you must have exclusive access to the database. If the database is being used, restrict access to a single user. To do this, follow these steps:
    1. Right-click the STS_Config database, and then point to Properties.
    2. In the Select a page pane, click Options.
    3. In the left pane, scroll down to the State options.
    4. Select Single from the list for the Restrict Access option.
    5. Click OK. A message box informs you that this action will close all connections to the database. To continue, click OK.
  3. Right-click the STS_Config database, point to Tasks, and then click Detach. The Detach Database dialog box appears.
  4. By default, the detach operation retains any out-of-date optimization statistics when you detach the database. To update the existing optimization statistics, click to select the Update Statistics check box.
  5. By default, the detach operation keeps any full-text catalogs that are associated with the database. To remove the catalogs, click to clear the Keep Full-Text Catalogs check box.
  6. The Status column displays the current database status as Ready or as Not Ready. If the status is Not Ready, the Message column displays hyperlinked information about the database. When a database is involved with replication, the Message column displays Database replicated. When a database has one or more active connections, the Message column displays the following:

    number_of_active_connections Active connection(s)

    Before you can detach the database, you must disconnect any active connections. To do this, click to select the Drop Connections check box. To obtain more information about a message, click the hyperlink.
  7. When you are ready to detach the database, click OK.
  8. Repeat steps b through g for the STS_ServerName_1 database.

    Note The newly detached database remains visible in the Databases node of Object Explorer until the view is refreshed. To update the view, click the View menu in the Object Explorer window, and then click Refresh.

Step Five: Uninstall SQL Server 2005

To uninstall SQL Server 2005, follow these steps:

  1. Click Start, click Run, type appwiz.cpl, and then click OK.
  2. In the list of Currently installed programs, click Microsoft SQL Server 2005, and then click Remove.
  3. On the Component Selection page, click SHAREPOINT: Database Engine under Select an instance.
  4. Under Remove SQL Server 2005 common components, select Workstation Components.
  5. Click Next.
  6. On the Confirmation page, click Finish.
  7. When the uninstall process is finished, click Add or Remove Programs in Control Panel, and then press F5 to update the list of installed programs.
  8. In the list of installed programs, select Microsoft SQL Server Native Client, and then click Remove.

Step Six: Install the release version of SQL Server 2005 Workgroup Edition

To install the release version of SQL Server 2005 Workgroup Edition, follow these steps:

  1. Insert Premium Technologies Disc 1 in the CD drive, and then click Install Microsoft SQL Server 2005 on the Autorun page. (You can also type drive:\Setup.exe at a command prompt to start the installation.)

    Note If Windows SBS 2003 R2 was preinstalled on the server, the OEM might have created a shortcut on the desktop to install Premium Technologies.
  2. On the End User License Agreement page, review the licensing agreement. To continue, accept the agreement.
  3. On the Installing Prerequisites page, SQL Server 2005 Setup installs the components that SQL Server Setup requires. When Setup has finished installing the required components, click Next.
  4. On the Welcome to the Microsoft SQL Server Installation Wizard page, click Next.
  5. On the System Configuration Check page, verify that you have no potential installation problems, and then click Next.
  6. If you are installing the first instance of SQL Server 2005, the Registration Information page appears. By default, Setup automatically enters the product key for you. Enter your Name and Company information, and then click Next.
  7. On the Feature Selection page, click the icon next to SQL Server Database Services, click Entire feature will be installed on local hard drive, expand SQL Server Database Services, and then make sure that all sub-features are included. Make sure that you include Full-Text Search.
  8. On the Feature Selection page, expand Client Components, click the icon next to Management Tools, and then click Entire feature will be installed on local hard drive.
  9. Make sure that Connectivity Tools and SQLXML Client Features are selected for installation, and then click Next.

    Note You may be unable to install the Client Components when you update the SQL Server Desktop Engine instance to SQL Server 2005. This behavior may occur if this is not the first instance of SQL Server 2005 that is installed on the server and if you did not install the Client Components together with the first SQL Server 2005 instance. If this is the case, SQL Server Setup displays a message that states that the Client Components have already been installed. To work around this issue, finish the Windows SharePoint Services instance of the SQL Server Desktop Engine migration, and then follow these steps:
    1. In Control Panel, click Add or Remove Programs.
    2. In Add or Remove Programs, click Microsoft SQL Server 2005, and then click Change.
    3. On the Component Selection page, click Workstation Components under SQL Server 2005 Common Components, and then click Next.
    4. Follow the instructions that appear on the screen until the Change or Remove Instance page appears.
    5. On the Change or Remove Instance page, click Change Installed Components.
    6. Under Client Components, click Management Tools, and then click Entire feature will be installed on local hard drive.
    7. Click Next to finish the wizard.
  10. On the Instance Name page, click Named instance.
  11. In the Named instance box, type SHAREPOINT.

    Note You must type the instance name in uppercase letters. If the instance name is not in uppercase letters, the migration to SQL Server 2005 Workgroup fails.
  12. On the Service Account page, click Use the built-in System account, and then click Local system for the account.
  13. On the Authentication Mode page, click Windows Authentication Mode.
  14. On the Collation Settings page, accept the default settings.
  15. When the Error and Usage Report Settings page appears, decide whether you want to automatically send error reports to Microsoft or to a corporate error-reporting server. You can also decide to send data about feature usage for SQL Server 2005 to Microsoft. Then, click Next.
  16. On the Ready to Install page, click Install.
  17. When SQL Server 2005 Setup prompts you to "Insert Disc 2," insert Premium Technologies Disc 2, and then click OK.
  18. On the Setup Progress page, click Next.
  19. On the Completing Microsoft SQL Server 2005 Setup page, click Finish.

Step Seven: Reattach database files to the Windows SharePoint Services instance of SQL Server 2005

To reattach the database files to the new Windows SharePoint Services instance of SQL Server 2005, follow these steps:

  1. In the Object Explorer of Microsoft SQL Server Management Studio, expand ServerName\SHAREPOINT (SQL Server 9.0.1399 - DomainName\administrator). DomainName is the name of the Windows SBS domain.
  2. Right-click Databases, and then click Attach.
  3. On the Attach Databases page, click Add.
  4. Locate the %systemdrive%\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\data folder, click the STS_ServerName_1.mdf file, and then click OK.
  5. On the Attach Databases page, click OK. Object Explorer in Microsoft SQL Server Management Studio appears.
  6. Repeat steps b through e to attach the STS_Config.mdf database file.
  7. To restart the Windows SharePoint Timer service, click Start, click Programs, click Administrative Tools, click Services.
  8. Right-click SharePoint Timer Service, and then click Properties.
  9. On the General tab, select Automatic for the Startup Type, click Start to start the service, and then click OK to close the SharePoint Timer Service Properties dialog box.
  10. Close Services.
  11. To restart the http://companyweb Web site, follow these steps:
    1. Click Start, click Server Management, and then double-click Advanced Management.
    2. Double-click Internet Information Services, double-click ServerName(local computer), and then double-click Websites.
    3. Right-click companyweb, and then click Start.

Step Eight: Configure permissions for the Windows SharePoint Services database

To configure permissions for the new Windows SharePoint Services instance of SQL Server 2005, follow these steps:

  1. Open SQL Server Management Studio, click Start, click Programs, click Microsoft SQL Server 2005, and then click SQL Server Management Studio.
  2. On the Connect to Server page, select Database Engine for Server type, select ServerName\SHAREPOINT for Server name, and then click Connect.
  3. In the Object Explorer pane, expand ServerName\SHAREPOINT (SQL Server 9.0.1399 - DomainName\administrator). DomainName is the name of the Windows SBS domain.
  4. Double-click Security, right-click Logins, and then click New Login.
  5. Type NT Authority\Network Service for Login Name, and then click OK.

    Notes
    • If you are running the Dutch, Portuguese (Brazil), or Swedish versions of Windows SBS 2003 R2 Premium Edition, you must enter the translation of the NT Authority\Network Service account name.
    • Do not click Search after you type NT Authority\Network Service, because SQL Server Management Studio will not find the NT Authority\Network Service account. If you have incorrectly entered the service name, you receive an error message after you click OK.
  6. Repeat steps d and e to add the DomainName\SBS SP Admins group as a New Login.
  7. In Object Explorer, expand Logins, and then double-click the NT Authority\Network Service account.
  8. In Login Properties - NT Authority\Network Service, click Server Roles in the Select a page pane.
  9. In the Server roles pane, click to select the dbcreator and securityadmin roles, and then click OK.

Step Nine: Turn on full-text search in Windows SharePoint Services

To turn on full-text search in Windows SharePoint Services, follow these steps:

  1. Click Start, click Run, type Control admintools, and then click SharePoint Central Administration.
  2. In Component Configuration, click Configure full-text search.

    Note If you receive the following error message, make sure that the SQL Server (SHAREPOINT) service is started:

    Configuration database can’t be found

    To do this, click Run, type Control admintools, and then click Services. If the service is not started, right-click the service name, and then click Start.

  3. Click OK to exit Services.
  4. Click to select the Enable full-text search and index check box, and then click OK.



Additional query words: R2 Recall SQL

Keywords: kbinfo kbtshoot kbhowtomaster KB924000



Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.


Retrieved from ‘https://www.betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive/924000&oldid=223382’
the Creative Commons 3.0 ShareAlike (except the Microsoft KB Archive).
Powered by MediaWiki