Quote:
Originally Posted by agriffin  I am sorry about the terminology mishap, I did not pull away from the client's terminology and back into project terminology. The Project Publish jobs is completing successfully, but the PWA is not updating. This can be replicated. Projects are both published by users and also by a nightly applicaiton that uses the PSI. I looked at the Queue and there weren't any failed jobs in there or anything that has been pending for awhile. | No problem at all -- please don't apologize. I simply wanted to ensure that we were both talking about the same thing.
Did you make sure you adjusted the History in the Manage Queue page? By default, it only shows the current date... I typically set it back -1 year (regardless of whether that's a valid date or not) to ensure that I retrieve all relevant data.
I must say that your problem is very interesting... I have the following questions: - When you republish yourself, does rogress ever fail to show?
- In an instance when progress is not showing correctly, have you opened the project from the Published store to ensure the data is all there?
- Is there any pattern to the symptoms (e.g. do PSI republishes not work, do only certain users experience this problem)?
- What patchlevel are you running?
- What is your topology like (e.g. deployed in a four-server MOSS farm, single server, one WFE with a DB)?
- How long have you waited for progress to show before republishing?
__________________ Stephen Sanderlin
Founder/Owner - EPMFAQ
VP of Technology - MSProjectExperts
Microsoft Project MVP If you found this message useful, please click the Thanks button in the post!
This electronic message, along with any information, advice, and opinions it contains, are mine alone and are not representative of my employer. All information is provided in "GOOD FAITH" and on an "AS IS" basis only. I provide no presentations or warranties, express or implied, including implied warranties of fitness for a particular purpose, merchantability, title, and noninfringement. I strongly advise you to extensively test any changes, workarounds, or techniques described herein on a development system prior to implementation in a production environment, and you are hereby notified that I bear no responsibility whatsoever for any loss, harm, or otherwise negative outcomes resulting from your actions, whether or not said actions were a result of this electronic message, directly or indirectly.  |