Question:
Why aren’t keys made in Community synching with Aurora/Keyscan?
Answer:
Please refer to the steps below for this error.
Steps:
- Make sure the Aurora server in Community is set to the right IP or localhost.
- In Advanced Settings/Enable AuroraSync Interface
- Click the blue "Test Connection" button to test the connection.
- Verify that the following services should be running in local Windows Services:
- Keyscan Aurora Agent
- Keyscan Aurora Communications
- Community AuroraSync
- . If they are not running, please start them by right-clicking on them in the local Windows Services and selecting "Start".
- Verify that there are no more than 10 groups in Keyscan Aurora.
- If there are more than 10, deactivate the excess groups.
- Double-check the user/pw they’re using in the Aurora Interface section of Community.
- This password should be the same as the Master access in Keyscan Aurora.
- Verify it works with Keyscan Aurora by logging into Keyscan Aurora using it.
- If a new password was created for Keyscan Aurora, logging in finishes the process. It isn’t a valid login until you log into Aurora with it. Remember, the wrong password can give a false positive when you test the connection.
- This password should be the same as the Master access in Keyscan Aurora.
- There should be two Common Area Access groups set up in the Community software: one for Resident Common, and one for Staff Common.
- The Keyscan Groups should be visible in those groups, set to either Auto or Selectable, as desired.
- Make sure the keys are also all checked in the adjacent tab (Credentials)
- You can only have 2 users logged into Keyscan Aurora at one time, and the Community login counts as 1 of them.
If issues persist, please get in touch with Dormakaba MultiHousing Technical Support at 800-849-8324, Options 1, then 3, then 1.
Additional information
Applies to: Community Server installations integrating with Aurora software by Keyscan.