Hi,
Hopping someone can help with this.
I have a user who's plan keeps failing to publish with the known error below:
____________________________________________________________________________
ReportingProjectChangeMessageFailed (24006) - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID". The conflict
occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmTask". The statement has been terminated..
GeneralQueueJobFailed (26000) - ReportingProjectPublish.ReportProjectPublishMessageEx
____________________________________________________________________________
I have followed Brian Smith's fix - http://blogs.msdn.com/b/brismith/archive/2012/05/01/project-server-2010-orphan-baselines-breaking-the-reporting-publish.aspx - by detecting orphaned baselines in the Draft DB and deleting them from both Draft and
Published, however issue persisted when user published project plan again.
We eventually decided to save the plan locally, delete server copy and publish the (saved) local copy. This worked for approx a week where noticed that user had managed to publish twice successfully.
Issue recurred again as above and I'm now lost for ideas.
User advises the changes he makes are as follows:
- Copy task summary (package) with x number of tasks underneath it, including external links which are greyed out, some of which can be inactive.
- Paste the copied data to the next line; which in turn makes the external links active and adds them as extra tasks to the task summary.
- Deletes the extra tasks.
- Proceeds to publish and gets above error.
While going through the pan with him, I also noticed that some of the external links i.e. those greyed out had a prefix of ERR i.e. ERR <Project_name>
Please Help!
Thanks