There are multiple reasons why a controller does not appear in the web application. In most cases, one of the following may be the cause:

1. EDJAgent is not running on the controller.

Verify that the EDJGAZER:EDJAGENT.286 application is running in the background on the 4690.

2. EDJAgent is not properly configured to communicate with the StoreGazer Server.

Verify the Address in the EDJGAZER:EDJAGENT.CFG matches the IP address of system running the StoreGazer Server application.

3. The 4690 does not have a network route to the StoreGazer Server machine.

Verify connectivity exists by issuing a PING command on the 4690 to the IP address specified in the EDJAGENT.CFG

4. The StoreGazer Server is not running.

Launch StoreGazer’s “Server Manager” application on the server machine. Right-click the crystal ball icon in the system tray (near the clock) and choose Configuration. In the section titled “Service Control”, the “Start Service” button should be grayed out and the status should appear as “Listening”.

5. The StoreGazer Server does not have the correct database configuration.

Verify the database settings by clicking on the Configure Databases button in the StoreGazer Server Configuration dialog of the Server Manager application. Verify that the database names are properly specified (StoreGazerV2 on the left, EDJCommon on the right). Verify that connectivity to these databases exists by using the “Test Connection” buttons.

6. The StoreGazer Server is listening on a different port than the 4690 is attempting to connect to.

Verify the 4690 Data Port in the StoreGazer Server Configuration dialog of the Server Manager application matches the port number defined in the EDJGAZER:EDJAGENT.CFG file on the 4690 controller.

7. A firewall is preventing the StoreGazer Server from receiving data from the 4690 controller.

Verify connectivity by opening the Statistics window of the Server Manager application on the server. On the 4690 controller attempt to FTP or Telnet to the IP and port number defined in the EDJAGENT.CFG file.

FTP example:

C:>ftp 192.168.0.49 1235
Connected to 192.168.0.49.

Telnet example:

C:>telnet 192.168.0.49 1235
Trying…
Escape character is ‘^]’..

In both cases, the Connections section of the Statistics window should show an increase in both the “Currently In Progress” and “Completed” values.

8. The EDJCommon database is not properly installed.

Using a SQL client tool (either Microsoft SQL Server Management Studio, or the SQL Mode window in the StoreGazer Web application, run the following statement:

SELECT *
FROM EDJCommon..stores
LEFT JOIN EDJCommon..systems ON stores.store_id = systems.store_id
WHERE stores.name = ‘0001’ AND ISNULL(systems.node,”) IN (”,’CC’)

If the results come up empty, the database may not be installed properly.

9. The StoreGazer database is not properly installed.

Using a SQL client tool (either Microsoft SQL Server Management Studio, or the SQL Mode window in the StoreGazer Web application, run the following statement:

SELECT *
FROM StoreGazerV2..controllers
WHERE store = ‘0001’ AND node = ‘CC’

If the results come up empty, the StoreGazer database may not be installed properly.

10. The StoreGazer Web application does not have the correct database configuration.

Verify the database configuration in the StoreGazer Web application’s web.config file. Ensure the database connection settings match those in the StoreGazer Server database configuration. It may be possible that the server is putting data into one database, but the web application is looking at a different database.

For more information, review the StoreGazer Web application Configuration section (4.4) of the StoreGazer Version 4 Installation Guide.

11. The controller is not accessible to any users because it is not in the System Management tree.
Sign in to the EDJCommon Web application. Under System Management, click the company where the store should appear, and verify the store name is listed on the right-hand side. If the store has been moved to a group folder, verify the store exists in that group folder.

12. The controller is not accessible to a specific user due to access list restrictions.

Sign in to the EDJCommon Web application. Click the User Management icon on the left. Right-click on the user’s name on the right-hand side and choose Properties. Click the Access Lists button at the top and select StoreGazer from the drop-down list of Applications. Verify that the group containing the store (as discovered earlier) has either a green or gray checkmark next to it. If not, click Modify and select that store (or one of its parents) and click OK.

If, after exhausting these possibilities, the controller still does not appear, contact EDJ for additional support.