Troubleshooting
The following is a list of problems, error codes and possible solutions that have been encountered when setting up Keytrade Pro Lux:
Connection Errors
| Error Message | Possible Causes/Solutions |
|---|---|
|
Could not communicate to the network server, error 3 – 407 proxy authentication required. Error code 0, no bytes received. Timeout error code 0X80040002. |
Problems communicating with Keytrade Lux's servers due to firewall/proxy problems.
|
|
Time out waiting for Proxy reply, error code 0x80040011. |
Problems communicating with Keytrade Lux's servers due to firewall/proxy problems.
|
|
Illegal Client ID: Error Code: 0x80040009. |
The User ID is not recognised by the login server (you cannot be authenticated).
|
|
Illegal Host Name 11001. |
Keytrade Pro Lux cannot connect to Keytrade Lux's server.
|
|
Could not create socket 10047. |
The PC is using an old version of Windows 95 Winsock – upgrade Winsock to the latest version. |
|
Illegal password: Error Code 0x8004000b. |
A wrong password has been entered.
|
|
You are currently logged in from IP address x.x.x.x Please close that connection before retrying to connect: Error Code: 0x8004000b. |
You are attempting to open Keytrade Pro Lux (log into an account) twice.
|
Key Errors
| Error Message | Possible Causes/Solutions |
|---|---|
|
0x8009005 – Could not decrypt session key, Key mismatch. |
Keytrade Pro Lux cannot read the key correctly because:
|
|
Key not been received by Keytrade Lux. |
The new key generated by Keytrade Pro Lux was not transmitted correctly to Keytrade Lux. Use the following procedure to regenerate the key and transmit it to Keytrade Lux:
|
|
Could not restore key from floppy, Error code: 08009004. |
Could not import the encryption key from Keytrade Pro Lux on one PC to another because of different encryption levels used by the two Keytrade Pro Lux. Use the following procedure to correct the problem:
|
|
Could not restore key. |
Could not load the encryption key into Keytrade Pro Lux. Use the following procedure to correct the problem:
If this does not work, on the PC receiving the key:
|
General Application Errors
| Error Message | Possible Causes/Solutions |
|---|---|
|
A newer version of this application is on the server. Please re-download this installation. |
Attempting to install Keytrade Pro Lux from an old installation file that is not longer valid. Download and install Keytrade Pro Lux again from Keytrade Lux web site. |
|
Connection Wrapper :: INIT OBJECT class not registered, Keytrade Pro Lux failed to initialise connection object. |
This can occur during upgrade of Keytrade Pro Lux. Some files have not been registered. Reinstall Keytrade Pro Lux. |
|
Getting the upgrade message repeatedly when logging into Keytrade Pro Lux. |
Keytrade Pro Lux is not being upgraded correctly. This is possibly caused by an intermediate proxy server caching old upgrade files and sending them to Keytrade Pro Lux instead of newer upgrade files.
|
|
CFD Module receives no price updates. |
If CFD trading should be allowed in the client's account:
|
|
Forex Trade module not not available in Trading > Forex menu. |
Contact a Keytrade Lux representative to ensure that both the Forex and CFD trading are enable for the client. |
|
Could not view the ,000 in the amount on the Forex Trading bar. |
The PC running Keytrade Pro Lux is running non-compatible regional settings. Change the regional settings of the PC to use your preferred digit separators and decimal symbols:
|
|
Operation return code = regdb_e_class not read (80040154). |
Keytrade Pro Lux is not registered correctly in the PCs operating system – reinstall Keytrade Pro Lux. |
|
Summary module – Sorry you aren't entitled to use this function. |
Use the following procedure to rectify the problem:
|
|
Trade Recaps : The following error was reported while trying to connect to Actuate e.Reporting Server "rep1pro":HTTP error code 401, Description:Illegal password. |
Client has changed password in Keytrade Pro Lux, and the new password has not synchronised with the Recaps System. Refer the case to Keytrade Lux for further investigation. |




