🚀 Overview

In Microsoft Access environments, particularly those utilizing FRx for financial reporting, IT administrators may encounter a specific automation failure identified as “Runtime error -2147319779 (8002801d) automation error library not registered.” This error is typically triggered when an end-user attempts to modify the environment configuration by setting a specific company as the default.

The root of the issue lies in a broken link between the application and its required data access components. Specifically, the system fails to interface with the necessary specification sets and system databases because a critical COM component in the Microsoft Data Access Components (MDAC) stack is not correctly registered within the Windows Registry.

⚙️ Key Technical Details

• Error Signature: The exception is explicitly labeled as Runtime error -2147319779 (8002801d).
• Primary Cause: The application relies on the ActiveX Data Objects (ADO) framework to manage database communication. When FRx attempts to access its internal system databases or specification sets, it calls upon an ADO Object dependency that is either unregistered or incorrectly referenced.
• Affected Component: The specific library responsible for this interaction is msadox.dll (Microsoft ADO Ext. for DDL and Security).
• Version Dependency: This dependency is introduced with MDAC Version 2.8 and all subsequent iterations.
• File Location: The library is standardly located in the following directory: C:\Program Files\Common Files\System\ado.

🛠️ Resolution Procedure

To resolve this error, the administrator must manually re-register the msadox.dll file to ensure the Windows Registry correctly points to the library.

1. Open an elevated Command Prompt (Run as Administrator) on the affected workstation.
2. Execute the registration command using the regsvr32 utility.
3. The full path to be targeted is: C:\Program Files\Common Files\System\ado\msadox.dll.

Once the registration is successful, the operating system will be able to provide the necessary interfaces for FRx to connect to its underlying databases, allowing the “Set as Default” operation to complete without error.

⚠️ Impact

If this library remains unregistered, users will be effectively locked out of switching between different company entities within the software. For IT administrators, this represents a localized workstation configuration issue rather than a server-side database corruption. While the data itself remains intact, the application’s “Automation” layer remains broken, preventing critical administrative tasks and reporting functions from being executed within Microsoft Access and FRx.

Read the full article on Microsoft.com