#Project and #ProjectServer 2010 SP2 released #PS2010 #SP2010 #Project2010

July 24, 2013 1 comment
Good news, Service Pack 2 for SharePoint Server 2010/Project Server 2010 and Project 2010 is available now.

The Service Packs contain all cumulative fixes since SP1, starting with the June 2011 Cumulative Update (CU) and the July 2011 Public Update (PU) all the way through to the April 2013 CU and May 2013 PU.  The Service Packs also contain previously unreleased fixes.  In addition to general product fixes, these fixes include improvements in stability, performance, and security.The complete list of fixes is available here.

All the download are available through Microsoft download center, and the link to each download is as below:

Project 2010 Service Pack 2 – http://support.microsoft.com/kb/2687457 – with full technical details of the client products athttp://support.microsoft.com/kb/2687523/en-us 
Downloads – x86 – x64
Project Server 2010 Service Pack 2 – http://support.microsoft.com/kb/2687452
SharePoint Server 2010 Service Pack 2 – http://support.microsoft.com/kb/2687453 – with full technical details for the server products at http://support.microsoft.com/kb/2687524
For other Office and Sharepoint SP2 packages please visit http://support.microsoft.com/kb/2687521/

More details related to update are here.

And as usual, don’t rush to install any update directly to production, try it first on your test environments.

via All about Enterprise Project Management (EPM) http://khurramjamshed.blogspot.com/2013/07/project-and-projectserver-2010-sp2.html

Khurram Jamshed
The author of the blog has an extensive experience of working as an EPM Consultant. Currently he is located in Dubai, UAE and working for Microsoft partner organization as Project Server specialist. He has a thorough experience of providing Project Management technical/functional consultancy to all sort of organizations. He is a certified PMP, a Project Server MCITP, and also received a MS community contributor award 2011.

This article has been cross posted from khurramjamshed.blogspot.com/ (original article)

#ProjectServer #PS2010 and #SP2010 Service Pack 2 Released #PPM

Paul Mather
I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011.
I am also a certified Prince2 Practitioner.

This article has been cross posted from pwmather.wordpress.com (original article)

Service Pack 2 has been released for Office 2010, this includes Project Server 2010 and SharePoint 2010. For links to all Office 2010 SP2 updates see the office update site below:

http://technet.microsoft.com/en-us/office/ee748587.aspx

Project 2010 SP2: http://support.microsoft.com/kb/2687457

Project Server 2010 SP2: http://support.microsoft.com/kb/2687452

SharePoint 2010 SP2: http://support.microsoft.com/kb/2687453

For a full list of fixes, download the following Excel file:

http://download.microsoft.com/download/9/5/9/959F3A24-80B3-4930-8FF8-D3C631BB878F/Microsoft%20Office%20and%20SharePoint%202010%20Service%20Pack%202%20Changes.xlsx

For more information see the following blog post:

http://blogs.technet.com/b/projectsupport/archive/2013/07/23/project-2010-and-project-server-2010-service-pack-2-sp2-released.aspx

Categories: Paul Mather, Work Tags:

#ProjectServer #PS2013 / #PS2010 Last Modified and Last Published fields in PWA #SP2013 #PPM #ProjectOnline

July 22, 2013 2 comments
Paul Mather
I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011.
I am also a certified Prince2 Practitioner.

This article has been cross posted from pwmather.wordpress.com (original article)

A query that has been asked by several of our clients in the past is: “The last modified date field in PWA is not updating”. In most scenarios the Last Published and Last Modified fields will match in the Project Center as shown below:

image

This is because the Project Center views look at the published data and both these fields will get updated with a publish. If you modify (save but not publish) a project from Project Professional or PWA the Last Modified date will not update which may cause confusion. If you click the project to go to the project details you will see the status bar does show the correct Last Modified date:

image

Incorrect in the Project Center view:

image

There are scenarios where the Last Modified date will update and show a later date than the Last Published date, for example if you modify the project information then save the project:

image

To avoid any confusion to PWA users I would recommend not displaying the Last Modified date in Project Center views.

Categories: Paul Mather, Work Tags:

#ProjectServer #Excel report with SQL Temporary Tables #PS2010 #PS2013 #SQL

