Answered by:
MS Project Professional 2007 resource loaded .mpp file published to EPM server but resources can't see their tasks in PWA

Question
-
Hi all:
I'm using MS Project Professional 2007 and I created the schedule as an .mpp file and assigned resources before I loaded the schedule to the EPM server. I created the resource names consistently with the names in the Enterprise resource pool and when I go into tools / assign resources and filter on enterprise resources, I see the resources I assigned to my project associated with the correct tasks. The only problem is that when these resources go into PWA, they can't see their assigned tasks even after I save and publish the project. If I create a new resource assignment while I am connected to the server, then the resource can see the new assignment, but I don't want to have to completely recreate the project assignments to remedy this situation. Can anyone tell me another way to fix it so that resources begin to see their assignments in PWA and can enter their time there?
Any suggestions would be greatly appreciated.
Thanks,
DavidThursday, September 4, 2014 5:38 AM
Answers
-
Djoliver1 --
You actually have two problems which need to be addressed separately. First, your Project Server administrator needs to get the Default Assignment Owner values specified for every human resource in the Enterprise Resource Pool. This will not take care of the problems with your project; it will simply eliminate the problem in all future projects
Second, YOU must manually specify the correct Assignment Owner for each resource in your project AND you must publish the project as well. After you take care of your project and publish the latest schedule changes, your team members will be able to see their tasks in PWA.
As far as a corrupted project, if you are using Project Server 2007, the only way to repair a corrupted project is to save it as an XML file. After doing this, close it, reopen it and create a new project from it using the Import Wizard, and then save it in Project Server 2007. Hope this helps.
Dale A. Howard [MVP]
- Marked as answer by Djoliver1 Monday, September 8, 2014 11:35 PM
Monday, September 8, 2014 1:15 PM
All replies
-
Djoliver1 --
Your problems began when you apparently manually typed the names of the resources in the project. If you navigate to the Resource Sheet view of your project, do you see the Local Resource icon to the left of each resource name? If so, that is why your resources cannot see their tasks in PWA.
The correct way to add enterprise resources to a project is to use the Build Team dialog. You can also use this dialog to swap local resources with enterprise resources, which is what you will need to do. Click Tools > Build Team from Enterprise. Select a local resource on the right side of the dialog, select the corresponding enterprise resource on the left side of the dialog, and then click the Replace button. You will need to do this for EVERY local resource in your project. After you swap all the local resources, make sure the Booking value for every resource on the right side of the dialog is set to Committed. Click OK, then save and publish your project. Your team members should now see their task assignments in PWA.
Hope this helps.
Dale A. Howard [MVP]
- Proposed as answer by epmXperts Thursday, September 4, 2014 2:20 PM
Thursday, September 4, 2014 10:53 AM -
Thanks for answering Dale. When I go to the resource sheet only the generic resources (3 out of 28) are local (head on project sheet icon) and I wasn't expecting anyone to be entering time in PWA for these 3 anyway. All the others are enterprise resources and the Booking Type of these = "committed". So unfortunately my problem is not going to be that simple to resolve.
Is there anything else you can think of that I or the administrator should check?
Is there anything elso I can suggest the administrator do to correct the problem?
Thanks again for answering...
David
- Edited by Djoliver1 Thursday, September 4, 2014 8:33 PM
Thursday, September 4, 2014 8:32 PM -
David --
Open the project and then apply the Gantt Chart view. Temporarily insert the column called Publish. Do you see a Yes value for every task? If you see No values, change them to Yes.
A second source of this problem could be the Assignment Owner values for each of your resource assignments. Apply the Resource Usage view and then temporarily insert the Assignment Owner column. Is each resource listed as his/her Assignment Owner for each of the tasks to which the resource is assigned? If not, set the correct Assignment Owner value for each task assignment for each resource.
Is you see a whole bunch of wrong Assignment Owner values are set to YOUR NAME, then you will need to check the resources in the Enterprise Resource Pool to make sure that the Default Assignment Owner value is set to each resource individually.
There are a couple more ideas for you to chew on. :) Hope this helps.
Dale A. Howard [MVP]
Thursday, September 4, 2014 8:37 PM -
Hey Dale. Published = Yes on all tasks. That's not it.
But you definitely hit the mark on Assignment Owner. That must be where the problem is. When I read that I remembered that when I go into PWA all the project tasks show up under My Tasks, which seemed wrong to me and I asked the administrator about that. he told me it was because I was the project owner. Now I know that was not a correct response on his part and I'll point it out to him.
I did check the Resources and Assignment Owner was blank. I tried to set it to be the Resource and it's a locked field. I can't do it. It doesn't surprise me that this field is locked because I suspect the administrator controls the Enterprise Resource pool. But what does it tell you that this field is blank. Since I'm getting the tasks in my My Task list, I expected to find my name there.
Anything else I should check?
Anything I should tell the admin about how to make the Resources the owners of their own tasks. I assume that should be the default. That can be corrected just as easily in the Resource Sheet View as in the Resource Usage view, I assume -- is that correct?
Thanks again for helping me figure out what the problem is.
David
Thursday, September 4, 2014 10:26 PM -
Djoliver1 --
Your Project Server administrator screwed up, plain and simple. He/she needs to specify a Default Assignment Owner value for every resource in the Enterprise Resource Pool, otherwise, you and all of your fellow PMs will continue to have this problem. If memory serves me correctly, as I have not used Project Server 2007 for many years, I believe he/she will need to do the editing in PWA from the Resource Center page. But he/she can try opening the Enterprise Resource Pool in Microsoft Project 2007 first, insert the Default Assignment Owner field, and then attempt to edit it. I think that will not work; if not, he/she will need to do it in PWA.
If I have answered your question with one of my responses, would you please mark it as the answer to your question? Thanks! And you are more than welcome for the help, my friend. :)
Dale A. Howard [MVP]
Friday, September 5, 2014 12:43 PM -
Dale:
Let me keep this open a little longer. The admin tried to set Assignment Owner on a couple resources, but those resources still could not see their tasks. I don't know what procedure he tried to do that. I'll copy your suggestions in an email to him and see if this is what he did.
If my project schedule is corrupted for some reason, do you know any way to fix it? For example, saving it as an .mpp, then saving it in RTF, or saving it in Project 2010, before loadiing it back into EPM server. I don't know... I'm just fishing, but those kinds of manipulations used to work in Project Server 2003. Any suggestions how to repair a corrupted file, if that is the problem?
Monday, September 8, 2014 4:21 AM -
Djoliver1 --
You actually have two problems which need to be addressed separately. First, your Project Server administrator needs to get the Default Assignment Owner values specified for every human resource in the Enterprise Resource Pool. This will not take care of the problems with your project; it will simply eliminate the problem in all future projects
Second, YOU must manually specify the correct Assignment Owner for each resource in your project AND you must publish the project as well. After you take care of your project and publish the latest schedule changes, your team members will be able to see their tasks in PWA.
As far as a corrupted project, if you are using Project Server 2007, the only way to repair a corrupted project is to save it as an XML file. After doing this, close it, reopen it and create a new project from it using the Import Wizard, and then save it in Project Server 2007. Hope this helps.
Dale A. Howard [MVP]
- Marked as answer by Djoliver1 Monday, September 8, 2014 11:35 PM
Monday, September 8, 2014 1:15 PM -
thanks so much Dale. you were a great help!!!!Monday, September 8, 2014 11:35 PM