Informix Error -1366: Unable to load application appname.

Reasons / Common Causes

-1366 fires when the Application Launcher (fglaunch) finds the named application's DLL but can't load it — per the official guidance, the DLL lacks the required NewEra entry points, so it's not actually a NewEra DLL.

1. A NewEra DLL name colliding with an existing, unrelated system library, per the official guidance's specific troubleshooting suggestion — fglaunch loaded the wrong DLL entirely.
2. A genuinely non-NewEra DLL placed where a NewEra application DLL was expected.

Solutions / Resolution

1. Verify whether the NewEra DLL shares a name with an existing system library, per the official guidance — rename or reposition the DLL to avoid the collision if so.

Examples

N/A

No specific triggering statement is documented — check for a naming collision between the NewEra DLL and an existing system library.

Diagnostic Checks

1. Check whether the named DLL's file actually has the required NewEra entry points, and whether a same-named system library is being loaded instead.

Related Errors / Related Topics

• -1365 — "Application appname not found." A related fglaunch error, about the application not being found at all rather than found but unloadable.
• -1367 — "DLL dllname is not a resource DLL - Application Terminating." A related fglaunch DLL error, about a resource-configuration mismatch.

The DLL fglaunch loaded lacks the required NewEra entry points — check for a name collision with an existing system library.