July 19, 2013 1 comment
Paul Mather
I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011.
I am also a certified Prince2 Practitioner.

This article has been cross posted from pwmather.wordpress.com (original article)

I came across an issue a while back and meant to blog about it but forgot until a colleague of mine today mentioned the same issue. This jogged my memory of the fix so I thought it was a good time to write the post. The issue isn’t Project Server related but the reports and queries we were creating were for Project Server.

If your SQL query in an Excel file uses temporary tables Excel will throw an error like the one seen below:

image

For the search engines the error is below:

The query did not run, or the database table could not be opened.

Check the database server or contact your database administrator. Make sure the external database is available and hasn’t been moved or reorganized, then try the operation again.

The error will occur if you have the select statement in the connection file definition command text or even calling a SQL stored procedure from the command text. The same fix applied to both, at the start of the select statement add “SET NOCOUNT ON” as shown below:

image

Now Excel will execute the query and return the data as expected. Smile

Categories: Paul Mather, Work Tags:

#ProjectServer #PS2013 Manage Alerts #SP2013

Paul Mather
I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011.
I am also a certified Prince2 Practitioner.

This article has been cross posted from pwmather.wordpress.com (original article)

A question I see and hear quite frequently is “Where has Manage My Alerts options gone in 2013?”. These have now moved the the PWA Settings page:

image

The two links for Manage My Alerts and Reminders and Manage My Resources’ Alerts and Reminders only appear once the SMPT server details have been enabled for the PWA instance. When the PWA notifications are removed from the PWA instance the two links are removed:

image

To enable notifications and enter the SMTP details, navigate to the Project Server Service Application in Central Admin, click Manage from the drop down menu next to the PWA site:

image

Enable the notifications and enter the SMTP server details on the Alerts and Reminders page. Once set, the two Manage Alerts links will appear on the PWA Sever Settings page under the Personal Settings heading. These links are permission controlled though.

Categories: Paul Mather, Work Tags:

How to backup deployed solutions

July 16, 2013 Leave a comment

Recently I had the need to backup all the solutions deployed to a test system before a code refresh, to achieve this I used the simple piece of PowerShell below.

 

$dirName = "C:\Solutions"
foreach ($solution in Get-SPSolution)
{
$filename = $Solution.SolutionFile.Name
$solution.SolutionFile.SaveAs("$dirName\$filename")
}

 

To run the PowerShell script simply create the folder c:\Solutions, or set another location in the script and run with Farm credentials or equivalent.

 

Happy SharePointing !

Categories: Work

Project Server Start Date Reporting Quirk

July 11, 2013 1 comment

I came across a little possible pitfall while generating some reporting for a client, which I thought I should share with the community.

 

In Microsoft Project, the Start Date in Project Information defaults to the Start Date of the first task in the plan.

image

Obviously this can be changed in the Project Information so that the Start Date of the Project does not necessarily reflect the Start of the first task in the plan, or the Project Summary task.

image

So which date does appears in the reporting database? Well, here are the results:

From the MSP_EpmProject_UserView view in the reporting database

image

As you can see, the date from the MSP_EpmProject_UserView displays whatever is set in the Project Information. This might cause some unexpected information in reports, so we need to expand our query to include the date from the Project Summary task:

image

So, when writing the specifications for your reports, make sure you’re clear which date the client wants – it’s not unheard of having a plan created a few months in advance of the work being realistically scheduled which might cause this confusion!

Obviously the clear process-driven workaround is to have your Project Managers ensure that the Start Date in Project Information is updated when scheduling the project!

Business Intelligence in the cloud, phew thank goodness… #Office365 #BI #SharePoint #PowerBI

So the Worldwide Partner Conference is going on in Houston at the moment and as much as I would love to be there, unfortunately projects here in London have to continue.  Still early starts and watching the world go by in Pret (coffee shop for those outside of the UK) is always interesting before the hub-bub of the day starts.

Anyway, as with every year at WPC, there are always exciting announcements and this year is no different.  We can hail this as official business intelligence in the cloud day!3731.SUMMARY_MobileBI_300x166.jpg-550x0

