Project Server 2013-Tasks updates not replicating on schedule page

Hi,
We have updated the custom fields data in MyTasks.aspx page, but those changes are not updating on Schedule.aspx page evnthough those tasks are approved.
Your help is greatly appreciated
Thank You,
Kusuma

Prasanna explained how to do this using a Macro, and he also points out the perils. What happens when you have two resources assigned to the task? If User A enters a value of A and User B enters a value of B? Which value would you have appear at the task
level?
You can ask the system to roll down values from Task to Assignment, however you cannot ask the system to rollup values from the Assignments to the Task level without providing custom logic to handle the all of the potential possibilities.
Between Prassanna and Barbara, you have a comprehensive answer, I am simply trying to help you understand their replies. The key to understanding this is the "one-to-many" relationship between tasks and assignments. In practice, you might have a policy of
"one assignment per task," but that is not typical, and there is no way for Microsoft to guess what is supposed to happen to your custom task/assignment fields when one assignment value does not match another assignment value on the same task.
Gary Chefetz, MCITP, MCP, MVP msProjectExperts
Project and Project ServerFAQs
Project Server Help BLOG

Similar Messages

Project Server 2013 Task Reassignment Privileges Off? (Works in Timesheet)

Version: Project Server 2013
I'm trying to give our users access to reassign tasks. I turned on "Reassign Task" on the Global Permissions and gave them security to "Assign Resource" on all their categories.
I've tested this, and the "Reassign" feature is available and working then they are on the "Timesheet" page, but it is grayed out and gives the message:
"This control is currently disabled. You might not have the right permission level to use this, you might need to select an object or item, or the control might not work in this context."
Again, the same task is available to be reassigned in Timesheet though.
My guess is that this is a Security Permission issue, because my account which I am the Administrator and Owner of the project, I can reassign tasks on both pages.
Any suggestions?
Thanks,
Justin
It's me

Hi Justin,
Just for your information, as far as I know, the "assign resources" is not necessary for using the "reassign task" feature. The "reassign task" global permission is enough.
To be sure to understand your issue, the "reassign task" button is available for you as admin or project owner, but not for users which you granted the "reassign task" permission to? Am I right?
You are talking about global permissions but did you add the "reassign task" to the
groups permission the users belong to?
Silly question, but do the users have select a task before trying to reassign it?
Hope this helps,
Guillaume Rouyre, MBA, MCP, MCTS |

After Project Server 2013 SP1 update (without updating Sharepoint Server 2013)

I get this error entering the PWA root:
Derived method
'RequiresWebPartClientScript' in type
'Microsoft.Office.Project.PWA.WebParts.PWAPart' from assembly
'Microsoft.Office.Project.Server.PWA, Version=15.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c' cannot reduce access
SharePoint Server 2013 version: 15.0.4420.1017
Project Server 2013 version: 15.0.4569.1506
There is no SP1 uninstall process? Totally lost!

Hi Ximet,
If you go to Central Administration > System Settings > Manage Servers in this Farm. Do you see Upgrade Available for the servers.
If they show Upgrade Available, can you run the SharePoint Config Wizard one more time or you can also try running the command "psconfig -cmd upgrade -inplace b2b -wait -force"
Just curious to know if the issue is because the binaries have not been updated properly.
In case the issue persists and is impacting your business, I would suggest that you raise a support ticket with Microsoft so that we can further assist you on the case.
Cheers! Happy troubleshooting !!! Dinesh S. Rai - MSFT Enterprise Project Management
Please click Mark As Answer; if a post solves your problem or Vote As Helpful if a post has been useful to you. This can be beneficial to other community members reading the thread.

After installing Project Server 2013 (without updating SharePoint Server 2013 SP1))

