My blog contains information on Microsoft Enterprise Project Management (EPM) Solution 2010/2007/2003. It covers Microsoft Project, Project Server, Project Portfolio Server, SharePoint, SQL Server, SQL Reporting Services, Analysis Services and OLAP for use in the MS EPM Solution.
August 2011 CU for Microsoft Project and Project Server 2010
Server Rollup Package(Recommended): Description of the SharePoint Server 2010 and Project Server 2010 Cumulative Update Server Hotfix Package (MOSS server-package, Project server-package): August 30, 2011 http://support.microsoft.com/kb/2553049 Individual Project Server Package: Only required if you do not install the Server Rollup. Description of the Project Server 2010 hotfix package (pjsrvwfe-x-none.msp): August 30, 2011 http://support.microsoft.com/kb/2553047 Project Client Package: Description of the Project 2010 hotfix package (project-x-none.msp): August 30, 2011 http://support.microsoft.com/kb/2584056 More information on deploying the Cumulative Update: The article below provides information on how to deploy the Project Server Cumulative Update. Updates for Project Server 2010 http://technet.microsoft.com/en-us/projectserver/gg176680.aspx As Project Server 2010 is now based on SharePoint Server 2010 we strongly recommend that you install the Project Server 2010 Server Rollup Package as there are a large number of individual server packages for SharePoint Server. The Project Server 2010 Server Rollup Package contains all the patches released in this Cumulative Update for SharePoint Foundation Server 2010, SharePoint Server 2010 and Project Server 2010. For those accustomed to Project Server 2007 Cumulative Updates, you should note that the MOSS Server Rollup Package does not contain the Project Server patches. You will need to make sure that you install the MOSS + Project Server Rollup Package (the link is provided below). As in Project Server 2007, the Server Rollup Packages are much larger but they will greatly simplify your Project Server patch deployment. Client Installation: Installation of the client patch is straightforward and is the same as it was in Project 2007. The instructions for installing the client patch are below. NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.
Download the hotfix from the link in the KB Article.
Extract the patch package by running the .exe file that you downloaded.
Run the extracted .exe file to apply the patch to your Project Professional/Standard client.
August 2011 CU for Microsoft Office Project and Project Server 2007
Server Rollup Packages: Description of the Windows SharePoint Services 3.0 cumulative update package (WSS server-package): August 30, 2011 http://support.microsoft.com/kb/2553022 Description of the Office SharePoint Server 2007 cumulative update package (MOSS server-package): August 30, 2011 http://support.microsoft.com/kb/2553020 Individual Product Packages: Description of the Office SharePoint Server 2007 hotfix package (sts-x-none.msp): August 30, 2011 http://support.microsoft.com/kb/2553019 Description of the Office Project Server 2007 hotfix package (pjsrvapp-x-none.msp, pjsrvwfe-x-none.msp): August 30, 2011 http://support.microsoft.com/kb/2553024 Description of the Office Project 2007 hotfix package (project-x-none.msp):August 30, 2011 http://support.microsoft.com/kb/2553105 More information on deploying the Cumulative Update: The article below provides information on how to deploy the Project Server Cumulative Update. Deploy cumulative updates (Project Server 2007) http://technet.microsoft.com/en-us/library/dd239177.aspx Service Pack 2 for both WSS and Office Servers 2007 are required for this Cumulative Update. The KB articles below provide information on how to download and install SP2 if you have not already done so. Description of Windows SharePoint Services 3.0 SP2 and of Windows SharePoint Services 3.0 Language Pack SP2 http://support.microsoft.com/kb/953338 Description of 2007 Microsoft Office servers Service Pack 2 and of 2007 Microsoft Office servers Language Pack Service Pack 2 http://support.microsoft.com/kb/953334 The Server CU is released in two different versions. The first version is in Individual Packages specific to a particular product like WSS and Project Server. These are smaller downloads but they do not include language packs or patches for other products so patches for those products would have to be downloaded and installed separately. The second version is the Server Rollup Packages. This is a set of two rollup packages which contains all the fixes for WSS, Project Server and MOSS. These packages should be used when MOSS is part of the deployment and/or you have language packs installed. The Server Rollup Packages are much larger but they will greatly simplify MOSS patch deployment. Client Installation: In order to install this hotfix, you will need to have Microsoft Project 2007 SP2 installed on the client. Description of Office Project 2007 Service Pack 2 (SP2) and of Office Project Language Pack 2007 Service Pack 2 (SP2) http://support.microsoft.com/kb/953326 Once we know that SP2 is installed, you will install the hotfix by performing the following steps: NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.
Download the hotfix from either the KB Article or by using the information at the end of this email.
Extract the patch package by running the .exe file that you downloaded.
Run the extracted .exe file to apply the patch to your Project Professional/Standard SP1 client.
It was a Friday which as usual starts from Client calls & I don't get the time to check my personal emails but on this day, i started my day with my gmail account & checking my emails , full of forum reply & few from others. I noticed an email from "support@microsoftcommunitycontributor" & subject was "Your online community contributions have been recognized by Microsoft". _____________________________________________________________________________________ Dear Amit,
Congratulations! We’re pleased to inform you that your contributions to Microsoft online technical communities have been recognized with the Microsoft Community Contributor Award.
The Microsoft Community Contributor Award is reserved for participants who have made notable contributions in Microsoft online community forums such as TechNet, MSDN and Answers. The value of these resources is greatly enhanced by participants like you, who voluntarily contribute your time and energy to improve the online community experience for others. ..................................................
When you are using the Office Web apps in SharePoint 2010 then you may come across this error…
“This workbook cannot be opened because it is not stored in an Excel Services Application trusted location.
To create an Excel Services Application trusted location, contact your system administrator.”
If you happen to be the system administrator and you’ve turned to googlebing google to find the answer hopefully this blog post will help you out! I believe this error is most likely if you are going over SSL as the default trusted location is just http:// Jump into central admin (please ignore my heath analyzer!) and goto Manage service applications. Click on Excel services Application. Then click on “Trusted file locations” You can see that http:// is already there, so you could just add https:// or put in a url to a specific location Fill in the boxes, I also ticked the trust children box.
Now, You should be able to open the Excel workbook from your sample excel report in BI center of Project server.
Ref:http://www.microsoft.com/showcase/en/us/details/34f2e816-bec5-4a5a-a7f8-b356dac292fc Project Server has a new infrastructure for building out a demand management process. This session covers the capabilities built in and how the workflow can be customized and extended to meet your business needs. This session will go over the following concepts: Developer experience in creating a Workflow; Deployment story for Project workflows; Administrator experience in creating Workflow Controlled Enterprise Project Types:
Today I was browsing the Project Server forum & found a very easy but interesting question about displaying the task calender information in report which pulls the data from Project Server Reporting database. Since this information is not available in reporting database so thought a workaround & get the information.
1. Tried creating a TAsk level text custom field using formula:
2. In the formula section, picked up the field Text> Task Calendar
3. Added Task Calendar & when I tried to save that, got the error:
The custom field could not be saved due to the following reason(s):
This formula contains references to one or more fields that do not exist in the system. Correct the formula and try again.
4. Now, I thought to create the same field from project professional :
- Open project professioanl & Connect to Server
- Click on Project Tab
- Click on Custom fields button on the ribbon
- Select Task (radio button) & selected Text from the drop downlist of "Type"
- Clicked on formula
- Also, Clicked on Add field to Enterprise
- Created a plan & kept the TAsk level calender & added the TASK_CAL_CF column & I was able to see the calender applied to the task copied to Custom field.Published the Plan
- Ran the below query, I was able to get the information in PS Reporting database SELECT [TaskUID],[TaskParentUID],[ProjectUID],[FixedCostAssignmentUID],[TaskName],[TASK_CAL_CF (Text1)]FROM [ProjectServer_Reporting].[dbo].[MSP_EpmTask_UserView]
What a beautilful weather & I was kinda enjoying but suddenly One of My coworker pinged me & asked me a question about the Project level custom fields (multiline Text) so while I explained him about the usage of this kind of field, thought to write down somthing which might help Project Server community :)
Text custom fields can be multiline up to 4000 bytes, for use in project detail pages (PDPs) and with workflows for demand management in Project Web App. Multiline text custom fields are not usable in Project Professional. so I added a Project level Multiline text field in my PDP & now I wanted to update this field in a given project from my PSI program.
Here is the code for the Console application : 1. You will need to add project web service (ProjectWebSvc) web ref in the solution: http://servername/pwa/_vti_bin/PSI/Project.asmx?wsdl 2. Its very basic code, which has TEXT_VALUE update for a Multiline field
_____________________________________________________________________ using System; using System.Diagnostics; using System.Net; using System.Data; using System.Text; using Microsoft.Office.Project.Server.Library; using PSLibrary = Microsoft.Office.Project.Server.Library;
ProjectWebSvc.Project proj = new ProjectWebSvc.Project();true;ProjectDataSet pds = null;
Guid projectGuid = newGuid("195D9230-4A41-438A-917F-FDB6B292F586"); //Project for which I want to update the Multiline text field
}foreach (ProjectWebSvc.ProjectDataSet.ProjectCustomFieldsRow row in pds.ProjectCustomFields)"TYPE your multiline text,TYPE your multiline text,TYPE your multiline text,TYPE your multiline textTYPE your multiline textTYPE your multiline text,TYPE your multiline text,TYPE your multiline text,TYPE your multiline textTYPE your multiline text,TYPE your multiline text,TYPE your multiline text";Guid sessionUId = Guid.NewGuid();proj.CheckOutProject(projectGuid, sessionUId, " ");Guid jobUId = Guid.NewGuid();proj.QueueUpdateProject(jobUId, sessionUId, pds,
proj.QueueCheckInProject(jobUId, projectGuid, false);true, " ");Guid.NewGuid();false, sessionUId, "none"); }
Enterprise Project Types (EPTs) are project templates that represent various types of projects and non-project work within the portfolio. For example, you can create an Enterprise Project Type to represent a HR related software Maintenance/development project or a marketing campaign.
An EPT is a combination of phases, stages, a single workflow, and Project Detail Pages. Each EPT represents a single project type. Normally, project types are aligned with individual departments, for example, marketing projects, IT projects, HR projects, and so forth. Using project types in Project 2010 now helps to categorize projects within the same organization that have a similar project life cycle
To create a new enterprise project type
On the PWA home page, click Server Settings.
Click New Enterprise Project Type. In the Name box, enter a name for the type (e.g HR_Project_EPT), and then provide a brief description in the Description box.
Select a workflow from the Site Workflow Association list. Once you associate a site workflow with a project type and save the type, you cannot go back and update the type to use a different workflow.
Select a project detail page from the New Project Page list.
If you selected No Workflow from the Site Workflow Association list, select the project detail pages that you want to include in this project type from the Available Project Detail Pages box, and then click Add to move them to the box on the right.
If the enterprise project type that you are creating is the one that all new projects should use by default, select theUse this as the default Enterprise Project Type during Project Creation check box.
Click the button next to the Departments field to select the departments that you want to associate with this project type, if it is appropriate.
If you want to associate an image with this project type, provide the URL for the image in the Type the URL box.
In the Order section, choose whether you want this project type to appear at the end of the list of project types, or if you want to control its placement in the list.
To include this type at the end of the list, select the Position this type at the end check box.
To control the placement of this type in the list, clear the Position this type at the end check box, and then choose the type that you want to appear just before the type that you are creating from the Choose the type before which the current type should be positioned list.
Select a template from the Project Plan Template list, if it is appropriate.
Select a template from the Project Site Template list, if it is appropriate.
Click Save to save this enterprise project type to the server, thus making it available for new project or proposal creation.