I’ve never actually seen this happen before - other than specific deny entries in /etc/cron.deny… But this is UNIX behaviour, not sure if it applies to Linux…
“man crontab” says the following :
If the /etc/cron.allow file exists, then you must be listed (one user
per line) therein in order to be allowed to use this command. If the
/etc/cron.allow file does not exist but the /etc/cron.deny file does
exist, then you must not be listed in the /etc/cron.deny file in order
to use this command.
Extending the hints given by @daniel.m.tripp , I would start with issuing these commands:
ls -al /etc/cron.allow >/dev/null 2>&1 && echo "cron.allow exists." || echo "cron.allow does not exist."
ls -al /etc/cron.deny >/dev/null 2>&1 && echo "cron.deny exists." || echo "cron.deny does not exist."
Depending on the results you will see if there are these files in the first place. If both are not there, you might have a different problem that you need to find the cause of.
(Issue them as the root user, because I’m not sure of the file permissions for these.)