Issue

Explanation/Workaround

The import of an ANSI CSV file from the Administration Console Users page will fail if the file contains non-ASCII characters.

To import users who have non-ASCII characters in their names, e-mail addresses, or user IDs, use Unicode encoding to save the file.

Issue

Explanation/Workaround

IMPORTANT NOTE for Planning Server installations.

A cumulative update has been released for SQL Server 2005 SP2. This update is called "Cumulative update package 3 for SQL Server 2005 SP2" and is also known as build 3186. All Analysis Services computers in your PerformancePoint Server environment must have this update applied prior to your Planning Server installation.

You can request the update package through Microsoft article 939537, Cumulative update package 3 for SQL Server 2005 Service Pack 2 (http://go.microsoft.com/fwlink/?LinkID=93385).

IMPORTANT NOTE for all PerformancePoint Add-in for Excel installations.

A cumulative update has been released for SQL Server 2005 SP2 (this build of the cumulative update package is also known as build 3186). Updated versions of the SQL redistributables that are prerequisites for PerformancePoint Add-in for Excel are available. This new version must be installed before you install PerformancePoint Add-in for Excel. The following download links for the updated redistributables are available:

1. Analysis Services 9.0 OLE DB Provider (SQLServer2005_ASOLEDB9.msi)
   
   For 32-bit client machines:
   
   ASOLEDB9.msi (http://go.microsoft.com/fwlink/?LinkId=93298)
   
   For 64-bit client machines:
   
   ASOLEDB9_x64.msi
   
   (http://go.microsoft.com/fwlink/?LinkId=93299)
   
   
2. ADOMD.NET Provider (SQLServer2005_ADOMD.msi)
   
   For 32-bit client machines:
   
   ADOMD.msi
   
   http://go.microsoft.com/fwlink/?LinkId=93296
   
   For 64-bit client machines:ADOMD_x64.msi
   
   http://go.microsoft.com/fwlink/?LinkId=93297
   
   

During data submission, if the business validations for ControlAndOwnership measure group fail, the following error is returned to the client: "The SharesOutstanding measure group submission failed."

Business validations for the ControlAndOwnership measure group may fail for various reasons. Refer to the "Business Data Validation" topic in the PerformancePoint Server 2007 Operations Guide (http://go.microsoft.com/fwlink/?LinkId=119747) for assistance.

Your SQL Server installation and SQL Client Redistributables may not match the language of your PerformancePoint Server installation.

If the languages do not match, you must install the English language versions for the SQL Server and SQL Client Redistributables.

The following text in the Planning Business Modeler Help topic: "About Dimension Member Properties" is incorrect:

"If a dimension member has a null or blank value for a foreign key property, also called a Member of Dimension property type, the member will not appear in the associated SQL Server Analysis Service (SSAS) database. To guarantee that a dimension member with a foreign key property appears in SSAS, make sure that the property is not null."

Updated text:

In Planning Business Modeler any dimension member that has a null or blank value for a foreign key property (Member of Dimension property type) will not generate an Analysis Services cube. All foreign key properties must be non-null to for Analysis Services cubes to build.

Resolution:  Open Planning Business Modeler and update all null foreign key values (Member of Dimension property type).

Changes that are made directly in SQL Server Analysis Services can disrupt synchronization with Planning Server user security settings.

If modifications are made in Analysis Services to Planning Server data, Analysis Services data may be out of sync with user security information that is stored in Planning Server databases. Make sure that all changes are made by using Planning Server. Also make sure that only authorized people have access to those Analysis Services databases.

Only members of the Modeler role can publish form templates to a Microsoft Office SharePoint Server 2007 storage location.

To allow all users to publish form templates to SharePoint storage locations, you must manually give the PerformancePoint Server Service Identity account the necessary permissions on the SharePoint Web site that hosts the storage location.

Imported strings cannot exceed 256 characters.

When you use the Planning Command Utility to import a dimension that contains a member property of type "string," the string size cannot be more than 256 characters or you will get an error.

Deleted application database information may not be recorded in log entries.

If there is an error when Planning Server tries to process an asynchronous work item, and the error is caused by a deleted application database, neither the Windows Event Viewer nor the Planning Server log file entry will contain information about the database.

bsp_CreateHierarchyFromDimension cannot be used with @HierarchyTableName parameter containing Unicode characters.

An incorrect temporary hierarchy table may be created when using the stored procedure bsp_CreateHierarchyFromDimension if the parameter @HierarchyTableName contains Unicode characters.

Stored procedure bsp_DI_ValidateLabelTable validates only one table at a time.

When validating a label-based measure group or annotation table, the stored procedure bsp_DI_ValidateLabelTable, only validates either Measure Group table or Annotation table, but not both, based on the AnnotationOnly parameter.

For example: If AnnotationOnly is set to True, the MG table is not validated but the Annotation table is. If AnnotationOnly is set to FALSE, the MG table is validated but the Annotation table is not.

You must specify a staging database before you can initialize an application.

If you plan to create an application by manually running the creation scripts, then you must specify a staging database before you run the scripts. Otherwise, you will receive an "Application not found" message when you try to initialize the application in the Planning Administration Console.

SQL Clustering failover could cause Planning Process Service to stop working.

If this happens, the user needs to restart Planning Process Service.

Text in rule expression editable fields sometimes converts incorrectly in East Asian Input Method Editors (IMEs).

When you enter text into a Rule Expression editable field while the mouse is positioned over that field, the text will not convert correctly in an East Asian IME.

To avoid this problem, make sure that the cursor is not positioned over the text field when you enter text into that field.

You cannot mix different collation databases in the Planning Server system.

Do not mix different collation databases in the Planning Server system. If you use a Staging Database that was built from a different SQL Server server, make sure that that the computer running SQL Server has the same collation as the one for the Planning Server system.

Exception error appears in the Planning Server Configuration Manager log file

During the upgrade process, Planning Configuration Manager attempts to restart the Planning Process Service. If the service is already stopped, an exception error is written to the PlanningVerbose<Date>.log file".

Planning Configuration Manager then successfully starts the service.

No action is required by the user.

You cannot upgrade pre-release versions of PerformancePoint Server to PerformancePoint Server 2007 SP1.

PerformancePoint Server 2007 SP 1 only upgrades the released version of PerformancePoint Server 2007.

Workaround:

Use one of the following solutions, depending on your situation:

• If you have a pre-released version of PerformancePoint Server, you must uninstall that version and then install the released version of PerformancePoint Server 2007.
  
  
• If you previously upgraded a pre-release version of PerformancePoint Server to the released version PerformancePoint Server 2007, you will need to perform some additional pre-installation configuration steps before you can run the SP1 upgrade. For additional details and instructions please contact your system administrator or Microsoft Customer Service.
  
  

Issue

Explanation/Workaround

Form templates that are published in PerformancePoint Add-in for Excel are represented as forms in Planning Business Modeler.

Do not delete forms from a model site.

You receive a foreign key error related to Intercompany when you try to save a model site.

This may occur if you change the type of a member of the Entity dimension if the Intercompany dimension is ever used as a Member of Dimension property.

The value for a Text (string) member property is an empty string instead of the default value NULL.

Although the default value for a Text (string) member property is NULL, the actual value may be an empty string. This behavior will not affect Planning Server features or functionality unless you have implemented a custom solution that accesses the SQL Server tables directly.

The TimeDataView dimension cannot be opened for editing.

You can view the members of the TimeDataView dimension by following these steps:

1. Check out the model.
   
   
2. In the Business Rules page of the model workspace, select a rule (or create a new rule) and click Toggle Scope Editor.
   
   
3. Under Define scopes, click the ellipsis button for TimeData View.
   
   or
   
   Right-click in the Rule expression box, point to Insert Member(s) of Dimension, then click TimeDataView.
   
   
4. The Select Members dialog box appears and displays the dimension members.
   
   

You might not be able to delete a member set if it was used in a model and the Security and Roles editor was used to set permissions on it.

To work around this issue, delete the business role that is causing the permissions conflict, and then re-create the business role.

If someone uses Planning Administration Console to Force Cancel Checkout an application, all models checked out in that application will have the checkout canceled. No warning is displayed to users who are working on such models. Any attempts to save the previously checked out models will fail without an error or warning message.

Administrators should inform users before they use the Force Cancel Checkout functionality of Planning Administration Console.

Push or pull rules can cause errors when you try to save a model with a model name that does not match the model label.

If you want to use push or pull rules you must change the model name to be the same as the label.

When you change the default value of a member property of a shared dimension, the new value is not saved when you check in or save the dimension.

When you save the shared dimension use Save Model Site instead of Save Dimension.

You cannot save the model site and you see the following error:

"The attempt to save the model site failed."

This occurs if you create a Member of Dimension member property that references a member from a new dimension that has not been saved. To avoid this error, save the new dimension before you create the member property. (On the Dimensions workspace, select the new dimension. On the Workspace Actions pane, click Save Dimension.)

You cannot save a new dimension that has the same label as a previously deleted dimension when you use the Save Dimension command.

To save a new dimension that has the same label as a previously deleted dimension, use the Save Model Site command in the File menu.

A foreign key error results when you try to save a model site.

You cannot delete a dimension that is used as a member of a dimension property in another dimension.

When you multi-select entries in a tree grid, drag and drop does not work.

Refresh or restart Planning Business Modeler to enable the shortcut menu and drag and drop.

An unhandled exception occurs after you use the scope member selector for an imported rule where the memberset scope that is specified is inconsistent with the current model.

When you import a business rule into a model that has a different memberset defined in the scope, you must manually modify the rule scope so that it is consistent with the new model.

If you delete a model site, PerformancePoint Server does not clear member labels from the underlying dimension tables.

Delete model site, or subsite-specific, dimension members before you delete a model site or subsite.

A change to a data connection made in Planning Administration Console is not visible in Planning Business Modeler. For example, if a data connection is deactivated, users may not know of the change until after they refresh the related model site.

Refresh the model site to see the changes in Planning Business Modeler.

If you have a model that uses one member set for a dimension and you change the member set, the security for the model will not be updated.

To ensure that permission changes are pushed to the cube, make a minor update to each role that is enabled for the model (for example, update the description), and then save the model.

If a Planning Server application includes Definition rules, a user who queries the cube can get a run-time error if the user does not have permission to access all the members that are referenced in the rule.

This behavior is by design. To avoid this issue, make sure that users have appropriate access permissions.

When changes to dimension mappings for an association are checked in from another instance of Planning Business Modeler, dimension mappings are not updated correctly on checkout.

Refresh the model site and open the association again.

You cannot add the None member to a member set in the Member Sets Maintenance page.

The Add as Sibling and Add as Child shortcut menu and toolbar commands might be disabled under the Source Member Set pane when the None member is selected. In this case, you can add the None member as a sibling or child by dragging the None member from the Source Member Set pane to the Destination Member Set pane.

Saving the model site or dimension, or checking in a dimension, fails after you create a member property that has the User dimension for a property of the Member of Dimension data type.

The User dimension cannot be used for Member of Dimension member properties. Instead, you can create a new dimension, load it with users, and then use this new dimension as a Member of Dimension member property.

If the job parameters of an intercompany reconciliation job specify a rule set instead of an individual rule, the assigned user will not be able to create a corresponding intercompany reconciliation report.

Assign only individual intercompany rules to business users, instead of intercompany rule sets.

Incremental migration does not correctly delete rules in the target system. As a result, if you have two systems that are being kept in sync (for example test and production) and you delete a rule in the source system, then do an incremental migration to a target system, the rule will still exist in the target system.

This can cause migration to fail if you delete a rule then add a new rule to the same rule set. The failure occurs because the target system will attempt to have two rules in the same position of the rule set.

Delete all designated rules from the target system before migrating.

Some dimensions appear in English instead of the appropriate language.

Dimensions that are required for a model type might not be translated from English to the appropriate language.

Text is truncated or missing in a text box.

This may occur because of font size and screen resolution settings. To avoid this, go to the Display Properties dialog box and set your theme to Windows Classic or Windows Standard.

During validation or deployment, certain cross model allocation rules incorrectly return the error "Member set is not defined correctly for cross model mapping. The number of members in source and target member sets in cross model mapping must match."

For more information, refer to Knowledge Base Article 942640.

Consider using model associations, instead of cross model allocation rules.

An attempt to deploy a model or model site fails and an error message is generated.

A model or model site may fail to deploy in the following situations:

• The model or model site was recently migrated and the default value for an attribute that links to the Time dimension was set to NULL. During migration, this NULL value was automatically converted to 0, which is an invalid value.
  
  
• A linked dimension was created in Planning Business Modeler where at least one attribute in the source dimension did not contain a value to link to in the destination dimension.
  
  

To fix the error, enter a valid value for the attribute and redeploy the model or model site.

If you save a new association for the first time when network service is unavailable, the association appears to save and check in without error. However, if you attempt to check out the association after network service is restored, the association cannot be checked out and an error message appears saying that the association is invalid.

If you attempt to save an association and you get an error message saying that the server is unavailable, do not assume that your changes are saved even if the status indicates that the association is checked in. When network service is restored, refresh the model site, re-create the association, and then save it.

The following text in the Planning Business Modeler Help topic: "About Dimension Member Properties" is incorrect:

"If you decide to enter a description, it must consist of no more than 512 characters, must start with a letter, and can contain symbols, punctuation marks, and alphanumeric characters."

Updated text:

"If you decide to enter a description, it must consist of no more than 512 characters or 256 double-byte characters, must start with a letter, and can contain symbols, punctuation marks, alphanumeric characters, and double-byte letters."

When you set user permissions to None on any member set, an error occurs when the business role is saved.

Although the None setting is valid, it does not serve a business purpose. You may ignore the error. All settings will be saved.

Time dimension member labels use the regional settings date format for the operating system, not the settings for the Planning Business Modeler client language.

Make sure to set the regional setting information (date time format) for the operating system to the correct format before you create the calendar in Planning Business Modeler.

You will not be able to create a member set that is based on properties for the User Dimension

If you select the Create a member set based on properties option to create a member set on the User dimension, the following error message will be displayed: "An error occurred while creating a hierarchy for the dimension. (Error code: PerformancePoint_225000062) Member set creation failed for dimension User."

Workaround: None. The creation of a member set on a User dimension is not supported when the member set is based on properties. Creation of a Member set through properties should work for all other dimensions.

Issue

Explanation/Workaround

On the Specify Companies and Mappings page, if you specify the same model site and model for two different companies, and the model sites/models have the same name but the capitalization is different for each (for example, Abc and ABC), the data load operation for each company finishes successfully. However, only the transactional data of the last company that was imported is persisted in the model.

When you select companies to include in the data import, you must use a unique model site and model combination for each company that you select.

The Data Import Wizard checks for case sensitivity in model site and model names, but Planning Server does not. This means Planning Server considers two different model sites/models that have the same name but different capitalization as the same model site/model, even though they are not.

Workaround:  Remove one of the companies from the list of companies that you plan to include in the data import.

When the Data Import Wizard attempts to load data into a PerformancePoint Planning application by using the Financial Data Mart (FDM) data provider with a starting date that is less than the FDM calendar starting date and an end date that is greater than the FDM calendar ending date, the Data Import Wizard load fails during the transaction.

Example:

FDM Calendar: begins 1/1/2000 and ends 12/31/2005.

Data Import Wizard Enter dates: 1/1/1998 to 12/31/20013.

Expected Results: Even though the calendar range dates are outside the FDM calendar, the dates should not cause the DIW to fail because the range encompasses the FDM calendar.

Use the correct start and end date in the Data Import Wizard.

Issue

Explanation/Workaround

If you use the validation option to delete and reload fact data, many of the rows in the measure group tables that you created by using rules will not load when you use data integration.

The data rows in the measure group tables reference system calculated members. During the data load process, these rows fail business validation, because data integration only allows valid data to be loaded into the model.

To load rows that reference calculated members, use the no validation option. You can do this by using Planning Command Utility with the /novalidation flag or by running a job in Planning Business Modeler.

The Alpine Ski House (ASH) Sample Application Guide does not discuss product functionality.

The Alpine Ski House (ASH) Sample Application Guide supports the ASH business case. For questions about product functionality, see Planning Business Modeler or PerformancePoint Add-in for Excel Help.

The calculation rules that are included in the ASH sample application may not be best practice solutions.

The calculation rules that are included in the ASH sample application were written to support the ASH business case. There may be more efficient or alternate ways to write these rules.

When an assignment is not listed in the PerformancePoint Add-in for Excel, the assignment must be manually instantiated from the Planning Business Modeler application.

To instantiate an assignment:

1. Connect to Planning Business Modeler and to the appropriate model site.
   
   
2. From the Site Browser, click Process Management.
   
   
3. From the View drop-down list box, select Assignments.
   
   
4. Click to highlight an assignment definition.
   
   
5. From the Process Scheduling Tasks pane, click Available Actions. The Available Actions for… dialog box appears.
   
   
6. In the Select action drop-down list box, select instantiate, and then click OK.
   
   

Some Rule IDs no longer map to the correct rules in the ASH sample application.

This is a known issue and it creates the potential for data loss and data duplication by certain jobs that run based on Rule IDs.

Installation of the ASH sample application fails on non-English PerformancePoint Server builds.

Installation of the ASH sample application will not succeed unless its language matches the language of the PerformancePoint Server build.

When the Alpine Ski House sample application is installed on a virtual machine, users who are specified in the DeploymentConfig.xml file must be valid users on the virtual machine.

Make sure that users who are specified in the DeploymentConfig.xml file are valid users on the virtual machine.

When member sets are created in the Alpine Ski House sample application, the None member must be added to every member set.

Add the None member to all member sets that are created in the sample application.

Model sites in the Alpine Ski House sample application must be deployed in a specific order.

Deploy the model sites in the following order:

1. Manufacturing
   
   
2. ResortMgmt
   
   
3. ASH_Corporate
   
   
4. ResortMgmt
   
   

Note:  To correctly validate the cross-model allocation rules, you must redeploy ResortMgmt after you deploy ASH_Corporate, as indicated in the preceding list.

If you install the Alpine Ski House (ASH) sample application on a German operating system, you must use a period (.) as the decimal symbol.

Prior to installing ASH on a German operating system, you must use Regional Settings to change the decimal symbol to a period (.). If you do not do this, data values will not display correctly. After ASH model sites are deployed, you can change the decimal separator back to your original symbol.

The MinimalVerification Sample Application fails.

The MinimalVerification can only be installed by the very first member of the Global Administrator role that is added to Planning Server.

When you deploy the Alpine Ski House (ASH) application under a Japanese operating system, deployment of the ResortMgmt subsite fails.

To deploy ASH successfully under a Japanese operating system, you must use the short date format of the locale (yyyy/mm/dd). Otherwise, the deployment of ResortMgmt subsite will fail.

You installed the Alpine Ski House (ASH) sample data on a computer that is running an English language version of the operating system set to the regional language. Now, the sample data displays the month and day in English, which causes time and month errors to occur.

Install the Multilanguage User Interface (MUI) before you install PerformancePoint Server.

1. Install the English language version of Windows 2003.
   
   
2. Install the localized MUI.
   
   
3. Install the English language version of SQL Server 2005.
   
   
4. Install the language version of PerformancePoint Server that you prefer.
   
   
5. Install the language version of the ASH sample data that you prefer, and then deploy it.