To migrate to the release version of Business Scorecard Manager 2005

1. Back up your scorecard metadata database. The default name is ScorecardServer.
2. In Control Panel, click Add or Remove Programs.
3. Remove the following:
   • Microsoft Office Business Scorecard Builder 2005
   • Microsoft Office Business Scorecard Manager 2005
4. Run the release version of Business Scorecard Manager 2005 to install the server components. You must select the Custom Setup installation option, and then clear the Database option. You will be prompted for the location of the existing metadata database.
5. Run the release version of Business Scorecard Builder 2005 to install the Business Scorecard Builder components.

To copy or move your Business Scorecard Manager metadata and retain element history and custom annotations

1. Detach your Business Scorecard metadata database from the instance of Microsoft SQL Server™ to which it is attached.
2. Copy or move the two database files (by default, ScorecardServer.mdf and ScorecardServer_log.LDF) to the new location. This new location might be another directory on the same computer or a directory on another computer.
3. Attach the Business Scorecard Manager metadata database to the appropriate instance of SQL Server in your production environment.
4. Modify the Web.config file for the Business Scorecard Manager Web service so that the <appSettings> section contains the connection information for the Business Scorecard Manager database, as shown in the following example:

   <add key="Bpm.ConnectionString"
    value="Integrated Security=SSPI;Initial Catalog=ScorecardServer; Data Source=myserver"/>

5. Repeat step 4 for all computers that are used to display scorecards in Microsoft Windows® SharePoint® Services or Microsoft Office SharePoint Portal Server.

To copy your Business Scorecard Manager metadata without retaining element history or custom annotations

