Performing a gradual migration: Project Server 2003 with Windows SharePoint Services 2.0 (on a different computer)

  • Article

This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.

 

Topic Last Modified: 2016-11-14

This article describes performing a gradual migration to Microsoft Office Project Server 2007 in which Microsoft Office Project Server 2003 is using Windows SharePoint Services 2.0 and resides on a different computer than the one you are migrating to.

Gradual migration: Project Server 2003 with Windows SharePoint Services 2.0 (on a different computer)

Warning

This is a very complex option involving several manual steps. Depending on the way Windows SharePoint Services 2.0 is configured, you may face additional complications. We recommend that you do not use this deployment option. Consider other migration options listed in IT deployment options for migration to Project Server 2007.

High-level steps for this option are given below.

Gradual migration with SharePoint Services

  1. Install Office Project Server 2007 on the new computer. (For more information, see Deploy Project Server 2007 to a server farm environment.) After installation, also provision a new Project Web Access site and make sure the new installation works correctly.

  2. Create a new "Windows SharePoint Services 2.0 Temporary Content Database" on the Windows SharePoint Services 2.0 virtual server and move the to-be-gradually-migrated project workspaces to this content database.

  3. Run the Windows SharePoint Services pre-upgrade scanning tool (PreScan.exe) on the Windows SharePoint Services 2.0 SP2 farm. (For more information, see Upgrading to Windows SharePoint Services 3.0.) This step prepares the Windows SharePoint Services 2.0 content database to be upgraded to Windows SharePoint Services 3.0.

  4. Attach a copy of the Windows SharePoint Services 2.0 Temporary Content Database to the Office Project Server 2007 farm. Once it is attached, the Windows SharePoint Services 2.0 sites in the content database are upgraded to Windows SharePoint Services 3.0. We recommend that you upgrade a copy of the Windows SharePoint Services 2.0 content database — not the original content database. At the end of this step, all the Project 2003 workspaces are upgraded to Windows SharePoint Services 3.0, but they are not linked to the projects.

    1. Open a command prompt and navigate to the location of the Stsadm.exe file (the default location is <Drive>:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\bin).

    2. Run the following Stsadm command to attach a copy of your Windows SharePoint Services 2.0 content database to Windows SharePoint Services 3.0 and upgrade it.

      stsadm.exe -o addcontentdb -url http://<server>:<port> -databasename <WSS v2.0 content database> -databaseserver <database server name>

      For example:

      stsadm.exe -o addcontentdb -url http://MyServer:80 -databasename WSS_V2_ContentDB -databaseserver Sample

    3. After running the Stsadm.exe command, you can track the progress of the upgrade by looking at the upgrade.log file in the ULS log directory (the default location is c:\program files\common files\Microsoft shared\web server extensions\12\logs\upgrade.log). The upgrade process has finished running on a given content database when the following line is included in the log:

      [SPManager] [DEBUG] [<Date> <Time>]: Using cached [SPContentDatabase Name=<DB NAME> Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.

    4. Navigate to the upgraded project workspaces to verify that the upgrade process has succeeded.

    5. If the upgrade process has failed for any reason (as indicated in the log), Windows SharePoint Services upgrade can be restarted. To restart the upgrade process, run the command Stsadm.exe -o upgrade and look at the logs to view the progress. The upgrade process has finished when the command prompt returns Operation completed successfully.

  5. Move the Windows SharePoint Services 3.0 sites from the "Windows SharePoint Services 3.0 Temporary Content Database" to the "Project Web Access Content Database" (or any other content database that is the final destination for these upgraded sites).

    1. Open a command prompt and navigate to the location of the Stsadm.exe (the default location is <Drive>:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\bin).

    2. Run the following Stsadm command to back up a project workspace. Repeat this for all SharePoint sites to be moved.

      Stsadm –o backup –url <SiteUrl> -filename <backupFileName>  (Stsadm –o deletesite –url <SiteUrl>

    3. Go to the SharePoint Central Administration Web site, and edit the MaxSites for the "Windows SharePoint Services 3.0 Temporary Content Database" such that no new sites can be created in it. Do this on every content database except the one to which you want to restore the project workspaces. This action forces creation of new sites into the content database that you want.

    4. Run the following Stsadm command to restore the project workspaces to the content database you chose in the previous step. Repeat this for all backed up project workspaces to be moved. Restore it to the site URL that is the final destination for these upgraded SharePoint sites. The illustration above assumes that the Project Web Access content database is the final destination.

      Stsadm –o restore –url <SiteUrl> -filename <backupFileName> Stsadm –o deletecontentDB –url <WebAppUrl> -databaseServer <SQLServerName> -databasename <NewContentDB>

    5. Run the following Stsadm command to delete the Windows SharePoint Services 3.0 Temporary Content Database:

      Stsadm –o deletecontentDB –url <WebAppUrl> -databaseServer <SQLServerName> -databasename <NewContentDB>

  6. Migrate and publish projects: As projects are published, the links between projects ,tasks, assignments and the Windows SharePoint Services items are fixed.

Repeat Steps 2 through 6 for every batch of projects or workspaces that you want gradually migrate.

Download this book

This topic is included in the following downloadable book for easier reading and printing:

See the full list of available books at Downloadable content for Project Server 2007.