Project Server Data Migration – Cheat Sheet


Data Migration can be a long difficult progress. In Project 2007 we made a lot of investiments to make this process a lot smoother for users.

 

This post provides a list of quick steps to migrate your Project Server 2003 data into Project Server 2007. I’ve done it several times and it works well. If there are any failures, the log gives you detailed information for troubleshooting the issue.

 

This list doesn’t provide a detailed documentation of the process or all the detailed steps or how to troubleshoot problems. For that, refer to the Beta 2 documentation.

 

1)    Install Project Server 2007 and provision a Project Web Access site

 

2)    Backup your clean Project databases (all 4 of them). If you run into problems you can restore the databases and start over

 

 

3)     Get your Project 2003 database ready. Restore an existing Project 2003 database onto the same SQL server as the Project Server 2007. Or create a linked server on the Project Server 2007 SQL Server (SQL Server instance->Security->Linked Servers). Link it to the Project Server 2003 SQL Server. In the security tab choose ‘be made with this security context’ and give a SQL Auth account (Eg. user: sa   password:<whatever>)

 

4)    Install Project 2007 Professional and choose the “install migration tool” advanced option in setup

 

5)    Change the default Migration ini file that gets installed with Project Professional (you can find it at Program FilesMicrosoft OfficeOffice12 P12MIGRATION.INI.SAMPLE)  Add in the right values for Project Server 2003 databases, Project Server 2003 Linked SQL Server, Project Server 2007 PWA etc. ***Spend some time to make sure all your parameters are valid. There are detailed explanation of each parameter***

 

 

6)     Run the migration tool from the command line:   “<drive>:Program FilesMicrosoft OfficeOFFICE12p12migrationtool.exe” -c “<location>p12migration.ini”

 

7)     Look at the command line/migration log to make sure everything is fine. If not, do corrections and re-run migration tool – it should start from where it stopped last.  If there is a irrecoverable problem, make changes in Project Server 2003, restore the clean Project Server 2007 databases and retry migration.

 

8)     If you have any local windows accounts (eg. <MachineBrad Sutton>), make sure you use PWA->edit user functionality to edit those accounts so that they are valid.

 

9)     Go to the migrated PWA site as an admin, edit each migrated security category, go to the “Views – add to category” section and add the ‘My Work’ set of views to the category. If you don’t add these views, migrated users will not be able to see any views when they navigate to the ‘My work’ page.

 

10)  Go to PWA->Server Settings->Operational policies->project workspace provisioning settings and choose ‘Automatically create a project workspace…” option. This is the more common option.  If you don’t want workspaces to be created automatically, you need not do this.

 

