Upgrade Question: PS 2003 --> PS 2007

[Russ]

Hi there,

I have performed a test migration/upgrade from Project Server 2003 to
Project Server 2007(on the same computer). I ran into a problem with the
linking between projects and their associated workspaces after the upgrade.
Basically, when I open an issue from a project workspace, I can navigate to
the linked task without any problem; however, if I open the task in Project
Server, I cannot navigate to the linked issue (I get an unknown error).

This brings me to a question I have about the whole upgrade/migration
process. According to the Project Server 2007 migration guide, I am supposed
to update the sharepoint connection settings in Project Server 2007 to point
to the web site collection under which all of my upgraded workspaces reside
(after migrating global data). See this excerpt taken from the migration doc
(page 94):

‘In the Site URL section, make sure that the Default Web Application and
Site URL points to the SharePoint site with the upgraded workspaces. If this
value is not set, the link from projects, tasks, and assignments to issues,
risks, and documents will not be fixed correctly when projects are migrated
and published.’

I skipped this step in my initial upgrade/migration test for the reason
described below .

This is the problem. In project Server 2003, there is no site collection
under which the workspaces are created. The project workspaces are site
collections themselves, which have been created under a managed path. If I
open up the sharepoint connection settings in Project Server 2007, and try to
set the url to point to the managed path, I get an error (The error says that
there is no site collection at ‘http://myserver/sites’)

Any ideas?

 

[winzigm]

Hi there,

I have performed a test migration/upgrade from Project Server 2003 to
Project Server 2007(on the same computer). I ran into a problem with the
linking between projects and their associated workspaces after the upgrade.
Basically, when I open an issue from a project workspace, I can navigate to
the linked task without any problem; however, if I open the task in Project
Server, I cannot navigate to the linked issue (I get an unknown error).

This brings me to a question I have about the whole upgrade/migration
process. According to the Project Server 2007 migration guide, I am supposed
to update the sharepoint connection settings in Project Server 2007 to point
to the web site collection under which all of my upgraded workspaces reside
(after migrating global data). See this excerpt taken from the migration doc
(page 94):

'In the Site URL section, make sure that the Default Web Application and
Site URL points to the SharePoint site with the upgraded workspaces. If this
value is not set, the link from projects, tasks, and assignments to issues,
risks, and documents will not be fixed correctly when projects are migrated
and published.'

I skipped this step in my initial upgrade/migration test for the reason
described below .

This is the problem. In project Server 2003, there is no site collection
under which the workspaces are created. The project workspaces are site
collections themselves, which have been created under a managed path. If I
open up the sharepoint connection settings in Project Server 2007, and try to
set the url to point to the managed path, I get an error (The error says that
there is no site collection at 'http://myserver/sites')

Any ideas?

I have same idea,

I planing that we create same tool which will be able move all old
Project workslaces under PWA site collection, but I still waiting for
first order.

in case that you need move few sites you can use STSADM

stsadm -o export
(backup old site)

stsadm -o import (restore content under PWA )

most likely relationship between tasks and documents will be broken!!