One problem that our customers appear to be running into is checking in projects. We do have a bug that appears to leave projects checked out when you wouldn't expect them to be. But I suspect that in many cases it may be that the architectural changes to 2007 have caused some of this confusion - and the default view of the queue may well hide the true cause of the problem.
So - check out these different scenarios to see if this covers your issues:-
- Project Professional says my project is checked out - but the server says it isn't. This is one we are looking at a hotfix for - but there is a simple workaround that seems to resolve in most cases. Open the project read-only, then close again. This seems to push through a check-in and then it can be opened read-write.
- The check-in says "Waiting to be Processed" and even using force check-in does not get it checked in. The force check-in option should really be called request check-in - as there is nothing forceful about it. It sinply puts a check-in request into the queue - but if the first one is just sitting there going nowhere then guess what - this second (third, fourth...) will not go any faster. The best approach for this type of error is to look in the queue for any outstanding jobs for the same project. If the problem happened yesterday (or before) then it may not show in the queue until you change the job history to include earlier dates. Many times we will hear "but the queue is empty..." which may just mean no failed jobs still sitting there from today - but the failure could have happenend last week or last month! Once you find the problem job then what should you do? Well, that depends on the nature of the job. If there is a save from Project Professional that is incomplete then getting the user who has the project checked out to open Project Professional and re-connect is the best approach. Cancelling a job of this type will lose data! Once you have resolved the initial issue and any other queued jobs for this project are processing (or cancelled if you really must) then the check-in should finally work.
- If your symptoms don't match these scenarios then you may need to log a support call to get this checked out (if you will excuse the pun).
UPDATE: Thanks to Ed Hanna and Brian Kennemer for bringing it to my attention - but it appears that closing Project using the X in the top right can lead to check-in issues. So best practice would be first to save and ensure that any communication with the server has completed (look in the status area after saving) and then using File, Close.
Technorati Tags: Project Server 2007