Publish hangs at 93% and fails - Description and solution

[Gil]

Hi,
I thought I will share the problem and solution we experienced
lately, hoping it will help others.

We are using Project server 2007 with Infrastructure update.
In many Projects, publish was hang at 93%, then fails, then blocking
the queue, with error messages like:
ProjectPublishFailure
UpdateSRAMessage (Summary Resource Assignment)
NullReferenceException: Object reference not set to an instance of an
object (this one is from logs our IT retrieved).

We tried many suggestions from this groups: Unpublished all
assignments (problem wasn't there), exporting to XML and importing
back (didn't help) and more..

We had to open a ticket with Microsoft, and they have solved this
issue:
They run the following query on our published database:

select * from MSP_ASSN_ENTERPRISE
where proj_uid='11111111-1111-1111-1111-111111111111'
and assn_finish_date > '2049-12-31 17:00:00.000'

This returned two faulty assignments, which their finish date was
greater than year 2049 (We have encounter this before, as a result of
the "spread actual work" bug, which is suppose to be fixed now).
Then they run another query on this database, in order to delete this
assignments (after making a backup to the database):

delete from MSP_ASSN_ENTERPRISE
where proj_uid='11111111-1111-1111-1111-111111111111'
and assn_finish_date > '2049-12-31 17:00:00.000'

After this action, all project were successfully published.
Gil.

 

[ProjmanZA]

Hi,
I thought I will share  the problem and solution we experienced
lately, hoping it will help others.

We are using Project server 2007 with Infrastructure update.
In many Projects, publish was hang at 93%, then fails, then blocking
the queue, with error messages like:
ProjectPublishFailure
UpdateSRAMessage (Summary Resource Assignment)
NullReferenceException: Object reference not set to an instance of an
object (this one is from logs our IT retrieved).

We tried many suggestions from this groups: Unpublished all
assignments (problem wasn't there), exporting to XML and importing
back (didn't help) and more..

We had to open a ticket with Microsoft, and they have solved this
issue:
They run the following query on our published database:

select * from MSP_ASSN_ENTERPRISE
where proj_uid='11111111-1111-1111-1111-111111111111'
and assn_finish_date > '2049-12-31 17:00:00.000'

This returned two faulty assignments, which their finish date was
greater than year 2049 (We have encounter this before, as a result of
the "spread actual work" bug, which is suppose to be fixed now).
Then they run another query on this database, in order to delete this
assignments (after making a backup to the database):

delete from MSP_ASSN_ENTERPRISE
where proj_uid='11111111-1111-1111-1111-111111111111'
and assn_finish_date > '2049-12-31 17:00:00.000'

After this action, all project were successfully published.
Gil.

Thanks Gil ,

Not to be a party pooper , i would just like to warn other users to
excerise extreme caution when directly Deleting / Changing in a
DataBase Table. This should only be done as a last resort.

Andre

 

[Shivaji Neogi]

Many Many Many thanks for the information you provided.
We had changed our calendar settings causing some task finish dates to move
to year 2050. Did not think this was causing the above problem until I read
your solution. I split my hair for 2 days trying to publish without success.
Your solution works and makes sense. I also understand that one has to be
careful with the delete queries run in the database. I manually went to the
project plan and changed the dates back to the correct dates. Once all the
dates were under year 2050, the project published without any issue.