Error relinking Project Site to Project in #ProjectServer 2010 #PS2010 #Project #EPM

July 20, 2011 at 3:55 pm | Posted in Administration, Workarounds | 2 Comments
Tags: , ,

Do you receive the error below when trying to relink a Project Site to Project in PWA > Server Settings > Project Sites?

The Web Site does not exist or is not configured for Project Server. Enter a Web Site that has been extended with a Project Server compatible template.


You will normally run into the issue if you have deleted a Project from Project Server, not deleted the Project Site, create a new project plan and then want to relink the original Project Site. If your Project Site is based on a Project Server template then the usual cause for this error is that either you have %20 (URL encoding for a space) in the Site URL or a default list such as the Risks or Issues list has been deleted and maybe a new custom SharePoint list with the same name has been created instead.

Firstly instead of using the %20 for the space actually put a space in the address box, for example use PWA/PM 1 instead of PWA/PM%201. If that doesn’t resolve your issue it is usually caused by the default risks or issues list being deleted. When you relink a Project Site using the Edit Site Address button in PWA > Server Settings > Project Sites it will validate the site by checking if the default Project Server Risks and Issues lists are present on the site.

There are two methods to relink this Project Site back to the Project if you have deleted the default list or lists.

The best option would be to recreate the default lists as described in this article: This would mean having to recreate all of the list items again, but would mean that you don’t have any Reporting Project synch WSS errors in the Project Server queue when you publish the associated project.

The other option is to relink the Project Site as it is using the steps below. In this example the Project is called PM 1 with a URL of PWA/PM 1.

  • Navigate to the PM 1 site and click Site Actions > Site Settings > Title, description and icon and edit the URL to PM 1z and click OK.


  • Create a new blank site for PM 1 in PWA > Server Settings > Project Sites with a URL of PM 1


  • Navigate to this new blank PM 1 site and click Site Actions > Site Settings > Delete this site then click Delete (confirm it is the blank site before deleting!)


  • Navigate to the PM 1z site, click Site Actions > Site Settings > Title, description and icon and edit the URL to PM 1 and click OK.


  • This original Project Site is now linked back to the new Project

Hope that helps anyone facing this issue.


How to check the SharePoint 2010 and Project Server 2010 service pack / patch level #PS2010 #ProjectServer #SharePoint #SP2010

July 8, 2011 at 7:59 pm | Posted in Administration | 1 Comment
Tags: , , ,

This article will show how to check the farm version for SharePoint Foundation 2010, SharePoint Server 2010 and Project Server 2010.

The farm patch level can be check in the Central Administration site, click “Upgrade and Migration” then “Check Product and Patch Installation Status”


The patch level of all farm components will be detailed here, as you can see below, Project Server is listed at the bottom:


The farm configuration database version can also be checked on the “Manage Servers in this farm” page:


You can also check the SQL databases directly just running the query below:

select     version
        ,    ID
        ,    UserName
        ,    TimeStamp
from versions

Or if you want to see everything:

Select * from versions

This query can be executed against most of the SharePoint 2010 databases and all of the Project Server 2010 PWA databases. Worth noting is that not all SharePoint databases have a versions table, also not all of the versions tables get updated with every update, it usually depends if there is a schema update.

SQL Alias vs DNS Alias for Project Server 2010 install #PS2010 #EPM #ProjectServer

July 6, 2011 at 5:44 pm | Posted in Installation | 2 Comments
Tags: , ,

When installing Project Server 2010 it is always best practice to use an alias name for the SQL server as this makes life easier should you want to move SQL servers at a later date. This raises the question, SQL alias (using SQL cliconfg utility – pic below) or a network DNS Alias name (CNAME or HOST Record).


Pic1: SQL Server Client Network Utility (cliconfg)

For Project Server 2007 I would have said there weren’t really any advantages for one method over the other but for Project Server 2010 it’s different. For Project Server 2010 I would always recommend using a network DNS Alias, the reason being is to do with creating Excel Services reports.

When a user either creates a new or edits an existing report in Excel, their Excel client will connect directly to the data source (either Reporting database, custom database or OLAP cube). The ODC file will contain the connection details, SQL server name (alias name if Project Server was installed with an Alias for SQL), and database or cube name. If you installed Project Server 2010 with a SQL Alias on the Application Server, the user’s client machine will not know anything about the SQL Alias name unless you set up the same SQL Alias on all users machines who will create Excel Reports. This is because SQL Alias are only local to the machine that is it created on. Using a network DNS Alias to alias the SQL server will remove this issue.

Paul Mather

Project Server 2007 / 2010 scheduled tasks not running #PS2010 #ProjectServer #EPM #PS2007

July 4, 2011 at 7:56 pm | Posted in Issue | Comments Off on Project Server 2007 / 2010 scheduled tasks not running #PS2010 #ProjectServer #EPM #PS2007
Tags: , ,

Scheduled jobs such as the daily scheduled backup in project server not running but work when you run them manually? I have seen this at many clients and the resolution is usually simple.

All of the scheduled jobs in Project Server 2007 / 2010 run from a SharePoint Timer Job, if you look in Central Administration at the timer job definitions you will see your project server jobs. These include:

  • Project Server Cube Admin Job
  • Resource Capacity Job
  • Scheduled Backup Job (one for each item)

