Christophe Fiessinger's Blog Updates on Microsoft's Enterprise Social Networking (ESN) and Project Portfolio Management (PPM) offerings
Quite often when you are performing customizations or when you want to troubleshoot your Project Server deployment it's useful to go "deep" and see what's happening under the SQL hood.
The best way to achieve that is to run a SQL Server Profiler trace on the SQL Server instance you want to analyze. Since Project Server 2007's architecture is based on a queuing system you will find a lot of "noise" if you run a standard trace.
I have attached at the end of this post a template I have created that eliminates a lot of the extra SQL queries due to the queuing system.
Please note that this trace only looks at databases with the suffix Published and ignores commands with prefix MSP_TimesheetQ.Happy tracing!
Bill Baer’s white paper: Database Maintenance for SharePoint is now live.
Table of Contents
On December 11th, 2007 Microsoft released Service Pack 1 (SP1) for the 2007 Microsoft Office System. We released this week the post-SP1 hotfix package (fixes made after the SP1 code base was locked down and up until SP1 is released), as well as Project Portfolio Server 2007 Service Pack 1.
This hotfix package is intended to correct only the problems that are described in the Knowledge Base (KB) articles mentioned below. Apply it only to systems that are experiencing this specific problem, or if the customer has been waiting for this package to deploy SP1.
I'll be hosting the following webcast targeted at IT Professionals on Thursday, March 20, 2008, 11:00 AM Pacific Time (US & Canada)
Out of the box, Microsoft Office Project Server 2007 is deployed on top of Windows SharePoint Services. In this session, we explain why customers are deploying Project Server 2007 with Microsoft Office SharePoint Server 2007 as well, and we describe how together these products offer the best combination of collaboration, project, and portfolio management. We review and demonstrate the added benefits of Report Center, Excel Services, key performance indicators (KPI), InfoPath Forms Services, Business Data Catalog, and Enterprise Search in the context of a Project Server deployment.
Register for this Live Webcast
Watch lectures delivered by experts in Microsoft Office SharePoint Server 2007, and download and read supporting white papers:
Advanced lectures and white papers
The Project Server 2007 Timesheet data population tool has been released on CodePlex: http://www.codeplex.com/EPMTSdatapop
The Project Server 2007 Timesheet Data Population Tool enables you to simulate timesheet entries in your farm. This tool can help you perform scalability studies of your PS architecture and validate the sizing of an existing architecture (by measuring timesheet queue throughput for instance). This tool can also be used to test timesheet customization, for instance the Timesheet Tied-mode code sample on Codeplex. This powerful tool should not be run a production environment!
The Timesheet Data Population tool is a console application written in C#. It uses standard PSI (Project Server Interface) web service methods to populate timesheets.
Please refer to the latest version of the Project Server Software Development Kit (SDK) for more information on the PSI methods and how to use them.
This solution starter was written initially to perform Project Server 2003 vs. Project Server 2007 benchmarks, and has been used since to perform scalability studies and to test timesheet customizations.
These hotfix are intended to correct only the problem that is described in the KB articles above. Apply it only to systems that are experiencing the specific problem.
Contact Microsoft Customer Support Services to obtain these hotfix.
PPS SP1 was released today.
Description of Project Portfolio Server 2007 Service Pack 1:
Download PPS SP1
This service pack can only be applied to an existing installation of Microsoft Office Project Portfolio Server 2007.
To install Microsoft Office Project Portfolio Server 2007, please see the deployment guide.
A new solution starter that demonstrates how to leverage InfoPath & Forms Services as well Windows Workflow Foundation (hosted by SharePoint) to create your own project initiation phase has been released on CodePlex.
The project initiation phase is different for every customers and organizations. It typically requires a set of custom attribute to be filled in a web based custom form; and then it needs to go through a custom approval process workflow reviewed by all key decision makers. InfoPath Forms services combined with a SharePoint’s sequential workflow enables you to achieve this business need. This solution starter also demonstrates the added value of deploying Project Server 2007 in a SharePoint Server farm (using InfoPath Forms Services).
The goal of this solution starter is thus to provide the following two code samples:
This solution starter requires Project Server 2007, InfoPath and Forms Services 2007, and Visual Studio 2008.
This solution starter was created for a presentation I delivered at the 2008 Office Developer Conference.
Please find below useful links when deploying Project Standard or Project Professional on a Terminal Services (or Citrix) environment.
A common issue I have heard/seen is that the version used on Terminal Services is incorrect (you need a Volume License Key) with this type of error message displayed: "This copy of Microsoft Office Project cannot be used on Terminal Server".
This issue is addressed in the following knowledge base article: http://support.microsoft.com/kb/924622
Other useful links are: