Force Check-in Enterprise Objects page is not working

Hi Again

last week i got a very strange support request form one of my clients that says (we wanted to force check in a project we went as instructed Server settings under database administration clicked on Force Check-in Enterprise Objects link and we got the error below)

This is a Project Server 2010 installation .

it wasn't a security issue , or SharePoint problem , i started digging in the ULS log and found the entry below

Exception occurred in method
Microsoft.Office.Project.Server.BusinessLayer.Admin.AdminReadCheckedOutEnterpriseProjects
System.IndexOutOfRangeException: Index was outside the bounds of the array. at Microsoft.Office.Project.Server.BusinessLayer.Admin.ReadCheckedOutEnterpriseProjects()
at Microsoft.Office.Project.Server.Wcf.Implementation.
PWAImpl.AdminReadCheckedOutEnterpriseProjects()

The problem
in my case the EGlobal project was checked out to a user that was deleted form the system causing the method to return an exception, in other cases it might be another project in this case it will be a bit more complicated to discover if that was the case leave me a comment will answer it for you

Solution is two parts
PLEASE PLEASE PLEASE PLEASE Take a back up of all of your databases before you start
1- the quick fix (Not supported by Microsoft)

run the script below against your published database , this will reset the checked out by column (basically
force check-in)

UPDATE [MSP_PROJECTS]
SET PROJ_CHECKOUTBY=null
WHERE PROJ_NAME='EGlobal'

2- the second and most important please install the latest updates by Microsoft


hope that helps

Malek

PDP Security

Hi ,

Im a bit in a rush so i will keep this simple and straight forward

A client asked me if they can hide a Project Detail Page (PDP) from certain users, i know that there is no out of the box settings to achieve that so i lunched Google and the first result was a blog for Andrew Lavinsky  (http://azlav.umtblog.com/2011/06/15/applying-security-to-a-pdp-redux/) the idea was to disable security inheritance on the PDP document level and assigning unique permission (Simple enough)  but if you already followed the link you will notice Andrew comment that there is an issue with that approach that it will only work under a very specific case

so i approached it a little bit different instead of setting up and changing permissions on the PDP level i simple created a SharePoint group (group who is allowed to view that PDP) and configured target audience for the Project Server Custom field web-part to target only that group.

and that is it , not the cleanest way the PDP name and link will still appear but it is the only way for the moment , please let me know if you have any better ideas

Cheers
Malek 

I have did something bad

Hello All , 

I will start with a big disclaimer  : 

 I have did this only for testing and because i needed this database to get attached this is a development environment , and what i did is totally 100% not supported not recommended .

Status Manager

Since this morning i have been straggling with the status manager problem .

the Project summary task status manager was the Server admin and not the owner .

this caused that some of the users trying to submit new assignments but its going to the project owner .

after trying for like 3 hours to change the status manager on the summery task and the simple solution is

the summery task status manager is the last user who published the project :D

hope this will help you

Timesheet Incorrect mode

Hello

recently i was facing a problem with some timesheets failing in the queue and no solution could be found in Google .

Basically the error reason is unknown and the error code is not clear , maybe it is generated after the latest update from Microsoft but anyway lets handle it

The error details are below

Queue type : Timesheet
Job Type : Timesheet Submit
In the error description you can see “Incorrect timesheet mode”


So after I looked over and over and couldn’t find a solution I made the biggest no in the Project server …. Yes I canceled the job from the queue and then I refreshed the timesheet and it turned into green and the status was approved and everything is perfect .

So far this is the solution I came up with and the data seams ok and no more problems is coming up