if you are looking for the problem that crontab -e wouldn't work on solaris, here is the article for it.
I got really puzzled when I first met the probem. On linux/UNIX, it never be a problem.
The reason is that cron reads /var/spool/cron/crontabs for all users when it starts, but won't read it after start unless you explicitly tell it do so.
So, solution one, restart cron process
svcadm restart cron
or svcadmin disable cron
then svcadmin enable cron
Solution two, force crontab read the crontab file.
crontab -l >cronfile
this way, new cronfile will be read by cron, thus your new job will run.
Solution three, send a HUP signal to cron
kill -1 <PID of cron>