You don' t need to run any of those commands manually after logging in because logging in runs those commands automatically before you see your first shell prompt. But, when you run a job with cron you don't login and your script has to do whatever it takes to create an environment in which the processes started by your script running under cron have the environment they need to get their work done.

As Jim McNamara suggested, create the following script in a file named get_cron_env:

Code:

#!/bin/bash
HOME="/home/admin"
cd "$HOME"
[ -f .bash_profile ] && . .bash_profile
[ -f .bash_login ] && . .bash_login
[ -f .profile ] && . .profile
env > environ.cron

Make that file executable with:

Code:

chmod +x get_cron_env

Set a crontab entry to run that script (using an absolute pathname for the script; not just get_cron_env).
And then run the commands:

Code:

env > /home/admin/environ.interactive
diff /home/admin/environ.cron /home/admin/environ.interactive

and show us the output.

There will likely be some differences because interactive environments have more stuff going on than background jobs like those started by cron. But, maybe we'll get lucky and see something that you can easily fix.

I can't help you find the source for the executable you have installed as /opt/CPsuite-R77/fw1/bin/upgrade_tools/upgrade_expor. If you (the royal you meaning some administrator inside your company) wrote software and didn't provide documentation on how to run it, track down who wrote it and get them to tell you exactly what you have to do to run it from cron.

If this is third party software you bought from someone else, read the documentation that came with it. If you bought code from someone and didn't get documentation that tells you how to run it; shame on you. Contact the vendor and ask for support.

If this is third party software you downloaded free from someone else, read the documentation that came with it. If you downloaded code without documentation and without source, and without support; you've got what you paid for and I wish you luck. If you downloaded free source, look at it and figure out what it is doing that keeps it from working under cron and fix it. Or send mail to the support site for that free software and ask for help.

And, of course, if you downloaded a bootlegged copy of someone's software from a black site, we have absolutely no sympathy for you and will not further assist you in trying to fix code you stole from its creators. (But, we assume that you would never do that.)