Hi Lev,
I'm not quite sure exactly why you're having the issue. I guess its
because the config from the unix system is trying to use the crontab
(which is the unix way of scheduling tasks. The Cron service on your
windows system which OTRS installs is not quite the same thing).
I believe its the incoming mail service that uses the crontab
functionality, i.e. check the mail account for new mail every 2
minutes
Its probably also used by the generic agent too.
See if you can find where the crontab.txt file its looking for is. (I
don't use a cron service, I installed each component individually and
use the windows scheduler). It's probably under your "program
files\OTRS" program directory somewhere. Compare the config.pm's (and
maybe the default.pm's) from both the linux and windows machines
looking for entries relating to cron. See how they differ.
Try to make the linux config.pm fit the syntax of the windows config.pm.
I hope that helps,
Rory
Support my 365 Challenge in aid of the Irish Cancer Society
www.365challenge.ie
2009/9/16 Lev Davidovich
Hi I am getting this message on the Windows command prompt when I try to restart OTRS Services
“can’t open directory crontab.txt No such file or directory”
and Apache fails to start.
Below are the steps I have taken to reinstall version 2.2.5 from our live Apache server to the latest Windows installation (2.4.4) on our Windows test machine.
i) downloaded the latest version of the Windows installer of OTRS 2.4.4 - DONE
ii) dropped the mysql database - DONE
iii) loaded dumped database from live server – DONE
iv) turned OTRS Services (Cron, Apache, MySQL) off - DONE
v) cleaned the /otrs/otrs directory of 2.4.4 - DONE
vi) replaced with 2.2.5 version of the same directory – DONE
vii) copied Config.pm from the live server to Windows box – DONE.
viii) added the following line toConfig.pm: $Self->{'SendmailModule'} = 'Kernel::System::Email::DoNotSendEmail';
ix) also, on Config.pm, changed paths “$Self->{Home} = '/opt/otrs’” to “$Self->{Home} = 'C:/PROGRA~1/OTRS/OTRS';” and “$Self->{'LogModule::LogFile'} = '/var/log/otrs.log';” to “$Self->{'LogModule::LogFile'} = 'C:/PROGRA~1/OTRS/OTRS/var/log/otrs.log';”
x) try to turn OTRS Services back on – Error message comes up
If I then drop the 2.2.5 live database, reload the 2.4.4 database, turn OTRS Services off, restore the original 2.4.4 otrs/otrs directory, there is then no problem turning OTRS Services back on and logging in to 2.4.4.
Clearly there is something about the database import it doesn't like - any ideas?
Thanks a million
Lev
P.S. I originally sent this request under the previous thread I was involved with but it hasn't appeared so I have sent it again under a slightly different thread title. My apologies therefore if this appears twice!!
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! http://www.otrs.com/en/support/enterprise-subscription/