none
WSS Site Relinking During Project Server Upgrade RRS feed

  • Question

  • I am in the process of upgrading from Project Server v2003 to v2010.  I am currently using the provided VME image with Project Server 2007 to prepare the data for upgrade.  I am attempting to relink all my project workspaces, per p. 26 of the VME.pdf.

    Steps followed:
    1.  Restored my MSP 2003 database to the Project2003SourceDB database on the VME
    2.  Restored my WSS 2.0 content database (which only containts Issues / Risks) to a new WSS_ISD_CONTENT database on the VME
    3.  Ran stsadm.exe -o addcontentdb -url http://vme -databasename WSS_ISD_CONTENT -databaseserver VME.  This step took several hours to complete, since it performed the in-place upgrade to WSS 3.0
    4.  Ran all three Project Server 2007 migration steps without error:
     1 – Run Verification
     2 – Run EntGlobal-ResPool Migration
     3 – Migrate Projects

    Now when I run: RelinkAllWSSSites http://vme http://vme/pwa
    every site which exists in the WSS_ISD_CONTENT database returns the following message to the command line:

     "Project <proj name> with GUID xxx does not have a site."


    After step 3, there are now two content databases associated to http://vme web application (where pwa is hosted from).  The DB I attached in step 3 shows 700+ sites (as I would expect).  If I manually navigate to the "Project Workspaces" under "Server Settings" in PWA, there are no project plans with associated sites.  If I manually create a site by highlighting a project in the list and clicking "Create Site", the site is created, but does not contain any of the existing issues / risks prior to upgrade.

    What am I missing here?  The VME.pdf documentation makes me feel like attaching and syncing should result in project plans having their workspaces automatically available from the 2007 PWA site, but that is not the case here.  Are there additional steps I am missing?

    Thanks for any help you can provide.
    Jason

    Friday, January 14, 2011 8:21 PM