I am facing the problem while opening project web app. I configured the SharePoint 2013 and project server 2013. Here is the detail what I performed the steps:
OS Server 2012 R2, SQL Server 2012, SharePoint server 2013 version
15.0.4420.1017, Project Server 2013 version
15.0.4454.1000. SharePoint configured and running successfully. After project web app site provisioning successfully completed. I got the below error.
Microsoft.Office.Project.PWA.WebParts.PWAPart' from assembly 'Microsoft.Office.Project.Server.PWA, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' cannot reduce access.
I run this psconfig -cmd upgrade -inplace b2b -wait -force. But still getting same error.
Previous steps:
Earlier I had also tried to install SharePoint Server 2013 SP1 "3823428". After the installation SP1 some of sharePoint site features suddenly stopped e.g: Cannot browse "Service Applications -->
Manage service applications" option even after re-start the server. This was previous error after upgrading SP1
"Method 'get_IsClientValid' in type 'Microsoft.SharePoint.WorkflowServices.WorkflowServiceApplicationProxy' from assembly 'Microsoft.SharePoint.WorkflowServices,
Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' does not have an implementation"
Anyone can help me!!! Thanks...
Faisal Numan

hello,
For SP2013 and PS2013 to work properly on Windows Server 2012 R2 you need to use the SP1 install media for both, download SharePoint 2013 with SP1 and Project Server 2013 with SP1
http://support.microsoft.com/kb/2891274
http://blogs.technet.com/b/office_sustained_engineering/archive/2014/03/03/announcing-availability-of-slipstreamed-office-2013-and-sharepoint-server-2013-with-sp1.aspx
http://blogs.technet.com/b/projectsupport/archive/2014/02/25/project-2013-and-project-server-2013-service-pack-1.aspx
Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS

Project Server 2013 Tasks differ in project site and plan

I have an Project Server 2013 enterprise plan that I created with an associated project site. The plan has tasks added to the timeline. The project site has a timeline webpart but the problem is the tasks added to the timeline differ.
Does anyone have any ideas what could be the problem here? I checked the timeline webpart and it's correct.
Thanks!
[Images below].
The following image is taken from the schedule PDP.
This image taken from the project site depicts what is out of sync.

Hi Guillaume,
Yes, I've checked the queue while publishing the project. It's successful without any errors. I don't remember if I checked the ULS logs, but what I suspect is that it will say something along the lines of orphaned tasks in the project site.
Anyways I've tried a number of things and I think the only 2 options I have are:
Re-create the project site then sync the plan to it
Ask MSFT for a script to resolve the orphaned tasks
For the same of time, I'm going to assess how long it would take to re-create the project site.
Thanks,
Roland

Project Server 2013 : Report table not updated with Published tables

Hello Team,
We found the issue that Publish and Reporting table have difference in work attribute. is their any way that we can refresh the Reporting table in one go.
Thanks.

If this issue is specific to one or few projects, using Save for sharing would be much more easier.
If this issue is for all the projects then as NicoOosthuysen recommended RDB refresh would be the option. Having said that you have to take extra measure before you start RDb refresh , since it is very high system resource and time consuming activity
Steps for Save for sharing
1. Open MS Project Pro 2013.
2. Open the project plan from the server.
3. Now save it locally without making changes in the File Name, using File > Share > Save For Sharing. Provide local location. Do not close Project Professional
4. Now save back the project back to server using File > Save As (Project Name should be grayed out)
5. Save and then publish the project plan.
Hrishi Deshpande Senior Consultant

Project Server 2013 Site Owner not changed when Project owner is changed

It seems when a project is created the project site "owner" is set to be the person that created the project. If the project owner is changed then site "Owner" is not updated. This is a problem on several fronts and I am almost
hoping it is an issue with my install.(We are running Project permissions mode)
Use Case 1: A project manager leaves the company and the New PM is added as the new project owner. After addition and publish the site owner remains the same as the original. this means the new pm can't share the site (to a stakeholder who is not in the
ERP) by adding them to the general "Contribute" group or otherwise.
Use Case 2: a planner creates a portfolio project and gets it through the workflow and all. the PM is assigned but can't add other stakeholders without going back to the planner and having them add them to the project site as an owner.
Question: Is this a feature or a bug? Is there a script to do this?
Seems kind of cumbersome and has already produced numerous issues for us.
Tasks

