jarvis cfds Troubleshooting
The following is a list of problems, error codes and possible solutions that have been encountered when setting up jarvis cfds:
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 Jarvis Invesment Management plc's servers due to firewall/proxy problems.
|
|
Time out waiting for Proxy reply, error code 0x80040011. |
Problems communicating with Jarvis Invesment Management plc'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. |
jarvis cfds cannot connect to Jarvis Invesment Management plc'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 jarvis cfds (log into an account) twice.
|
Key Errors
| Error Message | Possible Causes/Solutions |
|---|---|
|
0x8009005 – Could not decrypt session key, Key mismatch. |
jarvis cfds cannot read the key correctly because:
|
|
Key not been received by Jarvis Invesment Management plc. |
The new key generated by jarvis cfds was not transmitted correctly to Jarvis Invesment Management plc. Use the following procedure to regenerate the key and transmit it to Jarvis Invesment Management plc:
|
|
Could not restore key from floppy, Error code: 08009004. |
Could not import the encryption key from jarvis cfds on one PC to another because of different encryption levels used by the two jarvis cfds. Use the following procedure to correct the problem:
|
|
Could not restore key. |
Could not load the encryption key into jarvis cfds. 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 jarvis cfds from an old installation file that is not longer valid. Download and install jarvis cfds again from Jarvis Invesment Management plc web site. |
|
Connection Wrapper :: INIT OBJECT class not registered, jarvis cfds failed to initialise connection object. |
This can occur during upgrade of jarvis cfds. Some files have not been registered. Reinstall jarvis cfds. |
|
Getting the upgrade message repeatedly when logging into jarvis cfds. |
jarvis cfds is not being upgraded correctly. This is possibly caused by an intermediate proxy server caching old upgrade files and sending them to jarvis cfds 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 Jarvis Invesment Management plc 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 jarvis cfds 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). |
jarvis cfds is not registered correctly in the PCs operating system – reinstall jarvis cfds. |
|
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 jarvis cfds, and the new password has not synchronised with the Recaps System. Refer the case to Jarvis Invesment Management plc for further investigation. |