none
Project Publish failure messages (entity too large) RRS feed

  • Question

  • I am having multiple instances of the following error show up in the Queue when I look into jobs that have been classified as "Failed but not blocking correlation":


    The errors returned from the queue are as follows:
    Error ID: 24006
    Error ID: 26000


    Detailed error below - send it to the administrator for more detailed troubleshooting.


    <?xml version="1.0" encoding="utf-16"?>
    <errinfo>
      <general>
        <class name="Reporting message processor failed">
          <error id="24006" name="ReportingProjectChangeMessageFailed" uid="92e7e749-c069-e411-80de-005056806745" QueueMessageBody="Project UID='0c21706d-89f2-4035-89bd-7d88404288ab'. PublishType='ProjectPublish'" Error="Reporting publish failed. The entity '341f38b9-38d0-4040-aaf1-5d00882dddca' is too large" />
          <error id="24006" name="ReportingProjectChangeMessageFailed" uid="ea886553-c069-e411-80de-005056806745" QueueMessageBody="Project UID='0c21706d-89f2-4035-89bd-7d88404288ab'. PublishType='ProjectPublish'" Error="Reporting publish failed. The entity '341f38b9-38d0-4040-aaf1-5d00882dddca' is too large" />
          <error id="24006" name="ReportingProjectChangeMessageFailed" uid="f520786c-c069-e411-80de-005056806745" QueueMessageBody="Project UID='0c21706d-89f2-4035-89bd-7d88404288ab'. PublishType='ProjectPublish'" Error="Reporting publish failed. The entity '341f38b9-38d0-4040-aaf1-5d00882dddca' is too large" />
          <error id="24006" name="ReportingProjectChangeMessageFailed" uid="cf0b1a83-c069-e411-80de-005056806745" QueueMessageBody="Project UID='0c21706d-89f2-4035-89bd-7d88404288ab'. PublishType='ProjectPublish'" Error="Reporting publish failed. The entity '341f38b9-38d0-4040-aaf1-5d00882dddca' is too large" />
          <error id="24006" name="ReportingProjectChangeMessageFailed" uid="c19a9e8f-c069-e411-80de-005056806745" QueueMessageBody="Project UID='0c21706d-89f2-4035-89bd-7d88404288ab'. PublishType='ProjectPublish'" Error="Reporting publish failed. The entity '341f38b9-38d0-4040-aaf1-5d00882dddca' is too large" />
          <error id="24006" name="ReportingProjectChangeMessageFailed" uid="1f369b9b-c069-e411-80de-005056806745" QueueMessageBody="Project UID='0c21706d-89f2-4035-89bd-7d88404288ab'. PublishType='ProjectPublish'" Error="Reporting publish failed. The entity '341f38b9-38d0-4040-aaf1-5d00882dddca' is too large" />
        </class>
        <class name="Queue">
          <error id="26000" name="GeneralQueueJobFailed" uid="20369b9b-c069-e411-80de-005056806745" JobUID="e1d486e1-bf69-e411-80de-005056806745" ComputerName="84f99fe2-d82a-4bab-b8c9-a3d10bc8e620" GroupType="ReportingProjectPublish" MessageType="ReportProjectPublishMessageEx" MessageId="1" Stage="" CorrelationUID="cf1dcb9c-b494-f0bd-8e62-0b29d7073add" />
        </class>
      </general>
    </errinfo>

    When I search the database for the object associated with the entity ID, I'm finding that it has to do with tasks that are marked as milestones which may or may not have a zero duration and they also have resources on them.  I have done some testing to try to resolve the error with limited success.  In one case, changing the milestone flag from 'Yes' to 'No' has fixed the issue but that doesn't appear to work in all cases.  Has anyone run into this issue before?  If so, how did you manage to resolve it?


    • Edited by WMeierSNC Tuesday, November 11, 2014 5:10 PM
    Tuesday, November 11, 2014 5:10 PM

Answers

  • Hi

    The error message says "The entity '341f38b9-38d0-4040-aaf1-5d00882dddca' is too large" />"
    Check if the start and finish date of the tasks are beyond 1/1/1984 to 12/12/2049 ?

    Wednesday, November 12, 2014 4:20 PM

All replies

  • Hi

    The error message says "The entity '341f38b9-38d0-4040-aaf1-5d00882dddca' is too large" />"
    Check if the start and finish date of the tasks are beyond 1/1/1984 to 12/12/2049 ?

    Wednesday, November 12, 2014 4:20 PM
  • The scheduled start date is NULL for the record in the MSP_Tasks table and the scheduled end date is 12/31/2012. 
    Wednesday, November 12, 2014 5:06 PM
  • Krishnp nailed the answer.  Fixed the date and also apply the most recent Service Pack if possible.  This shouldn't happen but it does occasionally.

    Cheers


    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Thursday, November 13, 2014 11:59 PM
    Moderator