Multi-language and non-English Project Server instances can be updated again


Good news!

Multi-language and non-English Project Server instances can be updated again with the latest cumulative update packages. The December 2011 Cumulative Updates fixes the issue introduced in the June 2011 CU that caused non-English PWA instances to show English headers the Project Center page, My Tasks page and Resource Center page regardless of the selected language.

This issue has been fixed in the December 2011 CU.
In addition, the August, October and December 2011 also contain some fixes for other common problems. For a complete list of fixes see this article: http://msepm.hsquared.be/?p=294

So now you can safely update your non-English Project Server instance with the latest updates available for Project and Project Server.
You can find the December 2011 CU on these pages:

Microsoft Project 2010 and Project Server 2010 known issue list: December 2011


Find below an updated Excel file containing all the known issues for Microsoft Project 2010 and Microsoft Project Server 2010, up to and including the fixes from the December 2011 Cumulative Update.
I will update the file as new updates are released. So make sure you are downloading the latest version!

==> EPM2010 Known Issues (Click here if you have problems opening this file)

Information about Service Pack 1
A complete list of all issues fixed in Service Pack 1 for Project and Project Server 2010 is available from the Microsoft download center:
-> Microsoft Office 2010 Service Pack 1 Changes
-> Microsoft SharePoint 2010 and Office servers Service Pack 1 Changes

To verify the version of your Project Server environment or check the version after updating, see this excellent article written by Brian Smith:

http://blogs.msdn.com/b/brismith/archive/2010/09/23/how-to-tell-which-cumulative-update-hotfix-or-service-pack-version-of-project-server-2010-and-project-2010-you-are-running.aspx

The description on the individual hotfix pages lists the issues that have been fixed in the hotfix. So you have to browse through all the individual hotfix pages to find all known issues.

Secure Store Service: Cannot generate a Secure Store Service key


After starting the Secure Store Service service and creating the Secure Store Service service application, the first step is to generate a new key. But this might fail with following error:

An error occurred during the “Generate Key” process. Please try again or contact your administrator.

InĀ  addition, in the Windows Application event log, following message is logged:

The Secure Store Service application Secure Store Service is not accessible. The full exception text is: Cannot open database “Secure_Store_Service_DB_<ID>” requested by the login. The login failed.
Login failed for user “domain\user”

You might get this error if you changed the Secure Store Service application pool service account.
The user account used for the application pool under which the Secure Store Service service application is running needs to have db_owner access to the Secure Store Service database.

To resolve this issue, you need to grant db_owner access for the application pool account referenced in the error message. Or you can let SharePoint take care of it:

  • Go to Central Administration -> Application Management -> Manage service applications
  • Select your Secure Store Service service application and click Properties
  • Do not make any changes and simply click OK
  • SharePoint will reconfigure your Secure Store Service and grant db_owner access to the application pool account.

Verify that the account has been granted db_owner permissions on the database. If not, you need grant db_owner permissions manually.

You should now be able to generate the key.

Microsoft Project 2010 and Project Server 2010 known issue list: October 2011


Find below an updated Excel file containing all the known issues for Microsoft Project 2010 and Microsoft Project Server 2010, up to and including the fixes from the October 2011 Cumulative Update.
I will update the file as new updates are released. So make sure you are downloading the latest version!

==> EPM2010 Known Issues (Click here if you have problems opening this file)

Information about Service Pack 1
A complete list of all issues fixed in Service Pack 1 for Project and Project Server 2010 is available from the Microsoft download center:
-> Microsoft Office 2010 Service Pack 1 Changes
-> Microsoft SharePoint 2010 and Office servers Service Pack 1 Changes

To verify the version of your Project Server environment or check the version after updating, see this excellent article written by Brian Smith:

http://blogs.msdn.com/b/brismith/archive/2010/09/23/how-to-tell-which-cumulative-update-hotfix-or-service-pack-version-of-project-server-2010-and-project-2010-you-are-running.aspx

The description on the individual hotfix pages lists the issues that have been fixed in the hotfix. So you have to browse through all the individual hotfix pages to find all known issues.

Microsoft Project 2010 and Project Server 2010 known issue list: August 2011


Find below an updated Excel file containing all the known issues for Microsoft Project 2010 and Microsoft Project Server 2010, up to and including the fixes from the August 2011 Cumulative Update.
I will update the file as new updates are released. So make sure you are downloading the latest version!

==> EPM2010 Known Issues (Click here if you have problems opening this file)

Information about Service Pack 1
A complete list of all issues fixed in Service Pack 1 for Project and Project Server 2010 is available from the Microsoft download center:
-> Microsoft Office 2010 Service Pack 1 Changes
-> Microsoft SharePoint 2010 and Office servers Service Pack 1 Changes

To verify the version of your Project Server environment or check the version after updating, see this excellent article written by Brian Smith:

http://blogs.msdn.com/b/brismith/archive/2010/09/23/how-to-tell-which-cumulative-update-hotfix-or-service-pack-version-of-project-server-2010-and-project-2010-you-are-running.aspx

The description on the individual hotfix pages lists the issues that have been fixed in the hotfix. So you have to browse through all the individual hotfix pages to find all known issues.