project will not check in

[anovak]

Friends,

I’ve got a situation that seems to be concerning one particular
project that just won’t check in. Its owned by another user
although I can access it as the Admin.

There were several jobs out there stacked up in queue for save/
checkin type activity that just wouldn’t move even after the queue was
restarted on the server.

I attempted to force a check in , but nothing happens. I’ve cleared
the local cache, but no impact. I’ve cancelled all the jobs out there
that were waiting in the queue and now the project still shows up in
the force check-in screen with a “Cancelled" status.

I seem to be able to open edit, publish other projects and the job
runs through the queue.

I’m afraid that this particular project has become corrupted somehow.
Only other thing I can think of is deleted it and restore it from the
online item level backup.

Any ideas / solutions?

Thanks,
Andy Novak
UNT

 

[Gary L. Chefetz [MVP]]

Andy:

It seems your conclusion is very likely. Are you using Administrative
backups? If not, setup a nightly schedule with reasonable retention to make
things more manageable in the future.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com


Friends,

I’ve got a situation that seems to be concerning one particular
project that just won’t check in. Its owned by another user
although I can access it as the Admin.

There were several jobs out there stacked up in queue for save/
checkin type activity that just wouldn’t move even after the queue was
restarted on the server.

I attempted to force a check in , but nothing happens. I’ve cleared
the local cache, but no impact. I’ve cancelled all the jobs out there
that were waiting in the queue and now the project still shows up in
the force check-in screen with a “Cancelled" status.

I seem to be able to open edit, publish other projects and the job
runs through the queue.

I’m afraid that this particular project has become corrupted somehow.
Only other thing I can think of is deleted it and restore it from the
online item level backup.

Any ideas / solutions?

Thanks,
Andy Novak
UNT

 

[anovak]

Andy:

It seems your conclusion is very likely. Are you using Administrative
backups? If not, setup a nightly schedule with reasonable retention to make
things more manageable in the future.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting:http://www.msprojectexperts.com
For Project Server FAQS:http://www.projectserverexperts.com


Friends,

I’ve got a situation that seems to be concerning one particular
project that just won’t check in. Its owned by another user
although I can access it as the Admin.

There were several jobs out there stacked up in queue for save/
checkin type activity that just wouldn’t move even after the queue was
restarted on the server.

I attempted to force a check in , but nothing happens. I’ve cleared
the local cache, but no impact. I’ve cancelled all the jobs out there
that were waiting in the queue and now the project still shows up in
the force check-in screen with a “Cancelled" status.

I seem to be able to open edit, publish other projects and the job
runs through the queue.

I’m afraid that this particular project has become corrupted somehow.
Only other thing I can think of is deleted it and restore it from the
online item level backup.

Any ideas / solutions?

Thanks,
Andy Novak
UNT

A colleague informed me of an advanced option ("Cancel jobs getting
enqueued" within the Manage Queue Jobsscreen) I had to use that
clears out jobs in the queue that are in a certain state that
otherwise wouldn’t cancel out. In this case the check in job for that
project was in the process of being queued when the “freeze”
happened. So, apparently that non-cancelled job in the queue was
keeping the project from checking in.

Once I cancelled again using this option, I was able to go into the
“Force Checkin” screen and actually force the project back in “for
real”.

Trick is to figure out what might have caused this to begin with.
Any ideas?

Thanks,
Andy Novak
UNT

 

[Gary L. Chefetz [MVP]]

Andy, I couldn't give you a better guess than "cosmic rays." Sorry my
friend, but you could study the ULS logs if you remember the exact times and
your the logs are still there.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

Andy:

It seems your conclusion is very likely. Are you using Administrative
backups? If not, setup a nightly schedule with reasonable retention to
make
things more manageable in the future.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting:http://www.msprojectexperts.com
For Project Server FAQS:http://www.projectserverexperts.com


Friends,

I’ve got a situation that seems to be concerning one particular
project that just won’t check in. Its owned by another user
although I can access it as the Admin.

There were several jobs out there stacked up in queue for save/
checkin type activity that just wouldn’t move even after the queue was
restarted on the server.

I attempted to force a check in , but nothing happens. I’ve cleared
the local cache, but no impact. I’ve cancelled all the jobs out there
that were waiting in the queue and now the project still shows up in
the force check-in screen with a “Cancelled" status.

I seem to be able to open edit, publish other projects and the job
runs through the queue.

I’m afraid that this particular project has become corrupted somehow.
Only other thing I can think of is deleted it and restore it from the
online item level backup.

Any ideas / solutions?

Thanks,
Andy Novak
UNT

A colleague informed me of an advanced option ("Cancel jobs getting
enqueued" within the Manage Queue Jobsscreen) I had to use that
clears out jobs in the queue that are in a certain state that
otherwise wouldn’t cancel out. In this case the check in job for that
project was in the process of being queued when the “freeze”
happened. So, apparently that non-cancelled job in the queue was
keeping the project from checking in.

Once I cancelled again using this option, I was able to go into the
“Force Checkin” screen and actually force the project back in “for
real”.

Trick is to figure out what might have caused this to begin with.
Any ideas?

Thanks,
Andy Novak
UNT