Updating the FosVendorSyncService config file

Updating the FosVendorSyncService config file

The FosVendorSyncService config file must be updated when there is an update to FOS. The configuration file will be included in the FOS Installer. Below are the steps to update the FosVendorSyncService config file. 

1. Go to the directory where FosVendorSyncService is installed.


2. Open FosVendorSyncService.exe.config


3. Confirm the pervasive Database name, dll path, and service installation path are all listed correctly.

4. Restart the FOSVendorSyncService.

    • Related Articles

    • 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 ...

    • 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 (sqare) button at the top ...

    • FOS Airport Update Instructions (3.12 and greater)

      As of release 3.12.1, the FOS airport data source is changing from Universal to ARINCDirect. Below are the steps for the new airport update process. Step 1-2 only needs to be completed one-time, subsequent updates only require step 3. The airport ...

    • Updating the FOS Mobile Host

      Please note: The following are general instructions used to install the FOS Mobile Host. Please tailor your specific installation accordingly. FOS Mobile Host 1. Stop the existing FOS mobile host service. 2. Right click on the old back up config ...

    • Error: No connection could be made because the target machine actively refused it

      Error: The error message below may be seen in the FosVendorSyncService.log 12/20/2016 11:01:34 AM , Vendor Activation - Sync Started 12/20/2016 11:01:36 AM , No connection could be made because the target machine actively refused it SOURCE: System ...