"No such table" message

mieke · Post by **mieke** » Mon Jan 14, 2002 12:43 pm

I have webinator up and running, but when I check the monitor.log file I get the following entries -- repeated over and over again:

115 Jan 14 17:40:00 No such table: SYSSCHEDULE in the database: C:\Program Files\Thunderstone Software\Webinator\texis\testdb\
000 Jan 14 17:40:00 Can't prepare SQL SELECT in the function TXrunscheduledevents
000 Jan 14 17:40:00 TXrunscheduledevents() failed; resetting DDIC
002 Jan 14 17:41:00 Unable to open table C:\Program Files\Thunderstone Software\Webinator\texis\testdb\SYSSCHEDULE in the function opendbtbl

Post by **mark** » Mon Jan 14, 2002 3:31 pm

The installation must have had trouble making the schedule table for some reason. Go to a command prompt and run
texis -wipesched
(you may have to cd to c:\inetpub\scripts, or whatever you gave for your CGI directory during installation, first for texis to be found).

mieke · Post by **mieke** » Tue Jan 15, 2002 6:31 am

The SYSSCHEDULE table already exists, but the file is empty. When I use the texis -wipesched command I get the meassge:

176 table SYSSCEDULE already exists in data dictionary in the fcn createdbtbl

I tried to delete the file SYSSCHEDULE but I have a sharing violation. Rebooting did not help. (I thought I could delete it and then run -wipesched to create a new one.)

Is there a way to force the file to be overwritten when using the -wipesched command?

Any suggestions?

Post by **mark** » Tue Jan 15, 2002 10:00 am

from a command prompt run
monitor -k
then delete the SYSSCHEDULE.tbl file
then run
texis -wipesched

mieke · Post by **mieke** » Tue Jan 15, 2002 10:26 am

I was to delete the SYSSCHEDULE file, but I still get the previous error message when I run texis -wipesched (176 table SYSSCEDULE already exists in data dictionary in the fcn createdbtbl).

I have also noted that there are always 2 monitor proccesses running at any given time -- and if I kill one the other also dies.

Post by **mark** » Tue Jan 15, 2002 10:38 am

Sorry, I thought -wipesched would drop the table for you. Do this
texis -d /usr/local/morph3/texis/testdb -u _SYSTEM -p "" -s "drop table SYSSCHEDULE"

Post by **mark** » Tue Jan 15, 2002 10:41 am

Oops, sorry that was a unix path. You want
texis -d "C:\Program Files\Thunderstone Software\Webinator\texis\testdb" -u _SYSTEM -p "" -s "drop table SYSSCHEDULE"

mieke · Post by **mieke** » Wed Jan 16, 2002 6:16 am

Thanks, that seems to have fixed the problem with the table, but now having problems with multiple monitor processes attempting to start up.

Every hour the I get the following:

200 Jan 16 10:21:27 Texis Monitor version 04.00.1005675845 starting (pid 96)
200 Jan 16 10:21:27 Starting Dispatcher in the function SVmain
015 Jan 16 10:21:27 Texis Monitor pid 267 already running (pid 96)
200 Jan 16 10:21:27 Texis Monitor exiting due to error (pid 96)

Could this be in some way related to the fact that I no longer have a SYSSCHEDULE.tbl file -- perhaps the monitor has no idea when to start and just keeps on trying?

Post by **mark** » Wed Jan 16, 2002 9:58 am

SYSSCHEDULE should exist if you did -wipesched after the drop.

It's probably a perm issue of some kind. Run
monitor -k
from a command prompt. Then immediately do a search from a web browser. That should get the monitor started as the correct user.