jbourke
Knife Edge Software Owner
Here are some common error codes and their meaning.
12228: HTTP response is missing an expected header.
App: Launcher, RealFlight
Cause: In the past, this meant the HTTP response is missing the "content-length" header, which probably means the server machine is accessible but Registration Server App is not running. However, we believe recent code changes will make this error much less common. Instead, KEError 12243 should take its place most of the time (starting with version .410).
What you should do: Try the action again later. If you continue to have problems, contact RealFlight Support.
12243: [error text depends on the error]
App: Launcher, RealFlight
Cause: HTTP response with status code other than 200 OK. A number of different problems could lead to this error—too many to predict here. But the most likely cause is listed in the KEError 12228 description above.
What you should do: Try the action again later. If you continue to have problems, contact RealFlight Support.
16502: File copy error: [error text depends on the error]. Bytes read: [#], Bytes written: [#]. Make sure you have enough space on your hard drive.
App: Installer
Cause: In theory, any copy error during installation will cause this error, which includes a multitude of potential causes. In practice, it's usually caused by a bad CD. Test this by trying to copy the same file using Windows Explorer. If Windows can't copy the file, neither can the Installer.
What you should do: Contact RealFlight Support and tell them you suspect you received corrupted disks.
32494: Please contact technical support if the problem persists.
App: RealFlight
Cause: A problem has gone wrong while initializing the file system. As it turns out, in the current version of G3 this error will only occur when KEError 32495 occurs (see below).
What you should do: Contact RealFlight Support and tell them you suspect you received corrupted disks.
32495: You may need to reinstall. Please contact technical support if the problem persists.
App: RealFlight
Cause: One of the two main .DCKs (RFV3_1.dck or RFV3_2.dck) could not be found. If both files are present on disk, one of them is probably corrupt.
What you should do: Contact RealFlight Support and tell them you suspect you received corrupted disks.
12212: Unable to connect to server. Make sure you have access to the Internet (check firewall settings if applicable).
Description: [description text depends on cause of error]
App: Launcher
Cause: Most likely cause is no Internet connection, or a firewall preventing the app from establishing a socket connection to the server. This is the very first and most basic step in connecting to server to send/receive data. If it fails, it is probably a result of something on the user's end. If the Registration Server machine is completely down, that would also cause this error, but it cannot be caused simply by problems with the Registration Server app.
What you should do: Try the action again later. If you continue to have problems, contact RealFlight Support.
21023: Unable to register: Client/Server transaction failed.
App: Launcher
Cause: The online registration attempt has failed. This error will typically be preceded by another KEError in the 12000 range (such as 12212, described above). Therefore, in most cases it serves the function of telling us what action was being attempted when the previous error occurred, and as such doesn't have a cause of its own.
What you should do: Try the action again later. If you continue to have problems, contact RealFlight Support.
21039: Unable to obtain the latest available version number: server transaction failed.
App: Launcher
Cause: The Launcher needs to find out what the latest version available on the server is before it can perform updates. Like KEError 21023 (described above), this error will typically be preceded by another KEError in the 12000 range. Fixing that problem will fix this one.
There are three different times this error can occur:
1. When the user clicks "Update to Latest Version"
2. When the user clicks "Update to Specific Version"
3. When the Launcher performs its automated check on startup (this only happens when the "Check for updates before starting RealFlight" option is enabled)
What you should do: Try the action again later. If you continue to have problems, contact RealFlight Support.
12228: HTTP response is missing an expected header.
App: Launcher, RealFlight
Cause: In the past, this meant the HTTP response is missing the "content-length" header, which probably means the server machine is accessible but Registration Server App is not running. However, we believe recent code changes will make this error much less common. Instead, KEError 12243 should take its place most of the time (starting with version .410).
What you should do: Try the action again later. If you continue to have problems, contact RealFlight Support.
12243: [error text depends on the error]
App: Launcher, RealFlight
Cause: HTTP response with status code other than 200 OK. A number of different problems could lead to this error—too many to predict here. But the most likely cause is listed in the KEError 12228 description above.
What you should do: Try the action again later. If you continue to have problems, contact RealFlight Support.
16502: File copy error: [error text depends on the error]. Bytes read: [#], Bytes written: [#]. Make sure you have enough space on your hard drive.
App: Installer
Cause: In theory, any copy error during installation will cause this error, which includes a multitude of potential causes. In practice, it's usually caused by a bad CD. Test this by trying to copy the same file using Windows Explorer. If Windows can't copy the file, neither can the Installer.
What you should do: Contact RealFlight Support and tell them you suspect you received corrupted disks.
32494: Please contact technical support if the problem persists.
App: RealFlight
Cause: A problem has gone wrong while initializing the file system. As it turns out, in the current version of G3 this error will only occur when KEError 32495 occurs (see below).
What you should do: Contact RealFlight Support and tell them you suspect you received corrupted disks.
32495: You may need to reinstall. Please contact technical support if the problem persists.
App: RealFlight
Cause: One of the two main .DCKs (RFV3_1.dck or RFV3_2.dck) could not be found. If both files are present on disk, one of them is probably corrupt.
What you should do: Contact RealFlight Support and tell them you suspect you received corrupted disks.
12212: Unable to connect to server. Make sure you have access to the Internet (check firewall settings if applicable).
Description: [description text depends on cause of error]
App: Launcher
Cause: Most likely cause is no Internet connection, or a firewall preventing the app from establishing a socket connection to the server. This is the very first and most basic step in connecting to server to send/receive data. If it fails, it is probably a result of something on the user's end. If the Registration Server machine is completely down, that would also cause this error, but it cannot be caused simply by problems with the Registration Server app.
What you should do: Try the action again later. If you continue to have problems, contact RealFlight Support.
21023: Unable to register: Client/Server transaction failed.
App: Launcher
Cause: The online registration attempt has failed. This error will typically be preceded by another KEError in the 12000 range (such as 12212, described above). Therefore, in most cases it serves the function of telling us what action was being attempted when the previous error occurred, and as such doesn't have a cause of its own.
What you should do: Try the action again later. If you continue to have problems, contact RealFlight Support.
21039: Unable to obtain the latest available version number: server transaction failed.
App: Launcher
Cause: The Launcher needs to find out what the latest version available on the server is before it can perform updates. Like KEError 21023 (described above), this error will typically be preceded by another KEError in the 12000 range. Fixing that problem will fix this one.
There are three different times this error can occur:
1. When the user clicks "Update to Latest Version"
2. When the user clicks "Update to Specific Version"
3. When the Launcher performs its automated check on startup (this only happens when the "Check for updates before starting RealFlight" option is enabled)
What you should do: Try the action again later. If you continue to have problems, contact RealFlight Support.