Issues that are fixed in Microsoft Office Servers by the Microsoft Office Servers Infrastructure Update

Issues with Project Server 2007 that were found after this update

• Assume that you have published a project that has assignments. The assignment owner differs from the assignment resource, and the task has an enterprise task custom field that has been configured to roll down to assignment rows. In this case, if the assignment owner moves to the My Work link in the left navigation pane of Project Web Access and then tries to update the assignment, the assignment owner may receive the following error message:
  An unexpected error has occurred.
  Microsoft is aware of this issue and is developing a solution.
• If you save a project that has many task custom fields, it may take a long time to save the project. For example, it make take an hour to save a project has 20 custom fields. Microsoft is aware of this issue and is developing a solution.

Back to the top

Issues that the update fixes

• Workflows run on e-mail-enabled lists by running as the user who designed or deployed the workflow instead of as the user who modified or created the parent item.
  
  Note This issue applies to e-mail-enabled items only.
• Workflows that have versioned conditions do not work correctly after the workflows are deployed by a site template (.stp).
• Workflows that contain Delay activities are not returned consistently after the set amount of delay time passes.
• When users are authenticated anonymously, they cannot use a Business Data Catalog (BDC). This update enables the BDC to explicitly let anonymously authenticated users access the BDC.
• A BDC consumes a Line of Business (LOB) Web service, and the LOB Web service returns large data sets. When this occurs, the HTTP connection times out. This update lets you configure the time-out value by using the object model.

Back to the top

Improvements that the update provides

SharePoint Server 2007

• When you detach and then reattach a content database or when you restore a content database by using the STSADM -o command, a full crawl is not always required.
  
  Note Only post-update farms and content databases that are backed up or detached from an updated farm are affected by this improvement.
• Improvements to scalability and performance are included to support incremental search crawls.
• Improvements are made to the time that is required to update and to upgrade Microsoft Windows SharePoint Services sites.
  
  Note Only post-update farms are affected by this improvement.
• Improvements are made in stability when you upgrade a farm that has many host header-based named site collections.
• Support is included for Kerberos authentication to access Shared Services Provider (SSP) Web services in a server farm.
• Performance improvements are made to the MySiteCleanupJob function in a multi-SSP farm.
• Search crawl speed is improved.
• After you apply the update, Microsoft Office 2003 files or 2007 Microsoft Office files that are embedded in a 2007 Office document are searchable.
• Address the issue that occurs when you try to convert a business data list that is based on the BDC entity model to a DataTable form, and the conversion fails. This behavior occurs when the schema for data list contains fields that are type Nullable. After you apply the infrastructure update, type Nullable fields are converted to type DBNull. DataTable forms support fields of type DBNull.
• Increases the number of parameters that can be defined for use with the Backend API in the BDC model from 30 parameters to 255 parameters.
• Address the issue that occurs after you add a BDC column that is associated with an address book to a Shared Documents folder on a SharePoint server. When you either press CTRL+K or click the Check Names icon to try to resolve a partial name that you typed into the BDC column, you may receive the following error message: :
  Could not resolve specified value.

Project Server 2007

Custom fields stability improvements

• Improves support for copy-and-paste operations when you edit lookup table values in Project Web Access.
• Resolves issues that occur with graphical indicator calculations.
• Resolves issues that occur in custom field formula calculations.
• Resolves issues that occur when you try to download the ActiveX controls that you have to have for a custom field formula definition that uses Project Web Access.

• When you change a value by using the Edit Properties page, you cannot see the corresponding graphic indicator in Project Center.
• When Project Server 2007 evaluates field formulas, it uses an incorrect order of operations.
• When you save or publish a project plan from the Edit Project Properties page, project-level formula custom fields lose their values.
• When you try to validate formulas on the Edit Custom Fields page, you cannot download the Project Server 2007 ActiveX controls. Therefore, you cannot validate the formulas.
• You publish a project from the Edit Project Properties page. If the calculated custom fields reference cost fields, the calculated custom fields are recalculated incorrectly. The resulting cost value is incorrect by a factor of 100.
• An enterprise formula custom field contains a reference to another enterprise formula custom field. In this case, the field is not updated when the project is saved, is published, or is recalculated.

• The Paste button is now visible on all pages and functions as expected.
• On the Edit Lookup Table page, an Export item is added to the Excel & Print Grid feature.

Project Server performance improvement

