In this document:

 
 

 

 
 

Migrate a SHAREPOINT Instance of SQL Server 2000

The steps to migrate the SHAREPOINT SQL Server 2000 instance are nearly identical to the steps to migrate the SHAREPOINT WMSDE instance to SQL Server 2005 Workgroup Edition. Use the following procedure to migrate the SHAREPOINT SQL Server 2000 instance to SQL Server 2005 Workgroup Edition.

To migrate the SHAREPOINT SQL Server 2000 instance to SQL Server 2005 Workgroup Edition

Overview of steps:
  1. Complete the procedure "To prepare the http://companyweb Web site," earlier in this document (now below at step one). Note that you must uninstall SQL Server 2000 by using Add or Remove Programs, not WMSDE.

    Important
    Before you uninstall SQL Server 2000, review Article 920899 in the Microsoft KnowledgeBase (http://go.microsoft.com/fwlink/?LinkID=68562). The article addresses known issues with uninstalling SQL Server 2000 with Service Pack 4.

     

     

  2. Complete the procedure "To create the SQL Server 2005 Workgroup Edition SHAREPOINT instance," earlier in this document (now below at step two), to complete a new installation of SQL Server 2005 for Windows SharePoint Services.

  3. Complete the procedure "To configure permissions for the new SHAREPOINT instance of SQL Server 2005" (now below at step three)

  4. If you are installing the Dutch, Swedish, or Portuguese (Brazil) versions of Windows SBS 2003 R2 Premium Edition, complete the procedure "Dutch, Portuguese (Brazil), or Swedish installations only," earlier in this document (now below at step four). Otherwise, skip this step.

  5. Complete the procedure "To attach the database files to the new SHAREPOINT instance of SQL Server 2005." (now below at step five)

  6. If you enabled full-text searching for Windows SharePoint Services when you upgraded the SHAREPOINT WMSDE to SQL Server 2000, you do not have to enable it again after migrating to SQL Server 2005. If you did not enable full-text searching previously, follow the steps provided in the procedure "To turn on full-text search in Windows SharePoint Services," earlier in this document. (now below at step six)

Important
You must be logged on to the Administrator account or another account that is a member of the Domain Admins security group to install SQL Server 2005.

STEP NUMBER ONE:

Prepare CompanyWeb

Before you begin the migration, you must prepare the http://companyweb Web site.

To prepare the http://companyweb Web site
  1. Stop the http://companyweb Web site. To do so, click Start, and then click Server Management. In the Server Management console pane, double-click Advanced Management, double-click Internet Information Services, double-click ServerName (local computer), and then double-click Websites, where ServerName is the name of your server computer. Right-click companyweb, and then click Stop.

  2. Stop the SharePoint Timer Service. To do so, click Start, point to Administrative Tools, and then click Services. Double-click SharePoint Timer Service to open the Properties dialog box. On the General tab, click Stop. Choose Manual for the Startup Type. Click OK to apply the changes and to close the SharePoint Timer Services Properties dialog. Leave Services open for the next step.

  3. Stop the MSSQL$SHAREPOINT service. While still in Services, right-click MSSQL$SHAREPOINT, and then click Stop.

  4. Back up the Windows SharePoint Services database files. To do so, browse to %SystemDrive%\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\data, and then copy the following files to a backup location of your choosing:

    • STS_ServerName_1.mdf

    • STS_Config.mdf

    • STS_ServerName_1.mdf_log.LDF

    • STS_Config_log.LDF

    where ServerName is the name of your server.

    Note
    By default, the SHAREPOINT WMSDE database files are installed in %SystemDrive%\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\data. However, you may have installed the database files in a different location.

    <<<<To prepare for the next step, flip ISA 2004 to log to flat file loggings, rather than MSDE  to ensure that your network will not go into lockdown mode or change the ISA so that it won't go into lockdown mode >>>>

    In ISA on the monitoring, on the right hand side, click into all three logging and make sure that they are logging to file

    Or change the setting so that the ISA server won't go into lockdown mode as documented here:

    http://www.microsoft.com/technet/isa/2004/plan/disablelockdownonlogfailure.mspx

     

    Remove the SHAREPOINT WMSDE instance. Click Start, point to Control Panel, and then click Add or Remove Programs. Select Microsoft SQL Server Desktop Engine (Sharepoint), and then click Remove. Click Yes to confirm that you want to delete MSDE (SharePoint). You must restart the computer before you continue with the following procedures.

    <<<For SQL 2000, what you want to remove is SQL 2000, not MSDE... reboot the server after this step>>>>

    It doesn't matter if you say "yes" or "no" when prompted for removing unneeded files.

    Then put the msde files that SQL just removed back AND check the shared memory checkbox:

     

    Note
    If the original copies of these files become corrupted or overwritten, you need to use the backup copies to reattach to the SHAREPOINT instance of SQL Server 2005 that you create later in this document. In order to successfully reattach the backup copies to the database, you must copy the backup copies of the above database files back to %SystemDrive%\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\data.

     

    Important
    Before you uninstall SQL Server 2000, review Article 920899 in the Microsoft KnowledgeBase (http://go.microsoft.com/fwlink/?LinkID=68562). The article addresses known issues with uninstalling SQL Server 2000 with Service Pack 4.

     

    STEP ONE FOR FIXING MSDE'S - PUT BACK THE FILES

    http://support.microsoft.com/default.aspx?scid=kb;en-us;918767

    The instructions that work are as follows:

    In the C:\Program Files\Microsoft SQL Server SP4\WMSDE\Setup folder find the sqlrun.cab file and double click on it, find the two MSXML files and put them back in the needed folders:

    Double click on the SqlRun.cab file and find the two MSXMLSQL files inside the cab file and extract them:

    Double click and click on Extract.  Dump it into a folder "My docs" will work just fine, just as long as it's a place you can remember to find.

    Once you get them into "My documents", strip off the excess file names

    MSXMLSql.dll.CD093EA8_A990_4429_AF6A_29A30691991E should be renamed to MSXMLSql.dll (just strip off the excess characters on the end) and moved to the C:\Program Files\Microsoft SQL Server\80\Shared folder like this:

    The file MSXMLSQL.RLL.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC should be renamed to MSXMLSQL.RLL (just strip off the excess characters on the end) and copied to the C:\Program Files\Microsoft SQL Server\80\Shared\Resources\1033 file like this:

    Set up the folders if these folders are not in place

    (the rest of this section is merely the text of the KB article, you can now skip to the "Shared Memory" checkbox section))

    SYMPTOMS

    Consider the following scenario. You remove an instance of one of the following products:
    Microsoft SQL Server 2000 Desktop Engine (also known as MSDE 2000) Service Pack 4 (SP4)
    SQL Server 2000 Desktop Engine (Windows) SP4
    Microsoft SQL Server 2000 SP4
    You then run programs that use other instances of MSDE 2000 SP4, SQL Server 2000 Desktop Engine (Windows) SP4, or SQL Server 2000 SP4. In this scenario, these programs may fail. Then, the program in question generates the following error message:
    Failed to load msxmlsql.dll
    Note This error message might also be logged in the program's log file.

    The following is a typical scenario in which this problem occurs:
    Microsoft Windows Small Business Server 2003 SP1 is running on the computer.
    Microsoft Windows SharePoint Services is running on the computer, and the computer connects to its own instance of SQL Server 2000 Desktop Engine (Windows) SP4.
    Microsoft Windows Server Update Services (WSUS) is installed on the computer, and the computer connects to its own instance of SQL Server 2000 Desktop Engine (Windows) SP4.
    After you remove the instance of SQL Server 2000 Desktop Engine (Windows) SP4 that Windows SharePoint Services uses, WSUS cannot run on the computer. If SQL Server 2000 SP4 is installed on the computer that is running Windows Small Business Server 2003 SP1 and you remove SQL Server 2000 SP4, WSUS cannot run on the computer.

    CAUSE

    The problem occurs because of the following conditions:
    The Msxmlsql.dll file is deleted from the %programfiles%\Microsoft SQL Server\80\Shared folder when you remove the instance of MSDE 2000 SP4, the instance of SQL Server 2000 Desktop Engine (Windows) SP4, or the instance of SQL Server 2000 SP4.
    The Msxmlsql.rll file is deleted from the %programfiles%\Microsoft SQL Server\80\Shared\Resources\1033 folder when you remove the instance of MSDE 2000 SP4, the instance of SQL Server 2000 Desktop Engine (Windows) SP4, or the instance of SQL Server 2000 SP4.
    In some cases, the %programfiles%\Microsoft SQL Server\80\Shared folder will be deleted after you remove the instance of MSDE 2000 SP4, the instance of SQL Server 2000 Desktop Engine (Windows) SP4, or the instance of SQL Server 2000 SP4.

    Therefore, programs that use the other instances of MSDE 2000 SP4, SQL Server 2000 Desktop Engine (Windows) SP4, or SQL Server 2000 SP4 on the computer cannot run if the programs depend on the Msxmlsql.dll and Msxmlsql.rll files.

    WORKAROUND

    To work around this problem, restore the Msxmlsql.dll file to the %programfiles%\Microsoft SQL Server\80\Shared folder. To do this, use one of the following methods.

    Note If the %programfiles%\Microsoft SQL Server\80\Shared folder is deleted from the computer, you have to create the Shared\Resources\1033 folder structure in %programfiles%\Microsoft SQL Server\80, and then use one of the following methods.

    Method 1

    Restore the Msxmlsql.dll file from the MSDE 2000 SP4 installation package. To do this, follow these steps:
    1. Extract the MSDE 2000 SP4 installation package to a folder. Assume that the package is extracted to the default folder (C:\SQL2KSP4).
    2. Run the following command at a command prompt:

    expand “C:\SQL2KSP4\MSDE\SETUP\SQLRUN.CAB” –F:MSXMLSQL.DLL* “%programfiles%\Microsoft SQL Server\80\shared”
    rename “%programfiles%\Microsoft SQL Server\80\shared\ MSXMLSql.dll.CD093EA8_A990_4429_AF6A_29A30691991E” MSXMLSQL.DLL
    expand “C:\SQL2KSP4\MSDE\SETUP\SQLRUN.CAB” –F:MSXMLSQL.RLL* “%programfiles%\Microsoft SQL Server\80\shared\Resources\1033\”
    rename “%programfiles%\Microsoft SQL Server\80\shared\Resources\1033\ MSXMLSQL.RLL.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC” MSXMLSQL.RLL

    Method 2

    Restore the Msxmlsql.dll file from the SQL Server 2000 SP4 installation package. To do this, follow these steps:
    1. Extract the SQL Server 2000 SP4 installation package to a folder. Assume that the package is extracted to the default folder (C:\SQL2KSP4).
    2. Copy the Msxmlsql.dll file in the C:\SQL2KSP4\x86\binn folder to the %programfiles%\Microsoft SQL Server\80\shared folder.
    3. Copy the Msxmlsql.rll file in the C:\SQL2KSP4\x86\binn folder to the %programfiles%\Microsoft SQL Server\80\shared\Resources\1033 folder.
    If you are running Windows Small Business Server 2003 SP1, you can restore the Msxmlsql.dll file and the Msxmlsql.rll file by using Method 1. The SqlRun.cab file is located in the %programfiles%\Microsoft SQL Server SP4\WMSDE\SETUP folder.

     

    STEP TWO FOR FIXING THE MSDE'S - CHECK THE SHARED MEMORY BOX

    http://support.microsoft.com/default.aspx?scid=kb;en-us;920899

    To do this, follow these steps:
    1. Click Start, click Run, type cliconfg, and then click OK.

    2. In the Client Network Utility dialog box, click to turn on the Enable shared memory protocol check box, and then click OK.

    3. Restart the computer.

     

     

STEP NUMBER TWO:

To create the SQL Server 2005 Workgroup Edition SHAREPOINT instance
  1. From the Autorun page of Premium Technologies Disc 1 (D:\Setup.exe, where D is the letter of your CD drive), click Install Microsoft SQL Server 2005.

    Note
    If Windows SBS 2003 R2 was preinstalled on your server, your original equipment manufacturer (OEM) might have created a shortcut on the desktop for installing SQL Server 2005.

     

     

  2. On the End User License Agreement page, review the licensing agreement. To continue, you must accept the agreement.

  3. On the Installing Prerequisites page click Install. SQL Server 2005 Setup installs the components that are required for SQL Server setup. When it finishes installing them, 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, then click Next.

  6. If this is the first instance of SQL Server 2005 that you are installing, 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 SQL Server Database Services and then click Entire feature will be installed on local hard drive. Expand SQL Server Database Services and ensure that all sub-features, including Full-Text Search, are set to install.

  8. While still on the Feature Selection page, expand Client Components, click Management Tools, and then click Entire feature will be installed on local hard drive. By default, Setup also selects Connectivity Components and SQLXML Client Features for installation. Click Next.

    Important
    If this is not the first instance of SQL Server 2005 that is installed on the server, and you did not install the Client Components with your first SQL Server 2005 instance, you may be unable to install Client Components when migrating the WMSDE SHAREPOINT instance to full SQL Server 2005. SQL Setup may prompt you with a message that the Client Components have already been installed.

     

    To work around this issue, complete the WMSDE SHAREPOINT migration, and then click Start. Point to Control Panel, and then click Add or Remove Programs. In Add or Remove Programs, click Microsoft SQL Server 2005, and then click Change. In Component Selection, click Workstation Components under SQL Server 2005 Common Components, and then click Next. Follow the SQL Setup Wizard until the Change or Remove Instance page. Click Change Installed Components. Under Client Components, click Management Tools, and then click Entire feature will be installed on local hard drive. Click Next to continue, and then complete the wizard.

     

     

  9. On the Instance Name page, click Named instance. In the Named instance box, type SHAREPOINT.

    Caution
    You must type the instance name that is shown, in uppercase letters. If the instance name is not in uppercase letters, the migration to SQL Server 2005 Workgroup will fail.

     

     

  10. On the Service Account page, click Use the built-in System account, and then click Local system for the account. Click Next.

  11. On the Authentication Mode page, choose Windows Authentication Mode. Click Next.

  12. On the Collation Settings page, accept the default of Dictionary order, case-insensitive, for use with 1252 Character Set for SQL collations (used for compatibility with previous versions of SQL Server). Click Next.

  13. When the Error and Usage Report Settings page appears, you can choose to automatically send error reports to Microsoft or to your corporate error-reporting server. You can also choose to send data about feature usage for SQL Server 2005 to Microsoft. Click Next.

  14. On the Ready to Install page, click Install.

  15. When SQL Server 2005 Setup prompts you to "Please insert Disc 2," insert Premium Technologies Disc 2, and then click OK.

  16. (Please note if you are installing these by copying the cdroms up to the server and installing from there, the end of "disk 1" will "bomb out", just browse to disk 2 location and restart the setup.exe from there. Select the client components as you were instructed earlier.
  17. Click Next when that button becomes available on the Setup Progress page.

  18. On the Completing Microsoft SQL Server 2005 Setup page, click Finish.

STEP NUMBER THREE

To configure permissions for the new SHAREPOINT instance of SQL Server 2005
  1. Open SQL Server Management Studio. Click Start, point to All Programs, point to Microsoft SQL Server 2005 and then click SQL Server Management Studio.

  2. On the Connect to Server page, ensure that Server type: is set to Database Engine and that Server name: is set to ServerName\SHAREPOINT, where ServerName is the name of your server. Click Connect.

  3. In the Object Explorer pane, expand ServerName\SHAREPOINT (SQL Server 9.0.1399 - DomainName\administrator), where DomainName is the name of your Windows SBS domain.

  4. Double-click Security, right-click Logins, and then click New Login.

  5. In Login name, type NT Authority\Network Service, and then click OK.

    Important
    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.

     

     

    Note
    Do not click Search after typing 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 4 and 5 to add the DomainName\SBS SP Admins group as a new login.

  7. In the Object Explorer pane, expand Logins, and then double-click the NT Authority\Network Service account.

  8. On the Login Properties page for NT Authority\Network Service, under Select a page, click Server Roles.

  9. Under Server roles, select the dbcreator and securityadmin roles. Click OK.

  10. Keep Microsoft SQL Server Management Studio open for the next procedure.

MARINA SECTIONS - Important
If you are running the Dutch, Portuguese (Brazil), or Swedish versions of Windows SBS 2003 R2 Premium Edition, you need to complete the following procedure in order to set the default full-text language before you finish attaching the databases to the new SHAREPOINT SQL Server 2005 instance. If you are not running the Dutch, Portuguese (Brazil), or Swedish versions of Windows SBS 2003 R2 Premium Edition, skip to the procedure "To attach the database files to the new SHAREPOINT instance of SQL Server 2005."

 

 

STEP FOUR - MARINA SECTIONS

Dutch, Portuguese (Brazil), or Swedish installations only
  1. While you are still in Microsoft SQL Server Management Studio, right-click ServerName\SHAREPOINT (SQL Server 9.0.1399 - DomainName\administrator), where DomainName is the name of your Windows SBS domain, and then click Properties.

  2. In the Server Properties page, under Select a page, click Advanced.

  3. Under Miscellaneous advanced properties, locate Default Full-Text Language. Highlight the current value and replace it with the language code that corresponds to your language. The language code for Dutch is 1043. For Swedish, it is 1053. For Neutral, it is 0. For Portuguese (Brazil), use Neutral because there is no language code for Portuguese (Brazil).

  4. Click OK.

  5. You are now ready to continue with the next procedure and attach the database files to the new SHAREPOINT instance of SQL Server 2005.

STEP FIVE

 

To attach the database files to the new SHAREPOINT instance of SQL Server 2005
  1. While still in Microsoft SQL Server Management Studio, in Object Explorer , expand ServerName\SHAREPOINT (SQL Server 9.0.1399 - DomainName\administrator), where DomainName is the name of your Windows SBS domain.

  2. Right-click Databases, and then click Attach.

  3. On the Attach Databases page, click Add.

  4. Browse to %SystemDrive%\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\data, select STS_ServerName_1.mdf and then click OK.

  5. On the Attach Databases page, click OK. The action finishes and Object Explorer in Microsoft SQL Server Management Studio appears.

  6. Repeat step 2 through 5 to attach the STS_Config.mdf database file.

  7. Restart the Windows SharePoint Timer Service by clicking Start, pointing to Administrative Tools, and then clicking Services. Right-click SharePoint Timer Service, and then click Properties. 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.

  8. Close Services.

  9. Restart http://companyweb by clicking Start and then clicking Server Management. In the Server Management console, double-click Advanced Management, double-click Internet Information Services, double-click ServerName (local computer), and then double-click Websites. Right-click companyweb, and then click Start.

STEP SIX

To turn on full-text search in Windows SharePoint Services
  1. Click Start, point to Administrative Tools, and then click SharePoint Central Administration.

  2. In Component Configuration, click Configure full-text search.

    Note
    If you encounter the error message, “Configuration database can’t be found,” ensure that the SQL Server (SHAREPOINT) service is started. To do so, click Start, point to Administrative Tools, and then click Services. If the service is not started, right-click the service name, and then click Start. Click OK to exit Services.

     

     

  3. Select the Enable full-text search and index component check box, and then click OK.