If you are getting the following a similar error message after trying to migrate/do a full backup from the central admin than you have run into a Backup/restore procedure mishandling. The solution to this problem would be a manual backup and restore of the Project Db’s as follows. If you are not familiar with this steps i would recommand to open a support call.
Error message :
Build in Backup functionality error Project Server Application Completing restore 8/12/2008 1:42 PM Object
Project Server Application failed in event OnPostRestore. For more
information, see the error log located in the backup directory.
FileNotFoundException: The site with the id
1a76a2bf-c0c2-4dd8-aec4-d1b615130ebe could not be found.
pwa Completing restore 8/12/2008 1:44 PM Object pwa failed in event
OnPostRestore. For more information, see the error log located in the backup
directory. InvalidOperationException: ProjectSite.OnPostRestore
[8/12/2008 1:40:08 PM]: FatalError: [pwa] Can’t obtain
ProjectPSISharedApplication restoring ProjectSite ‘pwa.
[8/12/2008 1:40:08 PM]: Error: Object Project Server Application failed in
event OnPostRestore. For more information, see the error log located in the
SQL Server management studio backup of the 4 Project Server Databases(Archive, Draft, Published, Reporting).
Then you have to restore them in the new environment.
If you created everything that is needed for the deployment that would be:
– Creating a web application for the PWA
– Creating a web application for the SSP
– Creating site Collection
– Creating a Shared Service Provider
Then you can provision the Project Web Access site. For every of the 4 databases you should mention the same name as you have mentioned when you restored the databases on the SQL Server.
The following steps are used to restore the WSS_Content_ProjectServer database (the name could change from one installation to another).
1. Back-up the exiting WSS_Content_ProjectServer database (full back-up)
2. If you are changing the SQL server restore the previously backed-up database with a different name (this is temporary, after finishing the procedure the database can be deleted).
3. On the new Project Server go to Central Administration and create a new Web application on a different port, for example 88. When creating it leave the default settings for the WSS_Config database. Run IISRESET /NOFORCE after process is completed.
4. In Central Administration, Application Management, Manage Content Databases select the Web Application running on port 88.
Attach to this Web Application the WSS_Content_ProjectServer database that has just been restored on the SQL server and delete the default databases. We now have practically on port 88 a Web Application with the old WSS_ Content database.
5. Open a command prompt and run the following command for export using stsadm (run it from the folder that contains stsadm:
stsadm -o export -url http://SERVERNAME:88/pwa -filename c:\projectserver.cab -cabsize 500 -includeusersecurity
The switch -cabsize 500 specifies the when reaching the 500 MB a second export file will be created. (<http://technet.microsoft.com/en-us/library/cc262759(TechNet.10).aspx>)
6. From the same command prompt using stsadm run the following command to import content on the new PWA site:
stsadm -o import -url http://NUMESERVER/pwa -filename c:\projectserver.cab -updateversions 3 -includeusersecurity
The switch -updateversions 3 is used in case there are already some files in the db that need to be overwritten. The value 3 means: Ignore (<http://technet.microsoft.com/en-us/library/cc261866(TechNet.10).aspx>)
7. Restore the link between projects and their workspaces:
a. Run the following query on the Published databases:
This script returns a string that will be used in the next step.
b. On the published database run the following query:
update dbo.MSP_PROJECTS set WSTS_SERVER_UID=’COPY THE STRING OBTAINED EARLIER HERE’ where WSTS_SERVER_UID is not null
Created a new SSP to replace the original SSP.
1) Go to SharePoint 3.0 Central Administration, Share Services Administration, New SSP.
2) Set the SSP Name, NEW Web application, Username and password.
3) After the SSP is successfully created click OK.
4) Click Change Default SSP and click OK.
5) Click Change Associations and then select each Web Application separately and click OK.
6) Finally, click the dropdown next to the original SSP and select Delete. Ensure the option “Remove without deleting the associated databases” is selected. Click OK