Comments (30)

  1. Tina says:

    That’s great!

  2. Lidiane says:

    I am glad you like it 🙂

  3. David Lewis says:

    I realize this is probably futile, but given all the attention over the years to whizzy new features, is there a chance of backfilling some bread and butter features that would make the basic project management processes oh so much easier?

    The prime exmaple in my book is tools to manage resource task sequences "by hand", including… (a) tagged links, so we can distinguish a link inserted to sequence/balance a resource from a logical dependency; (b) tools to quickly reassign tasks from one resource to another and (c) relink the task sequences easily, without having to manually rejigger the links.  

    Underlying all this is the — very widespread — observation that algorithmic resource levelling is…(how can I say this politely)… umm… useless (sorry), and the only way really to level is to manually sequence each resource’s tasks.  

    There’s much more along the same lines to deal with fractional assignments, multi-tasksing, coordinating tasks of different resoruces, etc etc, all in the same vein.  But what I’ve oulined above would be such a leap forward that I would fly to Redmond and hug the whole team!

    Sorry to hijack an irrelevant post for this rant, but after years of struggling with this stuff, I despair of ever being heard.  Aren’t you gflad you have a blog? ;-)))

    Thanks for at least listening.

    David Lewis (djlewis at triadic dot com)

  4. Oliver Lehmann says:

    May I…ummm…disagree? Resource leveling is a great function in Microsoft Office Project if you have learnt how to use it. Better would be critical chain, of course, but I do not expect this seriously.

    Oliver

  5. Igor Macori says:

    Segnalo un bel post ricco di indicazioni e trucchetti per migrare il DB di Project Server da un ambiente…

  6. Steffen says:

    Do you work with SQL 200 or 2005? What ist the best way to migrate Project Server with SQL and 2007?

    I have a PS2003 on SQL and would like to migrate the database and the to the Beta2.

    thanks Steffen

  7. Fraser Larcombe says:

    I am actually having some problems installing the desktop version, it crashes at about 15% through the installation, does it every time, doesnt give me any idea of what has happened just says send info to MS, which I have done.

    Any ideas, anyone else had the same problem?

    Fraser

  8. krishna says:

    plz reply

    immedeatly

  9. Lanka Van Dort - lankavandort@orion-sys.com says:

    Accidentaly deleted some resources from the Global Database. How to recover the resources? Using MS Porject 2003 Enterprise version. Thanks!

  10. Hrvoje says:

    What about migration from Project Server 2007 Beta2 TR to RTM version ?

  11. Rinat says:

    What about migration of sharepoint workspaces?

  12. Michael E says:

    any suggestions on this failed upgrade?

    01/09/2007 15:51:41.414   Project Server 2003 version is 11,2,15,20030816

    01/09/2007 15:51:41.414   Time to execute CUpgrader::CheckP11Version(): 0 ms

    01/09/2007 15:51:41.414   preparing Query select WADMIN_DEFAULT_LANGUAGE from dbo.MSP_WEB_ADMIN

    01/09/2007 15:51:41.414   preparing Query select WADMIN_DEFAULT_LANGUAGE from MSP_WEB_ADMIN

    01/09/2007 15:51:41.424   preparing Query select isnull(is_member(?), 0)

    01/09/2007 15:51:41.424   preparing Query select isnull(is_member(?), 0)

    01/09/2007 15:51:41.424   preparing Query select isnull(is_member(?), 0)

    01/09/2007 15:51:41.434   preparing Query select isnull(is_member(?), 0)

    01/09/2007 15:51:41.564   preparing Query select VERS_VERSION from dbo.MSP_VERSIONS where VERS_DEFAULT = 1

    01/09/2007 15:51:41.574   preparing Query select UPG_PHASE_RUN_STATUS from dbo.MSP_P12UPGRADE_UPGRADE_RUN_PHASES where UPG_PHASE_UID=? AND UPG_PHASE_RUN_STATUS = ?

    01/09/2007 15:51:41.574   preparing Query exec dbo.MSP_P12UPG_INSERT_OR_UPDATE_RUN_PHASE_STATUS ?, ?, ?

    01/09/2007 15:51:41.594   preparing Query exec dbo.MSP_P12UPG_CreateAllViewsToProjectServer2003 ?, ?

    01/09/2007 15:51:41.604   Executing query failed with -1

    01/09/2007 15:51:41.604   Cmd failed retcode= -1

    01/09/2007 15:51:41.604   Err1 = 37000 Err2 = [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find stored procedure ‘dbo.MSP_P12UPG_CreateAllViewsToProjectServer2003’.

    01/09/2007 15:51:41.604   preparing Query exec dbo.MSP_P12UPG_INSERT_OR_UPDATE_RUN_PHASE_STATUS ?, ?, ?

    01/09/2007 15:51:41.614   PWA Migration: Setup Views to Project Server 2003 — Failed.

    01/09/2007 15:51:41.614   Time to execute CUpgrader::UpgradePWASetupViews(): 40 ms

    01/09/2007 15:51:41.614   PWA Migration: Setup Views to Project Server 2003 — Failed.

    01/09/2007 15:51:41.614   Updating run table

    01/09/2007 15:51:41.614   preparing Query update dbo.MSP_P12UPGRADE_UPGRADE_RUNS SET UPG_RUN_STATUS = ?, UPG_RUN_FINISH_DATE = GETDATE() where UPG_RUN_UID = ?

    01/09/2007 15:51:41.614   Executing Query update dbo.MSP_P12UPGRADE_UPGRADE_RUNS SET UPG_RUN_STATUS = ?, UPG_RUN_FINISH_DATE = GETDATE() where UPG_RUN_UID = ?

    01/09/2007 15:51:41.634   Migration finished with return code 80004005

    01/09/2007 15:51:41.634   Project migration failed.

  13. Theron says:

    Hi,

    Is there any procedure/steps when migrating from Project Server 2007 to Project Server 2007.

  14. Thanks for this. It is a great help. Just a note for others: If your 2003 database is not yet upgraded to sp2a you can run the command line tool UPG10DB in the UtilitiesMigrationDatabase folder on the Office Project Server 2007 installation media.

    http://technet2.microsoft.com/Office/en-us/library/f1606be4-f257-4469-a35a-d9189d542ce41033.mspx?mfr=true

  15. Rully says:

    I had problem how to migration Ms project 2007 from one database server to other database server.

    for the first installation, application, database reside on same machine server.

    how to migration database ms project to other server and aplication still in old server.

    thanks before

    Rully

  16. Rully says:

    I have plan to migrate ms project sql server 2007

    from one server to other server.

    please advice and give me scenario case how to do it

    thanks

  17. Roger says:

    Hi there,

    Any suggestions for this error message:

    An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown.  Additional exception information: SharePoint Products and Technologies cannot be configured.  The current installation mode does not support SKU to SKU upgrades because there exists an older version of Windows SharePoint Services that must be upgraded first.

    Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException: Exception of type ‘Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException’ was thrown.

  18. Bartek says:

    Well i have trouble migrating PS 2003 to PS 2007 too ;/

    When i run the P12 migration tool it tells me that the project has succesfully migrated but… when i open PWA or try to access the project from PP – the project list is empty ;/

    Any ideas what might be worng … ?

  19. To Bartek:

    Hi Bartek, make sure you are adding your projects to the save and publish section of the .ini file.

    It seems that you just saved them.

  20. ivanlemus says:

    Hello,

    I am getting the error below when attempting a gradual migration form P2003 to P2007. Do you have any ideas about what could be causing it?.

    NOTE:

    – Project 2007 was upgraded with the "Infrastructure Update for Office Servers".

    – The error happens at the end of the upgrade.

    – I’ve looked in "[MSP_P12UPG_InstallDefaultData]" sproc on the Project Server -> Published DB and it references ‘P11_MSP_WEB_VIEW_FIELDS’…but can not find that object.

    – P2003 DBs hosted on sql 2000 and P2007 DBs are hosted on SQL2005.

    Thanks for all your help. Have a nice day.

    **********Phase:PWA migration start**********

    10/15/2008 13:43:30.577 preparing Query select UPG_PHASE_RUN_STATUS from dbo.MSP_P12UPGRADE_UPGRADE_RUN_PHASES where UPG_PHASE_UID=? AND UPG_PHASE_RUN_STATUS = ?

    10/15/2008 13:43:30.577 PWA Migration: Starting Phase Setup default migration data.

    10/15/2008 13:43:30.577 preparing Query exec dbo.MSP_P12UPG_INSERT_OR_UPDATE_RUN_PHASE_STATUS ?, ?, ?

    10/15/2008 13:43:30.593 preparing Query exec dbo.MSP_P12UPG_InstallDefaultData

    10/15/2008 13:43:30.936 Executing query failed with -1

    10/15/2008 13:43:30.936 Cmd failed retcode= -1

    10/15/2008 13:43:30.936 Err1 = S0002 Err2 = [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name ‘P11_MSP_WEB_VIEW_FIELDS’.

    10/15/2008 13:43:30.936 preparing Query exec dbo.MSP_P12UPG_INSERT_OR_UPDATE_RUN_PHASE_STATUS ?, ?, ?

    10/15/2008 13:43:30.936 PWA Migration: Setup default migration data — Failed.

    10/15/2008 13:43:30.936 Time to execute CUpgrader::UpgradePWASetupData(): 360 ms

    **********Phase:PWA migration end**********

    10/15/2008 13:43:30.936 Time to execute CUpgrader::UpgradePWA(): 360 ms

    10/15/2008 13:43:30.936 Updating run table

    10/15/2008 13:43:30.936 preparing Query update dbo.MSP_P12UPGRADE_UPGRADE_RUNS SET UPG_RUN_STATUS = ?, UPG_RUN_FINISH_DATE = GETDATE() where UPG_RUN_UID = ?

    10/15/2008 13:43:30.936 Executing Query update dbo.MSP_P12UPGRADE_UPGRADE_RUNS SET UPG_RUN_STATUS = ?, UPG_RUN_FINI

  21. ivanlemus says:

    Here is the solution to the question I posted (provided by MS support):

    1. Execute the script bellow against the project_2007_published_db.

    2. run the migration tool again.

    —————————————————

    DECLARE @RC int

    EXEC @RC = [Project2007_published_db_name].[dbo].[MSP_P12UPG_CreateAllViewsToProjectServer2003]

    ‘project2003_db_server_name’,’project2003_db_name’

    Note:

    ——

    replace these values with your own:

    – [Project2007_published_db_name]

    – ‘project2003_db_server_name’

    – ‘project2003_db_name’

    —————————————————-

    Thank you all. happy friday!

  22. ivanlemus says:

    hello all,

    i am getting the following error when trying to attach a SharePoint 2.0 content db to a windows sharepoint services 3.0. do you have an idea about what could be causing it?

    thx for all your help. have a nice weekend.

    command:

    ———————————————-

    stsadm.exe -o addcontentdb -url http://usnapvm3devepm1:80 -databasename DevEPM_temp_310 -databaseserver  usnapvm3devdb2

    errors:

    ———————————————–

    ———- C:PROGRAM FILESCOMMON FILESMICROSOFT SHAREDWEB SERVER EXTENSIONS12LOGSUPGRADE.LOG

    [SPWebTemplateSequence] [ERROR] [10/31/2008 11:41:57 PM]: Template PWS#0: SPSite Id=abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be accessed due to exception. Skipping this SPSite for template upgrade.  Exception: System.IO.FileNotFoundException: The site with the id abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be found.

    [SPWebTemplateSequence] [ERROR] [10/31/2008 11:41:57 PM]: Template PWS#0: SPSite Id=abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be accessed due to exception. Skipping SPWeb Id=813b3054-9e3f-46be-9c47-333c0e777afc for template upgrade. Exception: System.IO.FileNotFoundException: The site with the id abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be found.

    [SPWebTemplateSequence] [ERROR] [10/31/2008 11:41:57 PM]: Template MPS#0: SPSite Id=abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be accessed due to exception. Skipping SPWeb Id=2b60587a-59a1-4b34-aaa6-12bc0cd7e030 for template upgrade. Exception: System.IO.FileNotFoundException: The site with the id abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be found.

    [SPWebTemplateSequence] [ERROR] [10/31/2008 11:41:57 PM]: Template MPS#0: SPSite Id=abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be accessed due to exception. Skipping SPWeb Id=88bd14cf-8bf1-4e8e-8c47-91af6e16bf45 for template upgrade. Exception: System.IO.FileNotFoundException: The site with the id abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be found.

    [SPWebTemplateSequence] [ERROR] [10/31/2008 11:41:57 PM]: Template MPS#0: SPSite Id=abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be accessed due to exception. Skipping SPWeb Id=8832366c-f5bf-487f-a200-986a100c9bf6 for template upgrade. Exception: System.IO.FileNotFoundException: The site with the id abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be found.

    [SPWebTemplateSequence] [ERROR] [10/31/2008 11:41:57 PM]: Template MPS#0: SPSite Id=abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be accessed due to exception. Skipping SPWeb Id=ac80a789-b21a-4690-b2cc-c2375f87db81 for template upgrade. Exception: System.IO.FileNotFoundException: The site with the id abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be found.

    [SPWebTemplateSequence] [ERROR] [10/31/2008 11:41:57 PM]: Template MPS#0: SPSite Id=abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be accessed due to exception. Skipping SPWeb Id=e9cc310c-792e-4c93-97a7-f1e3384cdeab for template upgrade. Exception: System.IO.FileNotFoundException: The site with the id abaaba05-0a21-4a37-85a2-ff9fcb8d41af could not be found.

    [SPManager] [INFO] [10/31/2008 11:41:57 PM]: Inplace Upgrade session finishes. root object = SPContentDatabase Name=epm_migration1_il Parent=SPDatabaseServiceInstance Name=INSTANCE1, recursive = True. 7 errors and 0 warnings encountered.

  23. salamn says:

    hi sir

    iAM ENGINEER need the programs

    thanks

  24. mike says:

    The migration tool fails for me when it tries to migrate Enterprise Global…particularly with the Custom Fields in PS2003.

    — preparing Query select distinct TEXT_VALUE from dbo.MSP_TEXT_FIELDS where (TEXT_FIELD_ID = ? OR TEXT_FIELD_ID = ?) AND TEXT_VALUE IS NOT NULL

    — Executing query failed with -1

    — g_p11Comm.GetDistinctTextCustomFieldValues failed with 80004005

    What could this be? How can identify what custom field or outline code is causing this issue?

    **********Phase:Eglobal Migration start**********

    04/29/2009 11:36:44.819   preparing Query select UPG_PHASE_RUN_STATUS from dbo.MSP_P12UPGRADE_UPGRADE_RUN_PHASES where UPG_PHASE_UID=? AND UPG_PHASE_RUN_STATUS = ?

    04/29/2009 11:36:44.819   Getting Project info from Project Server 2007

    04/29/2009 11:36:44.819   preparing Query select PROJ_UID, PROJ_NAME, PROJ_TYPE from dbo.MSP_PROJECTS where PROJ_NAME = ?

    04/29/2009 11:36:44.819   Could not get info for global20090428162504 in Project Server 2007

    04/29/2009 11:36:44.819   preparing Query select PROJ_CHECKEDOUT from dbo.MSP_PROJECTS where PROJ_ID = ?

    04/29/2009 11:36:44.835   Eglobal is not migrated. Starting migration of Eglobal

    04/29/2009 11:36:44.835   preparing Query exec dbo.MSP_P12UPG_INSERT_OR_UPDATE_RUN_PHASE_STATUS ?, ?, ?

    04/29/2009 11:36:44.835   Starting upgrade of eglobal global20090428162504

    04/29/2009 11:36:44.835  

    04/29/2009 11:36:44.835   Opening project from Project Server 2003…

    04/29/2009 11:36:44.835   Executing Query insert into dbo.MSP_P12UPGRADE_PROJECT_UPGRADES (UPG_RUN_UID, UPG_PROJ_P11_ID, UPG_PROJ_UID, UPG_PROJ_P11_NAME, UPG_PROJ_STATUS, UPG_PROJ_TYPE, UPG_PROJ_START_DATE) values (?, 1934, ?, ?, 3, ?, GETDATE())

    04/29/2009 11:36:44.835   preparing Query insert into dbo.MSP_P12UPGRADE_PROJECT_UPGRADES (UPG_RUN_UID, UPG_PROJ_P11_ID, UPG_PROJ_UID, UPG_PROJ_P11_NAME, UPG_PROJ_STATUS, UPG_PROJ_TYPE, UPG_PROJ_START_DATE) values (?, 1934, ?, ?, 3, ?, GETDATE())

    04/29/2009 11:36:44.851   preparing Query exec dbo.MSP_P12UPG_DELETE_PROJECT_MAPPINGS ?

    04/29/2009 11:36:52.336   Time to execute P12UpgradeDoc::OpenP11Project(): 7485 ms

    04/29/2009 11:36:52.336   Executing Query update dbo.MSP_P12UPGRADE_PROJECT_UPGRADES set UPG_PROJ_STATUS = 4, UPG_PROJ_FINISH_DATE = GETDATE() where UPG_PROJ_P11_ID = 1934

    04/29/2009 11:36:52.336   Successfully Opened from Project Server 2003

    04/29/2009 11:36:52.601   Time to execute P12UpgradeDoc::FixUpLookupTableValueRowNumber(): 265 ms

    04/29/2009 11:36:52.601   preparing Query select distinct attr.ATTRIB_FIELD_ID from dbo.MSP_FIELD_ATTRIBUTES attr, dbo.MSP_PROJECTS proj where attr.PROJ_ID = proj.PROJ_ID and proj.PROJ_TYPE = 2

    04/29/2009 11:36:52.617   preparing Query select max(MD_PROP_ID_SECONDARY) from dbo.MSP_CUSTOM_FIELDS

    04/29/2009 11:36:52.617   Maximum existing enterprise assignment custom field pid = 255885314

    04/29/2009 11:36:52.617   preparing Query select distinct TEXT_VALUE from dbo.MSP_TEXT_FIELDS where (TEXT_FIELD_ID = ? OR TEXT_FIELD_ID = ?) AND TEXT_VALUE IS NOT NULL

    04/29/2009 11:36:52.632   Executing query failed with -1

    04/29/2009 11:36:52.632   Cmd failed retcode= -1

    04/29/2009 11:36:52.632   Err1 = 37000 Err2 = [Microsoft][ODBC SQL Server Driver][SQL Server]The text data type cannot be selected as DISTINCT because it is not comparable.

    04/29/2009 11:36:52.632   cmd.Execute failed with status hr = 80004005

    04/29/2009 11:36:52.632   g_p11Comm.GetDistinctTextCustomFieldValues failed with 80004005

    04/29/2009 11:36:52.632   Time to execute P12UpgradeDoc::FixupEnterpriseCustomFields(): 31 ms

    04/29/2009 11:36:52.632   FixupEnterpriseCustomFields failed with 80004005

    04/29/2009 11:36:52.632   Time to execute P12UpgradeDoc::Upgrade(): 7796 ms

    04/29/2009 11:36:52.632   Migration failed for project global20090428162504

    04/29/2009 11:36:52.679   Time to execute P12ProjectUpgrader::Upgrade(): 7843 ms

    04/29/2009 11:36:52.679   preparing Query exec dbo.MSP_P12UPG_INSERT_OR_UPDATE_RUN_PHASE_STATUS ?, ?, ?

    04/29/2009 11:36:52.695   Ent global migration failed with error 80004005

    **********Phase:Eglobal Migration end**********

  25. Parag Kharche says:

    I have migrated from PS 2007 to PS 2007 but facing problem in restoring project workspaces…

    How to restore…

    Reply..ASAP..

  26. Kannan says:

    I get the following error when i am trying to migrate from PS2003 to PS2007. The SQL Server 2000 and SQL server 2005 are on the same box. The project server 2003 database on SQL Server 2000 is restored on to SQL server 2005. Any help is appreciated

    08/13/2009 17:16:51.500   Log file Initialized

    08/13/2009 17:16:51.510   Migration tool version is 12,0,4518,1014

    08/13/2009 17:16:51.510   Configuration file is C:Documents and SettingsKannanMy DocumentsP12MIGRATION.INI

    08/13/2009 17:16:54.273   Connecting to Project Server 2007 Draft db…

    08/13/2009 17:16:54.374   Creating DSN: name = MSP-12-WORKING-DB-DSN, server = Server2003, db = ProjectServer_Draft, trusted = 1

    08/13/2009 17:16:55.205   Created DSN MSP-12-WORKING-DB-DSN

    08/13/2009 17:16:56.316   Connection string DSN=MSP-12-WORKING-DB-DSN;UID=;APP=2007 Microsoft Office system;WSID=SERVER2003;DATABASE=ProjectServer_Draft;Trusted_Connection=Yes

    08/13/2009 17:16:56.316   Connecting to Project Server 2007 published db…

    08/13/2009 17:16:56.326   Creating DSN: name = MSP-12-PUBLISHED-DB-DSN, server = Server2003, db = ProjectServer_Draft, trusted = 1

    08/13/2009 17:16:56.356   Created DSN MSP-12-PUBLISHED-DB-DSN

    08/13/2009 17:16:56.467   Connection string DSN=MSP-12-PUBLISHED-DB-DSN;UID=;APP=2007 Microsoft Office system;WSID=SERVER2003;DATABASE=ProjectServer_Draft;Trusted_Connection=Yes

    08/13/2009 17:16:56.467   Project Server 2007 url = http://Server2003/pwa

    08/13/2009 17:16:56.477   Creating Project Server 2007 soap object…

    08/13/2009 17:16:57.839   Creating Project Server 2007 resource soap object…

    08/13/2009 17:16:57.909   Creating Project Server 2007 winproj soap object…

    08/13/2009 17:16:58.169   Creating Project Server 2007 wssinterop soap object…

    08/13/2009 17:16:58.229   Getting all Upgraded Projects from Project Server 2007

    08/13/2009 17:16:58.249   preparing Query select distinct A.UPG_P11_ENT_ID, A.UPG_P12_ENT_UID, B.PROJ_NAME, C.UPG_PROJ_P11_NAME from dbo.MSP_P12UPGRADE_ENTITY_MAPS A, dbo.MSP_PROJECTS B, dbo.MSP_P12UPGRADE_PROJECT_UPGRADES C WHERE A.UPG_P12_ENT_UID = B.PROJ_UID AND A.UPG_P11_ENT_ID = C.UPG_PROJ_P11_ID AND A.MD_ENT_TYPE_UID = ‘CECFE271-6660-4ABE-97ED-208D3C71FC18’

    08/13/2009 17:16:58.339   preparing Query select WADMIN_VERSION_MAJOR, WADMIN_VERSION_MINOR, WADMIN_VERSION_REVISION, WADMIN_VERSION_BUILD from dbo.MSP_WEB_ADMIN

    08/13/2009 17:16:58.399   Project Server 2007 Project Server version is 12,0,15,45181014

    08/13/2009 17:16:58.399   Connecting to Project Server 2007 …

    **********Phase:Tool initialization end**********

    08/13/2009 17:16:59.952   Initializations succeeded, Starting migration

    **********Phase:Migration initialization start**********

    08/13/2009 17:16:59.952   Policy to fix up project server security categories = true.

    08/13/2009 17:16:59.972   Policy to never publish master projects = true.

    08/13/2009 17:16:59.982   WARNING: Projects will be migrated even if they have multiple status managers for the same task.

    08/13/2009 17:17:00.613   Adding to run table

    08/13/2009 17:17:00.613   preparing Query insert into dbo.MSP_P12UPGRADE_UPGRADE_RUNS (UPG_RUN_UID, UPG_RUN_MACHINE_NAME, UPG_RUN_STATUS, UPG_RUN_START_DATE) values (?, ?, 0, GETDATE())

    08/13/2009 17:17:00.633   Executing Query insert into dbo.MSP_P12UPGRADE_UPGRADE_RUNS (UPG_RUN_UID, UPG_RUN_MACHINE_NAME, UPG_RUN_STATUS, UPG_RUN_START_DATE) values (?, ?, 0, GETDATE())

    08/13/2009 17:17:00.743   Connecting to Project Server 2003 sql server project database

    08/13/2009 17:17:00.753   Creating DSN: name = P11-PROJECT-SERVER-DSN, server = Server2003, db = ProjectServer2003, trusted = 1

    08/13/2009 17:17:00.773   Created DSN P11-PROJECT-SERVER-DSN

    08/13/2009 17:17:01.033   Connection string DSN=P11-PROJECT-SERVER-DSN;UID=;APP=2007 Microsoft Office system;WSID=SERVER2003;DATABASE=ProjectServer2003;Trusted_Connection=Yes

    08/13/2009 17:17:01.043   Connecting to the Project Server 2003 sql server web database

    08/13/2009 17:17:01.043   Creating DSN: name = P11-PROJECT-SERVER-WEB-DSN, server = Server2003, db = ProjectServer2003, trusted = 1

    08/13/2009 17:17:01.063   Created DSN P11-PROJECT-SERVER-WEB-DSN

    08/13/2009 17:17:01.294   Connection string DSN=P11-PROJECT-SERVER-WEB-DSN;UID=;APP=2007 Microsoft Office system;WSID=SERVER2003;DATABASE=ProjectServer2003;Trusted_Connection=Yes

    08/13/2009 17:17:01.314   preparing Query select WADMIN_VERSION_MAJOR, WADMIN_VERSION_MINOR, WADMIN_VERSION_REVISION, WADMIN_VERSION_BUILD from dbo.MSP_WEB_ADMIN

    08/13/2009 17:17:01.634   Project Server 2003 version is 11,2,15,20030816

    08/13/2009 17:17:01.634   Time to execute CUpgrader::CheckP11Version(): 341 ms

    08/13/2009 17:17:01.634   preparing Query select WADMIN_DEFAULT_LANGUAGE from dbo.MSP_WEB_ADMIN

    08/13/2009 17:17:01.734   preparing Query select WADMIN_DEFAULT_LANGUAGE from MSP_WEB_ADMIN

    08/13/2009 17:17:01.784   preparing Query select isnull(is_member(?), 0)

    08/13/2009 17:17:01.924   preparing Query select isnull(is_member(?), 0)

    08/13/2009 17:17:01.924   preparing Query select isnull(is_member(?), 0)

    08/13/2009 17:17:01.995   preparing Query select isnull(is_member(?), 0)

    08/13/2009 17:17:03.377   preparing Query select VERS_VERSION from dbo.MSP_VERSIONS where VERS_DEFAULT = 1

    08/13/2009 17:17:03.687   preparing Query select UPG_PHASE_RUN_STATUS from dbo.MSP_P12UPGRADE_UPGRADE_RUN_PHASES where UPG_PHASE_UID=? AND UPG_PHASE_RUN_STATUS = ?

    08/13/2009 17:17:05.049   preparing Query exec dbo.MSP_P12UPG_INSERT_OR_UPDATE_RUN_PHASE_STATUS ?, ?, ?

    08/13/2009 17:17:05.620   preparing Query exec dbo.MSP_P12UPG_CreateAllViewsToProjectServer2003 ?, ?

    08/13/2009 17:17:05.690   Executing query failed with -1

    08/13/2009 17:17:05.690   Cmd failed retcode= -1

    08/13/2009 17:17:05.690   Err1 = 37000 Err2 = [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find stored procedure ‘dbo.MSP_P12UPG_CreateAllViewsToProjectServer2003’.

    08/13/2009 17:17:05.710   preparing Query exec dbo.MSP_P12UPG_INSERT_OR_UPDATE_RUN_PHASE_STATUS ?, ?, ?

    08/13/2009 17:17:05.740   PWA Migration: Setup Views to Project Server 2003 — Failed.

    08/13/2009 17:17:05.750   Time to execute CUpgrader::UpgradePWASetupViews(): 2063 ms

    08/13/2009 17:17:05.750   PWA Migration: Setup Views to Project Server 2003 — Failed.

    08/13/2009 17:17:05.770   Updating run table

    08/13/2009 17:17:05.770   preparing Query update dbo.MSP_P12UPGRADE_UPGRADE_RUNS SET UPG_RUN_STATUS = ?, UPG_RUN_FINISH_DATE = GETDATE() where UPG_RUN_UID = ?

    08/13/2009 17:17:05.770   Executing Query update dbo.MSP_P12UPGRADE_UPGRADE_RUNS SET UPG_RUN_STATUS = ?, UPG_RUN_FINISH_DATE = GETDATE() where UPG_RUN_UID = ?

    08/13/2009 17:17:06.050   Migration finished with return code 80004005

    08/13/2009 17:17:06.050   Project migration failed.

  27. Josh says:

    My organization is planning a 2k7 to 2k7 migration, to upgrade to a 64 bit OS and take advantage of some better hardware.

    The three key changes from an infrastructure standpoint are:

    -new os and hardware (x64)

    -new physical site (from east to west coast)

    -new domain (from an old legacy trusted domain to our new server/user/workstation domain)

    So far the approach we’ve taken is to simply import backups of the SQL data for Published, Archive, Draft and Reporting; essentially overwriting a previously provisioned pwa site. But we’ve found some problems.

    The user accounts are not available out of the gate, for some reason they need to be re-saved in the pwa interface (with no changes) to make them usable.  The second major problem is the workspaces, which obviously do not get migrated using the above-mentioned method. Should I be looking to migrate the PWA content database as well? and will this help us carry over the workspaces associated with our projects?

    Everything else appears to work; though we have not done full data review.

    -Josh

  28. namrata says:

    i want to know how we can migrate database from sql to oracle.

  29. Marcio Aleixo says:

    Don't get me wrong, but this is the easyest part of the migration…

    People don't use sharepoint in your company? If I have 3000 projects with project workspaces in sharepoint, evething working fine on Project Server 2003. What should I do with those 3000 project workspaces, with tasks, issues, risks… conected to the project tasks and everything?

    Do you have some step-by-step for this?

    Thank's