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

This edition was verified with Socket. An existing login manager explicitly configured for Pipe should be reviewed by the APPX administrator before using this recipe. The APPX login-manager Windows service is named Appx-554-31055-OSAuth; use your actual service name and installation path.

Close active APPX and ODBC sessions before restarting the login manager. Back up that APPX login-manager Windows service configuration, then run these commands separately in an administrator Command Prompt if a change to Socket is needed:

reg.exe export "HKLM\SYSTEM\CurrentControlSet\Services\Appx-554-31055-OSAuth" "C:\ODBC-Logs\appx-554-login-manager.reg"
"C:\appx\Appx.554\services\appxLoginMgr.exe" -modify -name=Appx-554-31055-OSAuth -AppxInterface=Socket
sc.exe stop "Appx-554-31055-OSAuth"
sc.exe start "Appx-554-31055-OSAuth"

Create the backup folder first if it does not exist. Wait for STOPPED before starting that APPX login-manager Windows service again, then confirm it is RUNNING and listening on the intended APPX port. Socket is the login manager's built-in default; its configuration can show #AppxInterface=Socket with no explicit AppxInterface override.

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 1992. Read Service, its blank default and custom aliases before changing the field.

Complete Install the 6.2.1 Client Driver first. It creates or updates AppxODBC while preserving the default dictionary. 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          1992/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 1992; 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.

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