Office Err Msg: Call to SqlConfigDataSource() Procedure Failed

 Last reviewed: September 16, 1996
Article ID: Q121113
The information in this article applies to:
  • Microsoft Office for Windows, version 4.3, 4.3-CD

SYMPTOMS

When you perform a custom installation of Microsoft Office Professional version 4.3 or 4.3-CD, the following error message will be returned after Setup has completed updating the system files and installing the required icons into the specified group: 

     Setup Error:
     Object ID 4990: Call to SqlConfigDataSource() procedure failed

CAUSE

This problem occurs if Microsoft Access version 2.0 is not selected to be installed when you perform the Custom Installation.

NOTE: This error message will also occur when you reinstall the custom installation, or when you change from a typical installation to a complete installation.

The error message does not harm the installation process. Setup attempts to to modify an Access file that is not there, hence the error message. If you click Ok, there should be no further problem.

RESOLUTION

To avoid this error message, choose to install Microsoft Access version 2.0 during the Complete/Custom installation of Microsoft Office. Then run the maintenance mode of the Setup program and remove Microsoft Access version 2.0.

NOTE: Running the maintenance mode of the Setup program and selecting the reinstall option will result in the same error message.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Office Professional for Windows, version 4.3 and 4.3-CD. This problem was corrected in Microsoft Office versions 4.3c and 4.3c-CD.

KBCategory: kbsetup kberrmsg
KBSubcategory:

Additional reference words: 4.30 Setup ErrorSetup object sqlconfig data
source




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: September 16, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.