Tags: EPM, Project Server 2010, PS2010
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 #ProjectServerJune 28, 2011 at 5:27 pm | Posted in Service Pack | Leave a comment
Tags: EPM, Project Server 2010, SharePoint 2010
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.
Tags: EPM, Project Server 2007, Project Server 2010
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.
Tags: EPM, Project Server 2010, PS2010
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