Christophe Fiessinger's Blog Updates on Microsoft's Enterprise Social Networking (ESN) and Project Portfolio Management (PPM) offerings
FYI a new version of the SDK was released yesterday (April 16th):
Thanks to Emmanuel, please find below the sequence to install a mixed Project Server 2003 & Project Server 2007 environment on the same server typically used for testing/merging data during a migration process.
· Install Winproj (Project Professional) 2003 first, and then install Winproj 2007. They work side by side and thus can coexist on the same machine.
Please note that only one of them will get registered as the default to open Winproj file formats. So for actions that involve opening Winproj from Project Web Access, you might end up getting the working version. To avoid this, it is advised to open WinProj before initiating actions from Project Web Access that would invoke WinProj.
· Install EPM 2003 Server and WSS 2.0 first, and then install EPM 2007 (you need to choose to install WSS 3.0 side by side with WSS 2.0 – NOT choose in place upgrade)
WSS 2.0 and 3.0 needs to be extended on different web applications. If EPM 2003 needs to coexist on the same web app as EPM 2007, then you need to add excluded paths for Project Server and MSADC.
· EPM 2003 and EPM 2007 ActiveX controls work side by side since they are distinctly named.
Thanks to Sharry please find below some useful steps when troubleshooting EPM 2007 queue issues:
1. Use Manage Queue page (Sever Settings -> Queue -> Manage Queue) to look at correlations (use the CorrelationUID column for help here) to see why a certain correlation is blocked. Usually if your queue is still working for other jobs/entities, then restarting the queue is not necessary. If you cannot see any problems and your queue is still working, then your filters on the Manage Queue page are not right – check them. Restarting the Queue is only necessary when nothing is processing. Using the “By Project” filter works nicely for looking at the queue job history of projects. For other correlations, use CorrelationUID.
2. Look first for Failed and Blocking states – those are the jobs that are “blocking” others on the same correlation (again, use the correlation UID here to see what jobs are affected). You can either retry these jobs if the error looks like something having to do with something recoverable (like loss of network or database connection), or you can cancel. Canceling with the default settings will cancel the entire correlation, so make sure you know what data you could be losing by doing so.
3. Are jobs stuck in the “Getting Enqueued” state? If so, WinProj needs to be opened again on that user’s machine who submitted the job to see if WinProj will continue sending the project. If that doesn’t work, then you will need to cancel the jobs in this “getting enqueued” state. Note that this effectively means that the save from WinProj never happened, and that data will need to be resaved again. This is the same thing that happens when you just blindly restart the queue. But at least doing it this way means that you know what is being lost.
4. Look at the error (click the link in the Error column) to get an idea about why the failure occurred. Sometimes you can correct the problem and re-save/re-submit your job.
5. Start comparing Event Logs to what you’ve found on the Manage Queue page. Look for errors around the same time as failed jobs in the queue.
6. SharePoint Logs (usually located here: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS ) . Same technique as #5 – look for errors around the same time as failed jobs in the queue.
Once you clear the blocking job(s), the queue should immediately resume processing on that correlation again, and pick up from where it last left off.
Due to popular requests, please find below a sample plan to migrate from EPM 2003 to EPM 2007. Use this plan as a guide and a reminder of all phases and tasks that need to be accomplished during the migration project. The effort (“work”) for each task does not necessarily represent what is required for your environment so use it with a “grain of salt”.
The migration project is divided into four phases:
1. Resource Planning – In this phase the hardware and personal resources must be requested and obtained. It is assumed that a full 4 working weeks will be needed to accomplish this.
2. Migration Planning - here initial training occurs, plans are made, expectations are set, and agreements from all parties are obtained.
3. Migration Test – Here a test system is built out, and the migration procedures are tried out and verified for correctness. This duration of this phase is difficult to predict as issues sometimes occur that must be addressed by support.
4. Production Migration – Here we build up a new production system, migrate the data, and have all users verify that the data has migrated correctly. When this step is successfully completed, the old system can be turned off.
Once in a while you might notice that the Project Server Queue Service is not processing any jobs and that the jobs keep piling up; a quick and easy way to restart the queue is to put the following four lines in a BAT file and launch it. You could also call it as a scheduled task once a week for instance.
@echo STOP the P12 Queuenet stop "Microsoft Office Project Server Queue Service"
@echo START the P12 Queuenet start "Microsoft Office Project Server Queue Service"
Please find below a sample script to setup Project Server 2007 using the command line (without using the WSS Central Admin pages):
To run the script below, change its extension to Stsadm_To_Configure_EPM2007.BAT and run it on the server where you are planning to configure Project Server (it assumes you have already installed the binaries, the WSS Farm has been configured and the Project Server service has been started).
The script will do the following:
To get help of STSADM command line arguments type the following:
stsadm –help actionname or stsadm –help projcreatepwainstance
The following language packs are now available for download here.Please note that these packs includes languages for the following applications: WSS, Office Server, Search, Project Server, and more ... :)
To find out how to deploy language packs for Project Server, read the following article.
ArabicCatalanChinese (Simplified)Chinese (Traditional)CzechDanishDutchEnglishFinnishFrenchGermanGreekHebrewHindiHungarianItalianJapaneseKoreanNorwegian (Bokmål)PolishPortuguese (Brazil)RussianSpanishSwedishThai
Common questions and answers on AS 2K5 permissions for EPM 2007 (thank you David & Steven):
Getting Cube to Build
1. Which application account is responsible for building the cube? Is this the SSP account? The SharePoint Timer Service account?
2. What are the database permissions needed for this account? DataReader on ReportServer? DataReader and DataWriter on OLAPdb?
DataReader on ReportServer, DataReader and DataWriter on OLAPdb (if using SQL as Analysis repository)
3. What are the system permissions needed for this account on the Project Server machines? On the SQL Server machine? On the Analysis Services machine?
Simple user on PS machine. Have not tested on separate SQL/AS machine, but for AS, it needs to be an AS Admin. In some cases I had to put it as a local admin on the SQL server.
4. Do you have a list of common error messages with their solutions?
Allowing Users to View the Cube
1. What permissions need to be setup for users to view the cube? I think part of this stems from the new Analysis Services 2005 security model.
Normally, the right security is added automatically to a defaut AS role during the cube build.
The user added to this role have the Data analysis Project server right. Typically in the Portfolio group
Application templates are out-of-the-box custom scenarios tailored to address the needs and requirements of specific business processes or sets of tasks in organizations of any size. They can be applied to a task, such as managing a help desk or tracking a marketing campaign, to easily create a dedicated Web-based application for a more efficient and effective way of working.
While application templates can be used to solve particular business needs, they also provide a starting point for partners and developers looking to build deeper SharePoint-based solutions. The templates make use of Windows SharePoint Services 3.0 capabilities and are compatible with Microsoft Office SharePoint Designer 2007 to help make customization easier.
Available here: New Application Templates for Windows SharePoint Services 3.0
By default Project Server 2007 gets deployed on top of WSS V3. I've listed below reasons why one should consider deploying Project Server 2007 with Microsoft Office SharePoint Server.