• Project Server 2010 & 2007

    Project workspaces retain look and feel of Project Server 2007 even after being migrated to Project Server 2010.

    • 0 Comments

    All the workspaces look and feel look like Project Server 2007 after upgrading content from Project Server 2007 to Project Server 2010 with the help of DB attach upgrade method.

    To get the new look and feel of Project Server 2010, we need to follow the steps given below;

    At the time of attaching a content database to Project Server 2010 we need to add a switch in “stsadm –o addcontentdb” command;

    “–preserveolduserexperience false”

    The whole command looks like;

    stsdm -o addcontentdb -url http://PWA:80 -databasename contentdatabasename -databaseserver SQLservername -preserveolduserexperience false

    PWA: Name of Project Web App

    80: Port number of PWA.

    If the environment has already been migrated and if we would like to get the 2010 look and feel, we need to follow below given step for each and every project workspace site.

    Open the affected workspace with system account.

    Click on Site Actions –> Visual upgrade.

    The site(s) will have new 2010 look and feel.

  • Project Server 2010 & 2007

    Project Server 2007 JUNE CU 2010 Released

    • 0 Comments

    Server Rollup Packages:

     

    Individual Product Packages:

     

    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 (~200MB each) but they will greatly simplify MOSS patch deployment.

    The article below provides information on how to deploy the Project Server Cumulative Update.

  • Project Server 2010 & 2007

    Integration of Project Server 2010 and Exchange 2010/2007

    • 0 Comments

    Recently I worked on interesting issue of Project Server 2010 and Exchange integration.

    Where customer has three exchange CAS servers (two Exchange 2010 servers and one exchange 2007 server)

    We followed   Configure Project Server 2010 to work with Exchange Server 2010 and Configure Project Server 2010 to work with Exchange Server 2007 R2

    But still we were getting following Impersonation errors in event log.

    PSError: GeneralExchangeSyncError (40500) System.Web.Services.Protocols.SoapException: The account does not have permission to impersonate the requested user.

    clip_image002

    After deep drill we understand due to new RBAC concept in exchange server 2010, first we need to use the New-ManagementRoleAssignment Exchange Management Shell cmdlet to assign the ApplicationImpersonation role to users in the organization. (Only in the case of Exchange 2010)

     

    To configure Exchange Impersonation for all users in an organization


    1. Open the Exchange Management Shell.

    2. Run the New-ManagementRoleAssignment cmdlet to add the permission to impersonate to the specified user. The following example shows how to configure Exchange Impersonation to enable a service account to impersonate all other users in an organization.

    New-ManagementRoleAssignment -Name:impersonationAssignmentName -Role:ApplicationImpersonation -User:serviceAccount

     

    To configure Exchange Impersonation for specific users or groups of users


    1. Open the Exchange Management Shell.

    2. Run the New-ManagementScope cmdlet to create a scope to which the impersonation role can be assigned. If an existing scope is available, you can skip this step. The following example shows how to create a management scope for a specific group.

    New-ManagementScope -Name:scopeName -RecipientRestrictionFilter:recipientFilter

    1. Run the New-ManagementRoleAssignment cmdlet to add the permission to impersonate the members of the specified scope. The following example shows how to configure Exchange Impersonation to enable a service account to impersonate all users in a scope.

    New-ManagementRoleAssignment -Name:impersonationAssignmentName -Role:ApplicationImpersonation -User:serviceAccount -CustomRecipientWriteScope:scopeName

    The RecipientRestrictionFilter parameter of the New-ManagementScope cmdlet defines the members of the scope. You can use properties of the Identity object to create the filter. The following example is a filter that restricts the result to a single user with the user name "John."

    Name -eq 'John'

    Taken from Configuring Exchange Impersonation

     

    Once it is done then we followed our Configure Project Server 2010 to work with Exchange Server 2010 article BUT  according to above document

     

    At the prompt, type the following command:

    Add-ADPermission -Identity (get-exchangeserver).DistinguishedName -User (Get-User -Identity <AppPoolAccount> | select-object).identity -extendedRights ms-Exch-EPI-Impersonation

    <AppPoolAccount> is the application pool account for the Project Server service application noted in the previous procedure.

    This would probably work fine in an environment with one Exchange server, but in the event you have more than one Exchange server the “Get-ExchangeServer” cmdlet would return an array of servers, causing the command to fail with “Cannot bind argument to parameter ‘Identity’ because it is null.”

    clip_image004

    To fix this the command will have to be run against every server running the Client Access Role. One way of doing this is to use the following PowerShell commands in the EMS:

     

    $CAS = get-exchangeserver | where { $_.ServerRole -match "ClientAccess" }

    $CAS | foreach-object {Add-ADPermission -Identity $_.DistinguishedName -User (Get-User -Identity DOMAIN\AppPoolAccount | select-object).identity -extendedRights ms-Exch-EPI-Impersonation}

    clip_image006

    Then we executed second command to configure exchange user

    At the prompt, type the following command:

    Add-ADPermission -Identity "<ProjUser>" -User <FarmAdministrator> -extendedRights ms-Exch-EPI-May-Impersonate

    <ProjUser> is the name of the Project Server user whom you are configuring, and <FarmAdministrator> is the SharePoint Server farm administrator account.

    clip_image008

    Then we are successfully able to integrate Project Server 2010 with Exchange Server 2010/2007 without any errors and we are able to pull tasks in Outlook and update the assignments from Outlook to Project Server 2010

    So in a nutshell just remember to use the New-ManagementRoleAssignment Exchange Management Shell cmdlet to assign the ApplicationImpersonation role to users in the organization. (Only in the case of Exchange 2010)

    And in the case of multiple exchange CAS servers use above script to bypass the “Cannot bind argument to parameter ‘Identity’ because it is null.” Error.

  • Project Server 2010 & 2007

    Project 2010 Webcasts Series

    • 3 Comments

    I am very excited while writing this post.  My coworker Kiran Khanvilkar who has extreme good knowledge and passion about MS Project, is going to deliver LIVE webcast’s on various topic’s of Project 2010.  

    Project 2010 new reporting functionality

    May 10, 2010 |  4:00 PM - 5:00 PM

    clip_image001Add to Calendar

    Project 2010 new reporting functionality: Project server 2010 offers integration with excels services to create reports using MS Excel. In this session we will look at new reporting and business intelligence features.                                                                                   

    Project server 2010 Task Delegation

    May 24, 2010 |  3:00 PM - 4:30 PM

                                                              clip_image001Add to Calendar

    Project server 2010 Task Delegation, editing plan from project web app, new time tracking and time sheet functionality.

    Project Server 2010 Demand Management

    June 07, 2010 |  4:00 PM - 5:00 PM

                                                             clip_image001Add to Calendar

    Project Server 2010 Demand Management with Demo.

    Project Portfolio Analysis

    June 21, 2010 |  3:00 PM - 4:30 PM

                                                              clip_image001Add to Calendar

    Project Portfolio Analysis:  Project Portfolio features are now a part of core Project Server product. In this session we will cover. In this session we will cover how to perform Portfolio analysis within project server 2010

    Speaker:  Kiran Khanvilkar

    Kiran is working as Senior Support Engineer for Project Server at Microsoft GTSC for more than four years. In current role he works with Microsoft worldwide premier customers on Project Server Implementation, troubleshooting and EPM best practices. Overall he has 8+ years of experience in field of Microsoft EPM and Microsoft Office products. Prior to joining Microsoft he worked as Corporate Trainer and has trained 800+participants on products like MS Project, MS Project Server, MS Excel, MS Access and VBA Programming.

  • Project Server 2010 & 2007

    Please share your feedback on Project reporting experiences to our product group.

    • 0 Comments

    http://blogs.msdn.com/project/archive/2010/04/07/how-do-you-report.aspx

    How do You Report?

    Project wants to know how you report. As we plan for future product improvements, we want to learn more about how you report on your project’s status today.

    · What tools do you use?

    · How often do you report on your project’s status?

    · What data do you care about?

    · How do you share your reports?

    · What do you find difficult with your current process?

  • Project Server 2010 & 2007

    Project Server 2007 April CU Released

    • 0 Comments

    You can read about the fixes included in the April CU from the following articles:

    Server Rollup Packages:

    (http://support.microsoft.com/kb/981043/ ) Description of the Windows SharePoint Services 3.0 Cumulative Update Server Hotfix Package (WSS server-package): April 27, 2010

    http://support.microsoft.com/kb/981043/

    Description of the Office SharePoint Server 2007 Cumulative Update server hotfix package (MOSS server-package): April 27, 2010

    http://support.microsoft.com/kb/981042/

    Individual Product Packages:

    Description of the Windows SharePoint Services 3.0 Cumulative Update server hotfix package (Sts-x-none.msp): April 27, 2010

    http://support.microsoft.com/kb/981040/

    Description of the Project Server 2007 hotfix package (Pjsrvapp-x-none.msp; Pjsrvwfe-x-none.msp): April 27, 2010

    http://support.microsoft.com/kb/981044

    Description of the Office Project 2007 hotfix package (Project-x-one.msp): April 27, 2010

    http://support.microsoft.com/kb/981732/

    Client Installation:

    In order to install this hotfix, you will need to have Microsoft Project 2007 SP1 installed on the client. The article at the URL below contains information on how install download and install SP1 should you not have it installed already.

    Note:  We strongly recommend that you install Project 2007 SP2 from the information earlier in the article.

    Description of Project 2007 Service Pack 1 and of Project Language Pack 2007 Service Pack 1

    http://support.microsoft.com/kb/937154/en-us

  • Project Server 2010 & 2007

    Microsoft Project 2010 Ignite

    • 0 Comments

    clip_image001

    We are very happy to announce the availability of the Microsoft Project 2010 Ignite beta training slides on Microsoft’s download site:

    http://technet.microsoft.com/en-us/library/ff358349(office.14).aspx

    The downloadable file contains the following eleven presentations that are used in the three-day training course delivered worldwide:

    · Project 2010 Ignite Introduction

    · Project 2010 Overview

    · Project 2010 Planning, Design, and Deployment

    · Project 2010 Upgrade and Migration

    · Project 2010 Demand Management

    · Project 2010 Portfolio Strategy

    · Project 2010 Timesheets and Statusing

    · Project 2010 Reporting

    · Project 2010 Administration

    · Project 2010 Operations

    · Project 2010 Developer

    The goal for the Project 2010 Ignite Program is to prepare EPM professionals for deployment, operations and customization of Project Server 2010, hence to build skilled EPM partners by General Availability scheduled for June 2010. The "Ignite" curriculum is targeted towards EPM consultants, IT Professionals, Admin Professionals and Developers that have experience deploying, operating and customizing Project Server 2007.  Content will be technical and will range from 300 to 400 levels (Experienced to Advanced/Expert). With this in mind, the "Ignite" content will not be designed to cover all Project Server functionality, only the new functionality of Project Server 2010 will be presented.  In other words the goal is to help better understand the differences, deltas and new features. The content will be a combination of instructor-led training, product demonstrations and hands-on labs. The Project 2010 "Ignite" training will be delivered in English by EPM experts from Microsoft.

    Ignite agenda and registration: https://dynamicevents.emeetingsonline.com/emeetings/websitev2.asp?mmnno=327&pagename=SITE52841

    Key Microsoft Project 2010 Resources

    · Project 2010 Web site: http://www.microsoft.com/project/2010

    · Project 2010 Demo Image: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=8e709e2e-c9a1-4c7e-90d6-a52bcc8e5daf

    · Project Server 2010 Beta TechCenter (TechNet): http://technet.microsoft.com/en-us/projectserver/ee263909.aspx

    · Project 2010 Beta Resource Center (MSDN): http://msdn.microsoft.com/en-us/office/ee695847.aspx

    · Project 2010 webcasts and podcasts: http://www.microsoft.com/events/series/epm.aspx?tab=webcasts

    · Project 2010 Forums: http://social.technet.microsoft.com/Forums/en-US/category/projectserver2010,projectprofessional2010

    I am Project 2010 ready, are you?

  • Project Server 2010 & 2007

    Project 2010 Beta launch!

    • 0 Comments
    image

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

    Explore More

  • Project Server 2010 & 2007

    Project Server 2007 PWA on Kerberos Authentication

    • 1 Comments

    Thanks to ajjose for this posting..

      Provisioning PWA Using Kerberos Authentication

    Step 1:

    Create web application with Kerberos Auth.

    clip_image002

    Step 2:

    Download Windows 2003 Support tools (http://support.microsoft.com/kb/892777)

    Steps 3:

    Create SPN’s for the web application/s

    Syntax:

    Setspn.exe -A HTTP/%SHAREPOINTSERVERFQDN% %SERVERFARMACCOUNT%

    Example: Setspn.exe –A HTTP/Servername.domain.com:20266 domain\account

    Step 4:

    In addition to setting the SPNs for each of your service accounts, you also need to trust each of the computer accounts and some of the service accounts for delegation. Trusting for delegation means that the accounts are allowed to delegate on a user's behalf.

    In order to trust for delegation you need to open Active Directory Users and Computers as a user with domain administration rights and follow these instructions

    • Locate the account and click 'properties'
    • Navigate to the 'Delegation' tab
    • Choose 'Trust this user/computer for delegation to any service (Kerberos)'

    clip_image004

    Note: if you do not see Delegation tab, Make sure you have raised the domain functionality level to Windows Server 2003 (Open Active Directory -> Right Click on Domain name -> Select Raise Domain Functional Level -> Select Windows Server 2003 -> Click on Apply

    Step 6:

    Login into MOSS server, Configure Component services to allow Kerberos

    Open Component Services on the MOSS server

                    > Navigation to Component Services > Computers > My Computer

                                      • Right Click on My Computer -> Properties - > Default Properties -> Default Impersonation Level = Delegate (see http://support.microsoft.com/kb/917409)

    clip_image006

    > Navigate to Component Services > Computers > My Computer > DCOM Config > IIS WAMREG Admin Service

    Click on Properties (for IIS WAMREG Admin Service) and navigate to the Security tab

    >Edit Launch and Activate Permissions

    >Grant all three of your application pool account 'Local Activation' permissions

    clip_image008

    Step 7:

    Create a new SSP using the new web application

    Change SSP to Kerberos ('STSADM.exe -o SetSharedWebServiceAuthn -negotiate')

    Enable Kerberos on IIS

                    cscript adsutil.vbs set w3svc/NTAuthenticationProviders "Negotiate,NTLM"

    Provision PWA on new SSP

    Additional Links

    http://technet.microsoft.com/en-us/library/cc263449.aspx

    http://blogs.msdn.com/martinkearn/archive/2007/04/23/configuring-kerberos-for-sharepoint-2007-part-1-base-configuration-for-sharepoint.aspx

  • Project Server 2010 & 2007

    Project Client 2010 Ribbon

    • 0 Comments

    Now all game is about RIBBON in project 2010 :)

    Our product group recently posted very interesting posting about Project 2010 look and feel

    Must visit on http://blogs.msdn.com/project/archive/2009/09/24/project-2010-introducing-the-ribbon.aspx

    image

  • Project Server 2010 & 2007

    Project Server 2010 an overview

    • 0 Comments

    WOW ...Project Server 2010 what a product!!! 

    Microsoft Project 2010, generally available next year, will provide teams and organizations of all sizes with the right project collaboration tools, and a pathway to step up to more advanced Project and Portfolio Management capabilities as their needs evolve.

    clip_image002

    A First Look for you.

     

    PWA Home Page

    Project Centre

    clip_image004

    clip_image006

    Editing Projects from PWA

     

    clip_image008

    clip_image010

    Scheduling and Change Highlighting

    Multilevel Undo on Web

    clip_image012

    clip_image014

    More type of Projects with Different Defined Workflows

    Project Authoring and Completely Configuration View

    clip_image016

    clip_image018

    Project Workflow Status

    Workflow Stage and View

    clip_image020

    clip_image022

    Project Information

    Defining Project from Workflow

    clip_image024

    clip_image026

    Portfolio Analysis

    Update the Portfolio after updating budget to less

    clip_image028

    clip_image030

    Making project Compliance

    Scatter Chart

    clip_image032

    clip_image034

  • Project Server 2010 & 2007

    Project Server 2007: Service pack 2 Webcasts

    • 1 Comments
    on April 28th,  Service Pack 2 (SP2) for Microsoft Office System – including Project and Project Server 2007 will be released, along with SP2 for all the other office applications, including Office SharePoint Server and also WSS excluding PPS.  We have a couple of webcasts organized on the morning of the 29th and the evening of the 30th which hopefully allow us to cover most time zones.  Join Adrian Jenkins and Christophe Fiessinger as they give an overview of this important release, best practices for deployment and also time for questions and answers.  As a reminder the key fixes in this release will be:

    Project (desktop)

    • The scheduling engine, Active Cache, and Gantt charts all have improvements.
    • There is additional reliability with earlier versions of the .mpp format.

    Project Server

    • Better memory management in the queue service.
    • Performance to certain database table indexes is improved.
    • Resource plans, build team, cost resources, and the server scheduling engine have improved.

    Details of the webcasts follow:

    Please note we will deliver the same webcast twice to accommodate different time zones, we will also record these webcast and will make them available on EPMConnect:

    • Wednesday April 29, from 8-9 am Pacific Time
    • Thursday April 30, from 5-6 pm Pacific Time

    Webcast Details

    April 29 – 8-9am Pacific Time
    April 30 – 5-6pm Pacific Time

    Meeting URL
    https://www.livemeeting.com/cc/lmevents/join?id=OEM042AM&role=attend&pw=ATT5678
    https://www.livemeeting.com/cc/lmevents/join?id=OEM042PM&role=attend&pw=ATT6789

    Event Info
    Meeting ID: OEM042AM
    Entry Code: ATT5678
    Meeting ID: OEM042PM
    Entry Code: ATT6789

    Back-up Audio
    (If you are unable to connect to the audio through the Computer Audio, you can dial in to the audio over a traditional telephony line)
    US/Canada: (1) (877) 241-9971
    International: (1) (503) 295-8000
    Pin: 3616
    US/Canada: (1) (877) 241-9971
    International: (1) (503) 295-8000
    Pin: 3616

    Requirements for Attending this Event
    We strongly suggest you test your computer's configuration: https://events.livemeeting.com/LM2007test.htm to ensure you are running the most current version of Microsoft Office Live Meeting.

  • Project Server 2010 & 2007

    SharePoint Designer 2007 is now FREE !!

    • 1 Comments

    SharePoint Designer 2007
     

    Brief Description 

    SHAREPOINT DESIGNER 2007 IS NOW FREE! Be sure to watch the video in the "Related Resources" below to learn more about details and future direction. Office SharePoint Designer 2007 provides the powerful tools you need to deliver compelling and attractive SharePoint sites and quickly build workflow-enabled applications and reporting tools on the SharePoint platform, all in an IT-managed environment.
     
  • Project Server 2010 & 2007

    Project Server 2007 Feb CU released

    • 1 Comments

     

    FEB CU comes in two different versions. The first version is in individual packages specific to a particular product like WSS , Project Server and MOSS. If you do not have MOSS installed and have already installed the infrastructure update for office servers then you can download and install these individual packages.

     

    The second version is the Office Server Rollup Packages. This is a set of two uber-packages which contains all the fixes for WSS, Project Server and MOSS. These packages should be used when MOSS is part of the deployment or infrastructure update has not been deployed to the server environment. The Server Rollup Packages are much larger (~200MB) but they will greatly simplify MOSS patch deployment.

     

    The Office Server Rollup Packages include all of the fixes included in the Infrastructure Update so installing these packages will allow you to skip the added step of deploying the Infrastructure Update. The Infrastructure update only needs to be installed once so this will not be a consideration for deployment that already have the Infrastructure Update installed.

     

     Individual Product Packages ( WSS 3.0 + PSVR2007 )

     

     

    Server :

     

    Description of the Windows SharePoint Services 3.0 hotfix package (Sts.msp): February 24, 2009

    http://support.microsoft.com/kb/961750

     

    Description of the Project Server 2007 hotfix package (Pjsrvapp.msp, Pjsrvwfe.msp): March 6, 2009

    http://support.microsoft.com/kb/968271

     

     

    Office Servers Rollup Packages  ( MOSS + PSVR2007 )

     

     

    Description of the Windows SharePoint Services 3.0 cumulative update package: February 24, 2009

    http://support.microsoft.com/kb/961755

     

     

    Description of the SharePoint Server 2007 cumulative update package (MOSS server-package): February 24, 2009

    http://support.microsoft.com/kb/961756

      

     

    Project Client :

     

    Description of the Project 2007 hotfix package (Project.msp): February 24, 2009

    http://support.microsoft.com/kb/966308

     

     

     

     

     

  • Project Server 2010 & 2007

    How do you find out what version of SharePoint or Project Server 2007 you are running?

    • 1 Comments

    The first approach is to open a web browser and got to the site settings page

     

    (Site Actions > Site Settings > Modify All Settings).

     

    The second approach is against the databases. Open SQL Server Management Studio, Connect to the server, new query, run the following:

     

    Use Sharepoint_ConfigDb

     

    SELECT *

     

    FROM Versions

     

    WHERE VersionId = '00000000-0000-0000-0000-000000000000'

     

    ORDER BY Id DESC

     

    This returns (columns reduced for readability):

     

    VersionId Version Id UserName Updates

     

    00000000-0000-0000-0000-000000000000 12.0.0.6219 4 MOSS\user 3

     

    00000000-0000-0000-0000-000000000000 12.0.0.4518 1 MOSS\user 2

     

    The top row is the latest version. The query is performed on the SharePoint Configuration database. If you have called this database something instead of "SharePoint_Config" change the query to reflect this.

     

    You can also look at the versions for Content Databases, by changing the database name. For example: FROM WSS_Content_MySites.[dbo].[Versions]

     

     

    MOSS Product Version

     

    MOSS 2007 OCT Cumulative update 12.0.0.6331

     

    MOSS 2007 Aug Cumulative update 12.0.0.6327

     

    MOSS 2007 Infrastructure Update 12.0.0.6318

     

    MOSS 2007 post SP1 hotfix KB948945 12.0.0.6303

     

    MOSS 2007 post SP1 hotfix KB941274 12.0.0.6301

     

    MOSS 2007 post SP1 hotfix KB941422 12.0.0.6300

     

    MOSS 2007 SP1 12.0.0.6219

     

    MOSS 2007 October public update 12.0.0.6039

     

    MOSS 2007 August 2007 hotfix 12.0.0.6036

     

    MOSS 2007 RTM 12.0.0.4518

     

     

    FOR PROJECT SERVER 2007

     

    **************************

     

    Use ProjectServer_Published

     

    SELECT *

     

    FROM Versions

     

    WHERE VersionId = '00000000-0000-0000-0000-000000000000'

     

    ORDER BY Id DESC

     

     

    Project and Project Server 2007 Hotfix Versions

    Number

    Release

    Server KB

    Client KB

    4518.1016

    RTM

    N/A

    N/A

    6061.5000

    RTM HF1

    N/A

    935557

    6018.5000

    RTM HF2

    936134

    N/A

    6019.5000

    RTM HF3

    N/A

    936517

    6020.5000

    RTM HF4

    936876

    N/A

    6023.5000

    RTM HF5

    937908

    937907

    6024.5000

    RTM HF6

    N/A

    938189

    6026.5000

    RTM HF7

    938891

    938889

    6027.5000

    RTM HF8

    N/A

    939182

    6028.5000

    RTM HF9

    939594

    939595

    6218.1000

    SP1

    936984

    937154

    6301.5000

    SP1 HF1 (Rollup)

    941426

    941657

    6304.5000

    SP1 HF2

    N/A

    949398

    6307.5000

    SP1 HF3

    N/A

    950284

    6308.5000

    SP1 HF4

    N/A

    950480

    6309.5000

    SP1 HF5

    950816

    N/A

    6310.5000

    SP1 HF6

    N/A

    951166

    6312.5000

    SP1 HF7

    951169

    N/A

    6313.5000

    SP1 HF8

    952000

    952067

    6314.5000

    SP1 HF9

    952289

    952293

    6316.5000

    SP1 HF10

    953136

    N/A

    6317.5000

    SP1 HF11

    953478

    953476

    6318.5000

    Infrastructure Update

    951297

    951547

    6327.5000

    CU1 - August 2008

    956061

    956060

    6331.5000

    CU2 - October 2008

    957696

    958138

    6334.5000

    CU3 - December 2008

    960313

    959643

    6341.5002

    CU4 – Feb 2009

    968271

    966308

    6422.1000

    SP2

    953334

    953326

    6503.5000

    Apr 09 CU

    968860

    969409

     

    *For Project Client you can check from Project Professional >>Help >>About Microsoft Office Project

  • Project Server 2010 & 2007

    Project Server 2007 ::Reporting (WSS Sync) Job Failed but not Blocking

    • 6 Comments

    Project Server 2007 ::Reporting (WSS Sync) Job Failed but not Blocking

     

    There could be multiple Scenario’s for the same based on error messages

    In error message please focus on SPListType=”xxxx” Error=”yyyyy”

     

    SP List ID   SP List Name

    1100            Issues

    1101            Risks

    1104            Deliverables

     

     

    Scenario 1.

    **********

     

    <error id="24018" name="ReportingWssSyncListFailed" uid="98df7838-4760-49ed-864c-a27773850d18" SPListType="1100" Error="Mismatched transaction." />
    <error id="24018" name="ReportingWssSyncListFailed" uid="64ee928c-6ca1-47ee-be13-d033c76bedba" SPListType="1101" Error="Mismatched transaction." />
    <error id="24018" name="ReportingWssSyncListFailed" uid="3cc8deea-acba-4bc1-bc3c-214643ed47aa" SPListType="1104" Error="Mismatched transaction." />
    <error id="24018" name="ReportingWssSyncListFailed" uid="a15bcba9-59c7-41d8-a634-d24e8b317ee0" SPListType="1100" Error="Mismatched transaction." />
    <error id="24018" name="ReportingWssSyncListFailed" uid="9ef51835-0e70-4cf3-85d9-809805044814" SPListType="1101"

     

    Workaround 1.

    **************

     

    As on the first line of the error message it is referencing to " SPListType="1100" Error="Mismatched transaction."

     

    1.     In the “Issue” list item there could be some issue item’s where “Assigned To” and “Owner” columns values are BLANK

    Update these values for all the listed issue items.

    2.     Now Publish the project plan

    3.     In Manage queue hopefully you will not see Reporting (WSS Sync ) error

    4.     If you still getting Reporting (Wss Sync) error then check the error message in manage queue and match the scenario

     

      

     

     Scenario 2.

    **********

     

    <error id="24018" name="ReportingWssSyncListFailed" uid="159dcef9-ed73-4a45-866e-1852c098d1e6" SPListType="1101" Error="Failed to prepare the transfer of SP list 1101 for project '7053e472-db33-49f3-a148-476cab370f6a'. The field Cost was missing from the SP list and was ignored." />

          <error id="24018" name="ReportingWssSyncListFailed" uid="076c5db8-a912-4f7d-ba36-db60bb037815" SPListType="1101" Error="Failed to prepare the transfer of SP list 1101 for project '7053e472-db33-49f3-a148-476cab370f6a'. The field Cost was missing from the SP list and was ignored." />

     

    Workaround 2.

    *************

     

    As above error is referencing to SPListType="1101" and . “The field Cost was missing from the SP list and was ignored."

    In this example “Cost” field was missing in Risk. Same pattern we can create other fields

     

    1.     Open project workspace on which you are getting this error.

    2.     From Quick Launch select “Risk”

    3.     Settings>>List Settings>>Create column

    4.     Create “Cost” field (check the default values from any working workspaces)

    5.     Now Publish the project plan

    6.     In Manage queue hopefully you will not see Reporting (WSS Sync ) error

    7.     If you still getting Reporting (Wss Sync) error then check the error message in manage queue and match the scenario

     

     

    Scenario 3.

    ***********

     

    <error id="24018" name="ReportingWssSyncListFailed" uid="159dcef9-ed73-4a45-866e-1852c098d1e6" SPListType="1101" Error="Failed to prepare the transfer of SP list 1101 for project '7053e472-db33-49f3-a148-476cab370f6a'. The field Description  was missing from the SP list and was ignored." />

     

    Workaround 3.

    ************

     

    In some examples we have also seen that under “Risk” Description field is there but still we get above error.

    In this scenario we need to delete this description field and recreate.

     

     

     

    ***If we don’t have any useful information on workspace and if you are ready to delete the workspace in that case recreation of workspace will resolve all above scenario’s

     

     

    *****************COMPLETE ERROR MESSAGE *******************************

     

    Error summary/areas:
    Reporting Wss list sync failed
    ReportingWssSyncListFailed

    ReportingWssSyncListFailed
    ReportingWssSyncListFailed
    Reporting transfer WSS links failed.
    ReportingWssTransferLinksFailed
    ReportingWssTransferLinksFailed
    ReportingWssTransferLinksFailed
    Reporting message processor failed
    ReportingWSSSyncMessageFailed

    ReportingWSSSyncMessageFailed
    Reporting ProjectWorkspaceInternalHRef field sync failed
    ReportingWssSyncHRefFailed
    ReportingWssSyncHRefFailed

    ReportingWssSyncHRefFailed
    Queue
    GeneralQueueJobFailed
    Error details:
    <?xml version="1.0" encoding="utf-16"?>
    <errinfo>
    <general>
    <class name="Reporting Wss list sync failed">
    <error id="24018" name="ReportingWssSyncListFailed" uid="98df7838-4760-49ed-864c-a27773850d18" SPListType="1100" Error="Mismatched transaction." />
    <error id="24018" name="ReportingWssSyncListFailed" uid="64ee928c-6ca1-47ee-be13-d033c76bedba" SPListType="1101" Error="Mismatched transaction." />
    <error id="24018" name="ReportingWssSyncListFailed" uid="3cc8deea-acba-4bc1-bc3c-214643ed47aa" SPListType="1104" Error="Mismatched transaction." />
    <error id="24018" name="ReportingWssSyncListFailed" uid="a15bcba9-59c7-41d8-a634-d24e8b317ee0" SPListType="1100" Error="Mismatched transaction." />
    <error id="24018" name="ReportingWssSyncListFailed" uid="9ef51835-0e70-4cf3-85d9-809805044814" SPListType="1101" Error="Mismatched transaction." />
    </class>
    <class name="Reporting transfer WSS links failed.">
    <error id="24019" name="ReportingWssTransferLinksFailed" uid="6b41c89e-5ab7-4e7f-a37c-064ffad25ebe" Error="Mismatched transaction." />
    <error id="24019" name="ReportingWssTransferLinksFailed" uid="024a683d-d743-4caa-9808-742d01c360b3" Error="Mismatched transaction." />
    <error id="24019" name="ReportingWssTransferLinksFailed" uid="6b624adf-cd8a-4963-8e45-7dbe3a2540b2" Error="Mismatched transaction." />
    </class>
    <class name="Reporting message processor failed">
    <error id="24016" name="ReportingWSSSyncMessageFailed" uid="44419642-fc21-47fa-bff8-ed83da43cbcc" QueueMessageBody="ProjectUID='91a74b99-5487-482e-adc7-a16c5e7878f9'. ForceFullSync='False'" Error="RDS failed while trying to sync one or more SP lists. The RDS queue message will be retried." />
    <error id="24016" name="ReportingWSSSyncMessageFailed" uid="58064d39-da8b-40ae-88e5-d00812f35265" QueueMessageBody="ProjectUID='91a74b99-5487-482e-adc7-a16c5e7878f9'. ForceFullSync='False'" Error="RDS failed while trying to sync one or more SP lists. The RDS queue message will be retried." />
    <error id="24016" name="ReportingWSSSyncMessageFailed" uid="8b183448-1b2e-49aa-a513-bb04502453d6" QueueMessageBody="ProjectUID='91a74b99-5487-482e-adc7-a16c5e7878f9'. ForceFullSync='False'" Error="RDS failed while trying to sync one or more SP lists. The RDS queue message will be retried." />
    <error id="24016" name="ReportingWSSSyncMessageFailed" uid="f9cabf75-98af-426f-9e6a-8d407f432ce4" QueueMessageBody="ProjectUID='91a74b99-5487-482e-adc7-a16c5e7878f9'. ForceFullSync='False'" Error="RDS failed while trying to sync one or more SP lists. The RDS queue message will be retried." />

    </class>
    <class name="Reporting ProjectWorkspaceInternalHRef field sync failed">
    <error id="24021" name="ReportingWssSyncHRefFailed" uid="03c01005-484a-407d-ac75-70663314fd95" Error="Mismatched transaction." />
    <error id="24021" name="ReportingWssSyncHRefFailed" uid="24f30780-5be8-4418-96b2-2a6c1baba4b1" Error="Mismatched transaction." />
    <error id="24021" name="ReportingWssSyncHRefFailed" uid="0a47f802-04b9-4072-ad0e-37ac7f84a9c4" Error="Mismatched transaction." />
    </class>
    <class name="Queue">
    <error id="26000" name="GeneralQueueJobFailed" uid="6d57df72-4042-406f-951d-072340df0803" JobUID="7a41ff5c-ecba-416a-9bc5-a5df6f6d7bbb" ComputerName="INVG2158" GroupType="ReportingWSSSync" MessageType="WSSSyncMessageEx" MessageId="1" Stage="" />
    </class>
    </general>
    </errinfo>

     

     

     

Page 1 of 1 (16 items)