Known issues and best practices in PerformancePoint Server 2007

This article describes the known installation issues, deployment issues, and best practices in Microsoft Office PerformancePoint Server 2007.

Known issues in PerformancePoint Server 2007

The following issues are known to occur in PerformancePoint Server 2007 in specific circumstances. Each issue that is listed here is individual and has no relation to the other issues. All information is presented "as is" and without warranty or guarantee.

Issue 1: Error message when you connect to PerformancePoint Monitoring Server from PerformancePoint Dashboard Designer: "Unable to connect to Server"

Symptoms

You install the Microsoft .NET Framework 3.5 before you install PerformancePoint Monitoring Server. Then, when you connect to PerformancePoint Monitoring Server from PerformancePoint Dashboard Designer, you receive the following error message:

Resolution

To resolve this problem, reinstall Microsoft ASP.NET AJAX 1.0 after you run the Monitoring Server Configuration Manager for the first time. By doing this, you can restore Windows SharePoint Services site functionality or Microsoft Office SharePoint Server site functionality.

Issue 2: A runtime error occurs when you connect to Office SharePoint Server from PerformancePoint Dashboard Viewer for SharePoint Services

Symptoms

You install Office SharePoint Server on a computer. Then, you install PerformancePoint Dashboard Viewer for SharePoint Services on the same computer. When you connect to Office SharePoint Server from PerformancePoint Dashboard Viewer for SharePoint Services, you encounter a runtime error. When this problem occurs, an event that describes an ASP.NET configuration warning is logged in the Application log. The description of the event is as follows:

Resolution

To resolve this problem, reinstall ASP.NET AJAX 1.0 after you run the Monitoring Server Configuration Manager for the first time to restore SharePoint site functionality.

Issue 3: You cannot install Microsoft SQL Server 2005 Management Objects Collection (XMO 9.0) on a computer that is running the SQL Server Reporting Services Add-in for Microsoft SharePoint Technologies

Symptoms

You install the SQL Server Reporting Services Add-in for Microsoft SharePoint Technologies, or you run SQL Server Reporting Services in SharePoint Integrated mode. In this situation, you cannot install SQL Server 2005 Management Objects Collection (XMO 9.0) on the same computer. This causes the following problems:

• You cannot install PerformancePoint Planning Server, which requires XMO 9.0.
• You cannot import KPIs from SQL Server because the import operation requires XMO 9.0 to connect to SQL Server.

Cause

This problem occurs because XMO 9.0 cannot be installed on a computer that is running the SQL Server Reporting Services add-in.

Note When you run SQL Server Reporting Services in SharePoint Integrated mode, the SQL Server Reporting Services add-in is installed.

Resolution

To resolve this issue, use one of the following methods.

Method 1

Install XMO 9.0 and the SQL Server Reporting Services add-in on separate computers. These products are not intended to be installed on the same computer as a production system. A single computer installation is intended only to provide a proof-of-concept environment for testing.

Method 2

Run SQL Server Reporting Services in native mode instead of in SharePoint Integrated mode. When SQL Server Reporting Services runs in native mode, the SQL Server Reporting Services Add-in is removed from the computer.

Method 3

If you want to import KPIs from SQL Server, you can manually re-create the KPIs in Dashboard Designer instead of importing the KPIs.

How to obtain and install optional components of PerformancePoint Server 2007

Microsoft Office Web Components (OWC) for pivot charts

These components work only on 32-bit Windows operating systems. For more information, visit the following Microsoft Web site:

Visio for strategy maps

You must install Microsoft Office Visio on all computers where you want to create strategy maps. For more information, visit the following Microsoft Web sites:

• http://technet.microsoft.com/en-us/library/bb905538.aspx (http://technet.microsoft.com/en-us/library/bb905538.aspx)
• http://office.microsoft.com/en-us/performancepoint/HA102446511033.aspx (http://office.microsoft.com/en-us/performancepoint/HA102446511033.aspx)

Report Viewer for SQL Server Reporting Services

To download and install Report Viewer for SQL Server Reporting Services on client computers, use the following download links. For Report Viewer for SQL Server 2005 and for versions of PerformancePoint Server 2007 that are earlier than PerformancePoint Server 2007 Service Pack 2, visit the following Microsoft Web site: For Report Viewer for SQL Server 2008 and for PerformancePoint Server 2007 Service Pack 2, visit the following Microsoft Web site: Note The Report Designer component is also available from the SQL Server 2005 installation CD. The Report Designer component is included with Business Intelligence Development Studio. For more information, visit the following Microsoft TechNet Web site:

Issue 4 Prerequisite issue with PerformancePoint Planning.

When you try to install PPS Planning and you do not have SQL Server Native Client SP2 installed the installation fails.

Resolution

To resolve this issue follow the steps in the following Microsoft Web Site: http://technet.microsoft.com/en-us/library/dd335965.aspx (http://technet.microsoft.com/en-us/library/dd335965.aspx)

Best practices

Before you install the PerformancePoint Dashboard Viewer component for SharePoint Services, we recommend that you manually back up the Web.config file that is associated with the SharePoint Web application. By default, the location of the Web.config file for a Web application on port 80 is as follows: