Christophe Fiessinger's Blog
Updates on Microsoft's Enterprise Social Networking (ESN) and Project Portfolio Management (PPM) offerings

  • Christophe Fiessinger's Blog

    Troubleshooting EPM 2007 Queue issues

    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.

  • Christophe Fiessinger's Blog

    Sample Project Server 2003 to Project Server 2007 Migration Plan

    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.

     Project Server Migration Plan

  • Christophe Fiessinger's Blog

    How to restart the Project Server Queue Service with one click?

    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 Queue
    net stop "Microsoft Office Project Server Queue Service"

    @echo START the P12 Queue
    net start "Microsoft Office Project Server Queue Service"

  • Christophe Fiessinger's Blog

    Configuring Project Server 2007 using the command line: STSADM

    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:

      1. Create Shared Service Provider (SSP) Site
      2. Create Project Web Access (PWA) Site
      3. Create SSP for Project Server Interface (PSI)
      4. Create PWA Instance

    To get help of STSADM command line arguments type the following:

    stsadm –help actionname or stsadm –help projcreatepwainstance

  • Christophe Fiessinger's Blog

    Time to Localize: More SharePoint Server 2007 Language Pack!

    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.

    Arabic
    Catalan
    Chinese (Simplified)
    Chinese (Traditional)
    Czech
    Danish
    Dutch
    English
    Finnish
    French
    German
    Greek
    Hebrew
    Hindi
    Hungarian
    Italian
    Japanese
    Korean
    Norwegian (Bokmål)
    Polish
    Portuguese (Brazil)
    Russian
    Spanish
    Swedish
    Thai

  • Christophe Fiessinger's Blog

    Analysis Services 2005 (OLAP) Permission for Project Server 2007

    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?

    SSP 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?

    http://blogs.msdn.com/brismith/archive/2007/02/14/common-error-messages-when-building-cubes.aspx

     

    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

  • Christophe Fiessinger's Blog

    New Application Templates released for WSS V3 that might help your EPM Deployement:

    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

  • Christophe Fiessinger's Blog

    Why consider a Project Server 2007 deployment with Microsoft Office SharePoint Server (MOSS)?

    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.

  • Christophe Fiessinger's Blog

    Why install x64 version of WSS 3.0, SharePoint Server 2007, and SQL 2005?

    Ever wondered what would be the advantages?

    How about installing SQL x64 on a Windows 2003 x64 server?

    Joel Oleson has written an excellent post on this subject: Why WSS 3.0 x64 and MOSS 2007 x64... What's the deal?

  • Christophe Fiessinger's Blog

    Common mistakes when configuring the Cubes Building Service (CBS) with SQL Server Analysis Services 2005

    Prior to troubleshooting your Analysis Services 2005 configuration to "build" your Project Server Cubes, I'll assume you have read the following KB article: 921116 

    During the CBS you get the following error: "Error: ActiveX component can't create object"

    -> Install the following SQL Server 2005 SP1 components:
     
    1. Microsoft SQL Server Native Client (sqlncli.msi)
    2. Microsoft SQL Server 2005 Management Objects Collection (sqlserver2005_xmo.msi)
    3. Microsoft SQL Server 2005 Backward Compatibility Components (SQLServer2005_BC.msi)

    DSO section in Analysis Services configuration file is malformed   

    The msmdsrv.ini is typically located in the following directory: C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Config, once you edit the file use a proper XML editor to ensure that are no carriage return; and no white space are present so that it's a properly formatted XML file.

    Ensure the proper sharing permissions have been set on the share DSO9 folder

    If you are using NTFS make sur both the user account used fot the CBS has been added to the Permission and the Security sections.

    N Tier Deployement

    If your EPM 2007 deployment contains multiple servers (front end with PWA and back end with SQL DB for instance) you'll have to use a domain account on the to configure the access the to AS repository. You'll also have to deploy the DSO components listed earlier on each from end server for it to communicate to the back end DB server.

    Ensure the account used to connect to the CBS has access to AS

     

Page 68 of 69 (689 items) «6566676869