Subj : Re: Event Won't Run
To   : Daryl Stout
From : Digital Man
Date : Sun Jan 16 2022 02:45:47

  Re: Re: Event Won't Run
  By: Daryl Stout to Digital Man on Sat Jan 15 2022 08:47 pm

 > Rob,
 >
 >  DM> Yes, and as you can see sbbs is tryint to execute the command-line you
 >  DM> specified, which as I recall, is executing a batch file. This is likely
 >  DM> failing because you have "Native Executable/Script" set to "No" (as I
 >  DM> previously stated and you quoted). Try changing that setting to "Yes".
 >
 >   Already tried that...no dice.

What does the event log output say when that happens?

 >  DM> Probably not, but if you determine the *context* of those errors (e.g.
 >  DM> by looking at the terminal server log output or the event thread log
 >  DM> output), you could determine more about *why* those errors might've
 >  DM> occurred. The error.log file alone is often not enough to root-cause an
 >  DM> issue, it's just an indication that there is a problem and that you may
 >  DM> have more research to perform to find and fix. --
 >
 >   I try to force the timed event to run, and all it does is give an error
 > 255, and it quits.

Yeah, it wouldn't matter if it was at the scheduled time or forced, sbbs can't execute the command-line you've configured. You've messed it up somewhere, just gotta figure out where. The log output would be helpful (and no, I don't mean the error.log file).
-- 
                                            digital man (rob)

Sling Blade quote #22:
Karl: I don't reckon you have to go with women to be a good father to a boy.
Norco, CA WX: 59.9øF, 30.0% humidity, 1 mph SSE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.14-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.