To assist in resolving an issue, the EDJ support team may request that debug logs be sent.  These logs often provide error messages or other information that can quickly lead to determining the cause of the issue and provide direction in resolving that issue.

EDJAgent Debug Log (EDJGAZER:LOGEDJAGENT.LOG)

To create this log, perform the following steps on the 4690 controller:

  1. Open the EDJGAZER:EDJAGENT.CFG file in a text editor (DREDIX, XE, etc.)
  2. Add the line “Debug=MAX”.  This line is not case-sensitive, and spaces around the “=” are ignored.  If there is already a “Debug=” line in the file, make sure it is not commented out (commented lines begin with “#”), and that the value is set to MAX.
  3. Restart the EDJGAZER:EDJAGENT.286 background process.
  4. Reproduce the problem, if necessary.  If the problem is occurring during startup, allow the process to run for at least 15 minutes.
  5. Edit the EDJAGENT.CFG file again to remove (or comment out) the “Debug=” line.
  6. Restart the background process again.

EDJServer Debug Log (EDJGAZER:LOGEDJSERVR.LOG)

To create this log, perform the following steps on the 4690 controller:

  1. Open (or create) the EDJGAZER:EDJSERVR.CFG file in a text editor (DREDIX, XE, etc.)
  2. Add the line “Debug=MAX”.  This line is not case-sensitive, and spaces around the “=” are ignored.  If there is already a “Debug=” line in the file, make sure it is not commented out (commented lines begin with “#”), and that the value is set to MAX.
  3. Reproduce the problem, if necessary.  If the problem is occurring during startup, allow the process to run for at least 15 minutes.
  4. Edit the EDJSERVR.CFG file again to remove (or comment out) the “Debug=” line.

EDJAgent Memory Dump (EDJGAZER:LOGSGDUMP.DAT)

To create this log, perform the following steps in the StoreGazer Web application:

  1. Load the Multi-Store Operations page.
  2. Select the EDJAgent request type.
  3. Select the “EDJAgent Memory Dump” option and click “Next”.
  4. Select the location(s) that should generate this log and click “Next”.
  5. Click “Execute” to instruct the selected location(s) to generate the log.

StoreGazer Server Debug Log (StoreGazerServerV2.log)

To create this log, perform the following steps on the StoreGazer Server system:

  1. Load the StoreGazer “Server Manager” application.
  2. Right-click the crystal ball icon in the system tray (near the clock) and choose Configuration.
  3. In the drop-down for “Debug Level”, choose DEBUG.
  4. Click the Save button.
  5. Reproduce the problem, if necessary.  If the problem is not reproducible on demand, allow the program to run in this state for anywhere between 15 minutes and 8 hours, depending on how long it takes for the problem to present itself.
  6. Repeat steps 2-4, changing the debug level back to WARN.

StoreGazer Web Application Debug Log (EDJ.StoreGazer.Web.Client.log)

To create this log, perform the following steps on the StoreGazer Web server.

  1. Open the “EDJ.StoreGazer.Web.Client.dll.log4net” file in a text editor.  This file is located in the folder where the StoreGazer Web application was installed.
  2. Locate any lines that say .  Change INFO to DEBUG.
  3. Make sure there is a folder named “logs” in the same location as this .log4net file.  If there isn’t, create one and grant the IIS_IUSRS group write access to the folder.
  4. Reproduce the problem, if necessary.
  5. Repeat steps 1-2, changing the levels back to INFO.