Error: Charter Vendor update failed: XML Document must have a top level element.
Error:
Charter Vendor update failed: XML Document must have a top level element.
Solution:
1. Increase the number of dynamic ports using "netsh" command OR
2. Reboot the system
Related Articles
ARINC Document - connection error
We have been made aware of an intermittent issue with transmission of documents to ARINC from FOS. After connecting with ARINC Engineering on this issue, we were advised they do see these errors and believe it is possibly due to network issues which ...Error: Save User ClassLibraryUserCredential.FOSSSOAccount failed
Error: Save User ClassLibraryUserCredential.FOSSSOAccount Failed Solution: There is currently an issue associated with invalid data being passed to FM from FOS. Please run the following script on the applicable database associated with which ever ...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. ...Connection to FOS failed GetMobileFilter error (-3): Error: invalid owner (error=51)
Error: Connection to FOS failed GetMobileFilter error (-3): Error: invalid owner (error=51). Please contact your FOS administrator for required changes to the FOS server. Resolution: Restart the FOSMobile Host ServicesConfiguring Aircraft for the Charter Vendor Alliance
The customer can select specific aircraft or all aircraft to for which they would like to send data to the vendor. The grid displays specific information that will be sent for each aircraft. The customer can choose to send “holes” in the schedule or ...