Troubleshooting FAQs for FOS Vendor Alliance
1. On the FOS server, check under Administrative Tools → Services. There should be a service running called ‘FosVendorSyncService’. If not ‘Running’, right-click and ‘Start’ the service.

2. On the FOS server, check the config file to ensure it is pointing to the correct FOS Database name. The default path for the config file is: C:\FOS\FosVendorSyncService.
If not located in this directory, try searching for ‘FosVendorSyncService.exe’ in a Windows Explorer Window.

a. Open the Config file with Notepad. Ensure the ServerDSN field is pointing to the proper FOS Database Name (the FOS Database name is found in the Pervasive Control Center).
b. To verify the FOS Database name, open the Pervasive Control Center (also located on the FOS Server). Right-click on the Database Name. Select Properties-- >Directories. The path loaded here should point to their FOS Data folder. This verifies the FOS Database name.

- If the Database name within the Config File does not match the Database name located in the Pervasive Control Center:
- Open the Config File
- Adjust the ServerDSN field to the proper name. Save the file.
- Restart the FosVendorSyncService.
3. On the FOS server, check the config file to ensure it is pointing to the correct FOS DLL location. The default path for the config file is: C:\FOS.
- Adjust the path to the proper name. Save the file.
- Restart the FosVendorSyncService.

4. If ensuring the ‘FosVendorSyncService’ service is running and the Config File matches the FOS Database Name, and the customer is still experiencing issues, we can now turn on the ‘Debugging’ within the Config File. This will produce a log file that can be captured and email to the FOS developers for additional troubleshooting.
- To do so, locate and open the ‘FosVendorSyncService.exe’ (Reminder: typically stored in C:\FOS\FosVendorSyncService)
- The value <add key= “Debug” value=”false” /> is set as the default for all customers. Modify the value field to ‘true’. Now it should read: <add key= “Debug” value=”true” />
- Save the Config File. Restart the ‘FosVendorSyncService’ in the Services section.
The log file will then generate after the amount of time that is set in the Vendor Alliance module → Interval Timer. The default value for this field is 10 minutes. See screenshot on next page.
- The defaulted location of the log file (this value is found in the Config File)→C:\FosVendorSyncService.log
- Send this file to the FOS Developers.
5. .NET 3.5 must be installed on Windows Server 2012 if the user is unable to start the Vendor Sync Service
Related Articles
Vendor Alliance Activation Process
Once the Account Number has been added to the appropriate Vendor, within Vendor Alliance Module, the Status on the Configured Vendors Column will initially read Processing New Vendor. After the FOSVendorSyncService has ran and updated on the server ...
How to Rename the FOS Database in the Vendor Alliance config file
1. Start Windows component services Click on the Windows start menu button and search for "component services" 2. Stop vendor alliance window services Click on Services (Local) Click on FosVendorSyncService Click on the stop button at the top 3. ...
Updating FOS
Updating Flight Operations System (FOS) (Only for FOS systems that are under a current support contract) Before running the FOS Installer, you will need to uninstall the FOS Vendor Alliance Program on the server. If your company has FOS Mobile, the ...
RESOLVED - FOS Mobile Airport Database
As of October 2025, this issue is resolved. Users will need to update their mobile application to version 5.0 if not set to automatically update. Within the mobile application, the following error regarding airport data could be seen. We are ...
Installing FOS Using the Installer
Install Pervasive: The FOS Installer does not include Pervasive now known as Actian Zen. You are able to install Actian Zen from actian.com. The Actian Zen/Pervasive Installer will come with a 30 Day Trial License. If you have your permanent License ...