Chapter 2: Install and Check APPX ODBC
Start the Gateway and Check Required Microsoft Files
Start and check the gateway
Here service means the Windows background service named Appx ODBC Data Gateway Server for Windows. The sc.exe commands below manage that program; they do not take the ODBC Service field's sqlnw alias. The alias instead selects a TCP port through the local services file. Read Windows services and service accounts and the optional ODBC Service field.
Open Command Prompt as administrator. Run the following separately:
sc.exe qc "Appx ODBC Data Gateway Server for Windows" sc.exe start "Appx ODBC Data Gateway Server for Windows" sc.exe queryex "Appx ODBC Data Gateway Server for Windows" netstat.exe -ano -p tcp
Check that BINARY_PATH_NAME is C:\Program Files (x86)\AppxODBCserver\bin\AppxODBC.exe. The expected state is RUNNING. Match its PID to the listening TCP socket. With a single sqlnw 1990/tcp mapping, the exact 5.5.1 package above listened on 1990, matching the installer default. An inherited sqlnw mapping can select a different port. Check the actual listener and keep the client and gateway mappings consistent. Match the client mapping to the listener.
The freshly installed gateway started with its packaged libraries, including ICU 51. No Boost library or ICU 59 replacement was added. Apply a dependency repair only when a startup error identifies the need.
If a component will not start
The reviewed 5.5.1 build projects and downloaded binaries identify older Microsoft runtime families:
| Component | Runtime family identified | Official Microsoft package |
|---|---|---|
| Gateway and ASQL | Visual C++ 2005, MSVCR80.dll; ASQL also imports MSVCP80.dll | Visual C++ 2005 SP1 MFC Security Update |
| Packaged ICU 51 libraries | Visual C++ 2010, MSVCR100.dll and, in some libraries, MSVCP100.dll | Visual C++ 2010 SP1 MFC Security Update |
| Supplied Dharma 9.01 driver | Windows MSVCRT.dll and system libraries | Use the matching APPX driver package and check the full loader error. |
Select vcredist_x86.exe, even on 64-bit Windows. The 2005 and 2010 downloads have the same filename; save them in separate folders. Check the Microsoft digital signature, run the appropriate installer and restart if requested. These are legacy runtime packages, and the download pages list older supported operating systems. They identify the dependency family; they do not certify this APPX release for Windows 11.
The test computer already had Visual C++ 2010 x86 10.0.40219 installed. The gateway package includes additional runtime files. This test does not establish that a clean Windows installation needs no runtime installation, or identify the oldest acceptable runtime patch. The newer v14 redistributable used in other cookbook editions is not a substitute for VC80 or VC100.
If Windows reports a side-by-side configuration or missing-DLL error, retain the complete message and check Event Viewer → Windows Logs → Application. Use the named dependency and its architecture to choose a repair; do not download individual runtime DLLs from unrelated sites.