Project Server 2010: Orphan baselines breaking the reporting publish

re: Project Server 2010: Orphan baselines breaking the reporting publish

Brian Smith - MSFT — Fri, 07 Sep 2012 19:34:12 GMT

Yes Frank - it was fixed in the client CU support.microsoft.com/.../2598351. "•Assume that you open a project in Project Server 2010. When you save the project in a different file format, the project on the server contains orphan baseline records." As the bad orphan baseline records can be persisted in the local cache it is also a good idea when loading the June CU to the client to clear projects from the local cache - of course making sure they are saved and checked in first.

Best regards,

Brian.

re: Project Server 2010: Orphan baselines breaking the reporting publish

Frank Miranda, MCP — Fri, 07 Sep 2012 19:13:03 GMT

So was this issue resolved in the June CU? I just read through what was fixed in that CU and I don't see any reference to this issue as being resolved.

We are currently running the April CU and are experiencing the exact problems listed above. I've run the queries found 955 entries between two projects. I can do the clean up however I'd like to get a permanent fix. I just wanted to get verification that the fix is included in the June CU.

re: Project Server 2010: Orphan baselines breaking the reporting publish

Christoph Mülder (SOLVIN information management) — Fri, 18 May 2012 06:38:51 GMT

Hi Brian,

I can confirm the issue that DFS mentions. I just wrote an E-Mail to you with the case number opened some days ago.

Regards

Christoph

re: Project Server 2010: Orphan baselines breaking the reporting publish

_-DFS-_ — Fri, 04 May 2012 07:45:18 GMT

Hi Brian!

ok, i will try to open case, and after that e-mail to you.

Thank you.

re: Project Server 2010: Orphan baselines breaking the reporting publish

Brian Smith - MSFT — Thu, 03 May 2012 14:03:49 GMT

DFS - looking deeper into this one and it appears the issue relates to plans where there is a baseline that does not have a cost contour. Still digging to get a good definition of exactly when this can occur - but assume this might be for a baseline that has work but no cost. As mentioned we do have a fix coming along. So far we haven't seen this too often - it would certainly help if your company could open a support incident as it may help expedite the fix. Once you have an incident open then e-mail me at brian.smith@microsoft.com and loop me in with whichever engineer you are working with. As this is a bug (quote OfficeQFE 33270) there will be no charge (or there will be a refund/non-decrement) - depending on the type of case.

Best regards,

Brian.

re: Project Server 2010: Orphan baselines breaking the reporting publish

Brian Smith - MSFT — Thu, 03 May 2012 13:55:12 GMT

Hi Walter, it is possible in some cases that a reporting DB refresh will overcome these errors - but only in cases where there have been un-corrected failures earlier in reporting jobs - such that, for example, a custom field was used in a plan but for some reason the metadata for that field was never correctly sent to the reporting DB (usually due to a queue job that failed and should have been re-tried). In thsi type of case your solution would work. What we are talking about with these cases are bugs that will NOT be overcome with an RDB refresh - and in fact as DFS points out - it will mean he is in a worse state than before - as now he will have many more fialed jobs and a more incomplete reporting database.

Please only offer solutions where you are confident that your answer is the correct one.

Best regards,

Brian.

re: Project Server 2010: Orphan baselines breaking the reporting publish

_-DFS-_ — Thu, 03 May 2012 06:12:27 GMT

Thank you, colleagues.

dear Brian!

i'm instaling all CU) but after February CU we didn't have this error...

i'm expecting your full blog posting with description

Walter, it's not good idea))

now i have about 2000 tasks which ended with errors

have a nice day!

re: Project Server 2010: Orphan baselines breaking the reporting publish

Walter Castillo Castillo — Thu, 03 May 2012 00:06:56 GMT

(Comment from Brian Smith - although Walter's solution can work in certain scenarios when this error appears - it is not applicable to these conditions - see my full reply to Walter below)

Hi DFS, I had same error on 2007 and 2010 like you, not the same error reported up.

Yo can recreate the Reporting Database.

1. Make an Administrative Backup of the Custom Fields

2. Restore the Custom Fields

This will take significant time, so do this on a nonworking time and don´t let it alone, stay monitoring the Project Server Jobs to certain it finish well.

Hope this help you.

Regards

WCC

wcastillo@epmworks.com

re: Project Server 2010: Orphan baselines breaking the reporting publish

Brian Smith - MSFT — Wed, 02 May 2012 13:50:45 GMT

Hi DFS, this certainly isn't the issue you are facing so not suprised the select returned NULL. However, in researching I found an issue I hadn't been aware of with the same error which has been occuring for customers since the February CU 2012 for Project Server 2007 was released - so I am assuming you hadn't loaded that one but just loaded the April one (which would include the same problem). The issue relates to a fix we did in February for baseline costs where it is missing a NULL check so can get the error you mention. We should be releasing a fix for this with the June CU - but I will try and find out if we have a workaround - the only one I see currently is to remove the baseline - which I'm guessing will not a be a good option for many of our customers. Sorry for the inconvenience this has caused you. I will probably do a full blog posting on this issueonce I have more information.

Best regards,

Brian.

re: Project Server 2010: Orphan baselines breaking the reporting publish

_-DFS-_ — Wed, 02 May 2012 06:58:51 GMT

good day Brain!

I fased similar situation for MOPS 2007 after installation April CU.

Standard Information:PSI Entry Point:

Project User:

Correlation Id: b0df3541-e9e2-442a-ae62-553d07d9139f

PWA Site URL: http://.../pwa

SSP Name: SharedServices

PSError: ReportingProjectChangeMessageFailed (24006)

RDS: The request to synchronize change(s) to project Project UID='fa51b8e3-9b78-4cf3-9890-75cf2af4d91f'. PublishType='ProjectPublish' failed.

Message: 'ReportingProjectChangeMessageFailed'

Error:Object reference not set to an instance of an object.

I receive such mistake at the publication of each\any project.

your select for draft DB returned NULL)

have you any ideas?