1. In Business Scorecard Builder 2005, create a new workspace file.
2. In the right pane of the Workspace Browser, for each element type, click <scorecard element> from server and insert all of the elements of that type into your workspace file.
3. Save the workspace file, and then close Business Scorecard Builder.
4. Run the Business Scorecard Manager server installation to create a new (empty) metadata database.
5. In Business Scorecard Builder, open the workspace file that you created in step 1.
6. On the Workspace menu, click Properties.

   Verify that the URL shown in the Server name box is correct. The URL consists of the http protocol specifier, a server name, and a port number (for example, http://myserver:46786/). The URL must reference the instance of the Business Scorecard Manager Web service that you installed in step 4.

   Close the Workspace Properties dialog box.

7. On the tool bar, click Publish All.

You must install Microsoft OLE DB Provider for OLAP Services (MSOLAP) 8.0. This driver ships with SQL Server™ 2000. You must install this driver whether you are using SQL Server 2000 or SQL Server 2005.

To install MSOLAP 8.0

1. Download SQL Server 2000 Service Pack 4 for Analysis Services Components (SQL2000.AS-KB884525-SP4-x86-ENU.EXE) from the Microsoft Download Center.
2. Run the downloaded executable file to extract the service pack files.
3. Run <extract location>\msolap\install\PTS\ptslite.exe to install the MSOLAP 8.0 driver and the Microsoft PivotTable® service.

This error occurs when you have selected the optional Reporting Services Export component and SQL Server Reporting Services was not installed on the local computer as the default instance.

SQL Server can be installed by using the default (unnamed) instance of SQL Server Reporting Services, a named instance SQL Server Reporting Services, or both. When the installation program for Business Scorecard Manager examines the installation requirements for the Reporting Services Export component, it detects only the default instance of SQL Server Reporting Services. You can address this issue in any one of the following ways:

• Install the default instance of SQL Server Reporting Services.
• Use a different computer that has the default instance of SQL Server Reporting Services installed on it.
• Install Business Scorecard Manager Server without selecting the optional Reporting Services Export component.

Some of the prerequisite software might be missing. In particular, make sure that you have installed Windows XP Service Pack 2.

This error message is displayed for various reasons. Check all of the following:

• That the name of the database server is correct.
• That the name of the database is correct.
• That the application pool that is assigned to the Business Scorecard Manager Web service is properly configured.

  The account that the selected application pool uses must have permissions to access the data source. For SQL Server 2005 data sources, you can add the account to the built-in db_datareader database role. For Analysis Services data sources, you must create a read-only role and then add the account to that role.

   Note   In order to display the scorecard on a SharePoint site, the account that the Windows SharePoint Services application pool uses also must be given read-only access to the data source.

This error occurs whenever an attempt to connect to the Business Scorecard Manager Web service is unsuccessful. When you receive this error message, it means that you are using an incorrect URL to make the connection to the Business Scorecard Manager Web service, that the Web service is not running, or that you do not have access to the Web service.

To check the URL that you are using to make the connection

1. On the Workspace menu, click Properties.
2. Verify that the URL shown in the Server name box is correct. The URL consists of the http protocol specifier, a server name, and a port number (for example, http://myserver:46786/).

   If the server name does not match the name of the computer on which the Business Scorecard Manager Web service is installed or the port number does match the port on which the Web service is listening, make the corrections and then click Test Connection. If the test is successful, you are ready to try the original operation again.

   If you are still unable to connect to the Business Scorecard Manager Web service, the Web service might not be running.

To determine whether the Web service is running

Do one of the following:

• Perform these verification checks:
• Verify that the IIS (World Wide Web Publishing) service is running.
• Verify that the virtual server on which the Business Scorecard Manager Web service is installed is in the Running state, not in the Paused state or Stopped state.
• Verify that the account identity assigned to the application pool that the Business Scorecard Manager Web service uses is valid (correct password, account not expired, and so on). Make sure that the account has the minimum required permissions.
• Check the Windows event logs. If there were problems starting the Business Scorecard Manager Web service as a result of security configuration issues with the account, there will be error entries in the security and system logs.
• Use your Web browser to check whether the Business Scorecard Manager Web service is running. To do so, type http://myserver:46786/pmservice.asmx in the address bar of your browser. If the PmService supported operations page opens, the service is running.

This error indicates that the Business Scorecard Manager Web service is running, but that it was unable to perform the requested operation. To resolve this issue, check the account that is assigned to the application pool that the Business Scorecard Manager Web service uses. This account is usually the built-in Network Service account.

If you are using a regular user account (either local or on the domain), make sure that the account has the minimum required permissions.

• The account is a member of the local IIS Worker Process group (IIS_WPG).
• The account is a member of the local Users group.
• The account has the Logon As a Service right.
• The account has the Logon As a Batch Job right.
• The account has Modify access to the following directories:

  %WINDIR%\temp

  %WINDIR%\Microsoft.NET\Framework\<version>\Temporary ASP.NET Files

• The account has Read access to the directory where the Business Scorecard Manager Web service resides. In most cases, this directory is the following:

  C:\Program Files\Microsoft Office Business Scorecard Manager 2005\Server\WebService

• The account has access to the Business Scorecard Manager metadata database and is a member of the BpmViewer and BpmDeveloper database roles.
• The account has Read access to the back-end data sources.

For more information, see this article in the Microsoft Knowledge Base.

When you type the name of the computer in the Server name box, an attempt is made to establish a connection with SQL Server Analysis Services on that computer. If the connection is successfully established (you do not receive an error message), the list of available Analysis Services databases is populated.

If the database that you want to use is not displayed, make sure the account identity assigned to the application pool that the Business Scorecard Manager Web service uses has permissions to access the database. Use SQL Server Management Studio to verify that an Analysis Services role has been created for the database and that the application pool account has been added to the membership list.

The Business Scorecard Manager Web service is configured to use Windows integrated security. If you log on by using a local computer account, the Business Scorecard Manager Web service will not accept your credentials. You must do one of the following:

• Configure the Business Scorecard Manager Web service to accept anonymous requests.
• Log on by using a domain account.

 Important   There are security implications to consider when you configure the Business Scorecard Manager Web service to accept anonymous requests. It is recommended that you use the default integrated security model when running the Business Scorecard Manager Web service.

The Business Scorecard Manager Web service usually uses internally-assigned permission to determine the level of access (if any) a user has to objects such as KPIs and scorecards. These internal permissions are assigned in Business Scorecard Builder and are stored in the Business Scorecard Manager metadata database.

In this security model, a scorecard is accessible to a user only if the user has been granted access to the scorecard itself and all of the KPIs in that scorecard. When the scorecard is accessible to the user, the identity that has been assigned to the Business Scorecard Manager Web service application pool is used to access the back-end Analysis Services data. Depending on what permissions have been established for the back-end data sources, some KPI data might not be displayed.

You can alter the security model that is used. Instead of using the identity that has been assigned to the application pool for the Business Scorecard Manager Web service to determine which KPI data is displayed, you can use the identity of the user who is making the request to determine what data is displayed. To do so, you must configure the Business Scorecard Manager Web service to pass through user credentials to Analysis Services for evaluation.

To configure the Business Scorecard Manager Web service to pass through user credentials

1. Use Notepad or another text editor to open the Web.config file that is associated with the Business Scorecard Manager Web service. By default, the file is located in:

   C:\Program Files\Microsoft Office Business Scorecard Manager 2005\Server\WebService

2. In the <appSettings> section, change the value of the Bpm.ConnectionPerUser key from false to true.

   If the entry for the Bpm.ConnectionPerUser key does not exist, you must add it. When it is complete, the entry should look like the following:

   <add key="Bpm.ConnectionPerUser" value="true"/>

3. Save the Web.config file, and then close it.

Repeat this procedure for the Web.config file that is used by Windows SharePoint Services or SharePoint Portal Server.

 Important   If the Analysis Services database is not located on the same computer as Windows SharePoint Services, you should configure your Windows SharePoint Services virtual server to use Kerberos authentication. This avoids the "two-hop" issue. For information about how to configure a Windows SharePoint Services virtual server to use Kerberos authentication, see the related article in the Microsoft Knowledge Base.

You might want to use the first KPI to obtain the Objective image only. You can hide the KPI from view, and set the weight of the KPI to zero to prevent it from being used in a roll up calculation.

Run the scorecard validation process to receive detailed information about the problem.

To run the scorecard validation process

1. In Workspace Browser, right-click the scorecard.
2. Click Validate.

This error can occur when you are using Microsoft Office 2003 Web Components to access data that resides in an Analysis Services cube. It can indicate that the Microsoft OLE DB Provider for OLAP Services (MSOLAP) has not been properly registered on the computer. Either re-install MSOLAP or perform the manual registration process shown below. It might be necessary for you to perform the registration process on both server computers and workstation computers.

To register Microsoft OLE DB Provider for OLAP Services

1. Open a Command Prompt window.
2. At the command prompt, type the following command:

   regsvr32 "c:\program files\common files\system\Ole Db\msolap90.dll"

3. Press ENTER.
4. When the status message box opens, click OK.
5. At the command prompt, type the following command:

   regsvr32 "c:\program files\common files\system\Ole Db\msolap80.dll"

6. Press ENTER.
7. When the status message box opens, click OK.

This error occurs when the optional Business Scorecard Manager Reporting Services Export component either has not been installed or has not been properly registered with SQL Server Reporting Services.

To install the optional Business Scorecard Manager Reporting Services Export component

1. In Control Panel, click Add or Remove Programs, click Microsoft Office Business Scorecard Manager 2005, and then click Change.
2. In the Business Scorecard Manager 2005 Server Setup wizard, on the Modify or Remove Installation page, click Modify, and then click Next.
3. On the Custom Setup page, click Reporting Services Export, and then click Entire feature will be installed on local hard drive.
4. Click Next.
5. On the Ready to Install? page, click Install.
6. On the Business Scorecard Manager Server Setup Complete page, click Finish to close the wizard.

If the problem persists and you have installed both SQL Server 2000 Reporting Services and SQL Server 2005 Reporting Services, it might be necessary for you to manually configure SQL Server Reporting Services to use the Business Scorecard Manager Reporting Services Export component.

To manually configure Reporting Services to use the Reporting Services Export component

1. Copy the following file:

   Microsoft.PerformanceManagement.Scorecards.DPE.dll

   to the following location:

   C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin

    Note   The preceding location is only an example. Your location will be similar, but it might vary, depending on what version and instance of SQL Server Reporting Services you have installed.

2. Use Notepad or another text editor to open the rsreportserver.config file, found in the following location:

   C:\Program Files\Microsoft SQL Server\MSSQL.3\ReportingServices\ReportServer

    Note   The preceding location is only an example. Your location will be similar, but it might vary, depending on what version and instance of SQL Server Reporting Services you have installed.

3. In the <Data> section, add the following entry:

   <Extension Name="ScorecardDPE"
    Type="Microsoft.PerformanceManagement.Scorecards.DPE.BpmConnection,
          Microsoft.PerformanceManagement.Scorecards.DPE"
   />

    Important   The Type attribute shown in the preceding code spans two lines for readability purposes only. When you place this entry in the configuration file, the Type attribute must be on a single line.

4. Save the file, and then close it.
5. Use Notepad or another text editor to open the rssrvpolicy.config file, found in following location:

   C:\ProgramFiles\Microsoft SQL Server\MSSQL.3\ReportingServices\ReportServer

    Note   The preceding location is only an example. Your location will be similar, but it might vary, depending on what version and instance of SQL Server Reporting Services you have installed.

6. Locate the following <CodeGroup> section:

   <CodeGroup 
    class="FirstMatchCodeGroup" 
    version="1" 
    PermissionSetName="Execution"
    Description="This code group grants MyComputer code Execution permission."
   />

   In this section, add the following entry:

   <CodeGroup 
    class="UnionCodeGroup" 
    version="1" 
    PermissionSetName="FullTrust" 
    Name="ScorecardDPEGroup" 
    Description="This code group grants the Business Scorecard Manager DPE code full trust.">
     <IMembershipCondition 
      class="StrongNameMembershipCondition" 
      version="1" 
      PublicKeyBlob="KEY"
     />
   </CodeGroup>

    Important   Replace the PublicKeyBlob placeholder shown above with the actual public key of the Microsoft.PerformanceManagement.Scorecards.DPE.dll assembly. You can use the Microsoft .NET Framework Strong Name Utility (sn.exe) to discover the public key. The following command displays the public key and the public key token.

   sn.exe -Tp Microsoft.PerformanceManagement.Scorecards.DPE.dll

   Currently, the public key for the Microsoft.PerformanceManagement.Scorecards.DPE.dll assembly is:

   002400000480000094000000060200000024000052534131000400
   0001000100b5fc90e7027f67871e773a8fde8938c81dd402ba65b9
   201d60593e96c492651e889cc13f1415ebb53fac1131ae0bd333c5
   ee6021672d9718ea31a8aebd0da0072f25d87dba6fc90ffd598ed4
   da35e44c398c454307e8e33b8426143daec9f596836f97c8f74750
   e5975c64e2189f45def46b2a2b1247adc3652bf5c308055da9

7. Save the file, and then close it.

If you are using Microsoft Visual Studio® to design Reporting Services reports, it might be necessary for you to manually configure Visual Studio.

To manually configure Visual Studio

1. Copy the following file:

   Microsoft.PerformanceManagement.Scorecards.DPE.dll

   to the following location:

   C:\Program Files\Microsoft Visual Studio 8\Common 7\IDE\PrivateAssemblies

    Note   The preceding location is only an example. Your location will be similar, but it might vary, depending on what version of Visual Studio you have installed.

2. Use Notepad or another text editor to open the RSReportDesigner.config file, which you can find in the following location:

   C:\Program Files\Microsoft Visual Studio 8\Common 7\IDE\PrivateAssemblies

    Note   The preceding location is only an example. Your location will be similar, but it might vary, depending on what version of Visual Studio you have installed.

3. In the <Data> section, add the following entry:

   <Extension Name="ScorecardDPE"
    Type="Microsoft.PerformanceManagement.Scorecards.DPE.BpmConnection,
          Microsoft.PerformanceManagement.Scorecards.DPE"
   />

    Important   The Type attribute shown in the preceding code spans two lines for readability purposes only. When you actually place this entry in the configuration file, the Type attribute must be on a single line.

4. In the <Designer> section, add the following entry:

   <Extension Name="ScorecardDPE"
    Type="Microsoft.PerformanceManagement.Scorecards.DPE.BpmConnection,
          Microsoft.PerformanceManagement.Scorecards.DPE"
   />

    Important   The Type attribute shown in the preceding code spans two lines for readability purposes only. When you actually place this entry in the configuration file, the Type attribute must be on a single line.

5. Save the file, and then close it.
6. Use Notepad or another text editor to open the RSPreviewPolicy.config file, which you can find at the following location:

   C:\Program Files\Microsoft Visual Studio 8\Common 7\IDE\PrivateAssemblies

    Note   The preceding location is only an example. Your location will be similar, but it might vary, depending on what version of Visual Studio you have installed.

7. Locate the following <CodeGroup> section:

   <CodeGroup 
    class="FirstMatchCodeGroup" 
    version="1" 
    PermissionSetName="Execution"
    Description="This code group grants MyComputer code Execution permission."
   />

   In this section, add the following entry:

   <CodeGroup 
    class="UnionCodeGroup" 
    version="1" 
    PermissionSetName="FullTrust" 
    Name="ScorecardDPEGroup" 
    Description="This code group grants the Business Scorecard Manager DPE code full trust.">
     <IMembershipCondition 
      class="StrongNameMembershipCondition" 
      version="1" 
      PublicKeyBlob="KEY"
     />
   </CodeGroup>

    Important   Replace the PublicKeyBlob placeholder shown in the preceding code with the actual public key of the Microsoft.PerformanceManagement.Scorecards.DPE.dll assembly. You can use the Microsoft .NET Framework Strong Name Utility (sn.exe) to discover the public key. The following command displays the public key and the public key token:

   sn.exe -Tp Microsoft.PerformanceManagement.Scorecards.DPE.dll

   Currently, the public key for the Microsoft.PerformanceManagement.Scorecards.DPE.dll assembly is:

   002400000480000094000000060200000024000052534131000400
   0001000100b5fc90e7027f67871e773a8fde8938c81dd402ba65b9
   201d60593e96c492651e889cc13f1415ebb53fac1131ae0bd333c5
   ee6021672d9718ea31a8aebd0da0072f25d87dba6fc90ffd598ed4
   da35e44c398c454307e8e33b8426143daec9f596836f97c8f74750
   e5975c64e2189f45def46b2a2b1247adc3652bf5c308055da9

8. Save the file, and then close it.

Before a particular report view can be displayed on the Web page, you must modify the Office Report View Web Part to use the group to which the report view has been assigned.

To configure the Office Report View Web Part

1. On the SharePoint site, click Modify Shared Page, point to Modify Shared Web Parts, and then click Office Report View.
2. In the Report View Menu Items list, select the group number or group numbers that contain report views that you want to use.
3. Click OK.

 Note   You can assign multiple report views to a single Office Report View Web Part either by selecting a group that contains multiple report views or by selecting multiple groups. When the Office Report View Web Part is assigned multiple report views, a drop-down list appears when the Web Part is displayed. By using the list, you can choose which report view you want to view.

Business Scorecard Manager can either present live data in a PivotChart report view or render a PivotChart report view as a static image. By rendering the PivotChart report view as a static image, users are not required to have Microsoft Office 2003 Web Components installed on their computers.

By default, a rendered image is cached for a period of 60 seconds. If the underlying data that is used to generate the PivotChart report view changes less frequently, you can improve performance by configuring Business Scorecard Manager to cache the images for a longer period of time. Use the following procedure to increase this cache time on each server that is running Windows SharePoint Services or SharePoint Portal Server.

To increase the Business Scorecard Manager report view image cache time

1. On the server that hosts Windows SharePoint Services or SharePoint Portal Server, open the Windows SharePoint Services Web.config file. By default, this file is located at c:\inetpub\wwwroot. You can use Notepad to open and edit the file.
2. In the <appSettings> section, set the value attribute of the BPM.ReportViewImageCacheTime key to the number of seconds that you want to use for caching images. If the entry does not exist, you must create it. It should look like the following example:

   <add key="BPM.ReportViewImageCacheTime" value="3600" />

3. Save the Web.config file, and then close it.

This error can indicate that although the instance of SQL Server on the computer that is hosting the Business Scorecard Manager metadata database is running, the credentials used to connect to the database do not allow access. Make sure the identity assigned to the application pool that Windows SharePoint Services or SharePoint Portal Server uses has the correct permissions to connect to the Business Scorecard Manager metadata database and that the identity is a member of both the BpmViewer and BpmDeveloper database roles.

If you used SharePoint Services to export the scorecard Web part, and then imported the Web part to another SharePoint site, you will need to modify the Web.config file used by SharePoint Services. The <appSettings> section must contain the connection information for the Business Scorecard Manager database as shown in the following example:

<add key="Bpm.ConnectionString"
 value="Integrated Security=SSPI;Initial Catalog=ScorecardServer; Data Source=myserver"/>

For more information about the possible source of this error, see this related article on the Microsoft Knowledge Base.

If the problem persists, reinstall Business Scorecard Manager Server.

• Generate the report to a file.
• Edit the report file to modify the Sizing property.
• Upload the file to the server on which Reporting Services is installed.

To generate the report to a file

1. In Business Scorecard Builder, make sure that the scorecard that you want to use for generating the report has been published to the Business Scorecard Manager server.
2. On the Tools menu, point to Deploy Scorecard, and then click To Reporting Service Report.
3. In the Create SQL Server Report wizard, on the Choose deployment method for SQL Server report page, click Save SQL Server report to File System, and then click Next.
4. Click Specify Scorecard on Server, select the scorecard that you want to use, click OK, and then click Next.
5. Select the scorecard view that you want to use, and then click Next.
6. In the SQL Server report name box, type a name for the report, and then click Finish.
7. In the Save As dialog box, in the File name box, type the name of the file that you want to use for the report, and then click Save.

After the report has been generated to a file, you can edit the report file to modify the Sizing property.

To edit the report file

1. Use Notepad or another text editor to open the file that you generated in the previous procedure.
2. Find all occurrences of the following text:

   <Sizing>Clip</Sizing>

3. Change the text to:

   <Sizing>AutoSize</Sizing>

4. Save the file, and then close it.

To upload the file to the Reporting Service server

1. In your browser, open your Reporting Services Web site (for example, http://myserver/reports).
2. Click Upload File.
3. Click Browse to find the file that you want to upload.
4. In the Name box, type the name that you want to assign to the report.
5. Click OK.