Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Upgrading project workspaces from Project Server 2003

Project Server 2007

Updated: May 7, 2009

Updated: 2009-05-07

In this article:

If you do not have any Windows SharePoint Services integration with Microsoft Office Project Server 2003, you can ignore this article. If you do, we recommend that you upgrade the relevant project workspaces before migrating the projects so that when the projects are migrated and published, the links between the projects and Windows SharePoint Services are fixed. The steps you need to follow depend on the option you chose for migration in IT deployment options for migration to Project Server 2007.

Full migration with Windows SharePoint Services 2.0 (on the same computer)

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 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 force an upgrade.

    1. stsadm –o upgrade

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

      Upgrade will be complete when the command prompt returns Operation completed successfully.

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

Gradual migration with Windows SharePoint Services 2.0 (on the same computer)

In this case, Windows SharePoint Services 2.0 will be installed side-by-side with Windows SharePoint Services 3.0, but none of the workspaces will have been upgraded yet. Using the SharePoint Central Administration Web site, select the workspaces corresponding to the projects you want migrated, and upgrade them to Windows SharePoint Services 3.0.

Full migration with Windows SharePoint Services 2.0 (to a different computer)

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. Install Office Project Server 2007 on the new computer. For more information, seeDeploy Project Server 2007 to a server farm environment.

  2. Run the Windows SharePoint Services pre-upgrade scanning tool on the Windows SharePoint Services 2.0 SP2 farm. (For more information see Upgrading to Windows SharePoint Services 3.0). This process prepares the Windows SharePoint Services 2.0 content database for upgrade to Windows SharePoint Services 3.0.

  3. Attach a copy of all the Windows SharePoint Services 2.0 content databases to the Microsoft 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 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 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.) Upgrade 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 upgrade, run the command Stsadm.exe -o upgrade and look at the logs to view the progress. Upgrade has finished when the command prompt returns Operation completed successfully.

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

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.

See Also

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.