upgrade prj wrkspaces from PS2003 to 2007

[Jennpenn07]

Hello, I am in the middle of migrating from PS2003 to PS2007. I have
successfully migrated all global data. I made a mistake and some of the
projects migrated too and are in the draft DB. I know that I need to upgrade
the worspaces bf migrating the projects so they link correctly when the
projects publish.

Does it matter that the projects have migrated already to the draft database?
Also this article confused me :
http://technet.microsoft.com/en-us/library/cc197564.aspx.
I dont understand what perameters are needed for the stsadm cmd. I assume
that -url wants http://ps2007server:port, -databasename wants ps2003 content
database and -databaseserver wants the 2003dbserver.
is this correct?

 

[Nach]

The links actually happen when you publish the projects. So I wouldn't worry
if the Projects are in the Draft DB and not published yet. You should do the
Database upgrade for sharepoint DB and then run the migration tool to publish
all projects.

The STSADM command is (Assuming you have a copy of 2003 Sharepoint database
in the new sql server)--
stsadm.exe -o addcontentdb -url "http://server:80" -databasename WSS2003
-databaseserver 2007sqlservername

Thanks
Nach

 

[Jennpenn07]

That helps, thank you.

The links actually happen when you publish the projects. So I wouldn't worry
if the Projects are in the Draft DB and not published yet. You should do the
Database upgrade for sharepoint DB and then run the migration tool to publish
all projects.

The STSADM command is (Assuming you have a copy of 2003 Sharepoint database
in the new sql server)--
stsadm.exe -o addcontentdb -url "http://server:80" -databasename WSS2003
-databaseserver 2007sqlservername

Thanks
Nach

 

[Jennpenn07]

ok i tried to run the stsadm as you suggested, but I get an error telling me
that the 2003sharepoint db must be empty. Should the -url perameter contain
the url for 2003 or 2007?

 

[Nach]

Hi,
I have never seen that error before. But that is the command I usually use.
The URL is that of PWA 2007.

Thanks
Nach

 

[Jennpenn07]

After searching the web i found one person that says he recieved this error
becaues he forgot to run the prescan tool. I am guilty of this too, so I
tried to run the tool but now that will not work either.

I try prescan.exe /v http://2003server:80 and I've tried the PWA url. The
cmd prompt returns an error just saying "error in the prescan tool, see log
fil" but there is no log file in the specified path.

 

[Nach]

Hi,

Lookslike you either you don't have all the steps for migration with you or
you are not following them in sequence. These are the steps that I have and I
hope it helps you --

Steps to follow after installing Project Server 2007

1.Create a backup of the Project Web Access databases (all four fresh
databases).
2.Backup Sharepoint Content DB from Project Server 2003 server
3.Run the Windows SharePoint Services pre-upgrade scanning tool on the
Windows SharePoint Services 2.0 SP2 farm. This process prepares the Windows
SharePoint Services 2.0 content database for upgrade to Windows SharePoint
Services 3.0.

Goto %PROGRAMFILES% \Common Files\Microsoft Shared\web server
extensions\12\BIN. Run it from Project Server 2003 Application Server.
prescan.exe /all

4.Back-up the Windows Sharepoint Services 2.0 database once it is upgraded.
Add a new database to Project Server 2007 farm and restore the upgraded
Windows Sharepoint 2.0 content database to the newly created database.

5.Run STSADM tool to attach the content database to Project Server (from
PS2007 Application server %PROGRAMFILES% \Common Files\Microsoft Shared\web
server extensions\12\BIN)
stsadm.exe -o addcontentdb -url http://<server>:<port> -databasename <WSS
v2.0 content database> -databaseserver <DB Server name>

This should work as I have followed this procedure everytime I do a migration.

Thanks
Nach