PWA 2007 Publish project error

[Tony]

Hi,

I was wondering is someone could help with an error we are getting when
loading a new project onto PWA2007. We have loaded projects before with no
errors lke this. We have set this up to publish a workspace using our
template, which has worked previously. Here is the error message, any help
would be appreciated:

Your ProjectPublish job failed. Its current state is Failed. It was 93%
complete. It entered the queue at 05/17/2007 18:27:07.

To get more information about the job failure, please go to Project Web
Access. Select Personal Settings from the left menu. Then select My Queued
Jobs.

The errors returned from the queue are as follows:
Error ID: 23000
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="">
<error id="23000" name="ProjectPublishFailure"
uid="541fa39e-fbfd-49f1-910d-e7c40dc71871"
projectuid="0c569eb8-8b06-4585-96ad-4cb6d96771fe"
messagetype="Microsoft.Office.Project.Server.BusinessLayer.QueueMsg.UpdateSRAMessage" messageID="177" stage="" blocking="Block" />
</class>
<class name="Queue">
<error id="26000" name="GeneralQueueJobFailed"
uid="f0fad77d-132d-4181-833d-4b025314a3fa"
JobUID="4f05684d-4020-4b56-b767-28aaa1bc786e" ComputerName="MELBNSHAREPOINT"
GroupType="ProjectPublish" MessageType="UpdateSRAMessage" MessageId="177"
Stage="" />
</class>
</general>
</errinfo>

 

[Mike Mahoney]

Tony

In my experience this is symptomatic of a problem with a resource
assignment, generally the imported data has a problem which is not picked up
by MSP but causes problems when saving or publishing to the project server.
I use two mechanisms to resolve the issue:
1) Save the plan to an xls format using msp wizard then reopen and save back
to ps 2007 format.
2) In existing plan display the publish field which will be set to Yes. Set
it to No for all tasks and publish the plan. Progressively set No's to Yes's
until publish fails. Then consider the corresponding assignments.

Painful

Mike

 

[Michael Brown]

Mike / Tony

Have you found this to work successfully? I've found a few plans the past
few days that I 've had to with this exact same situation. Plan seems fine
for a while and then all of a sudden we can't publish the plan - period.
Same error message.

Mike - what is the point of saving to Excel and then back to ps2007 format
in your solution - could you just display the 'published' field - set it to
no and republish? In your solution - are you ending up with an entirely new
plan? I don't want to lose actual hours posted to the plan - in either the
plan or the time reporting tables etc.

Any detailed information you can provide is GREATLY appreciated.
email: (e-mail address removed)
thanks!
- Michael Brown

 

[mike.mahoney]

Mike / Tony

Have you found this to work successfully? I've found a few plans the past
few days that I 've had to with this exact same situation. Plan seems fine
for a while and then all of a sudden we can't publish the plan - period.
Same error message.

Mike - what is the point of saving to Excel and then back to ps2007 format
in your solution - could you just display the 'published' field - set it to
no and republish? In your solution - are you ending up with an entirely new
plan? I don't want to lose actual hours posted to the plan - in either the
plan or the time reporting tables etc.

Any detailed information you can provide is GREATLY appreciated.
email: (e-mail address removed)
thanks!
- Michael Brown






- Show quoted text -

Michael

Sorry for the slow response. Publish issues often relate to a resource
assignment which is not a problem for MS Project but causes a problem
with project server. Where there is a "minor" corruption saving the
plan to a different format will generally remove the bad data (e.g xl
export). You can save the imported xl plan over the previous plan.
Actual hours will stay with the plan though you may have to re-enter
enterprise data.

regards

Mike

 

[jim]

This "fix" worked great for us when nothing else would. Even though we
have an old version of Excel on our workstations, the saving to an
Excel file and then re-importing did the trick. We had exactly the
same symptoms, down to the error number (23000, 26000, MessageID 177)
and the percentage of completion (93%).

We did have to re-associate the Enterprise resources with the resource
names, but it was a matter of clicking "yes" for each resource.