These jobs are created in Central Administration when you set up the scheduled jobs in PWA. If you find that some of the scheduled jobs no longer run automatically, editing the time of the job will usually resolve the issue. So for example, if your daily Project backup that scheduled to run at 02:00 is not working automatically, try editing the time of the job to 03:00 and check the following day to confirm it has worked. To confirm it has run you can check the queue history and add in the “Success” job completion state. You can always set the job to run again at 02:00 for the following night and that should still work. You would need to repeat this for all of the scheduled jobs that were not running automatically.

Project Server 2010 Database Maintenance Plans #EPM #PS2010 #ProjectServer

June 30, 2011 at 6:15 pm | Posted in Uncategorized | Comments Off on Project Server 2010 Database Maintenance Plans #EPM #PS2010 #ProjectServer
Tags: , ,

Just a quick post to mention that Microsoft have now released documentation on the recommended SQL server database maintenance plans for Project Server 2010. SQL Server database plans are very important in keeping Project Server performing reliably and smoothly. Please see the link below for more information:

Office 2010 / SharePoint 2010 / Project Server 2010 Service Pack 1 (SP1) #SP2010 #SharePoint #ProjectServer

June 28, 2011 at 5:27 pm | Posted in Service Pack | Comments Off on Office 2010 / SharePoint 2010 / Project Server 2010 Service Pack 1 (SP1) #SP2010 #SharePoint #ProjectServer
Tags: , ,

Service Pack 1 for the Office 2010 products is now available, for information please see:

The link to the Project Server 2010 KB article is:

The link to the download is:

As always, deploy this to a Test / Development environment and test thoroughly before applying to Production, also have a full roll back plan in place for Production.


Project Server 2010 Project Site default fields #ProjectServer #PS2010

June 20, 2011 at 2:14 pm | Posted in Fixes | 3 Comments
Tags: , ,

Getting synch errors in the Project Queue relating the Reporting WSS sync? Link to task functionality not working? Risks and issues not showing in the reminders web part on the PWA home page? If you have any of these issues then it is quite likely that you have either edited or deleted some of the default fields from the Project Site’s Risks or Issues lists. The Risks, Issues, Deliverables lists are integral to Project Server so the best advise is to leave the default fields alone and create new fields to meet your requirements. It is possible to hide the default fields if required.

One question I see quite a lot of the time is “How can we fix this issue once we have deleted or edited a default field from the Project Site?” The answer is simple but would mean data loss if you want to fix the issue on a Project Site that already had list items on the default Issues, Risks and Deliverables lists. If the issue exists in the current custom Project Site template then this can be resolved easily without any data loss. For both scenarios please see the steps below.

To fix the issue if it exists in your latest custom Project Site template, navigate to PWA and click Site Actions > New Site, select the latest custom template, add a name and URL and click create. Navigate to your new site and delete the default Risks, Issues and Deliverables lists by going to the list settings for each list / library and clicking “Delete this list”.


Click Site Actions > Site Settings > Manage Site Features, scroll down to the “Project Sites Collaboration lists”


Click “Deactivate” and click ok the the warning. Once complete the page will reload the site features, this time click “Activate” next to Project Sites Collaboration Lists.


Running through these steps will recreate the default Risks, Issues and Deliverables lists with all of the correct default fields, any custom fields or changes made to default fields will not be re-applied. Now create any custom fields / views needed on the Risks or Issues list but remember do not touch the default fields or views. Once the template is complete save the site as a template and set as the default site template in Project Server following the usual process. This would have fixed the issues mention above for new Project Sites that are created from the new custom template but the issues will still exist on current project sites.

To fix the issues on current project sites would mean that some data loss will occur. Any list items on the default Risk, Deliverables or Issues list will be lost and not recreated. To fix the issues on existing sites the same process applies as outline above but rather than creating a new site you will need to navigate to the Project site in question then delete the default Risks, Deliverables and Issues lists (remembering that the list items will be lost). If the list items are required, export the lists to Excel first, then you have a copy that can be used to create the items again manually once the lists are recreated. Once the default Risks, Deliverables and Issues lists have been deleted, click Site Actions > Site Settings > Manage Site Features. Deactivate the “Project Sites Collaboration Lists” feature then activate. As mentioned earlier this will recreate the default Risks, Deliverables and Issues lists with all of the default fields. This process will need to be repeated on all Project Sites where you want to resolve the issue and where you are happy to lose the existing Risks, Deliverables and Issues.

I would recommend that this process is carried out on test environment prior to production so that you are happy with steps outlined above.

Project Server 2010 Grid issue

June 20, 2011 at 1:19 pm | Posted in Issue | Comments Off on Project Server 2010 Grid issue
Tags: , ,

I would just like to share my findings with the behaviour of the Project Server 2010 grids. I was recently investigating an issue raised on one of the Project Server forums and thought I would blog the issue and workaround in case anyone comes across this in future. The issue is that the header rows don’t load correctly if you zoom your Internet Explorer window below 99%. Each grid behaves differently, the Project Centre grid will add an extra header row on the left hand side of the grid as shown below so that the Gantt row no longer aligns with the correct Project detail rows:


On the Tasks page, an extra row is added on both sides of the divider, but the rows are not level as seen below, Process Status and Mon 13/06 are positioned mid rows:


The Resource Centre also adds an extra header row as seen below:


This behaviour can be resolved by increasing the Internet Explorer zoom level to 99% or higher.

Hopefully that will help resolve this annoyance for anyone that has come across this issue Smile

« Previous Page

Create a free website or blog at
Entries and comments feeds.