Commerce Server Setup Err: Cannot Populate Database Tables

 Last reviewed: March 6, 1998
Article ID: Q177882
The information in this article applies to:
  • Microsoft Commerce Server, version 2.0

SYMPTOMS

When you set up the Commerce Server version 2.0 sample stores on a Internet Information Server (IIS) 4.0 machine, you will get the following error message: 

   Commerce Server 2.0 Setup - Cannot populate database tables.
When you click Details from the error dialog box, you will get the following error message: 

   Cannot populate database tables. Class not registered.
After you set up Commerce Server, and you try to reach a sample store (for example, http://machinename/clockped), your browser returns the following message: 

   Commerce.Datasource.1 error '80040154'
   Class not registered
   /ClockPed/global.asa, line 63
NOTE: The error message appears for each sample store.

CAUSE

An incorrect version of Access Data Object (ADO) is installed.

RESOLUTION

Before you set up Commerce Server version 2.0, you must first ensure that you have ADO version 1.0 or 1.1 installed on your server. If you installed the Microsoft Windows NT Server version 4.0 Option Pack over an existing Microsoft Internet Information Server version 3.0 installation, then you will already have ADO 1.0 installed. You can get ADO 1.1 by following the steps below:

  1. Go to the following web location:

    http://www.microsoft.com/data/ado/download.htm

  2. Click the link titled "Click here to proceed to the End User License Agreement"

NOTE: ADO version 1.5 will also cause the errors at the beginning of the article, so you must run version 1.0 or 1.1.

When you set up Commerce Server 2.0, select the custom setup option, and install one starter store at a time. The starter stores shipped with Commerce Server 2.0 are Clockped, Volcano Coffee (VC), Adventure Works (AW), and Microsoft Press.

NOTE: You could set up all the required components, SDK, documentation, Store Foundation and Store Builder Wizards, and one starter store as one step and then set up the remaining starter stores one at a time by running the custom set up repeatedly.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Commerce Server version 2.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Site Server version 2.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces): 

   S E R V P A C K

Keywords          : kbsetup CommSetup kbbug
Version           : WINNT:2.0
Platform          : winnt
Hardware          : ALPHA x86
Issue type        : kbbug
Solution Type     : kbpending

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 6, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.