A server is running Microsoft Office PerformancePoint Monitoring Server 2007. From a client computer, you create a Microsoft SQL Server Table data source or an Analysis Services 2005 data source in PerformancePoint Dashboard Designer. When you select a database or when you click Test Connection, you receive the following error message:

The PerformancePoint Server could not connect to the specified data source. Verify that either the current user or application pool user has Read permissions to the data source, depending on your security configuration. Also verify that all required connection information is provided and correct.

Additionally, the following event is logged in the Application log:

Date: Date
Time: Time
Type: Failure Aud
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: ComputerName
Source: MSSQLSERVER
Category: (4)
Event ID: 18456
Description: Login Failed for user ‘NT Authority\Anonymous Logon’. [CLIENT: IPAddress]

CAUSE

This behavior occurs for one of the following reasons.

Cause 1

The account under which the PPSMonitoringWebService application pool is running does not have read permissions for the database that you are trying to access.

Note If this is the cause, this behavior occurs regardless of whether you are using the scenario that described in the “Symptoms” section.

Cause 2

PerformancePoint Monitoring Server 2007 is configured for Kerberos delegation. Additionally, the instance of SQL Server to which PerformancePoint Monitoring Server 2007 tries to establish a connection resides on a different server. If the PPSMonitoring Web site is configured to use only the NTLM protocol, the PPSMonitoring Web site cannot delegate the user credentials from the client computer to the server that is running the instance of SQL Server.

WORKAROUND

Workaround 1

To work around this problem, follow these steps:

Workaround 2

To work around this behavior, configure the PPSMonitoring Web site to use the NTLM protocol and the Kerberos protocol. To do this, visit the following Microsoft Web site, and then follow the steps in the “Configure PerformancePoint Monitoring Server Web Services” section:

http://technet.microsoft.com/en-us/library/bb838775.aspx (http://technet.microsoft.com/en-us/library/bb838775.aspx)

STATUS

This behavior is by design.

MORE INFORMATION

The scenario that is described in the “Symptoms” section is a double-hop scenario. In a double-hop scenario, the client computer passes the user credentials to a second server that is running PerformancePoint Monitoring Server 2007. Then, the second server passes the user credentials to the server that is running the instance of SQL Server.

We recommend that you configure the identity of the PPSMonitoringWebService application pool to use a domain user account.

APPLIES TO

——————————————–

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

This article describes the following items about the hotfix package:

INTRODUCTION

Issues that the hotfix package fixes

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

PerformancePoint monitoring issue

MORE INFORMATION

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Office PerformancePoint 2007 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

To apply this hotfix, you must have the release version of Microsoft Office PerformancePoint Server 2007 installed. The version number must be 3.0.3520.00 or a later version number. To view the version number in PerformancePoint Server 2007, click About on the Help menu.

Note The hotfix must be installed on all client and server computers that have the affected component of PeformancePoint Server 2007 installed.

Restart information

You do not have to restart the computer after you apply this hotfix package. However, you must restart Internet Information Services (IIS) to apply the changes to the PerformancePoint Monitoring export functionality. To do this, follow these steps:

Hotfix replacement information

This hotfix replaces all previously released hotfixes.

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 issues that are listed in this article.

This hotfix will update the components to version 3.0.3705.00. To view the version number in PerformancePoint Server 2007, click About on the Help menu.

APPLIES TO

——————————————–

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

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

This article describes the following items about the hotfix package:

INTRODUCTION

List of issues fixed

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

PerformancePoint Server 2007 planning issues

PerformancePoint Server 2007 monitoring issues

MORE INFORMATION

Hotfix information

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

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451 (http://go.microsoft.com/?linkid=6294451)

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

Prerequisites

The following list contains prerequisites for the hotfix package:

Restart information

You must restart the computer after you apply this hotfix package.

To restart the server that is running IIS, you must run the IISReset command. To do this, click Start, click Run, type IISRESET, and then click OK. This command resolves the PerformancePoint Monitoring and PerformancePoint Planning functions.

Hotfix replacement information

This hotfix is not replaced by any later hotfix.

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 issues that are listed in this article.

PerformancePoint Server 2007, 32-bit versions

The global version of this hotfix uses a Microsoft Windows Installer package to install the hotfix. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date 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.

Download information

Microsoft Windows Installer .msp file information

After the hotfix is installed, the global version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the following table:

Pplsrv.msp

Pplxcli.msp

Pbmcli.msp

Pscsrv.msp

PerformancePoint Server 2007, 64-bit versions

The global version of this hotfix uses a Microsoft Windows Installer package to install the hotfix. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date 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.

Download information

Microsoft Windows Installer .msp file information

After the hotfix is installed, the global version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the following table:

Pplsrv.msp

Pplxcli.msp

Pbmcli.msp

Pscsrv.msp

For more information about how to install this hotfix, see the Readme.txt file that is included in the hotfix package.

APPLIES TO

——————————————–

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

You try to open a dashboard in Dashboard Designer in Microsoft Office PerformancePoint Server 2007. If you specified pixels for the size of the reports that the dashboard contains, you may receive an error message. However, the error message that you receive varies. For example, you may receive the following error message:

Unhandled Error Exception
A webpart zone may be resized by adjusting the pixel width and height in the Zone settings.

This problem occurs if you specify pixels for the size of the reports that the dashboard contains.

WORKAROUND

To work around this problem, follow these steps:

<Height Measurement="50" Units="Percent"/>
<Width Measurement="50" Units="Percent"/>

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.

MORE INFORMATION

If you specify Stacked for the zone orientation settings for a dashboard, we recommend that you specify the following settings for the reports in the dashboard:

APPLIES TO

——————————————–

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks