Upgrade Project Server 2007 sites to 2010.

Process to upgrade Project Server 2007 sites to 2010.


1. Make sure project wss site is in an isolated databases. If not, backup and restore site collection to different content databases by using a seperate temp web application.
2. Backup content dbs and project server databases from SQL Server (SP2007)
3. Restore content dbs and project server databases on SP2010/PS 2010 SQL server 
4. Run Mount-SPContentDatabase or add-contentdb commands for SharePoint content databases only, upgrade and attach SP content databases to project web application.
5. Create a new project web access site using Project service application management page,
    - Make sure you enter the same name of the site url which got upgraded in step 4.
    - Enter 4 Project server database names and create pwa.
6. Run Bulk project site update to fix project workspace link issue.


Note:
1. If you have project workspaces in your project server 2007 implementation remember to keep the same relative path name when you perform step 1 above.
i.e. /sites/projectworkspaces should be restored to temp web app and then upgraded to SP2010 as /sites/projectworkspaces and not with any other name. However for the pwa site name it may take a new name that needs to be restored.
2. Do not perform backup and restore of project workspace site collection to move between database for isolation. If you do it, the ID of the site changes and then Step 6 will not work as it performs an ID match to relink the pwa to the workspace sites.

SP2010 - Cannot create new site collections

Scenario: I was not able to provision a new project web access instance on a Project Server 2010 / SharePoint 2010 environment. Further troubleshooting this problem I realized that no new site collections could be created on the environment under the specific problematic web application only. Below is the error from ULS:

Failed to provision site [project web access instance name] with error: System.NullReferenceException: Object reference not set to an instance of an object.

   at Microsoft.SharePoint.Administration.SPContentDatabaseCollection.FindBestContentDatabaseForSiteCreation(IEnumerable`1 contentDatabases, Guid siteIdToAvoid, Guid webIdToAvoid, SPContentDatabase database, SPContentDatabase databaseTheSiteWillBeDeletedFrom)

Solution:

This is a case of at least 1 orphaned database associated to the problematic web application. 

1. Run below powershell command to get GUID of web application.

get-spwebapplication | ? {$_.displayname -eq "Problematic Web Application Name"} | fl

2. Run this SQL query against configuration database.

select ID, Name, CAST (properties as xml) from Objects where ID = 'GUID of webapp from Step 1'

3. The results returned from step 2 will have 1 column with the properties as xml. Click on the results and it should open a new window in SQL Mgmt studio with xml output.

4. Search for the word "m_Databases" in the xml output.

5. Carefully read through the tag that stores the above searched word. You should be able to see fld tags. Find out a tag which has fld tag with value null. This is the orphan database. Its GUID is the xml line above where you found null.

6. Cross verify all databases currently associated with the web application and make sure this database is not getting used.

7. Run below powershell script,

$webapp.contentdatabases.delete(‘ID-of-bad-content-db’) 

This script will throw an object reference error. Do not worry, it works its magic under the hood.

Try to create a new site collection now and it should work. 

Summary: The above problem occurs because if there one entry which has fld value set to null SharePoint thinks that that database is the most suitable one to create new site collections in. But since it is an orphaned database, it is unable to do so and reports the above error in ULS which is repeated every time a new site collection creation request is initiated with through SP user interface or Project Server interface.

Project Server 2010 - Waiting for resources

Scenario: Trying to provision new project server 2010 pwa instance. The status is stuck at "Waiting for resources" After some time checking the ULS logs and the content database statistics we releaize that a new site collection did get created.

Solution: Make sure that the SharePoint 2010 Timer service is "Started" on all servers where it is supposed to run.

Request for security token failed

Error:
Request for security token failed with exception: System.ServiceModel.FaultException: The server was unable to process the request due to an internal error.

Environment:
Microsoft Project Server 2010
Microsoft SharePoint Server 2010

Solution:
1. Start "Claims to Windows Token Service " on all servers in the farm.
2. IISRESET on all servers.

Project Server 2010 Administration

List of very important links for Project Server 2010 Administrators,

http://technet.microsoft.com/en-us/library/ff631141.aspx