Bob,
Unfortunately, you are seeing the behavior as designed. The Project Site Owner will always be the person, who created the project site (i.e. Project). This is because, after the initial creation, the only groups that are synced are:
<Site Name> Project Managers (Project Web App Synchronized)
<Site Name> Team Members (Project Web App Synchronized)
<Site Name> Web Administrators (Project Web App Synchronized)
The idea here is that, all 'sharing' of the project site will happen via the project schedule/Project Server. Anybody who is part of the Project team, will be given Team member access, and anybody with rights to save that project will be given project manager
acess on the Project site,
This is also good in a way, because, this prevents any license violations, (users who access project sites also should have PWA CAL), that could happen via direct sharing.
Having said that, you have couple of options:
1) Make it part of your process that when a owner changes, the admin (or workflow) manually adds the new owner to the Site Owners group.
2) Disable Project Site Sync, and manage it via the AD Groups (depending upon on your security model).
Cheers,
Prasanna Adavi, Project MVP
Blog:
Podcast:
Twitter:
LinkedIn:

Project Server 2010 - PDP updates not triggering Project Server Events

Hello,
We're experiencing an issue whereby when a user updates a Project PDP, no update is triggered and reflected in the reporting database.
My question is, which Server Side Event Handler is responsible for picking up PDP changes (i.e. Changes to Enterprise Custom Fields)?
Can someone please assist?
Thanks in advance.
What we have configured and is working as expected...
Event: Reporting
Event Name: ProjectChanged, ProjectCreated, ProjectDeleted

There may be multiple reasons for this.
1. SharePoint timer Job is malfunctioning:
For this try restarting SharePoint timer Job. through SP Powershell:
Stop SPTimerv4 , Start SPTimerv4
2: SharePoint Cache is full:
Reset SharePoint Cache by deleting all XML files ( except cache.ini
) in SharePoint Cache located in System Drive\ProgramData\Microsoft\SharePoint\Config\<GUID>
3: Check if Microsoft Project Server Event Service is running in Services.msc, try restarting it.

Project Server 2013 - Graphical Indicators - Not showing until the project is published via Project Pro 2013

Greetings -
I have a custom field on a PDP that is used to manually flag a project for review. Once the field is set to "Flag" a red flag should show on the Project Summary page prompting the Portfolio Manager to follow up. The red flag only appears
after publishing the project via Project Pro 2013 not by just editing the PDP via Explorer (Save and Check in).
This occurs on both projects that were created prior to the graphical indicator being added to the PDP and new projects.
Now if instead of using the red flag graphical indicator I just used the text "FLAGGED" that would work fine.
So is this a bug? Or is something setup incorrectly? Or is this how PWA is supposed to handle graphical indicators on the project summary page?
Any help would be much appreciated.

Hi Gunnery,
I made the following test: I create 2 project ECF both inserted in the Project details PDP:
for review: flag type field with graphical indicator in case value = yes
for review_2: text type field (with a yes/no look-up table) with graphical indicator in case value = yes
Whitout going to Project Pro, I'm able to modify the 2 fields for any project (created before or after the ECFs creation) and the graphical indicators are instantaneously shown in the summary project center view (just pressing F5).
Note that the graphical indicator is not shown in the PDP, just the text value. Note also that I've not been to Project Pro neither to PWA/schedule PDP to publish the project plan.
Then
Does that correspond to your need? Can you reproduce this example and validate wheither or not it works.
Guillaume Rouyre - MBA, MCP, MCTS

Project server 2013 kb2768001 update failed, Central admin and all sites not loading, showing 503 error

Hi I just tried to install the kb2768001 update and it failed. Now non of the sites in share point are loading. including Central admin. Share point is running, the logs are being updated.
what i have done so far,
- re boot the server
- reset iis
so far same results.
any help to fix this issue will be appreciated.

