Cascade Skyline - with Microsoft Logo and Project Support header - author Brian Smith

April, 2008

  • Brian Smith's Microsoft Project Support Blog

    More Role Guides for Project Server 2007 Now Available!

    • 1 Comments

    You may have already picked this up from some or all of the other Project blogs - but worth repeating as I know you have all been waiting for these!

    They are now available (similar to EPM 2003) here: Learn about available roles for Project Web Access

    Depending on your role in your organization and what security permissions are assigned to you, you will have access to different features of Microsoft Office Project Web Access. The following role guides present broad overviews of Office Project Web Access functionality from the perspective of the different roles you might have.

    Role Guide/Description

    • Administrator role guide
      Use this guide if you are an administrator of Office Project Web Access. You can also use it as a guide to help evaluate Office Project Web Access for your organization.
    • Project manager role guide
      Use this guide if you are responsible for day-to-day project management tasks such as creating, maintaining, and updating schedules, and coordinating with other project managers, resource managers, and team members.
    • Executive role guide
      Use this guide if you are responsible for a portfolio of projects, such as all the projects for an entire department.
    • Resource manager role guide
      Use this guide if you are responsible for managing resources and their skills and capabilities.
    • Team member role guide
      Use this guide if you are responsible for any of the day-to-day activities in one or more projects.
    Technorati Tags:
  • Brian Smith's Microsoft Project Support Blog

    What were you doing in 1984? Hopefully not updating tasks in your current projects!

    • 2 Comments

    If this blog had a sub-title it would be "Task updates never get to Project Professional - even when they (eventually) say 100% Success".  And the error message you might find in the ULS logs would be:

    Microsoft.Office.Project.Scheduling.SchedulingException: The engine's event horizon was extended beyond the maximum length of 36500 days. This may be caused by invalid task or assignment data. You can also change the value of the InitialProjectDays scheduling parameter.

    This error led us to review the project timescale, and at first glance the Project Information was showing reasonable start and finish dates - from late 2007 to mid 2008.  But when looking at the plan the project summary task went back, and back, and back...  There was a milestone task 100% complete for 1/4/1984 driving the start date of the project summary.  Not sure at this stage how it got in that state - but this makes the scheduling engine work very hard processing status updates (you may see the queue service using LOTS of RAM) and eventually it gives the above error (in my case after 30-40 minutes) but the job appears to have completed OK.  However no updates appear in the plan.

    The current workaround is just to correct the date, save and publish and then re-submit the time.

    Technorati Tags:
Page 2 of 2 (7 items) 12