So I went to the synchronet control panel -> BBS -> configure -> Text File Sections and as soon as I select that the scfg.exe blows up with a very unhelpful error message:th
"scfg.exe has encountered a problem and needs to close. We are sorry for
inconvenience."A little update on this, I found out this is happening not just with selecting Text File Sections but from any part of the scfg.exe program. Such as when I try to enter External Programs, Nodes, System, Networks, etc...
Hi all. I've been working on trying to set up my BBS on a different box as the box it's currently on ... well it's tired and needs a rest :)
Anyway I started by copying the entire contents of c:\sbbs over, then I downloaded and extracted the update .zip to update from 3.16c to 3.18b. Going through things everything seems fine except when I try to read any of the text files in the text files area nothing comes up.
So I went to the synchronet control panel -> BBS -> configure -> Text File Sections and as soon as I select that the scfg.exe blows up with a very unhelpful error message:
"scfg.exe has encountered a problem and needs to close. We are sorry for the inconvenience."
It then wants to send an error report to microsoft. I looked at the technical data in the report (without sending it) but I didn't see anything useful such as an exception message or type or stack trace or anything.
Any ideas?
p.s. I also have tried running the old version (3.16c) on this box and the text files section works fine and I can access that area of the configuration but there are issues with some door games. These door game issues don't show up on the current (old) box, however upgrading to 3.18b does fix the door game issues so that's why I'd prefer to get 3.18bworking.
A little update on this, I found out this is happening not just with selecting Text File Sections but from any part of the scfg.exe program.
Such as when I try to enter External Programs, Nodes, System, Networks, etc...
I guess I could try a clean install of the latest version but it seems like it would be a pretty big hassle to get it back the way I want with my modified ansis, files, message bases (complete with messages), and doors etc... that's why I went with the update instead.
Re: Text files not working?
By: Digital Man to Divarin on Wed Jan 13 2021 11:08:41
Okay I ran jsexec update.js and that got the text files section working again. I updated to 3.18c but the issues in scfg are still there. I also tried the various interface modes but the behavior is the same.
For simplicity I'll step through the program using -iD (standard i/o)
1: Nodes
This sub-menu seems to work fine
2: System
Reading xtrn.cnf ...
(crash)
3: Networks
This sub-menu seems to work fine
4: File Areas
Reading file.cnf ...
(crash)
5: File Options
Reading file.cnf ...
(crash)
6: Chat Features
Reading char.cnf ...
(crash)
7: Message Areas
This sub-menu seems to work fine
8: Message Options
This sub-menu seems to work fine
9: Command Shells
This sub-menu seems to work fine
10: External Programs
Reading xtrn.cnf ...
(crash)
11: Text File Sections
Reading file.cnf ...
(crash)
So it's not all areas after-all but a lot of them. I've taken a look at file.cnf, chat.cnf, and xtrn.cnf and they appear identical to the ones in the older (working) backup (same date/time stamp and size) I haven't run a crc check on them but at first glance they appear the same.
Do you mind sending me an archive of your ctrl/*.cnf files? Best to ftp to vert.synchro.net/incoming or email them to me to keep any sensitiveinformat
--Sure I'll e-mail the zip to you, thanks
digital man
Re: Text files not working?
By: Digital Man to Divarin on Thu Jan 14 2021 10:52:44
Do you mind sending me an archive of your ctrl/*.cnf files? Best to ftp to vert.synchro.net/incoming or email them to me to keep any sensitive informat --
Sure I'll e-mail the zip to you, thanks
Re: Text files not working?in
By: Divarin to Digital Man on Thu Jan 14 2021 07:47 am
Re: Text files not working?
By: Digital Man to Divarin on Wed Jan 13 2021 11:08:41
Okay I ran jsexec update.js and that got the text files section working again. I updated to 3.18c but the issues in scfg are still there. I also tried the various interface modes but the behavior is the same.
For simplicity I'll step through the program using -iD (standard i/o)
1: Nodes
This sub-menu seems to work fine
2: System
Reading xtrn.cnf ...
(crash)
3: Networks
This sub-menu seems to work fine
4: File Areas
Reading file.cnf ...
(crash)
5: File Options
Reading file.cnf ...
(crash)
6: Chat Features
Reading char.cnf ...
(crash)
7: Message Areas
This sub-menu seems to work fine
8: Message Options
This sub-menu seems to work fine
9: Command Shells
This sub-menu seems to work fine
10: External Programs
Reading xtrn.cnf ...
(crash)
11: Text File Sections
Reading file.cnf ...
(crash)
So it's not all areas after-all but a lot of them. I've taken a look at file.cnf, chat.cnf, and xtrn.cnf and they appear identical to the ones
yourthe older (working) backup (same date/time stamp and size) I haven't run a crc check on them but at first glance they appear the same.
Do you mind sending me an archive of your ctrl/*.cnf files? Best to ftp to vert.synchro.net/incoming or email them to me to keep any sensitive information protected. If I can reproduce it, I can fix it. It definitely sounds like something (a bug) that is being triggered by the content of
.cnf files.
Are you passing any other command-line arguments to SCFG?
I wonder if you copy your sbbs/ctrl directory to another path (e.g. /test/ctrl) and then pass that path on the command-line to SCFG (e.g. "scfg -id /test/ctrl"), do you encounter the same crashes?
Re: Text files not working?
By: Digital Man to Divarin on Sat Jan 16 2021 12:37 pm
Are you passing any other command-line arguments to SCFG?
I wonder if you copy your sbbs/ctrl directory to another path (e.g. /test/ctrl) and then pass that path on the command-line to SCFG (e.g. "scfg -id /test/ctrl"), do you encounter the same crashes?
No I wasn't using any other command-line arguments.
I tried copying the ctrl directory to c:\test\ctrl and ran c:\sbbbs\exec\scfg.exe -id \test\ctrl but it had the same behavior.
I also tried running the scfg from the old version against this copy ofctrl
(from the new version) and it did not crash so although the contents of the ctrl directory may be the cause in some way the old version of scfg doesn't seem to have an issue with any of the files in this directory while the new one does.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 409 |
Nodes: | 16 (2 / 14) |
Uptime: | 40:59:31 |
Calls: | 8,567 |
Calls today: | 7 |
Files: | 13,222 |
Messages: | 5,928,232 |