Check the Saved AppxODBC Connection (DSN)

Use the default dictionary

The gateway installer creates the appx SQL dictionary and writes the APPX server endpoint to appx.dbs\appx.env. Use that default dictionary. No additional mdcreate command is required for this recipe.

The default names refer to different things:

On an existing test installation, preserve the current DSN before replacing it under the same AppxODBC name. Keep the existing appx dictionary and import COUNTRY into it with ASQL.

Check the APPX login-manager interface

The tested 5.5.2 login manager uses Pipe and listens on TCP 31053. Preserve the working interface when following this edition. The ODBC gateway still connects to the login manager over its network endpoint; Pipe is the Windows login manager's engine interface.

Check the APPX login-manager Windows service and intended engine path before diagnosing a failed connection. Do not change a production login manager's interface merely because another APPX release uses a different setting.

Check the client driver and DSN

Leaving the ODBC Service field blank is valid for the standard connection. Blank uses the default sqlnw TCP-name lookup; entering sqlnw explicitly uses that same lookup. Leave Service empty for this recipe, as in the current login screenshots. The supplied driver installer omits this optional value; entering sqlnw is an explicit alternative. Keep Database appx: it selects the SQL dictionary and does not belong in Service. With either blank or explicit sqlnw, verify that the client's mapping reaches this gateway on TCP 1990. Read Service, its blank default and custom aliases before changing the field.

Use the supplied 5.5.2 driver installed above. Then check the gateway port mapping and the data source below.

1. On the client computer, back up C:\Windows\System32\drivers\etc\services and ensure that the sqlnw mapping resolves to the verified gateway port. For this cookbook the mapping is:

sqlnw          1990/tcp

Resolve duplicate or conflicting sqlnw entries before proceeding. Leave the ODBC Service field blank for this recipe. Entering the TCP alias sqlnw explicitly is also valid. Both use this mapping to reach TCP 1990; neither starts the gateway or changes its listener. Use a different named alias only for a deliberately configured alternate port. How the services file and fallback work.

2. Open C:\Windows\SysWOW64\odbcad32.exe and check System DSN for AppxODBC. This is the 32-bit ODBC Administrator. The program in System32 manages 64-bit drivers.
3. Select Configure. Keep Host as the gateway hostname, Database appx, and optional ODBC Service blank. Entering sqlnw explicitly is an alternative using the same TCP-name lookup. Keep the supplied AppxODBC Driver. Its DLL is C:\Program Files (x86)\AppxODBCDriver\dhsodbc.dll; Windows may display the equivalent short path. Driver version is 09.01.0000.

Next, import the COUNTRY metadata with ASQL. An empty dictionary cannot answer the sample queries until that import completes.