Forced Project Checkin (MSPS07)

  • Thread starter Ray Chiu (a1ahardware.florida at gmail)
  • Start date
R

Ray Chiu (a1ahardware.florida at gmail)

I have a project that is now read only and I have been trying to force a
check in (through PWA: Server Settings page, click Force Check-in Enterprise
Objects). This process is outlined here:

http://office.microsoft.com/en-us/projectserver/HA100998001033.aspx

"Manage Check-ins" permission is granted and should allow me to force check
in of this project (no luck so far).

I went to delete the Enterprise project, but PWA says I must forcibly check
it in first. Dohhhhh!

Is there any other consideration that I have missed? What do I need to do
to check in this project?
 
M

Marc Schoeni

Ray,

ASAIK this is one of the bigger bugs of the new product. We have one or
several projects like this in almost every installation of MOPS 2007. You
might want to restart the 'Microsoft Office Project Server Queue Service'
running on your Project Server.

If that doesn't solve the problem you might have to open the project in
read-only mode, export as an MPP/XML file and then re-import it to the
Project Server using another name.

Hope this helps...

Marc
MCP for EPM
www.diventis.ch
www.msepm.blogspot.com

"Ray Chiu (a1ahardware.florida at gmail)"
 
R

Ray Chiu (a1ahardware.florida at gmail)

I am not sure how to restart the queue.

PWA's 'Manage Queue ' page allows me to only Select, View & Cancel Jobs.

I did not see a mechanism for restarting the queue in the PWA's other Queue
page (Queue Settings). Do you have detailed instructions or a URL that can
provide guidance to restart the queue?

Thank you,
Raymond

BTW, does ASAIK mean: 'As Soon As I Know'?
 
R

Ray Chiu (a1ahardware.florida at gmail)

Marc,

We have an expression here in US, 'You're the man!'. Thank you for pointing
out the restart of the Queue. After restarting the Queue the projects were
checked back in.

It would good to know why the queue did not execute the task and be able to
take some kind of preventative measure to avoid the problem.

Again, thank you.

Raymond
 
S

Sharry Heberer [MSFT]

Hi Ray,

I see that your issue is resolved, but in case this helps for future
reference... The behavior you were seeing is likely not a bug, but
intentional in the design of the Queue.

If your project had any job in the queue that had failed and blocked or was
in "getting enqueued" state, then you need to resolve the issue that is
blocking the project in the first place, or cancel the enqueuing of the
incomplete job first.

If the problem was that the project was stuck in "getting enqueued" state,
then you need to find that job, select it by placing a checkmark next to it,
expand the Advanced Options section, put a checkmark in the box that says
"cancel jobs getting enqueued," then click the Cancel Jobs button. At that
point you would need to resubmit the force checkin and it should be
processed as normal.

If the problem was that the project had a failed/blocking job which was
preventing further processing on that job, then you need to simply select
that offending job and hit the Cancel Jobs button. The resubmit the force
checkin and it should go through.

Also, the reason you couldn't delete the project is that a) the project was
checked out, but also, b) no jobs for this project were being processed
anyway, so even if a) was not a factor, the deletion of the project still
would not have gone through the queue in this situation.

Why does it work when you restart the queue? Well, when the queue starts
up, it detects jobs which were not completely sent in and deals with them so
that they are not a factor anymore. This is why after restarting the queue
your jobs were able to be processed. This is only a failsafe measure,
however, and best practice is to knowingly deal with your stuck queue jobs
as I described above, so that you are aware of the issues your server is
facing.

HTH,
Sharry

"Ray Chiu (a1ahardware.florida at gmail)"
 
P

PedroJose

Ray, Ihave exactly the same issue!!!! How do I restart the queue
service???? Please help!

thx.

HF
 
R

Rod Gill

I run the following nightly (well before the cube rebuilds):


@echo STOP the P12 Queue
net stop "Microsoft Office Project Server Queue Service"

@echo START the P12 Queue
net start "Microsoft Office Project Server Queue Service"



Create a windows schedule task {control panel, schedule tasks} which runs
the above batch file nightly. Make sure it runs at a time when other
scheduled jobs AD sync, Cube Build Service are not running. Run the
scheduled job with the security credentials of user in the local admin
security group.



--

Rod Gill
Project MVP

Project VBA Book, for details visit:
http://www.projectvbabook.com

NEW!! Web based VBA training course delivered by me. For details visit:
http://projectservertraining.com/learning/index.aspx
 
P

PedroJose

Thanks!!

to do it once manually, do I go to the project server application server and
look for the queuing service properties I gues??
 
J

Jonathan Sofer

To do it manually you would log onto the Project Server front end server and
go to the services and look for the Micrsofot Office Project Server Queue
Service and restart it there.

Jonathan
 
P

PedroJose

I am completely at a loss here..... I had this issue last night, then
after reading these posts, I restarted the queue and nothing happened for a
while, but after a couple of hours it worked.... Does restarting the queue
service dumps all these 'stuck' jobs immdeiately??? This afternoon, I
was updating tasks and republishing when one of the projects gave me a 'can't
save' message, now it is stuck in 'waiting to be processed', and two other
projects also 'got stuck' on the same state. Can't force check them in, so I
have asked that the queue service be restarted (hoping that this would solve
this issue), but it now looks like nothing has happened again... not sure if
later at some point, these jobs are going to be cleared due to restarting the
queuing service. Can anyone please help? Is restarting the queue service
supposed to clear these jobs immediately??? (oh, I've also cleared the
cache...)

thanks.
 
J

James Fraser

I am completely at a loss here..... I had this issue last night, then
after reading these posts, I restarted the queue and nothing happened for a
while, but after a couple of hours it worked.... Does restarting the queue
service dumps all these 'stuck' jobs immdeiately??? This afternoon, I
was updating tasks and republishing when one of the projects gave me a 'can't
save' message, now it is stuck in 'waiting to be processed', and two other
projects also 'got stuck' on the same state. Can't force check them in, so I
have asked that the queue service be restarted (hoping that this would solve
this issue), but it now looks like nothing has happened again... not sure if
later at some point, these jobs are going to be cleared due to restarting the
queuing service. Can anyone please help? Is restarting the queue service
supposed to clear these jobs immediately??? (oh, I've also cleared the
cache...)
Click to expand...

I don't know that restarting the Queue will dump many of the jobs if
they previously failed. In my experience, 95% or more of those will
fail even after the Queue Service is restarted.
Is it possible that you saw those clear out of the queue history
around midnight? The queue history defaults to showing only the
current days jobs. Expand the history section to change the date
range.


James Fraser
 
P

PedroJose

Well, I looked at the log and open the advance options for the queue
management page, and selected the cancel jobs getting enqueued. Then cancel
the job that had the message "getting queued" and it cleared all other jobs.
Now the plans are checked back in. So the issue is fixed for now. I am now
just very nervious about what could happen, seems that you have to be
soooooooo careful with this tool. I have just deployed this at my company
and really hope nothing else major 'breaks'.....

Thank you very much for the help!! :)
 
C

Chris

I have been trying to view the entire thread on this and several other
discussions at
http://www.microsoft.com/office/com...n-us&mid=e0de9405-1caa-4d1a-8e3b-5a4485c4ff4d.

When I click on each thread I get the following message: "Error on page" in
the status line at the bottom-left corner of the IE Window (IE 7.0.5730.11).
This happens whether or not I am logged in to the discussion group.

Could there be a problem with my IE settings, we get frequent 'helpful'
updates pushed down from out network administrators.

Anyone have ideas/suggestions about remedies for this?
 
Top