Remember to check the Knowledge Base for a solution before you enter a new ticket.

Reset Key Interface for Lightspeed

Creation date: 5/28/2026 1:08 PM    Updated: 7/27/2026 8:47 AM
Argus IT Help Desk · Lightspeed
Reset the Key Interface for Lightspeed and Visionline
When Lightspeed won't make room keys, a 5-minute interface restart fixes it most of the time.
Use this article when Lightspeed won't make room keys. The fix is almost always to stop and restart the interfaces between Lightspeed and Visionline using Galaxy — about 5 minutes.
🔑  When to use this
  • Making a key in Lightspeed fails or hangs.
  • Lightspeed says the key was made, but the lock won't accept it.
  • The Visionline encoder works fine when tested directly, but Lightspeed-to-Visionline keys aren't going through.
💡 If keys also fail when made directly in Visionline standalone, the problem is Visionline or the encoder — not the interface. Call Visionline / ASSA ABLOY support instead.
You need Galaxy access to do this
An untrained user can do significant damage to property systems through this tool. Do not use someone else's login. No access? Submit a ticket — we'll either resolve it for you or grant access if your role warrants it.
📋  Before you start
1
Run a standalone Visionline test. Make a test key directly in Visionline. Works = this article will fix it. Fails = the issue is Visionline itself.
2
Let front desk know — no keys can be made from Lightspeed for ~5 minutes; hold check-ins.
3
Be at the workstation that runs Galaxy — usually the property's PMS or designated admin machine.
🛠️  The procedure
Step 1 — Sign in to Galaxy. You'll arrive at the main menu. Galaxy uses number-based menus: type the number, press Enter.
Step 2 — Navigate to the GSII Interface Menu. From the main menu type 14 (Database Maintenance Menu), then:
Database Maintenance Menu → 36 (System Admin Menu)
Database Maintenance Menu
System Administration Menu → 3 (Interface Administration Menu)
System Administration Menu
Interface Administration → 1 (GSI Interfaces)
Interface Administration
GSI Interface Administration → 3 (GSII Interfaces)

💡 The interface is GSII (Roman numeral two), not "GSI1" — that's the menu you want for Visionline.
Step 3 — Stop the interfaces. At the GSII Interface Menu (both interfaces running): enter action 2 (Stop Interfaces)
Stop Interfaces
then action 1 (Stop All)
Stop All
Enter your initials, then type reboot as the reason.
Initials and reason
Galaxy logs every stop/start — who and why. Use your own initials and "reboot" as a consistent reason. Wait a minute or two; once both interfaces show Down, enter Q to return to the previous menu.
Interfaces down
Step 4 — Start the interfaces. Back at the GSII menu: action 1 (Start Interfaces)
Start Interfaces
then action 1 (Start All), your initials, and reboot as the reason.
Start All
Step 5 — Wait through the startup messages. You'll see output that looks alarming — error lines and "Waiting for Server Ready" notices:
Startup output
This output looks worse than it is
The error lines are normal during startup. Watch for the success confirmation line and don't intervene — let it run. After a few minutes both interfaces should change to Running.
Step 6 — Test from Lightspeed. Both interfaces Running? Make a test key from Lightspeed. Works = done; let front desk know.
🔄  If this doesn't work
1
Repeat the stop and start once more — occasionally an interface needs a second cycle.
2
Confirm Visionline still works standalone. If it's stopped too, that's now the problem.
3
Call Lightspeed support if both ends look healthy but keys still won't go through.
4
Submit an Argus IT ticket if you're not sure what to do next.
🆘  When to submit a ticket
No Galaxy access and need this restarted · the procedure didn't fix it · interfaces won't start (keep failing back to stopped) · unfamiliar errors. Include: which property · whether Visionline standalone works · error messages/screenshots · when the issue started.
ArgusIT KB# 60003 · Tags: galaxy · keys · visionline · lightspeed · gsii