#ProjectServer #PS2010 / #PS2013 local master projects and tasks with no assignments

June 21, 2013 at 5:02 pm | Posted in Administration, Information, Issue | 1 Comment
Tags: , , , , ,

Something to be aware of when using local master projects in Project Server 2010 or 2013 when tasks in the sub projects have no assignments.

You will see random text / characters next to the Unassigned name as seen below:

clip_image001

The text / characters displayed will change depending on where you last clicked.

Repro steps below:

  • Open Project Pro and connect to the server
  • Create 1 project, create 3 tasks and assign an enterprise resource to all three tasks, save and publish the project.
  • Close and check-in the project
  • Create 1 other project, create 3 tasks and assign an enterprise resource to only 2 of the tasks leaving 1 task with no assignment, save and publish the project.
  • Close and check-in the project
  • Create a new project and insert both of the projects created above as read-only
  • Save the master project locally as a file, when prompted hit no to all when prompted to save changes to the two insert projects
  • Close the master project and again when prompted hit no to all when prompted to save changes to the two insert projects
  • Close Project Pro
  • Open Project Pro and connect to the server
  • Open the local master project and expand the two inserted projects
  • Switch to the Resource Usage view and notice the Unassigned resource name

clip_image001

  • Make changes such as expanding the Resource Name column, increase the work etc. and see the Unassigned name update.
    • After changing the Resource Name column width:

clip_image002

o Changing work:

clip_image003

o 2013:

clip_image004

clip_image005

#ProjectServer 2010 field calculation in PWA #PS2010 #MSProject #SP2010

June 18, 2013 at 3:44 pm | Posted in Administration, Configuration, Customisation, Fixes, Functionality, Information, Issue, Workarounds | 1 Comment
Tags: , , , ,

A quick blog post to highlight an issue and workaround for editing plans in PWA when using custom fields that use the inbuilt fields. This post uses Finish Variance as an example. The Finish Variance field doesn’t recalculate in PWA after making edits to plans, this only updates after changes in Project Pro. This post relates to the Finish Variance field but other fields will more than likely have the same issue.

In the screen shot below you will see a simple plan with 2 tasks that was created and baselined in Project Pro. There are 3 custom fields in the view:

Finish Variance RAG, the formula is IIf([Finish Variance] > 0, "Slipped", "On schedule")

Finish Variance (Calc) RAG, the formula is IIf([Task Finish Variance] > 0, "Slipped", "On schedule")

Task Finish Variance, the formula is ProjDateDiff([Baseline Finish], [Finish]) / 480

image

As you can see the Finish Variance and the Task Finish Variance values are currently the same and so are the 2 RAG fields.

Edit the plan in PWA and increase the task durations, for this example double the durations. Calculate the plan then save and publish the project. Refresh the page and you will see that the Finish Variance is incorrectly 0, the Finish Variance RAG is still green as this uses the Finish Variance field. The good news is that the custom field that calculates finish variance (Task Finish Variance) shows the correct values and the Finish Variance (Calc) RAG also shows the correct RAG.

image

To correct the Finish Variance values and the Finish Variance RAG, open the plan in Project Pro, press F9 to recalculate then save and publish. The Finish Variance default field now shows the correct values in PWA as does the Finish Variance RAG:

image

To get the RAGs to calculate correctly when editing in PWA you might need to create your own custom fields to replicate the calculations used on inbuilt fields. Obviously it would not be recommended to create too many task level calculated fields due to performance issues but hopefully that little workaround helps for key RAGs.

#ProjectServer and #SharePoint 2010 / 2013 June 2013 Cumulative Update #PS2010 #SP2010 #PS2013 #SP2013 #MSProject

June 15, 2013 at 9:24 am | Posted in Administration, CU, Fixes, Information | 3 Comments
Tags: , , , , , , , , ,

The Office 2013 June 2013 Cumulative Updates are now available, please see the links below:

http://support.microsoft.com/kb/2855356 

Project Server 2013 Server Roll up package June 2013 CU (Recommended):
http://support.microsoft.com/kb/2817415 (Delayed)
Project Server 2013 June 2013 CU (Included in the Server Roll up package):
http://support.microsoft.com/kb/2817341
Project 2013 June 2013 CU:
http://support.microsoft.com/kb/2817338

Also worth noting, install the March 2013 Public update: http://support.microsoft.com/kb/2768001 if installing the June 2013 CU.

The Office 2010 June 2013 Cumulative Updates are now available, please see the links below:

http://support.microsoft.com/kb/2855357

Project Server 2010 Server Roll up package June 2013 CU (Recommended):
http://support.microsoft.com/kb/2817368
Project Server 2010 June 2013 CU (Included in the Server Roll up package): 
http://support.microsoft.com/kb/2817378 & http://support.microsoft.com/kb/2817387
Project 2010 June 2013 CU:
http://support.microsoft.com/kb/2817385
Remember SP1 is a pre-requisite for the Office 2010 June 2013 CUs.

For more details please see:

http://blogs.technet.com/b/projectsupport/archive/2013/06/14/microsoft-project-server-2007-2010-and-2013-june-2013-cu-announcement.aspx
As always, test these updates on a replica test environment before deploying to production

#ProjectServer 2013 environment migration / rollover steps update #PowerShell #PS2013 #SP2013

June 3, 2013 at 11:37 am | Posted in Administration, CU, Fixes, Installation, Issue | 1 Comment
Tags: , , , ,

Something to consider when following the rollover steps outlined in the post below.

https://pwmather.wordpress.com/2013/05/02/projectserver-2013-environment-migration-rollover-steps-powershell-ps2013-msproject-sp2013/

If the target farm (Test / Dev) is a later patch level than the Content database and Project Web App database, they will need to be upgraded after mounting.

Upgrade the content database using the Upgrade-SPContentDatabase command and the Project Web App using the Upgrade-SPProjectDatabase. In 2010 the 4 PWA databases used to upgrade when provisioning the PWA site, in 2013 this process fails due to the Project Web App database being in compatibility range. The error found in the upgrade log can be seen below:

OWSTIMER (0x27C4)    0x467C    SharePoint Foundation Upgrade    SPUpgradeSession    aloop    DEBUG    Entering upgrade for [ProjectSite Name=8d511428-9d61-4731-96bd-28be45bfba6b]    72be219c-e53a-b0d0-1951-87ac137d4659
OWSTIMER (0x27C4)    0x467C    SharePoint Foundation Upgrade    SPUpgradeSession    ajxnf    ERROR    Cannot upgrade [ProjectSite Name=8d511428-9d61-4731-96bd-28be45bfba6b].    72be219c-e53a-b0d0-1951-87ac137d4659
OWSTIMER (0x27C4)    0x467C    SharePoint Foundation Upgrade    SPUpgradeSession    ajxng    DEBUG    Skip upgrading [ProjectSite Name=8d511428-9d61-4731-96bd-28be45bfba6b].    72be219c-e53a-b0d0-1951-87ac137d4659
OWSTIMER (0x27C4)    0x467C    SharePoint Foundation Upgrade    SPUpgradeSession    alooy    DEBUG    Exiting upgrade for [ProjectSite Name=8d511428-9d61-4731-96bd-28be45bfba6b].  Elapsed Time=[00:00:00]    72be219c-e53a-b0d0-1951-87ac137d4659

Create a free website or blog at WordPress.com.
Entries and comments feeds.