Application Support for CAE (Formerly Sabre Airline Solutions)
| Software Vendor: |
CAE |
| Application Name: |
FliteTrac, CrewTrac, CrewQual, etc. |
| Application Version: |
See below |
Note: In October 2021, CAE acquired the Sabre AirCentre product portfolio, including these older products.
Note: This product is APPROVED AND TESTED for use with DataExchange for real-time backup and synchronous database replication.
Note: This product is APPROVED AND TESTED for use with DoubleTake Availability for server-to-server (off-line) replication.
There is a very wide variety of application versions and database versions supported in this environment -- far too many to list. Because of this, we have removed our usual "supported versions" chart and have replaced it with the following information:
CAE/Sabre is typically FAR behind the curve on testing new releases. As of August 2023, a full 2 years after the release of Actian Zen v15, they have not yet even announced testing of this newer engine. However, users are currently implrmenting both PSQL v13 and Zen v14 with current versions of the product, so we do not expect any major issues.
The most recent Software Requirements documentation available for the CrewTrac application indicates the following, with the recommended options in bold:
| Software |
Workstation |
Server |
CrewWeb Server |
| Operating System |
Windows 7 or Windows Server 2012 R2, Server 2016, Server 2019 |
Windows 7 or Windows Server 2012 R2, Server 2016, Server 2019 |
Windows 7 or Windows Server 2012 R2, Server 2016, Server 2019 |
| Database |
PSQL v13 Client, Zen v14 Client |
PSQL v13 Engine, Zen v14 Engine |
PSQL v13 Client, Zen v14 Client |
After migrating data from one server to another, you may receive an ODBC error: "Non-DB File or Corrupted DB". This error does not actually mean that something is corrupted. However, it does indicate that the database that the application is attempting to connect to is invalid. The Sabre application opens up the file DB.CONFIG to obtain the database configuration information. It then attempts to connect to the database using this server name and Engine DSN name. If this information is incorrect, then the PSQL engine will return this error, which may or may not be displayed by the application. (Many Sabre applications simply crash or report some other error, like an Access Violation.) First, look at the DB.CONFIG file and determine if the server name is correct. Then, note the Engine DSN name. On the server, use the ODBC Administrator (32-bit) to confirm that the Engine DSN (with the name from DB.CONFIG) is created, and that it points to the right Named Database on the server.
If you are a software vendor and would like to add, remove, or modify your information on these pages, we'll be
happy to oblige. Simply contact us directly!
|
