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.

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

    • Interfaces Tab - Charter

      This section allows the user to define what information may be imported and exported to various third party charter tools. (Main View of Interfaces Tab - Charter) "Update Aircraft Availability (NATA upload interval)" Section Manually - This setting ...

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

    • Error - "Submit Status Failed" when submitting an expense from FOS Mobile

      Error: Submit Status Failed. Maximum requested length exceeded. Solution: The individual or department that manages the FOS Mobile Services on the server will need to increase the "maxrequestlength" field in the FOS Mobile Host configuration file to ...

    • Error: The request failed with HTTP Status 302: Redirect

      Error: The request failed with HTTP Status 302: Redirect Solution: 1. Ensure you are entering the correct Host URL into the device. URL must match in regards to HTTP or HTTPS. 2. Are you on FOS Version 3.11.3 or higher? In 3.11.3 this version of ...

    • Error: An error occurred while trying to rename a file in the destination directory (movefile failed)

      Error: An error occurred while trying to rename a file in the destination directory: MoveFile failed; code 183. Cannot create a file when that file already exists. Solution: Executable files are likely stuck open somewhere, either on the FOS Server ...