Microsoft® Office Business Scorecard Manager 2005 Compatibility Release Readme File

February 2007

© 2007 Microsoft Corporation.  All rights reserved.


Contents

1   How to Use This Document

2.  Overview of the Compatibility Release

3   Installing Business Scorecard Manager With SQL Server 2005

4   Business Scorecard Manager 2005 Known Issues

 

1   How to Use This Document

Back to Top


Welcome to the Readme file for Microsoft® Office Business Scorecard Manager 2005 Compatibility Release. This file contains important information that was not available when the documentation for the product was written. Workarounds are provided for known issues.

For additional information, see the Business Scorecard Manager 2005 Web site.

2   Overview of the Compatibility Release

Back to Top


Microsoft® Office Business Scorecard Manager Server 2005 Compatibility Release supports the ability to deploy Scorecards to Microsoft® Office SharePoint® Services 2007 (MOSS 2007) or Windows® SharePoint® Services (WSS) Version 3.0. 

Supported Platforms

Microsoft® Office Business Scorecard Manager Server 2005 Compatibility Release supports the Windows 32-bit platform.

 

3   Installing Business Scorecard Manager 2005 by Using Microsoft SQL Server 2005

Back to Top


The following are the prerequisites for installing Business Scorecard Manager with Microsoft SQL Server 2005.

Business Scorecard Manager Server Prerequisites

You must install the following prerequisite software in this order before installing the Business Scorecard Manager Server Web services:

1.       Microsoft Windows Server™ 2003 with Service Pack (SP) 1

2.       Microsoft .NET Framework 1.1, 2.0 or 3.0 with ASP.NET 1.1 enabled

3.       Microsoft Internet Information Services (IIS) 6.0

4.       Microsoft SQL ServerTM 2005

Note: To install Business Scorecard Manager Server on a computer on which SQL Server 2005 Analysis Services is already installed, you must run SQL Server 2000 Analysis Services PivotTable® Service Lite SP 4 (Ptslite.exe). This is installed when you install SQL Server 2000 Analysis Services SP 4. For more information, see Analysis Services Programming Redistributing Components.

5.       SQLXML 3.0 SP 3 (This is required if you use SQL Server Alerts.) Download SQLXML 3.0 SP 3.

6.       MSXML 4.0 SP 2. Download this from the Microsoft Download Center.

7.       ADOMD.NET 8.0. Download this from the Microsoft Download Center.

Note: If you upgrade to SQL Server 2005 after you have installed the Business Scorecard Manager Server Web service, you must set your default Web site to use ASP.NET 1.1. Otherwise SQL Server 2005 might change the version to ASP.NET 2.0. To set your default Web site to use ASP.NET 1.1, enter the following command at the command prompt:

%SystemRoot%\Microsoft.NET\Framework\v1.1.4322 aspnet_regiis.exe -s metabase-path

where metabase-path is the path to your Web site, for example W3SVC/1/ROOT.

Business Scorecard Manager Web Parts Prerequisites

The following components are prerequisites for Business Scorecard Manager Web Parts, listed in the order in which they should be installed:

1.       Microsoft Windows Server 2003 with SP 1

2.       Microsoft .NET Framework 1.1, 2.0 or 3.0 with ASP.NET 1.1 enabled

3.       Internet Information Services 6.0

4.       Microsoft SharePoint® Portal Server 2003, Microsoft Office SharePoint Services 2007, or Microsoft Windows SharePoint Services 2.0 or 3.0

SQL Server Reporting Services Prerequisites

The following components are prerequisites for SQL Server Reporting Services:

·         Microsoft Windows Server 2003 with SP 1

·         Microsoft .NET Framework 1.1, 2.0 or 3.0  with ASP.NET 1.1 enabled

·         Microsoft Internet Information Services (IIS) 6.0.

·         SQL Server 2005 Reporting Services (For more information, see Installing Reporting Services.)

Note: If you install SQL Server Reporting Services and have already installed either Windows SharePoint Services or SharePoint Portal Server on the same computer, there is a known issue with their not functioning properly together. See Troubleshooting a Side-by-Side Installation of Reporting Services and Windows SharePoint Services.

Business Scorecard Manager Server Database Prerequisites

Install SQL Server 2005 to set up your Business Scorecard Manager Server database.

4   Business Scorecard Manager 2005 Known Issues

Back to Top


The following are the known issues with Business Scorecard Manager 2005.

