Publish job 0% complete. Expected Wait Time 0s

R

Richard

I have Project Server 2007 and Project Pro. 2007 installed on a 2003 terminal
server. Enterprise Options is configured in Pro. 2007 and works. I can launch
Pro. 2007 window by going New->Project in Project Center on PWA. But after I
save a project and publish, words in the subjet line show in status bar,
won't change and nothing gets published.
 
R

Robert

I have Project Server 2007 and Project Pro. 2007 installed on a 2003 terminal
server. Enterprise Options is configured in Pro. 2007 and works. I can launch
Pro. 2007 window by going New->Project in Project Center on PWA. But after I
save a project and publish, words in the subjet line show in status bar,
won't change and nothing gets published.
Click to expand...

Richard,

Unfortunetly this is quite common with Project Server 2007. Try
restarting the Project Server Eventing and Queuing Services and see if
that pushes things along.
 
R

Richard

Thanks Robert. That fixed it. I am now concerned about how often it happens.
I hope I don't have to manually or by script restart the two services every
day!
 
S

Sharry Heberer [MSFT]

From your description it sounds like something is wrong with Project Pro, or
maybe the Active Cache in Project Pro. What you did by restarting the Queue
was to force the Queue to drop the save or publish job that Project Pro was
sending to the Queue so that it would essentially "unblock" the project so
that other jobs for the project will continue to be processed (but jobs for
other projects should have been moving along just fine). So essentially
when you restarted your Queue, you lost a job (data). I have posted proper
Queue troubleshooting techniques on this newsgroup several times - perhaps
you might want to review those before blindly restarting your Queue each
time. From my experience, at least 90% of the time someone complains of
"queue problems" the queue is actually behaving as designed, and the real
problem is some data in a project or some problem with Active Cache, etc.
Proper Queue education/troubleshooting will help to identify these trouble
spots to avoid any daily running of scripts to restart any services (which
is completely not recommended) or do some other special processing.
 
R

Richard

Thanks Sharry. I was new to this newsgroup. But I did find your previous
postings. They are pretty helpful.
 
S

Sharry Heberer [MSFT]

Great! Well I'd be happy to help further if those techniques don't work for
your particular problem.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
 
Top