If crond is not running the dataskq program correctly, it has to do with the system account for 'diradmin' expiring (this is rare).
You can type
[root@server]# chage -l diradmin Minimum: 0 Maximum: 99999 Warning: 7 Inactive: -1 Last Change: Apr 04, 2003 Password Expires: Never Password Inactive: Never Account Expires: Never
to see the current status.
If it looks more like this:
[root@server]# chage -l diradmin Minimum: -1 Maximum: -1 Warning: -1 Inactive: -1 Last Change: Nov 08, 2005 Password Expires: Never Password Inactive: Never Account Expires: Never
Then you'll need to run:
[root@server]# chage -m 0 -M 99999 -W 7 diradmin
I've heard other reports that it's an issue with AuthPAM