Geeks With Blogs
Mark Nichols' Blog Let me explain. No, there is too much. I will sum up.

I am writing this after a failed initial attempt to install Microsoft Business Scorecard Manager Evaluation Kit.  My problems started because I tried to fly by the seat of my pants using the 5 DVDs that should have combined to form a usable BSM environment.  Unfortunately, not quite everything you need is included and part of my problems had to do with the use of evaluation software.  Also, there are still some legacy requirements left over from the original development of BSM that used SQL Server 2000 that had to be found and installed.


First, if you are trying to install an evaluation environment using the BSM eval kit or if you are using eval software (specifically SharePoint Portal Server) from an independent source you will not be able to succeed if SQL Server 2005 is used as the database.  This is because SharePoint Portal Server (SPS) needs to be updated with SPS Service Pack 2 and you cannot do this with an evaluation version.  If this is confusing go to this page to see more detail.


If you have attempted to install SharePoint Portal Server and are in the “Create a Portal” step and it fails at 52% then it is (most likely) because SPS needs Service Pack 2 to communicate with SQL Server 2005.


Business Scorecard Manager Component Overview:

The system is based on combining 5 major Microsoft components:  Windows Server 2003, SharePoint Portal Server 2003 (based on Windows SharePoint Services), SQL Server 2000 or 2005, Microsoft Office and, of course, Business Scorecard Manager.


If you are interested in learning more about BSM (the product) then check out the MS web site.


Additional components that aren’t in the SQL 2005/SharePoint 2003/BSM install:

When you are installing Business Scorecard Manager you may come to a point where the installation does its “Analyzing Feature Requirements” thing and won’t let you proceed.  The list below shows a couple components that BSM needed that are left over from SQL Server 2000.





Microsoft ADOMD.NET 8.0




Microsoft OLE DB Provider for OLAP Services (MSOLAP) 2000 SP4 (8.00.2039)



Hotfix Rollup for SQL Server 2000 Analysis Services Service Pack 4 - Build 2174 for Client Systems

(Pivot Table Services)


Note: The download locations above are all directly from Microsoft.


My installation configuration:

  • MS Virtual Server – HIGHLY recommended when trying to create a test environment.  Also highly recommended to have plenty of RAM on hand.  Highly recommended to not use it if the resulting installation is to be used for production.  You will loose a significant amount of performance using Virtual Server but if you are testing installation or capabilities then by all means…
  • The machine I am using is a laptop with 1GB of RAM.  I needed the portability so that’s what I’ve got.  Wish I had more RAM – but it is working.  I allocated 512MB to the Virtual Server session.  I still got a warning when installing SQL Server 2005 but it was just a warning so I continued.  It did not prove to be a problem.


Installation Steps:

    1. Install Windows Server 2003 – Explaining how to install is outside the scope of this description.  Note that IIS 6 must also be installed for SharePoint to operate.
    2. Install SQL Server 2005 (This was one of the easiest installs)
      • Installed all components (IS, AS, RS)
      • Default Instance
      • Service account uses the built-in system account (local system)
      • Mixed Authentication Mode
      • Default Collation
      • Default Config on the Report Server
      • No Selections on the Error and Usage Report Settings
      • And away it went.  Took about 3 hours on my laptop.
    3. Minor Timeout: As one of the benefits of using Virtual Server, I copied the virtual machine files to a backup location.  If anything happens now during the install I can copy the backed up VM and start again at step 4.
    4. Before installing SharePoint you need a system account for SharePoint to use to perform admin tasks as well as create and access the SQL Server databases.  If you are using a singe server for all components the account can be local to the machine otherwise it must be a domain account.  I created a local account called “SPS_Admin”.  Whether you create a new account or plan to use an existing one, you will need to know the password for the account in a later step.
        • Add the account to the “Power Users” group
    5. Create a new SQL Server login using the account from step 4 (above) and add it to the “Database Creators” and “Security Administrators” roles.
    6. Install SharePoint Portal Server 2003: Print out a copy of “Installing SharePoint Portal Server without the Database Engine” from SharePoint Portal Server 2003 Administrator's Guide and follow the steps in the guide up to step 12 (Completing the MS Office…click Finish.  Note the following in step 10:
      • On the “Provide a valid Microsoft Windows account” screen, enter the account name and password of the account that you created in the first step above.  Even if you do not create a domain account, be sure to enter the account name using the domain\account format.  If you created a local machine account enter machinename\account.  The installation will accept the account name without the domain but it will cause major problems later.
    7. When the SharePoint Portal Server installation completes, click “Next” and then “Finish”.
    8. At this point the SharePoint “Configure Server Farm Account” page will appear.  You need to install Windows SharePoint Services Service Pack 2 and SharePoint Portal Server Service Pack 2 so either minimize the window or click the IE icon in the address bar and drag it to your desktop.  You will need to get back to this window later.
    9. Install Windows SharePoint Services Service Pack 2.  If you don’t have it you can find it here.
    10. Now install SharePoint Portal Server Service Pack 2.  If you don’t have it you can find it here.
    11. Reopen the “Configure Server Farm Account” page from step 8 (above) and continue following the directions in the “SharePoint Administrator’s Guide”.  You should be able to complete the configuration and creation of a portal successfully.
    12. Install Business Scorecard Manager Server.  During the “Analyzing Feature Requirements“ check, BSM may inform you that you need to install other components.  The two additional components that it required from me are listed above and there are links to download them if you needed.
    13. (Optional) You can now install the Business Scorecard Manager Builder if you want to have it on the same machine.


That should do it.  Good Luck!


Posted on Friday, February 10, 2006 8:07 AM .NET Observations | Back to top

Related Posts on Geeks With Blogs Matching Categories

Comments on this post: Installing Business Scorecard Manager 2005 - Using SQL Server 2005

# re: Installing Business Scorecard Manager 2005 - Using SQL Server 2005
Requesting Gravatar...
Hi Mark,

We have installed Business Scorecard Manager & Builder 2005 Trial Version on Windows 2005 server with SQL Server 2005 as database and Windows Sharepoint Services 2.0.

We are facing problem while connecting to the database using data source, following is the error message:

“The Business Scorecard Manager server could not connect to the data source. Verify all of the required data has been entered and the required connection information is correct”

We have created Sharepoint Site on port- 90, while IIS Server admin is on port- 80.

We have given permission in Database for User: “NT AUTHORITY\NETWORK SERVICE”.

Still Builder is NOT able to connect to Server, Can you throw some light on our problem. What could be the issue ?


Deepak Talim

Left by Deepak Talim on Aug 09, 2006 6:52 AM

# re: Installing Business Scorecard Manager 2005 - Using SQL Server 2005
Requesting Gravatar...

Instead of using the network service account try creating a domain account with access to the SQL database and then set your app pool to use that account.

Left by Mark Nichols on Aug 09, 2006 2:51 PM

Your comment:
 (will show your gravatar)

Copyright © Mark Nichols | Powered by: