PRB: Ordinal 301 Error When Installing MDAC

Last reviewed: December 22, 1997
Article ID: Q178211

The information in this article applies to:

Microsoft Data Access Components, version 1.5

SYMPTOMS

When installing the Microsoft Data Access Components (MDAC), version 1.5, you may see one of the following errors:

   The ordinal 301 could not be located in the dynamic link library
   ODBC32.dll

-or-

   A device attached to the system is not functioning.
   LoadLibraryEx() failed on:
   C:\Program Files\Common Files\system\ole db\msdasql.dll

CAUSE

One of these errors may be triggered when MDAC 1.5 attempts to register the Msdasql.dll file (the OLE DB Provider for ODBC Drivers) and the Odbc32.dll file on a computer that has not been updated to ODBC version 3.5.

MDAC 1.5 attempts to install ODBC version 3.5 during the same installation process. However, if any of the ODBC DLL files are currently loaded in memory, ODBC 3.5 is not completely installed until the next reboot. Msdasql.dll requires that the ODBC 3.5 files be completely installed; when the ODBC 3.5 files are not completely installed, an error message is generated.

RESOLUTION

Reboot the machine, and then run the MDAC installation program immediately before starting any other programs or services. The MDAC installation program should now complete successfully, because the updated ODBC 3.5 components are copied to their proper locations by Windows during the reboot process. This allows the rest of the MDAC components (ODBC drivers, OLE DB, ADO, RDS, and so on) to successfully finish installation.

REFERENCES

http://www.microsoft.com/data

Keywords          : mdacSetup
Version           : WINDOWS:1.5
Platform          : WINDOWS
Issue type        : kbprb

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

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: December 22, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.