• Several database indexing adjustments are made to improve performance of core client-and-server scenarios, such as "Save and Publish" scenarios.

Logging tracing improvements

• Resolves an issue in which log messages are duplicated and incorrectly tagged.
• Resolves an issue in which the volume of messages is too large. The update does this by lowering the trace severity for high-volume, notification-only messages, and by logging only critical failures on final queued-action retries.
• Improves the logging detail for errors that are detected during server-side formula calculations.

Resolutions for issues that occur during migration from Project 2003 to Project 2007

• You edit the duration on a fixed duration task that has a task calendar and some actual work, and then you save your changes. When you do this, the duration value is recalculated to a different value.
• A milestone task that has ASAP constraints in a "Schedule from Finish" project finishes as soon as possible instead of finishing on the scheduled finish date for the project.
• When you open a "Schedule from Finish" project that was created in Project 2003, the task duration of a fixed duration task may change. This issue occurs when the the following conditions are true:
  • The affected fixed duration task has multiple resource assignments.
  • One or more of the assignments is at 0% units.
  • One or more of the assignments starts at a later date than the task.
• You edit the duration value of a fixed duration task that has splits. ("Splits" means that work is occurring in more than one segment.) When you do this, the duration is recalculated to an incorrect value.
• You have both a work resource and a material resource on a fixed unit task. When you change the work value on the work resource, the task's duration increases. However, the material resource has a work value that is equal only to the original duration of the task.
• When you try to assign a material resource to a fixed duration task that has a non-standard calendar, the assignment fails. This issue occurs if the fixed duration task already has work resources and actual work.

Queue Management user interface improvements

• Changes the Queue Management default view to highlight potential issues.
• Adds new Queue Management views that display active jobs and blocked jobs.
• Adds a new filtering option that shows related jobs and that helps users troubleshoot error messages.
• When you save a project, Project Server displays a Synchronizing dialog box that shows the progress of the save operation. This dialog box helps prevent you from prematurely shutting down the system and potentially losing data.
• Resolves Queue Management UI scalability issues to let you use the available page space more effectively. This improvement reduces the need for paging and scrolling when you troubleshoot queue issues.
• Adds a view that displays the following jobs, regardless of selected history:
  • Jobs that are being queued
  • Jobs that are waiting to be processed
  • Jobs that have failed
  • Jobs that are blocking other jobs
  By default, the Cancel jobs being enqueued option is selected to show partly completed saves.

Improvements in Reporting Database performance and data integrity

• Adds new helper procedures that you can use to create and to manage custom indexes and views in the Reporting Database.

• You trigger a new administrative restoration procedure while a previous restoration procedure is still in progress. When you do this, the Reporting Database update fails, and any queued jobs are now blocked. Additionally, you may receive one or more of the following error messages:
  This type of project cannot pe transfered to reporting database.
  Note You receive this error message if the published database contains inactive projects or templates.
  System.Data.SqlClient.SqlError: Violation of PRIMARY KEY.

Timesheets and My Tasks stability and usability

• Resolves the most common usability issues that prohibit deployment for some customers.
• Reduces the need for double-entry by end-users.
• Adds some end-user functionality that existed in Project 2003. For example, the update adds the following functionality:
  • You can sort on any column.
  • The My Tasks page can be grouped.
  • You can determine the hierarchy of a task. This functionality can be useful if you have multiple tasks that have the same name.
  Note If you plan to track the status for material usage through Project Web Access, avoid assigning material resources to the same task as work resources.
