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.
Comments
0 comments
Please sign in to leave a comment.