KNOWLEDGE BASE ARTICLE

Umango Service Intermittently Stops With ODBC Error

This issue is only applicable to versions earlier than Umango 23.

This issue can present itself in server environments that are running unsupported versions of the Access runtime. The result can be intermittent ODBC issues when Umango attempts to make database calls.

When this issue occurs, the Windows Event log may show entries similar to the one below:

The system has called a custom component and that component has failed and generated an exception. This indicates a problem with the custom component. Notify the developer of this component that a failure has occurred and provide them with the information below.
Component Prog ID: 6[ODBC][Env 00000175EE6689C0]
Method Name: IDispenserDriver::CreateResource
Process Name: UmangoService.exe
Exception: 148f8c4
Address: 0X00007FFE357B37DD

To resolve this issue, please do one of the following:

1. Move Umango to a dedicated server and do not install any database drivers or MS Office software on the server. Only install the prerequisite software as prompted by our installer (which includes the MS Access runtime). This is the preferred option - running Umango on its own server is always strongly recommended
2. Remain with the existing server but uninstall all copies of MS Office and MS Access. Then re-install the Access 2010 or 2013 runtime engine (this is a prerequisite)
3. Remain with the existing server but upsize Umango to run an SQL Server database instead of the default Access database. If the client chooses this option they should follow the upsizing steps detailed in our knowledge base

Link to this article http://umango.com/KB?article=117