I did run the Config wizard. that failed too.

Project Server 2013 - User does not have permission to create a WSS site

We have Auto-Publish enabled for the project by the Owner. The issue is that when a user submits his updates, the updates are auto approved and auto-published but it also ends up showing below error to the user.
General
•User does not have permission to create a WSS site.:
◦GeneralSecurityAccessDenied (20010). Details: id='20010' name='GeneralSecurityAccessDenied' uid='---'.
•Queue:
◦GeneralQueueJobFailed (26000) - CreateWssSite.CreateWssSiteMessage. Details: id='26000' name='GeneralQueueJobFailed' uid='---' JobUID='---' ComputerName='---' GroupType='CreateWssSite' MessageType='CreateWssSiteMessage' MessageId='1' Stage='' CorrelationUID='54a0c79c-da9b-c011-2554-5fb474e440c6'.
For more details, check the ULS logs on machine --- for entries with JobUID ---.
And in the Project Queue, the failed job type and job state are
Job type- Project Site Update
Job State - Failed But Not Blocking Correlation
We have disabled Site Provisioning for Project publish.
Can anyone point us on how auto-publish works and what all permission is required by users or owners?

Hi Goahh,
It might be that your issue has nothing to do with the rules set to auto-publish the project. Try to inactivate the auto-publish for a test project and try if the publication by itself works. Or simply try to publish a project from MS Project Pro and see
if you still get the error message.
Has it been working before?
Check also that the "Manage SharePoint Foundation" permission is enabled for the security groups in question.
Hope this helps,
Guillaume Rouyre, MBA, MVP, P-Seller |

Project Server 2013 - Project Plan crashes frequently

Team,
We are using EPM , and everytime we update the project plan using enterprise project, the plan crashes and it does not allow me to publish the plan on the Project server.
Please suggest solution for the above
We are using Project Server 2013
Regards
Vidhya

Vidhya --
First of all, is your Project Server 2013 system updated with the latest Cumulative Updates and/or with Service Pack 1 (just released yesterday)? If not, I would strongly suggest that you update your system and your copies of Microsoft Project 2013
with Service Pack 1 at the earliest date possible.
Second, regarding this project in particular, I would strongly suspect that this project is corrupted. To resolve the corruption, you will need to use the Save for Sharing feature in Microsoft Project 2013. To do this, right-click anywhere on
a ribbon tab in Microsoft Project 2013, such as the Tasks tab, and then select the Customize Quick Access Toolbar item on the shortcut menu. In upper left corner of the Project Options dialog, click the Choose Commands From pick list and select
the All Commands item. In the list of commands on the left side, select the Save For Sharing item and click the Add button to add it to the list on the right. Click the OK button when finished.
To use the Save for Sharing feature, do the following:
Open the enterprise project in question.
Click the Save for Sharing button in the Quick Access Toolbar.
In the Save dialog, save the MPP file to a location where you can find it easily, such as your computer Desktop, for example.
Close the MPP file.
Reopen the MPP file.
Click File > Save As and then save the project.
When the Save operation is done, try publishing the project.
Please let us know if this helps.
Dale A. Howard [MVP]

Project Server 2013: customize JSGrid (Project Center, MyTasks, etc...) ?

Hi,
In Project Server 2010, it was possible to customize the JSGrid, thanks to the tutorial included in the SDK "Walkthrough:
Customizing the PWA Ribbon and Accessing the JS Grid". It works really fine, and I used this possibility in many Project Server 2010 implementation for Customer.
I would like to make it on Project Server 2013, but the same code doesn't work. I found some posts
here, where people had the same issue, but no clear answer.
The Project Server 2013 SDK does not contain the same tuto upgraded for 2013, and I hope that this possibility still exists.
If somebody has a very basic example to show how to execute some custom code on Focus Change event, or clic, or what ever event happening on this JSGrid, it would be very nice to share.
My installation is On Premise, not in On Line.
Thank you for your help !
Sylvain

