How To: Restart the Application

Restarting the GateKeeper application is a common first step when troubleshooting. The application reloads all settings and reconnects to hardware when it starts.

---

Step 1: Close the running application

Method A: Close normally

1. Click the X button in the top-right corner of the application window.
2. Expected: The application closes within a few seconds.

Method B: Force close (if the application is frozen)

1. Press Ctrl+Shift+Esc to open Task Manager.
2. Find AbeTech.GateKeeper.Conveyor.WinForm in the process list.
3. Click on it to select it.
4. Click End Task.
5. Expected: The process disappears from the list.

If the process does not end, click End Task again or right-click and select End Process Tree.

---

Step 2: Wait a few seconds

Wait about 5 seconds before restarting. This allows: - Network ports to be released - Serial port connections to close - File handles to be freed

---

Step 3: Start the application

Method A: Desktop shortcut

1. Double-click the GateKeeper Conveyor shortcut on the desktop.
2. Expected: The application window appears.

Method B: Direct launch

1. Open File Explorer and navigate to C:\gatekeeper\conveyor\
2. Double-click AbeTech.GateKeeper.Conveyor.WinForm.exe
3. Expected: The application window appears.

Tip: If the application requires Administrator privileges, right-click and select Run as Administrator.

---

Step 4: Verify startup

After the application starts:

1. Check for error messages: If an error dialog appears, note the message. See Application Errors.
2. Check hardware connections: Open the Diagnostics panel and verify all devices show "Connected." See Verify Hardware Status.
3. Check validation mode: Verify the correct validation mode is selected.
4. Turn validation ON if needed (or wait for auto-start if configured).

---

Step 5: Check the log

If the application started but something seems wrong:

1. Open C:\gatekeeper\conveyor\logs\gatekeeper-YYYYMMDD.log (use today's date).
2. Scroll to the bottom and look for recent startup messages.
3. Look for [ERR] entries that may indicate a problem.

---

When restarting is NOT enough

If the problem persists after restarting:

• Hardware still disconnected: The hardware itself may have an issue. See Hardware Disconnected.
• Same error reappears: The problem may be in the configuration. See Verify Configuration.
• Application won't start at all: See Application Errors.

---

Teasdale: Job state after restart

For Teasdale sites, if a job was in progress when the application was closed:

• If AutoStartValidation is true: The application will automatically resume the paused job on startup.
• If AutoStartValidation is false: A "Resume Job" button will appear. Click it to continue the paused job.
• The state file is stored at C:\gatekeeper\conveyor\data\teasdale_job_state.json.
• If the state file is corrupted and the application will not start correctly, delete the state file and restart. The current job progress will be lost.