Error -10002

This error message means that the Genie Client application cannot see the Genie Server application on the Server computer. Typically you will get this message when trying to log in.

Click OK and the Connection to 4D Server window will appear as below

This window displays recently used databases. Although it shows Genie in this window, this doesn't mean that Genie Client can actually see Genie Server. It simply means that Genie has been accessed previously. That is, this window will always display Genie, regardless of whether the Server is running or not.

To determine whether Genie Client can actually see Genie Server, you must click on the TCP/IP tab in this window.

If Genie is displayed in this window, it means that the IP address of the Server has changed since last log on. In this case you can log on simply by clicking on Genie, then click OK.

If this window does not display Genie, then it means that Genie Client cannot see or connect to Genie Server.

The most common causes of this problem are:

1. Genie Server isn't running.

2. Genie Server hasn't fully launched, usually because there is a dialog box asking you to select a data file to open.

3. Genie Server is currently performing a backup.

4. Genie Server has frozen or crashed.

5. The Hub or Switch is "jammed". This can sometimes occur after a power failure.

6. There is a loose Ethernet cable between the Client machine and the Server.

7. The IP address of the Client or Server computers have been changed so that they are no longer in the same subnet or IP range.

8. You have an active Firewall on one or both of the computers.

To determine the cause of the connection failure, you should perform the following diagnostic steps. Please perform these checks prior to calling the Genie support line.

Check Your Server

Go to the Server computer. Make sure it is running. Make sure Genie Server is running and fully opened. You should be able to see the Genie Server process window as shown below.

In this window make sure that you can see that the data file is the correct one i.e. it should just read Genie.4DD

Make sure there are no other dialog windows open. For example if your data file had been renamed, Genie Server will be asking you to select a data file to open.

Check the Backup Scheduler to ensure that a backup isn't currently occurring. "Backup in Progress" would be visible at the bottom of the Genie Server window.

Click on the File menu to make sure that it is active and that Genie Server hasn't frozen.

If you haven't solved the problem yet, then the problem lies with your network. Either there is a faulty physical connection (cable or hub), or a problem with the computers network settings.

QUESTION: Is it only one client computer that is unable to log in?

If so, then the problem is probably with the ethernet cable or the network settings of just this computer. If none of the Clients can log in, then the problem is probably with the hub, the ethernet cable attached to the Server, or the network settings on the Server computer.

You should physically remove and then reinsert the ethernet cable from the computer and the hub. Make sure that the hub has power i.e. there are flashing green lights visible. Try removing the power from the hub, quit Genie Server and turn all computers off. Wait 30 seconds, then return power to the hub, start the Server and start the other computers on the network.

If you still cant log in with Genie Client, then you need to check the IP Addresses and the Subnet mask for the Server and the Clients.

IP Addresses

To find the IP Address of a computer see Discovering Your IP Address for either Windows or Macintosh.

The IP Address should usually be set to something like 192.168.0.x, where x can be any number between 1 and 255. Each computer on the network must all have a unique IP Address, but they must all start with the same three numbers, i.e. 192.168.0.

Wireless networks traditionally use an IP Address in the 10.0.0.x range.

The Subnet mask is usually 255.255.255.0.

The IP Address can either be set manually or be automatically assigned from other computer or router.

Pinging

Once you are sure that the IP Addresses for the computers are set correctly, you can test the actual network by "pinging" other computers on the network. Pinging sends "packets" of data to the IP Address of another machine and then waits for a reply from that machine to tell it that the packet arrived.

The ping test should be done on the client which is unable to login. See Ping Testing the Network for either Windows or Macintosh.

If you receive a reply then the client computer can see the server. Otherwise, you will get a message saying that the packets were lost. If this is the case, then you need to double check the physical connections i.e. the ethernet cables and hub.

Connecting Manually

If you can ping the server successfully but still cannot access Genie on the server, you can try to connect manually. To do this, click on the Custom tab of the Connection to 4D Server window.

In the Database Name field, enter Genie.4DC.

In the Network Address field, enter the IP address of the server computer. To find the IP address of your server perform the Discovering your IP Address instructions on your server machine.

If it still cannot connect to Genie Server, then the most likely problem is that a Firewall has recently been installed or activated on one of these computers.

Firewalls

Norton's Internet Security/Norton Antivirus is a common software package in use on Windows. If you have recently installed this, or have other firewall software installed, you should try disabling it.

The Windows XP inbuilt firewall is also known to prevent login. This MUST be disabled or an exception set for Genie Client.

To do this go to Start > Control Panel > Security Centre > Windows Firewall. You can either set it to Off or click the Exceptions tab and add Genie Client as an exception using the Add Program... button.

Faulty Hardware

If you are still unable to log in with Genie Client, then the problem is probably one of the following:

1. A faulty hub. You may need to get a replacement.

2. A faulty cable on the client or server machine. If you can't login from any client, then try replacing the ethernet cable attached to the server with a cable from one of the client computers. If only one client is able to log in, try replacing the cable attached to this computer with a cable from another client.

3. A faulty ethernet card. If none of the clients can login then it is the server's card that needs replacing, otherwise it's the client's computers card.

In this case you need to contact your hardware/network administrator to resolve the problem.