Project Server 2010 : Project Center "Unknown Error"

UPDATE:


OK, it has been released. Only in the server roll up package though


http://support.microsoft.com/kb/2598251


See below from Brian Smith:

Thanks Bram, Ricardo and others on the thread - the fix has already released, but I had been waiting for the KB which has only just gone live, http://support.microsoft.com/kb/2598251 .  The fix is also included in the server roll-up packagehttp://support.microsoft.com/kb/2597152.  It is not however included in the non-roll-up packageshttp://support.microsoft.com/kb/2597932 - and you will need to load the hotfix if you use that CU.  The other non roll up package -http://support.microsoft.com/kb/2597138 has been removed from the download site as the 2598251 fix includes everything that was in the 2597138 CU, plus the fix - so can be used in place of that Project Server only fix.

I am just researching what is happening with the clean-up scripts, as the fix will stop the problem happening, but will not clean up existing situations where the dupplicate data already exists.  I'll respond back here and also be doing a blog post shortly.

Best regards,

Brian.

Regards


Andre 




UPDATE:


It would seem like the "Duplicate" values issue might be caused by either the Oct 2011or Dec 2011 CU, as there has been multiple reports of this issue and it seem to have been confirmed as a bug, the bad thing is there is currently no ETA on the fix. For more information look here.


ISSUE:

Recently we have had an issue with our Project Center displaying a "Unknown" error. Not very helpful is it ?

I had a look in the ULS Logs and found this :

Exception occurred in method Microsoft.Office.Project.Server.BusinessLayer.Project.ProjectGetProjectCenterProjectsForGridJson Microsoft.Office.Project.Server.DataAccessLayer.FilterDal+FilterException: Error during filter query execution.   Query:     declare @ResUid UniqueIdentifier; set @ResUid = 6a113512-b8e9-4b00-946b-d5aa0370da33;  declare @PermUid UniqueIdentifier; set @PermUid = a120a079-75bc-4f0f-b376-3fb0ae9ac940;  declare @ViewUid UniqueIdentifier; set @ViewUid = 89cedcbe-a490-41fa-b250-1072b23eef23;  declare @P0 UniqueIdentifier; set @P0 = e2804b03-9932-45dc-b2b3-eaee70255708;  declare @P1 UniqueIdentifier; set @P1 = 05a5da48-bb66-43e2-820e-68c703436b47;  declare @P2 UniqueIdentifier; set @P2 = 1fd4f36a-ff57-4587-9829-6bc20029efff;  declare @P3 UniqueIdentifier; set @P3 = c523981a-928c-4982-a026-335c93e78156;    

I have removed a large part of the error to save some space here, but the answer is in the error above!

So when looking at the error i see a "FilterDal+FilterException: Error during filter query execution". So what i did is navigate to to Server Settings > Manage Views. I then checked which Project Center views have Filters applied by default on the view (Regardless if it is/was the applied view)I then removed the filter from the view(s).

After i removed the views and saved them and re-checked if i could go to Project Center, and suddenly the by now very Infamous "Unknown Error" is no longer there. If i then manually apply the filter to view it works ! I know its no ideal, but it's a work around so that users can browse the Project Center.

At this point in time i cannot say for certain what have caused the issues. But i can only speculate. We have had a corruption of a schedule due to issues with Outline Codes. It would seem (Once again i am speculating) that a "Known" issue is causing the corruption of the custom fields:(http://social.technet.microsoft.com/Forums/nl-BE/projectserver2010general/thread/236336b7-bbcb-4db3-9483-e4dd940aaff5 )

Have a look at the Image below, most of the fields are look-up codes, and note how they are duplicated even they  have not been created as "Multiple Selection" fields, like project Phase, Project Status etc,so somehow those fields got corrupted:

In a nutshell i Think these items might be related. The schedule actually opens and publishes but the issue seem to be on the Web whilst displaying the PDP, and then ultimately corrupting the filter in the Project Center Views. Even deleting the Project did not fix it though, but by know we know, once its broken something it's very difficult figuring out how to fix something that already broken, as apposed to prevent it from happening again.

I will test by deleting the Views and re-creating them again. If i find out more i will update this post. I hope someone might find some value in this.

Greetings

Andre