4.1 Scorecards and Report Views must be added manually to the Web site when running Microsoft Office SharePoint Services 2007 (MOSS 2007) or Windows SharePoint Services 3.0

Description: Users must deploy Scorecards and Reports to Microsoft Office SharePoint Services 2007 (MOSS 2007) or Windows SharePoint Services 3.0 (WSS 3.0) manually.  If the user attempts to deploy the scorecard from within Scorecard Builder, an error similar to the following occurs:

An error occurred during the processing of /Pages/*.aspx.

Workaround: To deploy to SharePoint, open the required Web site and add the scorecards and/or report views to Web Parts manually.  Refer to the technical white paper Business_Scorecard_Builder_Publishing_To_Moss_2007_WP.doc for detailed steps.

4.2  Using localhost as the server name yields blank pop-ups when running Microsoft Office SharePoint Services 2007 (MOSS 2007) or Windows SharePoint Services 3.0 locally

Description: If you are running Microsoft Office SharePoint Services 2007 (MOSS 2007) or Windows SharePoint Services 3.0 in a single machine environment, and you are using “localhost” as the server name when you deploy scorecards, blank pop-ups will appear on the Web site.

Workaround: Change your server connection to reference the machine name instead of “localhost.”

4.3  SQL Server 2005 Reporting Services application pool must have Reader or higher permissions to deploy Scorecards to Reporting Services.

Description: If you attempt to deploy a Scorecard to SQL Server 2005 Reporting Services, and the Reporting Services application pool does not have at least Reader permissions, the following error will occur:

An error has occurred during report processing. (rsProcessingAborted) Get Online Help.   Query execution failed for data set 'DataSet1_0'. (rsErrorExecutingCommand) Get Online Help.  The data set obtained from the Server is invalid.

Workaround: At a minimum, grant Reader privileges to the Reporting Services application pool identity.

4.4  Business Scorecard Manager application pool must use .NET Framework Version 1.1.

Description: By default, Business Scorecard Manager Setup uses the SharePoint default application pool, which uses .NET Framework 2.0 in MOSS 2007 or WSS V3. If the application pool that is running the BSM web site also runs a .NET 2.0 site, there will be process conflict and neither site will work.  This is by design.

Workaround: The application pool under which Business Scorecard Manager is running must not run any .NET Framework 2.0 site.

4.5   Installation of a database on a remote computer fails if you do not have permissions on the remote computer.

Description: When you install a database on a remote computer, you must have permissions on that remote computer.

Workaround: You must use a domain account or configure the system manually to use the remote computer account to install the database.

4.6  You cannot preview a scorecard report in Report Designer when you use SQL Server 2005.

Description: If you open the version of Microsoft Visual Studio that is installed with SQL Server 2005, then create a Report Server project and add a Business Scorecard Manager scorecard report to it, an error message will display when you attempt to preview the scorecard report

Workaround: Copy the DPE file (Microsoft.PerformanceManagement.Scorecards.DPE.dll) into the following folder to resolve the problem: C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies.

Or:  Deploy the project to the Report Server by using Report Designer (or by using Scorecard Builder), and view it there. The error appears only when you attempt to preview the report in Report Designer.

4.7  You cannot install alert functionality when you have c SQL Server 2005 Notification Services installed.

Description: Business Scorecard Manager alert functionality is incompatible with Microsoft SQL Server 2005 Notification Services.

Workaround: Install SQL Server 2000 Notification Services.

4.8  When SQL Server Reporting Services and Windows SharePoint Services are installed using the default settings on the same computer, they do not function properly.

Description: If you install SQL Server Reporting Services and either Windows SharePoint Services or SharePoint Portal Server on the same computer, they do not function properly.

Workaround: A known issue prevents SQL Server Reporting Services and either Windows SharePoint Services or SharePoint Portal Server from functioning properly on the same computer. For more information, see Troubleshooting a Side-by-Side Installation of Reporting Services and Windows SharePoint Services for assistance in working around this problem.

4.9  A corrupt MSDTC log file causes an error when you install Business Scorecard Manager Server.

Description: If you have a corrupt MSDTC log file when you install Business Scorecard Builder Server, the following error occurs: "The installer has encountered an unexpected error installing this package. This may indicate a problem with this package." The error code is 25619.

Workaround: Reset the MSDTC log file by running the following commands at the command prompt:

MSDTC -resetlog

Net Start MSDTC

4.10  A scorecard view that takes longer than 90 seconds to render triggers a "Server Error in '/' Application" error message.

Description: If you use the IIS default connection timeout settings (90 seconds) and a complicated scorecard takes more than 90 seconds to render, the system displays the "Server Error in '/' Application" error message, and does not render the scorecard.

Workaround: Change the default connection timeout settings in IIS to a number that is higher than 90 seconds (for example, 5 minutes).

4.11  An error message displays if you install the database feature when IIS is not installed.

Description: If you do not have IIS installed when you attempt to install Business Scorecard Manager and you attempt to install only the database feature, the installation fails and you receive the following error message:

Cannot connect to Internet Information Server. (-2147221164)

Workaround: Click Ignore in the error message to complete Setup successfully.

4.12  The alert service (NS$ScorecardAlertInstance) is set to Manual Startup by default.

Description: The alert service (NS$ScorecardAlertInstance) is set to Manual Startup by default. It does not start automatically when the server starts.

Workaround: To configure the alert service to start automatically when the server starts up, you must change the startup type of this service to Automatic by using the Services Administration Tool. For more information see Configuring an NS$instance_name Service.

4.13  You cannot connect to the server to retrieve data in some instances when you use the sample scorecard that is included in Business Scorecard Manager.

Description: The sample scorecards that are included in Business Scorecard Manager use the default setting localhost for the database connection. When you choose a KPI, click Report Views, then click a report view, click Edit and then click Configuration, an error sign displays in the bottom left corner of the graph. When you click this error sign, you see the following error message:

Failed to get data. If available, errors returned from the provider are listed below. * Cannot connect to the server 'localhost'. The server is either not started or too busy.

Workaround: Run the sample scorecards on the computer on which Business Scorecard Manager Server is installed because the localhost database is on this server computer. Or, you can replace every instance of localhost with the computer name of the server that you are using.

4.14  When you configure scorecard views, the same dimension can be used for any of the following: column member, row member, and page filter.

Description: Each cell in a SharePoint Portal Server 2003 or Windows SharePoint Services page represents a particular slice of a Microsoft SQL Server Analysis Services cube. When you configure a scorecard view, the same dimension can be used in multiple cells as a column member, a row member, and a page filter. Specifying a column member, row member, and page filter are all methods of filtering data. The result of using the same dimension in numerous scorecard cells is data overlap.

Workaround: When you build scorecard views, do not overlap dimensions in filter sets.

4.15  A blank tree view appears in the Select Display Folder dialog box when you try to view display folders for a deep tree view hierarchy.

Description: When you create a new scorecard in the Create Scorecard Wizard and you enter a folder path that is 100 levels or more deep in the (Optional) Default Display Folder Location text box, and then click Select Display Folder, the Select Display Folder dialog box is empty.

Workaround: Scroll all the way to the right to see the highlighted folder.

4.16  Deploying an empty scorecard to a SQL Server report causes a validation error.

Description: When you try to deploy an empty scorecard to a SQL Server Reporting Services report, a validation error message appears in the dialog box where you specified the scorecard view name, and the Next button is also disabled.

Workaround: Do not deploy empty scorecards to SQL Server Reporting Services report.

4.17  Unexpected results occur when you click Back in the Ready to Install dialog box in the Business Scorecard Server Setup wizard during a custom installation.

Description: If you install Business Scorecard Manager Server by using the Custom option in the server installation wizard, and you do not select a database, you will reach a page where you are asked to attach a database. If you click Back in the Ready to Install dialog box to return to the Attach Database screen, the wizard returns you to the Web Service dialog box rather than going back to the Attach Database page.

Workaround: In the Web Service dialog box, click Next, which takes you to the Attach Database page of the wizard.

4.18  The scorecard collapses when you set the default expansion depth for the scorecard to 20 or higher.

Description: In Business Scorecard Builder, select a scorecard, open the Scorecard View editor, select Cell Options in the navigation pane of the editor, and then set the Default Expansion Depth to 20. When you view the scorecard in the Scorecard View Web Part on your SharePoint site, the scorecard is collapsed and no data displays.

Workaround: Do not set the default expansion depth any higher than the actual number of levels for the scorecard.

4.19  Web sites that are created with IIS and then upgraded to Windows SharePoint Services must be configured to work with Business Scorecard Manager 2005.

Description: If you create a Web site with Internet Information Services (IIS), and then upgrade it to a Windows SharePoint Services site, you receive the following error message:

A Web Part or Web Form Control on this Web Part Page cannot be displayed or imported because it is not registered on this site as safe.

Workaround: Take the following steps:

1.       On the computer that is running Business Scorecard Manager Server, create a new Web site in IIS in a different port, and upgrade the site to a Windows SharePoint Services site.

2.       Follow the procedure in the Microsoft Office Business Scorecard Manager Web Part Help titled, "Add an Office Scorecard View Web Part to a Web page." The following error appears:

A Web Part or Web Form Control on this Web Part Page cannot be displayed or imported because it is not registered on this site as safe.

3.       From the existing Web.config file for the Web site, copy the following SafeControl line and paste it into the Web.config file of the new site:

SafeControl Assembly="Microsoft.PerformanceManagement.Scorecards.WebParts, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Namespace="Microsoft.PerformanceManagement.Scorecards.WebParts" TypeName="*" Safe="True"/

The following error occurs:

One of the properties of the Web Part has an incorrect format. Windows SharePoint Services cannot deserialize the Web Part. Check the format of the properties and try again.

And an event in the application log states:

Missing the Connection String in the config file. Please add Bpm.ConnectionString to the web.config.

4.       Copy the appSettings portion of the Web.config file for the existing site into the Web.config file for the new site.

4.20  The user account provided during alert installation cannot send alerts because it does not have the correct permissions.

Description: During Business Scorecard Manager installation the installer verifies that the user account provided for alerts is a valid user account; however, the installer does not verify that this user account has permissions to send alerts.

Workaround: Ensure that the user account used for alerts is a member of the Users group on the server where alerts are installed, and ensure that the account has the proper permissions to send e-mail through the SMTP server. Also, ensure that this user account has the Log on as a service right, and does not have the Deny log on as a service right.

4.21  You cannot uninstall or modify the Business Scorecard Manager Server database during Setup.

Description: You install Business Scorecard Manager Server without selecting the Database check box in the Setup window during a custom installation and then run server Setup again. When you complete the installation process and check the Web.config file, you see that the Business Scorecard Manager server is still attached to the same database.

Workaround: To uninstall the server, use the SQL Server administration tools. To reattach a current Web server instance, update the Web.config file to change the InitialCatalog values, configuring the following settings: Catalog=[databasename] and Source=[servername].

4.22  Installation fails when you attempt to modify the setup after you complete the recommended installation.

Description: If you run setup and install Business Scorecard Manager Server by using the recommended installation, then run Setup again by using the Modify option, click Business Scorecard Manager Server and select Entire content will be stored on local hard drive, you see validation errors that prompt you to change the port and server names. When you attempt to complete the installation, the following (or a similar) error message displays:

Failed to connect to SQL database (-21474672359 ScorecardServer1)

Workaround: When running Setup by using the Modify option, install features individually. For example, to add Reporting Services Export, click the feature and select Entire feature will be installed on local hard drive. Do the same to install Web Part and Web Services. You might be prompted to change the port during installation. If this occurs provide a valid port number and continue with the Setup. The port will not change after the installation is completed.

4.23  You cannot uninstall Business Scorecard Manager Server if you manually uninstall your Web site by using IIS Manager.

Description: If you uninstall your Web site by using IIS manager, and you attempt to uninstall Business Scorecard Manager server, the uninstallation fails and you receive the following error message:

Failed to find Web Site Metabase path: 'Business Scorecard Manager Web Service

Workaround: Create a new Web site in IIS manager and call it “Business Scorecard Manager Web Service,” and then run the uninstallation again.

4.24  Alerts do not function properly when you use a remote database.

Description: If you do not have SQL Server Notification Services installed properly on the correct computers, alerts do not function properly when you use a remote database.

Workaround: To install alerts in the remote database environment, you must install the database component of SQL Server Notification Services on the remote database. You must then install the engine component and client components of SQL Server Notification Services on the computer that is running Business Scorecard Manager Server.

4.25   If you set the To Date setting for the Date Range property to Date Not Specified, an unhandled exception error message occurs.

Description: If you select Date Range from the Type drop down list in the Custom Properties dialog box for a scorecard, select the Date not specified check box next to To date, and then click OK, you receive an error message that states that there was an unhandled exception.

Workaround:  Always specify dates when using a date range as a custom property.