Start the Gateway and Check Required Microsoft Files

Install Microsoft's 32-bit Visual C++ runtime first

Ensure that the Microsoft Visual C++ v14 Redistributable (x86) is installed on the gateway computer and on each Windows computer running the 32-bit ODBC driver. An existing current installation does not need to be installed again. Choose x86, including on 64-bit Windows: the runtime architecture must match the application. See Microsoft's runtime download guidance.

Why this runtime: the reviewed 5.5.3 and 5.5.4 Windows build projects select the Visual Studio 2019 v142 toolset. ASQL's Release configuration uses the dynamic C/C++ runtime (MultiThreadedDLL, or /MD), and both downloaded gateway executables import VCRUNTIME140.dll. This identifies the Microsoft v14 runtime family. Use the official x86 download linked above for these 32-bit components. Visual Studio or the Boost development tools do not need to be installed on user desktops.

The source projects do not pin an exact compiler patch or redistributable installer version, so they do not establish the oldest acceptable runtime patch. Microsoft's current v14 redistributable supplies compatible runtime updates. Version 14.51.36247.0 was installed and tested for this cookbook; it is a tested version, not a claimed minimum.

1. Save the Microsoft download as vc_redist.x86.exe.
2. Open its Properties > Digital Signatures and confirm the signer is Microsoft Corporation.
3. Run the installer, choose Install or Repair, and restart Windows if requested.
4. Start and check the gateway service. Complete the client driver setup and COUNTRY check; if both succeed, continue without adding other runtime files.

For a scripted installation from an administrator Command Prompt, run:

vc_redist.x86.exe /install /quiet /norestart

Exit code 0 indicates success; 3010 indicates success with a restart required. Complete that restart before treating the installation as finished.

If the gateway still does not start

Additional runtime files are a conditional package repair, not a general requirement to install the Boost development tools. Prefer a complete matching gateway package or dependency bundle supplied by APPX Support.

The particular 5.5.3 and 5.5.4 gateway downloads tested on October 14, 2026 explicitly reference ICU 59 and boost_regex-vc142-mt-x32-1_71.dll, while their installer archives contain ICU 51 and omit that Boost DLL. Installing Microsoft's signed x86 runtime 14.51.36247.0 did not resolve that separate dependency: both gateways failed to start with only the Boost DLL removed and started when it was restored. This finding applies to those downloaded builds; it does not establish that every installation of these APPX releases needs the same repair.

A missing dependency can appear in Windows Event Viewer > Windows Logs > System as:

The Appx ODBC Data Gateway Server for Windows service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

Event 7009 may also report:

A timeout was reached (30000 milliseconds) while waiting for the Appx ODBC Data Gateway Server for Windows service to connect.

These messages alone do not identify the missing DLL. Check the actual gateway package and its dependencies before applying the conditional gateway package repair. Microsoft Visual C++ runtime files, ICU and Boost Regex are separate components; one installer does not substitute for all three.

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 these commands one at a time:

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 points to C:\Program Files (x86)\AppxODBCserver\bin\AppxODBC.exe. The expected service state is RUNNING. Match its PID to the LISTENING entry on TCP 1992. That port is separate from the APPX login-manager port, 31055 in this example.

If an earlier installation left the service pointing to the wrong folder, stop it and correct only that service's path:

sc.exe stop "Appx ODBC Data Gateway Server for Windows"
sc.exe config "Appx ODBC Data Gateway Server for Windows" binPath= "\"C:\Program Files (x86)\AppxODBCserver\bin\AppxODBC.exe\""
sc.exe start "Appx ODBC Data Gateway Server for Windows"