Answers

  • Thank you to both Khurram and Andrew!  Their posts led me to do the following:

     

    The initial problem I was having was around that fact that I had two SharePoint content databases associated to the PWA web application.  The first (and seemingly default) contained the PWA sites and the second had all the restored WSS Issues / Risks sites.  So following Khurram's suggestion, I did:

     

    1.  Central Admin --> Application Management --> Create web application

    2.  Created a new web application on port 999, creating yet another content database

    3.  PWA --> Server Settings --> Project Workspace Provisioning Settings

    4.  Change the Default Web Application to the new web application created in step 2.

     

    The above steps are what forced my migrated content database to be used during workspace creation and relinking from PWA.

     

    Now, in order to get the sites relinked:

     

     

    1.      Using this query, I can identify what the workspace url is:

    SELECT FullUrl FROM Webs WHERE Title like = '%project plan name%'

    2.      When I navigate to the site, it is online.  Loading the Issues page returns:

    "One or more field types are not installed properly. Go to the list settings page to delete these fields."

    3.      To fix this, Settings --> List Settings --> Views --> All Views --> click OK (I change nothing, just click Ok.  I don't know why this works...).

    4.      All the issues are back on the page.

    5.      Back to PWA --> Server Settings --> Project Workspaces --> Create Site for the project plan from step 1.

    6.      I enter the "FullUrl" from step 1 in the Site URL of the dialog box.  Clicking Ok results in error:

                "The Web site already exists.  Change the name of the web site you are trying to            create, or select a different site collection and try again."

    7.      To get around having to delete and republish project plans to address this error, I manually inserted the WSS info into MSP_PROJECTS table of the Published database using the below query: 

    UPDATE [ProjectServer_Published].dbo.MSP_PROJECTS
    SET  
     WPROJ_ISSUE_LIST_NAME = issues.listid
     ,WPROJ_RISK_LIST_NAME = risks.listid  
     ,WPROJ_STS_SUBWEB_NAME = w.FullUrl                 
     ,WSTS_SERVER_UID = 'A057DA65-F336-4B1B-9454-AF8F2E37A900'
     ,WSS_PWA_ADMIN_ROLE_ID = 1073741845
     ,WSS_PWA_PROJECT_MANAGER_ROLE_ID = 1073741846
     ,WSS_PWA_TEAM_MEMBER_ROLE_ID = 1073741847
     ,WSS_PWA_READER_ROLE_ID = 1073741848
    FROM 
     [ProjectServer_Published].dbo.MSP_PROJECTS P       INNER JOIN
     [WSS_ISD_CONTENT].dbo.WEBS W                                        
          ON REPLACE(P.PROJ_NAME, '_Published', '') COLLATE DATABASE_DEFAULT = W.TITLE COLLATE DATABASE_DEFAULT     
                                  INNER JOIN
     [WSS_ISD_CONTENT].dbo.DOCS issues
      ON issues.SITEID = W.SITEID
      AND issues.leafname = 'AllItems.aspx'
      AND issues.dirname like '%issues'            INNER JOIN
     [WSS_ISD_CONTENT].dbo.DOCS risks
      ON risks.SITEID = W.SITEID
      AND risks.leafname = 'AllItems.aspx'
      AND risks.dirname like '%risks'
    WHERE 
     w.title = ‘project plan name’

     

     

    8.      Refreshing the Project Workspaces grid from PWA and the Site Address is now listed and navigates to the workspace.

     

     

    With that being the case, I revisited the RelinkAllWSSSites.exe.  I used the <a href=” http://code.msdn.microsoft.com/PS2007Rename/Release/ProjectReleases.aspx?ReleaseId=2028”>Project Rename utility </a> to remove the _Published string from a project plan name and ran RelinkAllWSSSites http://vme:999 http://vme/pwa this time.  The site relinked successfully!

     

    My dilemma now is that when I run the Project Rename utility against multiple projects, it takes about 1 minute per plan and throws queue errors along the way, but that's an entirely new thread...

     

    Thanks for everyone who assisted.  It’s truly appreciated.

    Jason

    Monday, January 24, 2011 4:29 PM

All replies

  • Hello Jason - Detroit

    I haven't used this tool, but I have seen some tools in CodePlex to manage this. 

    http://projectworkspacesync.codeplex.com/

    http://blogs.msdn.com/b/project_programmability/archive/2009/02/10/project-workspace-sync-release-to-codeplex.aspx

    Cheers!


    Michael Wharton, MBA, PMP, MCT, MCSD, MCSE+I, MCDBA
    www.WhartonComputer.com
    Monday, January 17, 2011 12:58 AM
    Moderator
  • following the  steps i was able to relink the project workspaces after migration data from PS 2003 to PS 2007.:

    1. Once you restored all the 5 databased successfully, i.e. 4 Project Server databases and 5th is the content db of your Web application (if your PWA is sharing the same db)
    2. Provision the new PWA instance using the 4 databases.
    3. Try accessing the project workspace of any of your project, if you encounter this: "The page not found" - you have to relink your sites.
    4. Create a new web application on port, lets say 999
    5. Remove the content database of this new web application from the central administration
    6. Add the content database of your old web application ( which we have just restored) to this new web application
    7. Download Project Resource Kit (http://www.microsoft.com/downloads/en/details.aspx?FamilyID=A33D253C-6424-48E4-B87E-0861D1977BB7&displaylang=en)
    8. Extract to your local folder
    9. Run the command prompt
    10. Browse to the folder and type: RelinkAllWSSSites.exe http://<newWebAPP:999> http://server/newPWA
    11. Now browse your PWA, and you should see all Projects and their sites.

    Also browse through this post:http://technet.microsoft.com/hi-in/library/dd630722%28en-us,office.12%29.aspx

     

    Let us know if it helps.

     


    | Khurram Jamshed | Follow my blog about Enterprise Project Management Solution | http://khurramjamshed.blogspot.com |
    Tuesday, January 18, 2011 6:23 AM
  • To relink your project sites try the 'Bulk Update Project Site' option under Server Settings.

    Christine

    Tuesday, January 18, 2011 1:54 PM
    Moderator
  • Thanks for your reply.  I tried the steps above, but the same "does not have a site" message continues to get returned.

    Digging into the database, it looks like the GUIDs that map the MSP project plans to the WSS sites are not making it through the 2003 to 2007 migration, which would explain why nothing is getting relinked.  I need to investigate further.  I'll post back when I know more.

    Tuesday, January 18, 2011 8:53 PM
  • I have not needed to do this (2003 to 2010 migration), but I think you might be able to get it going by using the WSS Relinker from the Resource Kit (http://www.microsoft.com/downloads/details.aspx?FamilyId=A33D253C-6424-48E4-B87E-0861D1977BB7)

     

    EDIT: Oops, see that I am rather late with this reply...apologies :)

    Wednesday, January 19, 2011 6:37 AM
  • I've spent the last couple days executing another v2003 to v2007 migration through the Virtual Migration Environment (following the same steps described in the initial post), having the same results as originally posted.

    Looking in the tables of both databases I can see the GUIDs that link the SharePoint lists to MSP project plans are not migrating into v2007.  I run the following query in the v2003 database:

    SELECT *
    FROM [Project2003SourceDB].[dbo].[MSP_WEB_PROJECTS]
    WHERE WPROJ_ISSUE_LIST_NAME IS NOT NULL

    All the projects which have issues sites associated are returned in the result set.

    Following the execution of "3 – Migrate Projects" and the RelinkAllWSSSites command from the VME server, I run the following query against the v2007 database, expecting to see the same list of projects.  Except this time, nothing is returned.

    SELECT *
    FROM [ProjectServer_Published].[dbo].[MSP_PROJECTS]
    WHERE WPROJ_ISSUE_LIST_NAME IS NOT NULL

    While RelinkAllWSSSites.exe is running, I can see through SQL Profiler the following call which seems to determine whether or not to attempt to a relink.  Every call returns a single row with NULL values for the WSS fields.

    exec MSP_WEB_SP_QRY_GetWSSInfoForProjUID @proj_uid='xxx'

    I've also tried to manually "Create Site" through Server Settings --> Project Workspaces from PWA, thinking it may relink the existing issues / risks, but it does not.


    Does anyone have any guidance of where I might be going wrong here?
    Thanks.
    Jason

    Friday, January 21, 2011 4:01 PM
  • I'm a bit late to the party, but a couple of questions:

    1) Can you actually hit the workspaces in the 2007 VME directly by typing the URL into the browser?

    2) If yes to #1, can you relink the project to that specific workspace by entering the URL in the Site Provisioning interface?

    (And being from Columbus, I won't hold the Detroit thing against you. :-))

     


    Andrew Lavinsky [MVP] Twitter: @alavinsky
    Monday, January 24, 2011 2:26 AM
    Moderator
  • Thank you to both Khurram and Andrew!  Their posts led me to do the following:

     

    The initial problem I was having was around that fact that I had two SharePoint content databases associated to the PWA web application.  The first (and seemingly default) contained the PWA sites and the second had all the restored WSS Issues / Risks sites.  So following Khurram's suggestion, I did:

     

    1.  Central Admin --> Application Management --> Create web application

    2.  Created a new web application on port 999, creating yet another content database

    3.  PWA --> Server Settings --> Project Workspace Provisioning Settings

    4.  Change the Default Web Application to the new web application created in step 2.

     

    The above steps are what forced my migrated content database to be used during workspace creation and relinking from PWA.

     

    Now, in order to get the sites relinked:

     

     

    1.      Using this query, I can identify what the workspace url is:

    SELECT FullUrl FROM Webs WHERE Title like = '%project plan name%'

    2.      When I navigate to the site, it is online.  Loading the Issues page returns:

    "One or more field types are not installed properly. Go to the list settings page to delete these fields."

    3.      To fix this, Settings --> List Settings --> Views --> All Views --> click OK (I change nothing, just click Ok.  I don't know why this works...).

    4.      All the issues are back on the page.

    5.      Back to PWA --> Server Settings --> Project Workspaces --> Create Site for the project plan from step 1.

    6.      I enter the "FullUrl" from step 1 in the Site URL of the dialog box.  Clicking Ok results in error:

                "The Web site already exists.  Change the name of the web site you are trying to            create, or select a different site collection and try again."

    7.      To get around having to delete and republish project plans to address this error, I manually inserted the WSS info into MSP_PROJECTS table of the Published database using the below query: 

    UPDATE [ProjectServer_Published].dbo.MSP_PROJECTS
    SET  
     WPROJ_ISSUE_LIST_NAME = issues.listid
     ,WPROJ_RISK_LIST_NAME = risks.listid  
     ,WPROJ_STS_SUBWEB_NAME = w.FullUrl                 
     ,WSTS_SERVER_UID = 'A057DA65-F336-4B1B-9454-AF8F2E37A900'
     ,WSS_PWA_ADMIN_ROLE_ID = 1073741845
     ,WSS_PWA_PROJECT_MANAGER_ROLE_ID = 1073741846
     ,WSS_PWA_TEAM_MEMBER_ROLE_ID = 1073741847
     ,WSS_PWA_READER_ROLE_ID = 1073741848
    FROM 
     [ProjectServer_Published].dbo.MSP_PROJECTS P       INNER JOIN
     [WSS_ISD_CONTENT].dbo.WEBS W                                        
          ON REPLACE(P.PROJ_NAME, '_Published', '') COLLATE DATABASE_DEFAULT = W.TITLE COLLATE DATABASE_DEFAULT     
                                  INNER JOIN
     [WSS_ISD_CONTENT].dbo.DOCS issues
      ON issues.SITEID = W.SITEID
      AND issues.leafname = 'AllItems.aspx'
      AND issues.dirname like '%issues'            INNER JOIN
     [WSS_ISD_CONTENT].dbo.DOCS risks
      ON risks.SITEID = W.SITEID
      AND risks.leafname = 'AllItems.aspx'
      AND risks.dirname like '%risks'
    WHERE 
     w.title = ‘project plan name’

     

     

    8.      Refreshing the Project Workspaces grid from PWA and the Site Address is now listed and navigates to the workspace.

     

     

    With that being the case, I revisited the RelinkAllWSSSites.exe.  I used the <a href=” http://code.msdn.microsoft.com/PS2007Rename/Release/ProjectReleases.aspx?ReleaseId=2028”>Project Rename utility </a> to remove the _Published string from a project plan name and ran RelinkAllWSSSites http://vme:999 http://vme/pwa this time.  The site relinked successfully!

     

    My dilemma now is that when I run the Project Rename utility against multiple projects, it takes about 1 minute per plan and throws queue errors along the way, but that's an entirely new thread...

     

    Thanks for everyone who assisted.  It’s truly appreciated.

    Jason

    Monday, January 24, 2011 4:29 PM
  • To relink your project sites try the 'Bulk Update Project Site' option under Server Settings.

    Christine

    Thanks Christine, that was the simple fix I needed for our 2010 server. Saved me tons of time.

    Mike


    MP

    Friday, August 16, 2013 5:50 PM