Now many of the projects I work on consider Office 365 as a platform, however the more enterprise you go, the more the requirements tend to need some level of business intelligence.  I was excited before with the release of SQL Reporting Services Online, however as functional as it is, limitations and costs current pose this solution to be only for the fully cloud invested.

My new hopes for BI in the cloud however seem to be starting to be answered in the form of Power BI for Office 365.

Using the capabilities already available on premise (Data Explorer, GeoFlow, Power Pivot and Power View) with tweaking, some re-branding and a little bit of mobile love (mobile apps to be available also (Windows 8, RT and iPad, HTML5) it looks like we may have an answer.

This to my mind almost completes the Office 365 capabilities to truly propel the cloud for use in the projects I get involved in.  (Project Management, Business Intelligence, Intranets, ECM solutions).

I urge you all to read up on the following and register for the preview coming “later this summer”.  I have a feeling this is going to be major!

Details:

    0027.imge.png-550x0

As I try things out, I will post my findings and any limitations I come across, but hopefully with the new OData / REST capabilities of Excel and SSRS, we should be able to have some fun with SharePoint list data!

Enjoy…

#ProjectServer #PS2013 #Excel Pivot Table limitation

Paul Mather
I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011.
I am also a certified Prince2 Practitioner.

This article has been cross posted from pwmather.wordpress.com (original article)

Just a quick post to highlight a limitation / issue with Excel Pivot Tables that I hadn’t seen before, details below.

This particular Pivot Table uses a Data Model that contains two OData feeds from Project Server 2013, one for Project details and one for Task details. The connections can been seen below:

image

The relationship has been set up as follows:

image

I have added Programme, Project Name, Task Name and Task Start to the Pivot Table. Programme and Project Name are from the Projects table and Task Name and Task Start are from the Tasks table. The Project Name is filtered to just one project:

image

Looking at the Pivot Table, it looks the CPS Test project has many tasks but in fact this project only has 4 tasks:

image

To resolve the issue you have to add a numerical field from the Tasks table to correct the aggregation:

image 

Hope that helps Smile

Categories: Paul Mather, Work Tags:

OLAP Cube Error – Cannot process the Project custom field

June 27, 2013 1 comment

Just a quick note to let you know about an error I came across today.

In Project Server 2010, I had a field called “Objective”. This was associated with a lookup table of the same name, which was single-value select. This field was added to the Project OLAP cube, which built successfully. So far so good!

I then changed the field type to multi-select, and left the cube to build overnight. Came back the next day to a failed OLAP build. The exact error I got in the queue was this:

  • CBS message processor failed:
  • CBSMetadataProcessingFailure (17005) – InitCustomFieldDimensions cannot process the Project custom field ‘Objective’. Details: id=’17005′ name=’CBSMetadataProcessingFailure’ uid=’c69b0459-5d1f-4d78-a410-f56cd32eca97′ QueueMessageBody=’Setting UID=00007829-4392-48b3-b533-5a5a4797e3c9 ASServerName=<SQLServer> ASDBName=OLAPCube ASExtraNetAddress= RangeChoice=0 PastNum=1 PastUnit=0 NextNum=1 NextUnit=0 FromDate=10/30/2012 00:00:00 ToDate=10/30/2012 00:00:00 HighPriority=True’ Error=’InitCustomFieldDimensions cannot process the Project custom field ‘Objective”.

Hmmm…OK, must be the change I made to the field. I need this field to be multi-value, but I don’t necessarily need it in the cube for reporting. So, I went to remove the field from the cube but it wasn’t listed. Weird. I thought re-saving the OLAP configuration and re-building it would just flush out the field since it was no longer listed in the cube configuration. I got the same error in the queue again.

The only fix I found for this was to re-create the OLAP cube with all of the same settings as previously, minus the “Objective” field, which I couldn’t add anyway as multi-value fields aren’t available to add to the cube.

Hope this helps you out if you come across this error in the future.

Lester

Edit: it seems that this was a known issue back in 2011, which hasn’t yet been fixed. More info on Brian Smith’s blog here: http://blogs.msdn.com/b/brismith/archive/2011/02/04/project-server-2010-take-care-changing-custom-fields-to-allow-multiple-values.aspx

Design a site like this with WordPress.com
Get started