Delay between republish and PWA update

M

MaryS

We're seeing some strange occasional delay between the time a PM accepts task
updates from Team Members, (and, of course, saves the project and republishes
the assignments to the web) and the time the Team Members (or anyone) sees
the changes in PWA.

I've seen the updates appear almost immediately, but another PM published
his updates and reported having to wait almost an hour for the web changes.
Aside from user error (not saving the updates, not republishing, not
refreshing the web page), is there some reason why these updates are taking
so long to show up in PWA?

Not sure whether this is related, but we had another instance of a Team
Member updating tasks, pressing "Update All", getting the message that the
updates would be sent to the PM, and finding out the next day that the PM
never received the email and did not have the tasks in his update queue.
When he repeated the steps the next morning, the email and updates were
almost immediate. May be a totally different issue.

We're using Project 2003, and the database and web server are on the same
physical server.

Can anyone point me toward some logical cause? Couldn't find anything in
the group discussions.

Thanks.
 
G

Gary L. Chefetz \(MVP\)

Mary:

It's not uncommon at all for there to be a processing delay in the system.
These are caused by a backup in the views processing folder. Sometimes this
is an indication of a large amount of activity, or very large project plans,
or badly maintained project plans.

Your second instance sounds like the user didn't really complete the
transaction.

--

Gary L. Chefetz, MVP
"We wrote the book on Project Server
http://www.msprojectexperts.com

-
 
M

MaryS

Thanks, Gary.

The PM who noticed the delay has a huge plan, and mine was a tiny test plan
- so your explanation makes sense for both.

And on the second problem, I did not see the team member actually perform
the update, so I can't confirm that he really did. We'll watch for something
more repeatable....and I suspect we won't find it.

I appreciate your quick answers. And I'm looking forward to the release of
the new Project Server 2003 book.....coming soon??

Mary

Gary L. Chefetz (MVP) said:
Mary:

It's not uncommon at all for there to be a processing delay in the system.
These are caused by a backup in the views processing folder. Sometimes this
is an indication of a large amount of activity, or very large project plans,
or badly maintained project plans.

Your second instance sounds like the user didn't really complete the
transaction.

--

Gary L. Chefetz, MVP
"We wrote the book on Project Server
http://www.msprojectexperts.com

-
Click to expand...
 
G

Gary L. Chefetz \(MVP\)

few more weeks.

--

Gary L. Chefetz, MVP
"We wrote the book on Project Server
http://www.msprojectexperts.com

-
MaryS said:
Thanks, Gary.

The PM who noticed the delay has a huge plan, and mine was a tiny test plan
- so your explanation makes sense for both.

And on the second problem, I did not see the team member actually perform
the update, so I can't confirm that he really did. We'll watch for something
more repeatable....and I suspect we won't find it.

I appreciate your quick answers. And I'm looking forward to the release of
the new Project Server 2003 book.....coming soon??

Mary
Click to expand...
 
D

Doug

Mary: I set up project so that I get an email when ever a resource updates
their tasks. Then in Outlook, I set up a rule to handle all the emails and
place them in a single folder. I now have a record of when a resouce has
updated their tasks.

Doug
 
M

MaryS

Thanks, Doug, good suggestion!

Our PMs are finding it hard to tell from the email which task(s) have been
updated. Would be nice to easily change the text of the email messages so
only the updated tasks are listed, but for now, it's simple enough to view
Updates in PWA.

Mary
 
Top