I'm running a script that retrieves data. I usually let this script run overnight. When I check it, usually hours after I start the script, I get the error "Abnormal program termination". Do you have any ideas what might be causing this?
abnormal program termination
-
Kai
- Site Admin
- Posts: 1272
- Joined: Tue Apr 25, 2000 1:27 pm
abnormal program termination
Are there any error messages printed out or in the vortex.log that pertain to that script? How exactly is the script retrieving data; via <fetch>, <timport>, <read>? What is it doing with the data? What SQL statement(s) might have been executing at the time of the error?
-
sourceuno
- Posts: 225
- Joined: Mon Apr 09, 2001 3:58 pm
abnormal program termination
There are no error messages in the log file that pertain to the script. The script is retrieving data using <fetch> and then inserting the text of the page along with a few other fields into some tables. I haven't really investigated where the exactly the script is stopping. It might be possible that it exits before an insert.
-
Kai
- Site Admin
- Posts: 1272
- Joined: Tue Apr 25, 2000 1:27 pm
abnormal program termination
Try to narrow down the exact SQL statement that was running at the error. Also, what version of Vortex is this (texis -version)?
-
sourceuno
- Posts: 225
- Joined: Mon Apr 09, 2001 3:58 pm
abnormal program termination
Here's the version info:
Texis Web Script (Vortex) Copyright (c) 1996-2001 Thunderstone - EPI, Inc.
Commercial Version 3.01.984682785 of Mar 15, 2001 (i686-intel-winnt)
I'll try insert some dummy statements to find out where the error is occuring and let you know where it stops if I see it.
Texis Web Script (Vortex) Copyright (c) 1996-2001 Thunderstone - EPI, Inc.
Commercial Version 3.01.984682785 of Mar 15, 2001 (i686-intel-winnt)
I'll try insert some dummy statements to find out where the error is occuring and let you know where it stops if I see it.
-
mark
- Site Admin
- Posts: 5519
- Joined: Tue Apr 25, 2000 6:56 pm
abnormal program termination
Vortex will generally print a script name and line number when there's an error in a script, or otherwise bails out. Make sure you're not suppressing putmsg output.