Troubleshoot PerformancePoint Monitoring Server

Updated: 2008-10-23

The following list contains information that you can use to resolve problems with Monitoring Server and its associated components. The procedures are not listed in sequence; you can perform them as required.

• Strategy maps do not correctly export or display   Strategy maps in a deployed dashboard might not correctly export to Microsoft Office Excel or Microsoft Office PowerPoint. Strategy maps that are configured to render as images might not display correctly in the dashboard. By default, the strategy map report type is not enabled to support the following:

  • Export to PowerPoint

  • Export to Excel

  • Render as Image

  This is by design. To enable the exporting functionality, ensure that Microsoft Office Visio is installed on the server that runs Windows SharePoint Services.

• SQL Server prompts for account configuration   If Windows SharePoint Services is installed on a separate computer from the Microsoft SQL Server computer that hosts the Monitoring Server databases and Windows SharePoint Services is running under a computer account, you might be prompted during setup if the computer being used can be added to the bpmdeveloper role in the PerformancePoint Monitoring databases. This is necessary to view dashboards that have been exported to SharePoint sites.

• Dashboard functionality cannot be uninstalled   If Windows SharePoint Services is uninstalled, the computer account is not removed from the bpmdeveloper role. You must manually remove the computer account from the bpmdeveloper role after you uninstall Monitoring Server to remove the dashboard viewing functionality in Windows SharePoint Services.

• Subsite cannot be configured   If a SharePoint subsite is added, Monitoring Server does not copy the master page to the new subsite. Therefore, when adding a subsite, you must manually copy the master page of the site to re-use it.

• ODBC connectivity fails   When creating an Open Database Connectivity (ODBC) data source, whether the Monitoring Server computer is 32-bit or 64-bit determines which ODBC connections are available. For example, because Office Excel and Microsoft Office Access have 32-bit drivers, an ODBC connection to Office Excel or Office Access cannot be created if Monitoring Server is installed on a 64-bit server.

  To create an ODBC connection from a 64-bit server, the connecting application must have a 64-bit ODBC driver. If an application (such as Office Excel or Office Access) does not have a 64-bit driver, consider the following workarounds:

  • Use the Office Excel 2007 workbook or Excel Services data source to connect to Excel data.

  • Create a custom data connection to the data source. For information about creating a custom data connection, see the PerformancePoint Monitoring SDK.

  • Install Monitoring Server on a 32-bit computer.

• Access Denied error occurs   An Access Denied error occurs while running the Monitoring Server Configuration Manager. During configuration, a custom SharePoint master page, PerformancePointDefault.master, is installed. You must add the configuration manager as a site collection administrator on the SharePoint site collection to successfully complete this installation. That is, the user must be logged on with an account that is a site collection administrator on the SharePoint site collection before installing Monitoring Server.

• Unauthorized Access error occurs   An Unauthorized Access error may occur if the Users group permissions are set incorrectly in the %System Drive%:\Windows\Temp directory on SharePoint Server when a user tries to export a Dashboard component to Office Excel or Office PowerPoint from SharePoint Server. By default, the Users group has Read and Execute permissions for the %System Drive%:\Windows\Temp directory. Organizations commonly remove or restrict the User group rights for the Temp directory. The Users group must have Read and Execute permissions for the Temp directory on SharePoint Server.

• Damaged directory occurs   If the Monitoring Server installation directory or its contents are damaged or deleted, you must reinstall Monitoring Server to restore full functionality.

• Dashboard Designer cannot be downloaded and fails with an error   This failure is caused because the Microsoft .NET Framework version 2.0 is not installed on the computer where the installation is being attempted. To resolve this issue, perform the following steps:

  1. Install the Microsoft .NET Framework version 2.0.

  2. Install Dashboard Designer.

• NetLocalGroupAddMembers fails   The failure is by design. Installing a different localized build for Dashboard Designer when one has already been installed causes the first build to be retained. The new localized build is not used in Dashboard Designer. The first installation will always be the one used regardless of the localization of all future installed builds.

  Installing any localized build for Dashboard Designer after a different localized build causes ClickOnce deployment technology to use the first locale. To correct this condition, you must clear the ClickOnce cache before Dashboard Designer is started.

  To clear the ClickOnce cache, perform the following procedure.

Clear the ClickOnce cache