J
Jason
We have a homegrown application that interacts with project server. After
upgrading to projectserver 2007 and changing the application to work with it,
we get errors in the Queue.
The application uses the PSI and calls QueueUpdateProject.
When there are resources assigned to any summary task in the associated
project, the "Project Update from PSI" gets stuck in the queue with state:
"Failed and Blocking Correlation". The Project Checkin, Project Publish, and
Project Publish Notifications are all stuck behind it with status: "Blocked
Due to a Failed Job".
If I cancell the blocking job, force checkin the project, then open it and
remove any resources assigned to summary tasks and republish, the command
then works just fine.
I know that assigning resources to a summary task is not "best practice",
however MS Project allows it, so in my opinion this shouldn't cause errors
when updating through the PSI.
Any ideas? this is a huge issue for us.
Thanks!
upgrading to projectserver 2007 and changing the application to work with it,
we get errors in the Queue.
The application uses the PSI and calls QueueUpdateProject.
When there are resources assigned to any summary task in the associated
project, the "Project Update from PSI" gets stuck in the queue with state:
"Failed and Blocking Correlation". The Project Checkin, Project Publish, and
Project Publish Notifications are all stuck behind it with status: "Blocked
Due to a Failed Job".
If I cancell the blocking job, force checkin the project, then open it and
remove any resources assigned to summary tasks and republish, the command
then works just fine.
I know that assigning resources to a summary task is not "best practice",
however MS Project allows it, so in my opinion this shouldn't cause errors
when updating through the PSI.
Any ideas? this is a huge issue for us.
Thanks!