ACC97: MS Exchange ISAM Driver Requires Manual Registration

Last reviewed: November 13, 1997
Article ID: Q161173
The information in this article applies to:
  • Microsoft Access 97

SYMPTOMS

Moderate: Requires basic macro, coding, and interoperability skills.

When you try to use the Microsoft Messaging Driver in your Visual Basic code to import, export, or link a Microsoft Outlook or Microsoft Exchange folder, you may receive the following error message:

   Run-time error '3170':
   Couldn't find installable ISAM.

CAUSE

When you install the Microsoft Messaging Driver from the Data Access Pack in the Office 97 ValuPack, the Setup program copies the driver to your hard drive, but Setup does not register the driver in the Microsoft Windows registry.

RESOLUTION

You can use the Microsoft Register Server, Regsvr32.exe, to manually register the Microsoft Messaging Driver file in the Microsoft Windows registry. Regsvr32.exe is installed in your Windows\System folder by Microsoft Internet Explorer version 3.01 or later. You can also obtain a copy of Regsvr32.exe from Microsoft's download services.

For information about installing Microsoft Internet Explorer 3.02, please see the following articles in the Microsoft Knowledge base:

   ARTICLE-ID: Q159707
   TITLE     : Office 97 Requires Internet Explorer 3.01

   ARTICLE-ID: Q164475
   TITLE     : Availability of Internet Explorer 3.02 for Windows 95 and
               NT 4.0

For information about obtaining a stand-alone copy of Regsvr32.exe, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q161983
   TITLE     : ACC97: Regsvr32.exe Available on MSL


In Microsoft Windows 95 and Microsoft Windows NT 4.0

  1. Quit Microsoft Access if it is running.

  2. Click the Start button, and then click Run.

  3. In the Run dialog box, type the following command in the Open box. Note that the path to Regsvr32.exe and MSExch35.dll may be different on your computer.

          C:\Windows\System\Regsvr32.exe C:\Windows\System\MSExch35.dll
    

In Microsoft Windows NT 3.51

  1. Quit Microsoft Access if it is running.

  2. In Program Manager or File Manager, click Run on the File menu.

  3. In the Run dialog box, type the following command in the Command Line box. Note that the path to Regsvr32.exe and MSExch35.dll may be different on your computer:

            C:\Winnt\System32\Regsvr32.exe C:\Winnt\System32\MSExch35.dll
    
    

STATUS

Microsoft has confirmed this to be a problem in Microsoft Access 97. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

REFERENCES

For more information about the Windows Registry values for the Microsoft Outlook/Exchange driver, search the Help Index for "Microsoft Exchange Data Source Driver, initializing."

For more information about obtaining the Microsoft Outlook/Microsoft Exchange driver, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q159322
   TITLE     : ACC97: Paradox, Lotus, & MS Exchange/Outlook ISAMs in
               ValuPack

For more information about using the Microsoft Outlook/Microsoft Exchange driver, refer to the Microsoft Exchange/Outlook Driver section of the acread80.wri file in the C:\Program Files\Microsoft Office\Office folder.


Additional query words: ISAM Outlook Off97
Keywords : IsmOthr kberrmsg kbusage
Version : 97
Platform : WINDOWS
Hardware : x86
Issue type : kbbug
Solution Type : Info_Provided


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