Friday, September 16, 2011

Accessing Issues in opening the project details page in PWA 2010 for Team Members group:

Issue: 
Team Members get “access denied” error (see error screenshot below) and are not able to open Project details page (PDP) or Schedule of a selected project from Project Center.


Resolution:
There is a restriction in 2010 version. In PWA 2007, team members were able to see the project detailed schedule after clicking the project link in Project Center without any issue. In PWA 2010, we use Enterprise project templates (EPT) during creation of a new project. That EPT can consist of multiple PDPs. Here in this default EPT, we have 2 PDPs (Project Details & Schedule). This Project Detail PDP shows the custom project level fields information and it is the same what we had  “Edit Project Properties”  button in PWA 2007 project center  to view or edit project custom level  fields by Project managers. In 2010, the Project schedule PDP is a part of default ETP, so TM needs to have at least “Open Project” permission to access the page.
Steps:
1-      Go to PWA main site and click Server Settings
2-      Click Manager group and select Team Members Group
3-      Click “My Tasks” category and turn on “Open Project” permission (see screenshot below)


Note:
A team member can open a schedule in MS Project Professional if TM has this “Open Project” permission. If your organization does not want TM group to have access the schedule in Project Pro, you can easily disallowed  “Log on to Project Server via Project Professional" permission for Team Member group so no one can access schedule via MS Project at all.

Friday, September 2, 2011

JScript error in My Tasks page in PWA 2010

Environment: Project Server 2010 (Tasks page)

Issue:

After successfully migration of Project Server 2007 data into the Project Server 2010 version, I got a JS error when I try to enter date in Actual Finish Date field or any other date field (see attached screen shot) and in result, I was not able to enter any information.




Solution:

For some unknown reason, the "Tasks" page generated this error after migration 2007 version data. Following steps need to follow to fix this error

  1. Go to Central Administration
  2. Click Manage Service Applications >>Project Server Service Application
  3. Delete the specific PWA instance
  4. Create again with same "Project Web App Path" name and use the same existing four Project Server databases
  5. After Provisioned, go to Tasks page , you will not get any more the sepcific error mentioned above.
Cheers!