Rickman
12th June 2008, 10:47
Hi there,
Does anybody have a idea what is going wrong?? :confused:
Recently we've installed BaaN (SP25) on a new server.
During migration tests, we couldn't start the BaaNJobDaemon
If we check the properties of the JobDaemon within BaaNMan, the
command of jobd.bwc is set to -- ttaad5206m000.
If the service is started, the command spontaneously changed to
-- ottiexdbup e:/baan/tmp/ottiexdbup.0 45 and the service won't
start. We have to restart the server, because the service stays 'starting'
If we changed the command to ttaad5206m000, it changes again when
the service is started.
I was wondering why the command is set to "-- ottiexdup ......" :-?
Rickman
Does anybody have a idea what is going wrong?? :confused:
Recently we've installed BaaN (SP25) on a new server.
During migration tests, we couldn't start the BaaNJobDaemon
If we check the properties of the JobDaemon within BaaNMan, the
command of jobd.bwc is set to -- ttaad5206m000.
If the service is started, the command spontaneously changed to
-- ottiexdbup e:/baan/tmp/ottiexdbup.0 45 and the service won't
start. We have to restart the server, because the service stays 'starting'
If we changed the command to ttaad5206m000, it changes again when
the service is started.
I was wondering why the command is set to "-- ottiexdup ......" :-?
Rickman