Hi,
In fact for filtering, you have to use delegate.
The "HandleFilter" function must be created by you. You have to bind this function to the correct delegate.
For filtering, the main delegates are:
SP.JsGrid.DelegateType.AutoFilter
SP.JsGrid.DelegateType.LaunchFilterDialog
SP.JsGrid.DelegateType.GetAutoFilterEntries
The post
here explains the process for 2010. For Project Server 2013, the difference is that we don't have the same objects.
Here you can find the way to declare the delegate in Project Server 2013, with the SetDelegate method:
var pc; // Contains the Project Center extension object.
var JsGridControlInstance;
var JsGridSatellite;
_spBodyOnLoadFunctionNames.push("ProjectCenterMain");
function ProjectCenterMain() {
pc = new ProjectCenterExtension();
function ProjectCenterExtension() {
if (typeof projectCenterComponent === 'undefined')
return;
JsGridSatellite = projectCenterComponent.get_GridSatellite();
JsGridControlInstance = projectCenterComponent.get_GridSatellite().GetJsGridControlInstance();
JsGridSatellite.get_tableViewParameters().bAutoFilterableColumns = true;
JsGridControlInstance.SetDelegate(SP.JsGrid.DelegateType.AutoFilter, HandleFilter);
JsGridControlInstance.SetDelegate(SP.JsGrid.DelegateType.LaunchFilterDialog, FilterDialog);
JsGridControlInstance.SetDelegate(SP.JsGrid.DelegateType.GetAutoFilterEntries, FilterMenu);
function HandleFilter(newState) {
alert("Filter !");
function FilterDialog(param) {
alert("FilterDialog !");
function FilterMenu(param) {
alert("FilterMenu !");
My advice to search, is to put a break point on the ProjectCenterExtension function, and through debugger, tou can drill down in the main methods and properties.
Often you will see functions with get_XYZ(), and then be able to make the matching with the Project Server 2010 syntax.
For the filtering implementation, I beleive that you can deal with your article based on 2010: it should work as soon as you will get the equivalent objects in 2013.
Hope it helps !
Sylvain

Project Server 2013 SP1 only

Hi,
Can Project Server be updated to SP1 and leave SharePoint without it? it seems there is some kind of trouble
http://social.technet.microsoft.com/Forums/en-US/45b56c00-b894-445d-9e4b-c44b158f0531/after-project-server-2013-sp1-update-without-updating-sharepoint-server-2013?forum=projserv2010setup
Thanks

Hi,
We need SharePoint Server SP1 installed first and then install Project Server SP1

Project Server and Project Pro 2013 - Tasks not allowing Uncomplete Work to be rescheduled

We are current;y running Project Server 2013 on Premise and using timesheets to update task status. We are using the proactive task scheduling to let the allocations, work and dependencies drive the schedule to get accurate project finish dates.
We have several projects that give an error stating "Change would modify work entered by a team member" and "We can't make that change because Project Web App is set to only allow actual work to be entered by a team member through Timesheets
or My Work" when setting the status date and Updating the Project and selecting reschedule Uncompleted Work to start after the status date. We have determined that usually it is only a single task causing the error. we have tried to remove the resource
when no actuals have been entered but we get the same issue. Any help would be greatly appreciated.

Paul,
Looks like the settings "Only allow task updates via Tasks and Timesheets" has been enabled on your PWA (under Server Settings >> Task Settings and Display).
But the setting is used to prevent any updates to actual work from project pro, and will throw the error you mention above, if a PM tries to update the actual work.
I am not sure why the "Rescheduling of uncompleted work" would thrw this error, but worth checking that setting.
Cheers,
Prasanna Adavi, Project MVP
Blog:
Podcast:
Twitter:
LinkedIn:

Project Server 2013-Tasks updates not replicating on schedule page

Similar Messages

Maybe you are looking for