• The following usability improvements have been added to the Timesheet and My Tasks views:
  • When you use the TAB key to enter a cell, you are in Overwrite mode instead of Edit mode. This means that you do not have to clear the contents of the cell to replace the cell contents. You can type directly into the cell.
    
    This improvment is available in any view that has a grid in it.
  • You can now differentiate between different tasks that have the same name. To do this, click the list next to the task's name, and then click Tasks Path. A window is displayed that shows you a list of the task's summary tasks.
  • When you are in Timesheet view, you can now reorder all fields, not only custom fields. Additionally, you can remove those fields that you do not want to see.
  • You can set manual field widths for any of the fields. This gives you better control of the page layout.
  • In the Timesheet and My Tasks views, grids now have both horizontal and vertical scroll bars to help with navigation.
    
    Previously, the Windows Internet Explorer page was resized. This condition meant that you would have to scroll the whole page to see fields that were off the screen.
  • In the Timesheet view, you can add the Remaining Work field. If the Time entry by timesheet only task setting is enabled, you can change the remaining work for project tasks that you are updating in the Timesheet view.
  • When you are working in the Timesheet or My Tasks view, you scroll to parts of the grid that are to the right side and that are down the page. When you do this, the column headings may be visible. This condition makes it difficult to know which task and column you have selected.
    
    To make it easier to know which task and column you have selected, a stationary row and column indicator now displays the task name and the heading (column).
  • You can now sort on any field in a Timesheet or My Work view.
  • In the My Work view, there is now a Submit All button. This new feature lets you select and then submit multiple tasks at the same time, regardless of what page they lie on.
  • Grouping functionality is added to the My Tasks view.
  • In Microsoft Office Servers Service Pack 1, a Web Part property named Hours per day was added to the My Tasks view. This property lets you enter daily actual work in a grid in the My Tasks view. This Web Part property is now exposed in the View Options area. It appears as Timephased View.

• When you enter time in the My Work page in the timephased grid, the time data may not stay in the period in which you entered it.
• You cancel a StatusingStatusSubmitting event and then submit a task. When you do this, an unexpected error may occur on the My Tasks page.
• You use the Weekdays/Date format for a Web Part, and a task has a finish date that occurred in the previous year. In this case, you may receive the following error message on the My Tasks page:
  An unexpected error has occurred.
• When you change the currency setting, the Timesheet Web Part may not load.
• The My Tasks page does not support sorting by custom fields.
• You cannot click the Progress field multiple times on the My Task page.
• The timephased grid in the My Tasks view incorrectly assumes that work is entered in hours. Now, the timephased grid examines the Web Part settings to determine the correct time interval.
• The timephased grid in the My Work page does not respect the hours-per-day definition for a project. The appearance of work values differs from what you expect.

Back to the top

Content Deployment issues that the update resolves

Issues that incremental software updates fix

• An incremental import procedure may fail if a feature that has a custom content type was reactivated on the destination site.
• Unpublished changes to published pages do not cause the pages to be unpublished later on the destination site.
• When permissions are reinherited on the source site, the changes are not propagated incrementally.
• You delete a permission level on the source site, and then you perform an incremental import procedure. When you do this, you receive the following error message:
  Permission level cannot be found.
• An incremental import procedure fails, and you receive the following error message:
  FatalError: You cannot perform this action on a checked out document.
• During an export procedure, you receive the following error message:
  Violation of PRIMARY KEY constraint
• In some cases, the document Title field is not deployed by an incremental deployment job.
• In some cases, if you make permissions changes on the source site or on the destination site, you receive the following error message:
  The specified name is already in use.
• You delete or rename an item, and then you create a new item that has the same name as the deleted or renamed item. When you do this, an incremental deployment job fails.
• When pages have independent permission settings, an incremental deployment job fails.
• You delete a file and a folder. In some cases, when you do this, an incremental deployment job fails.

Issues that are fixed in the Windows SharePoint Services 3.0 Infrastructure Update

• When you remove a user from a group, the change is not propagated to the destination site during an incremental deployment job.
• Some source Web settings that are related to the Search function are not propagated to the destination site.
• The content deployment process can time out incorrectly for large deployment jobs.
• Miscellaneous deadlocks occur in Microsoft SQL Server.
• Quick deployment jobs behave incorrectly when the Variations feature is used.
• A quick deployment job fails when pages are "quick-deployed" while the quick deployment job is running.
• The operation may fail when you run a one-time job manually.
• In some cases, a content deployment job becomes stuck in a "Preparing" state.
• In some cases, a deployment job reinstates items that were ghosted on the source site.
• Custom master page settings on the source site are not propagated to the destination site during deployment.

Back to the top

Update information

Prerequisites

Restart information

Update replacement information

Registry information

Back to the top

How to determine whether the infrastructure update is installed in Project Server 2007

USE <Project_Server_Draft_Database>
select count(*) from versions WHERE Version = '12.1.153.0'
USE <Project_Server_Published_Database>
select count(*) from versions WHERE Version = '12.1.162.0'
USE <Project_Server_Reporting_Database>
select count(*) from versions WHERE Version = '12.1.151.0'
USE <Project_Server_Archive_Database>
select count(*) from versions WHERE Version = '12.1.153.0' 

Back to the top