I too have this problem and cannot do anything to get it resolved. Yours is the only post I’ve found that lists the issue. Happened after I ran the upgrade scripts to .17 from the sysadminpro module. After it completed, sysadmin was disabled and I could not upgrade/enable it.
I found the solution to my own problem. I hope this helps you:
I was able to resolve it by doing the following from an SSH CLI session logged in as root:
1.) I attempted to manually enable sysadmin and was unsuccessful ( amportal a ma enable sysadmin)
2.) I was unable to delete sysadmin because of dependencies (amportal a ma -f delete sysadmin)
3.) I decided to remove all modules to eliminate the dependency problems. This worked, with some errors. (amportal a ma deleteall)
4.) I then reinstalled all modules. This worked, with some dependency failures (amportal a ma installall)
5.) I then was able to log back into the web GUI and update/install all failed modules from the module admin page. This worked without any errors. All settings remained intact, and the updated version of Sysadmin was installed and functional.
The process you detail above is exactly what I did on my system (deleteall and installall). Everything worked after that, except that I couldn’t install the sysadmin module again. I can download it but when trying to install it I get the error that references the crontab entry.
I’m not sure what the error means, but I did notice that a fully upgraded system was necessary to reinstall an updated sysadmin. I’d first try reinstalling all modules from the module admin page (make sure you’re including the extended modules, as some of your old PBX settings likely depend on them), and make sure your framework is up to date. I hope this helps,
Thanks for the hint. When I ran the crontab command it didn’t work. After looking at the issue a bit closer I found that Crontab was no longer installed on my system for some odd reason. Not sure if the upgrade messed something up or what. What I ended up doing was just installing Crontab again using ‘yum install crontabs’
Very strange, the Crontab command and packages were missing from my system but all my cron jobs were still there.
After installing Crontab I was able to install the sysadmin module without any issue.