Provider Cannot Be Found Error when Translating .IntLib to .DBLib

Created: April 17, 2021 | Updated: August 12, 2021

Trying to convert an .IntLib into a .DBLib using the menu option Tools ► Import from Integrated Libraries when the .DBLib is active in the workspace brings up this Error: "An error was encountered exporting. Provider cannot be found. It may not be properly installed. The export has been aborted."

Starting in Version: 18.0
Up to Version: Current

Solution Details

To determine if this is an issue with the file, try the same steps on a known good file such as the Miscellaneous Devices.IntLib example library which can be found here: 
C:\Users\Public\Documents\Altium\[ADversion]\Library

This might be a Microsoft Access issue. You can try performing the on-line repair of Office from Windows's control panel.  Different methods are required based on the version you are using.   Here is a link to a Microsoft office support article that should help:
https://support.microsoft.com/en-us/office/repair-an-office-application-7821d4b6-7c1d-4205-aa0e-a6b40c5bb88b

You can also try installing the 64-bit Microsoft Access Database Engine (2010) from here:
http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=13255

From an elevated command prompt (run cmd.exe from a Windows search - right click and choose run as administrator), enter the file path and name of the 64-bit Microsoft Access Database Engine (2010) install file, followed by a space and the switch /passive, for example: 

C:\Users\<ProfileName>\Downloads\AccessDatabaseEngine_x64.exe /passive. 
The /passive switch runs the installation without showing (and skipping over) any error messages.

Open the Registry Editor (regedit.exe from a Windows search) and browse to the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0\Common\FilesPaths. Delete or rename the mso.dll registry entry.
Note that if you do not delete the mso.dll registry entry, you may get a reconfiguring message each time an Office application is accessed.
 

Was this article helpful?
0
0
Found an issue with this document? Highlight the area, then use Ctrl+Enter to report it.

Contact Us

Contact our corporate or local offices directly.

We're sorry to hear the article wasn't helpful to you.
Could you take a moment to tell us why?
200 characters remaining
You are reporting an issue with the following selected text
and/or image within the active document: