What is the cause of the Denied Access...

What is the cause of the Denied Access... 

Denied Access : ‘Not Authorized at this time’

When access is denied with the denied reason 'Not Authorized at this time' , various possible causes may explain the denial:

In the definition of the cardholder Access group, this reader may have a weekly program which is in red period at that time

→ Check the weekly program of this reader in the corresponding Access group screen.

In the definition of the cardholder Access group, this reader may have a crisis level lower than the actual crisis level of the site

→ Compare the crisis level of this reader in the corresponding Access group screen with the actual crisis level defined in the Manual action>Crisis level screen.

The current date is defined as a holiday 

→ Check in the Holiday screen if the day is a Holiday or a Special day.

Denied Access : 'Non Allocated Badge'

Access with the label 'Non Allocated Badge' is generated when the corresponding card has never been downloaded to the corresponding controller but its record is present in the database. 

→ Make sure that the corresponding card is allocated to a cardholder in the Badge screen.

→ Check that the reader and the card have the same defined technology on the software.

→ Check that the corresponding reader is included in the Access group of the cardholder.

Denied Access : 'Unknown Card'

Access with the label 'Unknown Card' is generated when the corresponding card has never been downloaded to the corresponding controller. 

→ Check the reader format is compatible with the existing card codes in the Reader>Badge format screen. 

→ Check that the corresponding reader is cabled in the same way as other readers.

→ Check that the reader and the card have the same defined technology on the software.

→ Check that the corresponding reader is included in the Access group of the cardholder.

Denied Access : 'Supervisor'Access denied with the denied reason 'Supervisor' , is generated when transaction codes from 20 to 29 are sent. 

→ The transaction codes from 20 to 29 are reserved for the system use and cannot be used by cardholders. 

When access is denied with the denied reason 'Full/Lock/No answer from Door' , various possible causes may explain the denial:

If the controller is defined as Parking controller on the software, the parking may be full.

→ Check the actual free places of the corresponding parking zone in the Modules>Parking Zone screen.

The reader may be defined on ‘Door closed’ mode on the software.

→ Check if the "Door Closed" option is set on both Security levels of the corresponding reader in the Reader>Access mode screen.

The door relay may have a weekly program which is in red period or may be disabled by a global reflex.

→ Check if the "Door Relay" has a weekly program or the "Input group status indication" option in the Output screen of the corresponding relay.

The reader may have the 'Feedback' option and the cardholder has passed his badge without opening the door. 

→ Check if the "Feedback" option is set in the Reader>Door control screen of the corresponding reader.

→ Check in the Report Wizard of the software how the access has been denied.

The reader may be an Alarm Keypad and the cardholder who wishes to access is not defined as ‘Supervisor’.

 → Check if the reader is linked to an Input Group in the Reader>Misc. screen of the corresponding reader and if the cardholder has the "Supervisor" option in the Cardholders>Personal screen.

• Cardholder Access group may not include this reader

→ Check in the Access group of the corresponding cardholder if this reader is included (V green).

• The current date is defined as a holiday 

→ Check in the Holiday screen if the day is a holiday and if the corresponding cardholder has the option "No access during holidays" marked on the cardholders screen.

• The controller firmware date is from 18/06/06

→ There was a bug in the firmware from 18/06/06. It was fixed in version from 11/12/06.

Denied access ‘Inhibited Cardholder’ 

Access denied with the denied reason 'Inhibited Cardholder' , is generated when the corresponding reader has the weekly program "<Use Personal WP>" in the access group of the cardholder and when this cardholder does not have any Personal weekly program.

→ Check if the weekly program of this reader in the corresponding Access group screen is set on "<Use Personal WP>".

→ Make sure that the corresponding cardholder has any "Personal weekly program" selected in the Cardholders screen. 

Troubleshooting steps:

→ Try a similar cardholder with the same definitions as the denied one to see if the problem reproduced.

→ Check that the 'Re-sending card definitions after "denied" event' option is set in Tools>Options>Server (if not, set the option and restart the application) and pass the card twice, wait 3-4 seconds between the passes.

→ If the previous step did not help, initialize the controller.

→ If the problem persists use the Report Wizard to check the following:

1. when this person accessed to this reader for last time

2. if that person has been denied on other readers

3. if other people accessed to the same reader at the same time

4. if recent changes have been done in the database on: the cardholder, his/her access group, the reader

5. if communication problems have occurred recently on this controller.

If case you want to report the problem to us:

Go to Tools>Options>Journal and set the option "Show commands for information", restart the application and note the command that is sent when this person is downloaded. Send this info to our technical support along with the main DB and the Journal. Specify the reader name, the cardholder name and the time and date when access was denied.