Got a weird one happening. I am running 3.19b as a Door Server and my Timed Events don't work anymore I can't force them and all they do is return a 255 result code in the error log. I am know I am being vague, but where can I start to look first, I have run the files in question from a command prompt and they run with no issues. Basically, the files in question are Tradewars auto maints which ran with no issues on 3.18, I know the events work with 3.19 as I am running 3.19c as a BBS and everything works.. Anyone have ideas where I can start with this??
Got a weird one happening. I am running 3.19b as a Door Server and my Timed Events don't work anymore I can't force them and all they do is return a 255 result code in the error log.
I am know I am being vague, but where can I
start to look first, I have run the files in question from a command prompt and they run with no issues. Basically, the files in question are Tradewars auto maints which ran with no issues on 3.18, I know the events work with 3.19 as I am running 3.19c as a BBS and everything works.. Anyone have ideas where I can start with this??
A "255 result code in the error log" sounds like the Synchronet even thread is running and its attempting to run the events. If you try to force an event to run, do you see new activity in the event thread log output or a new error?
I'm assuming the Tradewars maintence is a 16-bit DOS program. Do native 32-bit Windows events run okay? It'd be good to isolate which *kinds* of events you're having problems with. If only 16-bit DOS events are
failing, then that would start to indicate a problem with NTVDM
(assuming we're talking about a Windows version of Synchronet here) - is this a 32-bit Windows install or are you using NTVDMx64?
The pasted output of your event log would help too.
--
digital man (rob)
On 10 Nov 2022, Digital Man said the following...
A "255 result code in the error log" sounds like the Synchronet even thread is running and its attempting to run the events. If you try to force an event to run, do you see new activity in the event thread log output or a new error?
I see a new error every time I try to force a event to run.
I'm assuming the Tradewars maintence is a 16-bit DOS program. Do native 32-bit Windows events run okay? It'd be good to isolate which *kinds* of events you're having problems with. If only 16-bit DOS events are failing, then that would start to indicate a problem with NTVDM (assuming we're talking about a Windows version of Synchronet here) - is this a 32-bit Windows install or are you using NTVDMx64?
I am running 16 bit maint progams on a 32 bit Windows Install, I just tried to force a AVAT in and see nothing on the services window, or Terminal Server window of it running.
The pasted output of your event log would help too.
Here is the end of it, nothing about AVAT-IN being run and this is the results of the maint files trying to run..
Thu Nov 10 00:00:00 2022 master/a2a9dc027
evnt GO Timed event: GO returned 255
Thu Nov 10 00:01:00 2022 master/a2a9dc027
evnt TJLOTTOM Timed event: TJLOTTOM returned 255
Thu Nov 10 00:15:00 2022 master/a2a9dc027
evnt TWARAM Timed event: TWARAM returned 255
Thu Nov 10 00:15:00 2022 master/a2a9dc027
evnt TW3MAINT Timed event: TW3MAINT returned 255
Thu Nov 10 02:00:00 2022 master/a2a9dc027
evnt TW2MAINT Timed event: TW2MAINT returned 255
Is it possible the event services aren't running?
This set up is a 3.19b
which was installed from scratch then a migration from a 3.18 system took place
after I upgraded that system to 3.19b. Thanks for the help..
Just as an add on, I just added the Events window and AVAT-IN worked. When I force say the Tradewars even it shows Semaphore signaled for Timed event. It says it is running it, and then it returns the 255. This is a new Windows 10 install from last month.. Wondering if it is a Windows issue instead even though I can run the files a DOS prompt...
I figured it out... On my original system I had these Timed Events with the Native Executable flag as NO, I just changed them all on the new system to YES and they all work now. It seems to work now so I am happy.. LOL Thanks to You Rob and MRO for helping out...
AL
that's why i said to post the config
when you do an update from an older version you have to change that. that's what happened to daryl and me.
---
Sysop: | Chris Crash |
---|---|
Location: | Huntington Beach, CA. |
Users: | 585 |
Nodes: | 8 (0 / 8) |
Uptime: | 26:45:49 |
Calls: | 10,757 |
Files: | 5 |
Messages: | 452,124 |