What is the cause of the denied access ‘Reader not allowed’

When access is denied with the denied reason 'Reader not allowed' , various possible causes may explain the denial:

• 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.

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.