Reset the Key Interface for Lightspeed and Visionline

ℹ️ 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. This takes about 5 minutes and resolves the issue most of the time.

🔑 When to Use This

Run through this procedure when:

• You're trying to make a key in Lightspeed and it 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 with Visionline or the encoder itself — not the interface. Call Visionline / ASSA ABLOY support instead.

⚠️ Who Can Do This

🛑 You need Galaxy access to perform this fix. An untrained user can do significant damage to property systems through this tool. Do not use someone else's login. Submit a ticket and we'll either resolve the issue for you or grant access if your role warrants it.

📋 Before You Start

1. Run a standalone Visionline test first. Make a test key directly in Visionline. If that works, this article will fix the problem. If it doesn't, the issue is with Visionline itself, not the interface.
2. Let front desk know. No keys can be made from Lightspeed for about 5 minutes during the restart. Front desk should hold off on check-ins.
3. Be at the workstation that runs Galaxy — usually the property's PMS workstation or designated admin machine.

🛠️ The Procedure

Step 1: Sign in to Galaxy

Open Galaxy and sign in. You'll arrive at the main menu.

Step 2: Navigate to the GSII Interface Menu

Galaxy uses a number-based menu. At each prompt, type the number and press Enter.

From the main menu, type 14 to enter the Database Maintenance Menu, then work down through these menus:

Database Maintenance Menu — enter 36 (System Admin Menu):

System Administration Menu — enter 3 (Interface Administration Menu):

Interface Administration — enter 1 (GSI Interfaces):

GSI Interface Administration — enter 3 (GSII Interfaces):

💡 Note: The interface is GSII (Roman numeral "two"), not "GSI1". This is the menu you want for Visionline.

Step 3: Stop the Interfaces

You should now see the GSII Interface Menu showing both interfaces running.

Enter action 2 (Stop Interfaces):

Then enter action 1 (Stop All):

Enter your initials, then type reboot as the reason:

💡 Galaxy logs every stop and start — who did it and why. Use your own initials and reboot as a consistent reason.

Wait a minute or two. Once both interfaces show Down, enter Q (Quit) to return to the previous menu:

Step 4: Start the Interfaces

You're back at the GSII Interface Menu with both interfaces showing Down.

Enter action 1 (Start Interfaces):

Then enter action 1 (Start All), enter your initials, and type reboot for the reason:

Step 5: Wait Through the Startup Messages

You'll see startup output that looks alarming — error lines and "Waiting for Server Ready" notices:

⚠️ This output looks worse than it is. The error lines are normal during startup. Watch for the success confirmation line. Don't intervene — let it run.

Wait the full startup cycle (a few minutes). Once it settles, both interfaces should change to Running.

Step 6: Test From Lightspeed

Once both interfaces show Running, go to Lightspeed and try to make a test key. If it works, you're 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 is still working standalone. If Visionline has stopped working too, that's now the problem.
3. Call Lightspeed support. If both ends look healthy but keys still won't go through, this is beyond the interface.
4. Submit an Argus IT ticket if you're not sure what to do next.

🆘 When to Submit a Ticket

Submit a ticket if:

• You don't have Galaxy access and need this restarted on your behalf.
• The procedure didn't fix the problem.
• The interfaces won't start (they keep failing back to stopped).
• You're seeing unusual error messages you don't recognize.

Please include:

• Which property the issue is at.
• Whether Visionline standalone works.
• Any error messages from Galaxy or Lightspeed — screenshots are ideal.
• Time the issue started if you know it.

Related Articles

• The Basics to Try When You Have a Problem (KB# 10001)
• How to Fill Out a Ticket (KB# 10002)

ArgusIT KB# 60003 | Original: November 7, 2019 | Revised: March 3, 2020 | Rebuilt: May 25, 2026

Tags: galaxy, keys, visionline, lightspeed, interface, GSII