• Article

Upgrade project workspace data from Project Server 2003

 

Applies to: Project Server 2010

Topic Last Modified: 2010-12-17

Important

This procedure is optional and only needs to be performed if you want to migrate your Windows SharePoint Services 2.0 project workspace sites and content.

This article describes how to migrate your Windows SharePoint Services 2.0 project workspace data to Windows SharePoint Services 3.0. This part of the data migration process from Project Server 2003 to Project Server 2007 is only necessary if you want to migrate your project workspace data. There are two ways that this can be done:

  • If you do an in-place upgrade from Windows SharePoint Services 2.0 to Windows SharePoint Services 3.0, you can run an Stsadm command to make your workspaces active.

  • If you are migrating to a different computer, you can back up your Windows SharePoint Services 2.0 database to restore them to the Windows SharePoint Services 3.0 computer to upgrade it.

Migrating Windows SharePoint Services 2.0 project workspace data to Windows SharePoint Services 3.0 by doing an in-place upgrade

In this case, all the Windows SharePoint Services 2.0 workspaces would have already been upgraded to Windows SharePoint Services 3.0 when you chose the in-place upgrade option when installing Windows SharePoint Services 3.0. But the upgraded project workspaces may not be active. Do the following to make them active.

  1. Open a Command Prompt window and navigate to the location of 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 force an upgrade.

    stsadm -o upgrade

    To check progress, you can look at the upgrade.log file: <drive:>:\program files\common files\Microsoft shared\Web server extensions\12\logs\upgrade.log

    The upgrade process will be complete when the command prompt returns Operation completed successfully.

  3. Browse to the upgraded project workspaces and ensure that they work correctly.

Migrating Windows SharePoint Services 2.0 project workspace data to Windows SharePoint Services 3.0 by using a backup and restore approach

If you installed Office Project Server 2007 on a clean computer and if you want to migrate Windows SharePoint Services data, you will be using the content database backup-and-restore approach. It involves the following steps:

Full migration with Windows SharePoint Services

  1. Run the Windows SharePoint Services pre-upgrade scanning tool on the Windows SharePoint Services 2.0 SP2 farm. if it has not already been done (as noted in the pre-migration tasks). This process prepares the Windows SharePoint Services 2.0 content database for upgrade to Windows SharePoint Services 3.0.

  2. Attach a copy of all the Windows SharePoint Services 2.0 content databases to the Office Project Server 2007 farm: Once attached, the Windows SharePoint Services 2.0 sites in the content database are upgraded to Windows SharePoint Services 3.0. We strongly recommend that a copy of the Windows SharePoint Services 2.0 content database be upgraded — not the original content database. At the end of this step, all the Project Server 2003 workspaces will have been upgraded to Windows SharePoint Services 3.0, but they will not yet be linked to the projects.

    1. Open a Command Prompt window and navigate to the location of 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 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 <DB Server name>

      For example:

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

    3. After running Stsadm.exe, you can track the progress of the upgrade by looking at upgrade.log 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 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 upgrade has succeeded.

    5. If upgrade fails for any reason (as indicated in the log), the Windows SharePoint Services upgrade process 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.

When the migration tool saves and publishes projects later in the migration process, the links between projects, tasks, and assignments and the SharePoint Foundation items will be fixed.