Userlog Update Temporarily Fixed License Expiration Error
Error:
Userlog successfully applied and users are able to log in, but some time later the Expiration warning message re-appears.
Solution:
If the userlog is correct the culprit is likely the expiration date listed in Flight Manager. When the interface manager runs it pulls this date through the FM interface overriding the date listed in the userlog.
Related Articles
Hosted Customer Userlog
Billing will send a userlog.btr file via a ticket to FOS Technical Support stating that it needs applied and pointing our the customer contact. 1. Change the requester of the ticket to the FOS Customer contact. 2. Coordinate a time with the customer ...
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
eAPIS Tech Support: How to update password
FOS will continue to integrate with the eAPIS web service. Instead of using customer credentials, FOS will utilize credentials managed in Flight Manager (FM). FOS Tech support updates the eAPIS credentials inside FM internal every 45 days. FM will ...
Btrieve Error: Invalid owner (error=51) sched_open_files: TripLegs (Thread 0)
Error: When error is received when opening up the Interface Manager on a new hosted instance. Invalid owner (error= 51 ) sched_open_files: TripLegs (Thread 0) Solution: If the userlog is encrypted, restore the decrypted user log and then encrypt the ...
BFOS Flight Manager Error
Error: An FM account was unable to be created for this FOS account since your Flight Manager Default User Account (BFOS) is not valid or populated. Solution: To resolve this error, both the BFOS username in the FOS Company profile and internal FM ...