Support
Access-Control Door Will Not Unlock
Door Hardware
Summary
Follow the four stages below to diagnose a valid credential is presented but the controlled door does not release without losing evidence, configuration or device ownership.
Applies to
- Electric strikes, maglocks and gate relays
- Managed access-control doors
Difficulty and time
Difficulty: Advanced
Estimated time: 20 to 60 minutes
What you will need
- The exact model and current firmware or app version
- Administrator access where authorised
- A photo or screenshot of the current status
- One controlled test case and its exact time
What this guide covers
- Preserve and reproduce the fault
- Open the correct diagnostic screen
- Correct the proven cause
- Verify and document the result
Use this page when a valid credential is presented but the controlled door does not release. It includes the menu or screen to look for, the status that matters and a repeatable proof test.
Exact labels can differ between recorder, controller, app and firmware versions. If the named screen is not present, do not guess at destructive options; note the model and current version for support.
Before you start
Protect the current system and record a baseline before changing anything.
- Write down the exact symptom: reader beeps or grants access, but the strike, maglock or gate does not change state.
- Photograph the current status, error text, wiring or timeline as applicable.
- Record the last known working time and anything changed immediately before the fault.
- Photograph wiring and record relay/lock settings before changes; keep the approved door/fire design available.
Door locking and egress are safety-critical
Do not defeat request-to-exit, emergency release or fire interfaces. Electrical and locking work should be performed by appropriately qualified people.
If the required option is missing or the result does not match this guide, stop and identify the exact model before continuing.
What usually causes this
- Access level denies the credential
- Wrong door/relay is mapped
- Lock PSU or cabling failed
- Door/lock is mechanically binding
Step 1: Preserve the current state and reproduce the fault
Begin with a repeatable baseline so you know whether a later change genuinely helped.
- Reproduce the problem once and record: reader beeps or grants access, but the strike, maglock or gate does not change state.
- Note whether every device or user is affected, or only one.
- Compare one working path with the failing path if a comparison exists.
- Photograph wiring and record relay/lock settings before changes; keep the approved door/fire design available.
Step 2: Open the correct screen and inspect the evidence
The primary diagnostic location is Access-control client > Monitoring/Event Log > select door, then Door Parameters > Relay/Lock settings. Do not change anything until the displayed state is recorded.
- Open Access-control client > Monitoring/Event Log > select door, then Door Parameters > Relay/Lock settings. Menu wording can vary by model and firmware; use the nearest equivalent label.
- Observe whether the event log says Granted, Denied or no credential event.
- Use an authorised remote-open command and listen for controller relay operation.
- Have a licensed/competent person check lock power and voltage at rest/command, respecting fire/egress interfaces.
Step 3: Correct only the cause you proved
Use the matching correction below. Make one change, save it, then repeat the same test.
- If denied, correct credential, schedule or access-level configuration rather than lock wiring.
- If granted but no relay action, verify correct door/relay mapping and unlock duration.
- If relay changes but hardware does not, repair the lock power, cabling, suppression or lock hardware path.
- Correct fail-safe/fail-secure configuration only against the approved door and fire design.
Step 4: Verify, monitor and document the handover
A saved setting is not proof. Test the real outcome locally first, then test any app, cloud or client path separately.
- Test valid credential, invalid credential and authorised remote open.
- Confirm the door relocks and latches reliably.
- Operate request-to-exit and emergency/fire release paths as required by the site procedure.
- Confirm each event is logged with correct door and outcome.
Controlled support test
Situation: The reported symptom was: reader beeps or grants access, but the strike, maglock or gate does not change state.
Solution used: The current state was recorded in Access-control client > Monitoring/Event Log > select door, then Door Parameters > Relay/Lock settings, one matching correction was made, and the same test was repeated.
Why this was chosen: This separated the proven cause from unrelated settings.
Installation notes: The final screenshot and test time were saved with the handover record.
Official reference used for this guide
Menu names differ between releases. Confirm model-specific behaviour in Hikvision Access Control Terminal User Manual before firmware, reset, storage or security-sensitive work.
Common mistakes
- Changing several settings before repeating the original test.
- Using a factory reset, initialise or format option as an early troubleshooting step.
- Treating an app symptom as proof that the local hardware or recording has failed.
- Failing to record the model, version, exact error and test time before escalation.
- Assuming similar-looking models use identical menus or features.
Troubleshooting table
| Symptom | What to check | What to do next |
|---|---|---|
| reader beeps or grants access, but the strike, maglock or gate does not change state | credential denied, wrong relay mapping, failed lock power/cabling, incorrect fail-safe logic or mechanical binding | Open the named diagnostic screen, record the displayed state and use the matching correction above. |
| The named menu is not visible | Different firmware, permissions or model capability | Do not substitute a destructive menu. Capture the model and version and use its official manual. |
| The change saves but the fault remains | The selected cause was not the root cause | Undo the change if appropriate, return to the baseline and compare the failing path with a working one. |
| Local test works but app or client test fails | Account, permission, cloud or remote-network path | Keep the proven local configuration and diagnose the remote path separately. |
| Problem returns later | Intermittent power, cable, storage, network or schedule condition | Record the new failure time and status; correlate it with logs, events and the last known working interval. |
When to contact support
Contact SecurityWholesalers support when the log shows Granted but the correctly mapped relay or lock-power path does not operate, or any egress/fire behaviour is uncertain.
Send the order number if available, exact model, firmware or app version, screenshot of Access-control client > Monitoring/Event Log > select door, then Door Parameters > Relay/Lock settings, the failure time, and the result of the local proof test.
Related support guides
- Access Control Support Guides - Browse every guide in this support area.
- All Technical Support Guides - Return to the complete support library.
Related buying guides
- Access Control Buying Guide - Door hardware, credentials and system-planning guide.
Relevant product categories
- Access Control Products - Controllers, readers, locks and credentials.
- Door Strikes - Electric strike hardware.
- Maglocks - Electromagnetic locking hardware.
Still stuck?
Need help choosing or setting up a system? Contact SecurityWholesalers support with your order number, product model and a clear description of the issue.
Frequently asked questions
-
Where should I click first for access control door not unlocking?
Start at Access-control client > Monitoring/Event Log > select door, then Door Parameters > Relay/Lock settings. Record the existing state before changing it because labels and available options can vary by model and firmware.
-
What should I look for on that screen?
Look for Granted versus Denied, the reason code, correct door/relay, unlock duration and door contact transition.
-
What must I avoid changing during the first check?
Do not defeat request-to-exit, emergency release or fire interfaces. Electrical and locking work should be performed by appropriately qualified people.
-
How do I prove the correction worked?
Run valid, invalid, remote-open and safe-egress tests and confirm the door unlocks, relocks and logs each outcome.
-
Why might my menu names look different?
Recorder, controller, camera, app and firmware releases can use different labels. Use the closest equivalent only when its function is clear; otherwise record the model and version for support.
-
Should I factory-reset the device?
Not as an early step. A reset may erase users, network settings, recording configuration, licences or cloud ownership. Back up the configuration and confirm the recovery plan first.
-
What should I send technical support?
Send the exact model and version, screenshot of Access-control client > Monitoring/Event Log > select door, then Door Parameters > Relay/Lock settings, exact error text, failure time, what changed before the fault and the result of the controlled local test.
-
Can configuration changes recover data or events that were never recorded?
No. A correction can restore future operation, but it cannot recreate footage, alarm events or access transactions that were never stored.