Description of the PerformancePoint Server 2007 hotfix package: December 22, 2008

This article describes the Microsoft Office PerformancePoint Server 2007 issues that are fixed in the hotfix package that is dated December 22, 2008.

• The issues that the hotfix package fixes.
• The prerequisites for installing the hotfix package.
• Whether you must restart the computer after you install the hotfix package.
• Whether the hotfix package is replaced by any other hotfix package.
• Whether you must make any registry changes.
• The files that the hotfix package contains.

PerformancePoint Server 2007 hotfixes are created for the release version of PerformancePoint Server 2007. All PerformancePoint Server 2007 hotfix packages and PerformancePoint Server 2007 service packs are cumulative.

A hotfix package is available for PerformancePoint Server 2007. The build of this hotfix package is 3.0.4300.00. The release version of PerformancePoint Server 2007 must be installed before you apply this hotfix. The build of the release version of PerformancePoint Server 2007 is 3.0.3520.0.

Issues that the hotfix package fixes since PerformancePoint Server 2007 Service Pack 2

This hotfix package fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:

If the version of PerformancePoint Server 2007 is 3.0.3999.1 or a later version, the application databases are not upgraded when you install PerformancePoint Server 2007 SP2

You applied a PerformancePoint Server 2007 hotfix that has a version number of 3.0.3999.1 or a later version number. When you try to upgrade a Planning server to PerformancePoint Server 2007 SP2, the upgrade process may complete successfully. However, the upgrade of the Application Databases may fail.

This problem occurs because a PerformancePoint Server 2007 Planning component has a setting that limits the version number up to 3.0.3999.00.

This problem is also documented in Microsoft Knowledge Base (KB) article 960815. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
When you work on a workflow object in Planning Business Modeler, Planning Business Modeler may consume lots of memory or generate an out-of-memory error

When you access a workflow object in Planning Business Modeler, you may receive an out-of-memory error.

This problem occurs because the following data that is related to the workflow object is unnecessarily uploaded to the planning database when you create or update a workflow object:

• The change list for the form assignment
• Formulas in the form
• Formulas in the form assignment

As the number of users and submissions increase, the change list becomes very large and consumes lots of memory. This memory consumption can be reduced by eliminating unnecessary data processing.

After you schedule a job to run on a recurring basis in Planning Business Modeler, the job accumulates delays in its schedule

If you schedule a job to run on a recurring basis, the job accumulates delays in its schedule. For example, you schedule a job to run on an hourly basis starting at 9:00. The job starts to run at 9:00 for the first time. However, the job starts to run at 10:01 for the second time, at 11:02 for the third time, and so on.

This problem occurs because of the time that the Planning server starts to process the job.

After you install this hotfix, the scheduled jobs that run on a recurring basis have the following behavior:

• If you specify a start date and time for a job, any recurrence starts exactly at the date and time of the recurrence setting. For example, you schedule a job to run monthly. The start date and time is 12/1/2008 at 10:00 A.M. Any recurrence starts on the first day of the month at 10:00 A.M after 12/1/2008.
• If you specify the Start job manually option for a job, you have to manually start the job for the first time. Then, any recurrence starts exactly on the date and time of the recurrence setting. For example, you schedule a job to run monthly, and you manually start the job on 12/1/2008 at 10:00 A.M. Then, any recurrence starts on the first day of the month at 10:00 A.M after 12/1/2008.

Important notes about this hotfix package

• We recommend that you back up all PerformancePoint Server 2007 databases before you apply this hotfix package.
• You can roll back PerformancePoint Server 2007 to an earlier version. To do this, follow these steps:
  1. In the Add or Remove Programs item in Control Panel, click to select the Show updates check box.
  2. Click the hotfix that you want to remove, and then click Remove.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problems that are described in this article. Apply this hotfix only to systems that are experiencing the problems described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Hotfix 961041 includes PerformancePoint Server 2007 Service Pack 2

For more information about the PerformancePoint Server 2007 issues that are fixed in PerformancePoint Server 2007 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

Prerequisites

The following list contains prerequisites for the hotfix:

• The release version of PerformancePoint Server 2007 must be installed before you apply this hotfix.
  
  Note You must apply this hotfix on all client computers and servers that have the affected component of PerformancePoint Server 2007 installed.
• To apply this hotfix, you must run the PerformancePoint Planning installation files that are appropriate for your situation:
  • The Planning Server Pplsrv.msp installation file
    This installation must be completed on the Planning server only.
  • The Planning Excel Client Pplxcli.msp installation file
    This installation must be completed on all client computers that are running the PerformancePoint Add-in for Excel.
  • The Planning Business Modeler Pbmcli.msp installation file
    This installation must be completed on all client computers that are running the PerformancePoint Planning Business Modeler.
• To apply this hotfix, you must run the PerformancePoint Monitoring installation files that are appropriate for your situation:
  • The Monitoring Server Pscsrv.msp installation file
    This installation must be completed on the Monitoring server only.

How to obtain the build information for PerformancePoint Planning Server

The build of PerformancePoint Planning Server is the same as that of Planning Business Modeler and of the PerformancePoint Add-in for Excel. To obtain the build of PerformancePoint Planning Server, use one of the following methods.

Method 1: Obtain the build information for Planning Business Modeler

1. In Planning Business Modeler, click About Planning Business Modeler on the Help menu.
2. In the About Planning Business Modeler dialog box, notice the version number of Planning Business Modeler.

Method 2: Obtain the build information for the PerformancePoint Add-in for Excel

1. In Microsoft Office Excel 2007, click the PerformancePoint tab.
2. On the PerformancePoint tab, click About in the Help group.
3. In the About PerformancePoint Add-in for Excel dialog box, notice the version number of the PerformancePoint Add-in for Excel.

How to obtain the build information for PerformancePoint Monitoring Server

The build of PerformancePoint Monitoring Server is the same as that of PerformancePoint Dashboard Designer. To obtain the build of PerformancePoint Monitoring Server, follow these steps:

1. In PerformancePoint Dashboard Designer, click the Microsoft Office Button, and then click Options.
2. In the Options dialog box, click the Resources tab.
3. On the Resources tab, notice the number after File Version.

Restart information

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix replaces all previously released versions of PerformancePoint Server 2007.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issue that listed in this article.

The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

PerformancePoint Server 2007, 32-bit versions

Planning serverPerformancePoint Add-in for ExcelPerformancePoint Planning Business ModelerPerformancePoint Monitoring Server

PerformancePoint Server 2007, 64-bit versions

Planning ServerPerformancePoint Add-in for ExcelPerformancePoint Planning Business ModelerPerformancePoint Monitoring ServerFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: