Error Publishing Enterprise Projects Containing Budget Cost Assign

[luai7]

Whenever I try to publish an enterprise project that contains a Budget-Cost
resource assigned to its summary task (Row-0), I get the below error that
appears in the "My Queued Jobs". If I remove this assignment, publishing goes
allright!!

Any Ideas??

Error summary/areas:
Queue
GeneralQueueJobFailed
Error details:

<?xml version="1.0" encoding="utf-16"?>
<errinfo>
<general>
<class name="Queue">
<error id="26000" name="GeneralQueueJobFailed"
uid="f6bac563-093a-4c19-87d1-03db4ca9114e"
JobUID="fa278c7e-640d-42c2-8314-5a07af476d31" ComputerName="PROJSERV"
GroupType="PublishNotifications"
MessageType="ProjectPublishSendNotificationMessage" MessageId="1" Stage="" />
</class>
</general>
</errinfo>

 

[Dmitry]

I have the same problem

 

[Sushant]

I am facing a similar issue and I have not assigned the cost resource to the
Summary, were you able to find any resolution?

 

[luai7]

Hi Sushant,

Unfortunately I did not manage to solve this problem yet and I have not
received any help until now on this forum regarding this issue. Effectively,
this will prevent us from using this feature in our implementation of PS2007
for the year 2007-2008 :-(

To be honest, I am not sure if this is a bug or if there is something that
we have to do .... !!!

Any help regarding this issue from anyone is highly appreciated.

 

[Morten]

Hi luai7

We have the same problem and so far we have found two workarounds.
The problem seems to be that Generic Cost resources don't have an assignment
owner and therefore the all notifications will fail within the specific
project when a Generic Cost Resource is assigned to a task. I don’t
understand the logic in this and expect it to be a bug.

1. Workaround

Don’t setup smtp-mail account - this is not a valid option in our solution

2. Workaround

On the table MSP_ASSIGNMENTS in both the draft and published database we
have created a trigger changing values of the assignment owner

UPDATE MSP_ASSIGNMENTS
SET res_uid_owner=Null
WHERE res_uid_owner='00000000-0000-0000-0000-000000000000'

The above workarounds is not a supported way to fix the bug - but our only
way so far.