Thunderstone Support Forums

I am getting the following upon any search.

ERROR: Could not open SYSTABLES In the function: ddopen
ERROR: Could not connect to C:\Morph3\onemade In the function: openntexis
ERROR: Not logged into a database
ERROR: n_texis() failed In the function: TexisExec()

I have been having quite a few problems since we converted to windows 2000 server.

Our most recent issues were apparent memory leaks upon search. We are using the API to access Texis. While trying to figure out what the leaks were, I found a bunch of Abend signal 11's in the monitor log. Then, the following error appeared.

000 May 2 11:27:54 Assertion EX failed in file s:\texis\fdbf.c, line 269
000 May 2 11:27:55 CORRUPT OPERATION IN THE FDBF FILE c:\morph3\onemade\SYSTABLE.tbl in the function readhead

So, I tried to do a kdbfchk on it and it appeared to repair it, but now I'm getting the could not open the SYSTABLES error.

I'm going nuts here, so any help is appreciated.

One other thing, I am using a version of Texis from april 5, 2000.

Thanks,
Justin Law

btw, I don't actually have a SYSTABLES.tbl it is called SYSTABLE.tbl

It looks as if the file was severely corrupted, and you may have lost all the data in it. If you want to open a ticket and send us the old and new file we can look for clues as the the cause.

You can create a new database, copy the SYSTABLE.tbl file from there, and then addtable each of the tables in the database.

Thanks, that worked great. I am still getting the abend 11 errors, any idea what that's about.

Are there any other messages in monitor.log just before the abend with the same PID or close time?

the log looks like this over and over again.

200 May 2 18:01:54 ABEND signal 11
200 May 2 18:01:54 ABEND signal 11
200 May 2 18:02:04 ABEND signal 11
200 May 2 18:02:04 ABEND signal 11
200 May 2 18:02:15 Contacting license server
000 May 2 18:02:15 Could not contact license server
200 May 2 18:02:18 ABEND signal 11
200 May 2 18:02:18 ABEND signal 11
200 May 2 18:02:29 ABEND signal 11
200 May 2 18:02:29 ABEND signal 11
200 May 2 18:03:00 ABEND signal 11
200 May 2 18:03:04 ABEND signal 11
200 May 2 18:03:04 ABEND signal 11
200 May 2 18:03:09 ABEND signal 11
200 May 2 18:03:09 ABEND signal 11

This just happened today.

200 May 3 20:01:06 ABEND signal 11
200 May 3 20:01:06 ABEND signal 11
200 May 3 20:01:11 ABEND signal 11
200 May 3 20:01:14 ABEND signal 11
200 May 3 20:01:43 ABEND signal 11
200 May 3 20:02:32 Contacting license server
000 May 3 20:02:32 Could not contact license server
200 May 3 20:17:32 Contacting license server
000 May 3 20:17:32 Could not contact license server
000 May 3 20:20:59 Corrupt next header at 0xF4C in KDBF file c:\morph3\onemade\SYSINDEX.tbl in the function read_rest_data
200 May 3 20:20:59 ABEND signal 11
000 May 3 20:21:00 Corrupt next header at 0xF4C in KDBF file c:\morph3\onemade\SYSINDEX.tbl in the function read_rest_data
200 May 3 20:21:00 ABEND signal 11
000 May 3 20:21:00 Corrupt next header at 0xF4C in KDBF file c:\morph3\onemade\SYSINDEX.tbl in the function read_rest_data
200 May 3 20:21:00 ABEND signal 11
000 May 3 20:21:00 Bad lock wrong sid in the function checkserver
000 May 3 20:21:00 Bad lock wrong sid in the function checkserver
000 May 3 20:21:00 Bad lock wrong sid in the function checkserver

followed by this a few hours later

000 May 3 20:21:00 Bad lock wrong sid in the function checkserver
000 May 3 20:21:00 Bad lock wrong sid in the function checkserver
000 May 3 20:23:25 Corrupt next header at 0xF4C in KDBF file c:\morph3\onemade\SYSINDEX.tbl in the function read_rest_data
200 May 3 20:23:25 ABEND signal 11
000 May 3 20:23:25 Corrupt next header at 0xF4C in KDBF file c:\morph3\onemade\SYSINDEX.tbl in the function read_rest_data
200 May 3 20:23:25 ABEND signal 11
000 May 3 20:23:31 Corrupt next header at 0xF4C in KDBF file c:\morph3\onemade\SYSINDEX.tbl in the function read_rest_data
200 May 3 20:23:31 ABEND signal 11
000 May 3 20:25:22 Corrupt next header at 0xF4C in KDBF file c:\morph3\onemade\SYSINDEX.tbl in the function read_rest_data
200 May 3 20:25:22 ABEND signal 11

I don't know if continually trying to contact the license server or the ABEND signal 11 errors are to blame for corrupting the files or what. Any suggestions would be appreciated.

Note that the search actually works while the ABEND signal 11 error is occurring. Every couple of hours though, it appears a memory leak occurs, and the dllhost.exe running the com+ .dll that accesses the texis api's maxes out the machines ram. I can fix it simply by stopping that process. But now, for the second day in a row, a table is apparently corrupted. I just don't get it.

Any help is appreciated.

I just noticed something really wacky. There is an SQL statement in my SYSTABLE.tbl. I can't even imagine how it got in there. I know my code doesn't access the SYSTABLE.tbl. The sql statement obviously is a search that ran against the texis engine, but how and why did it get into the SYSTABLE.tbl.

It sounds as if there is something really wrong with your system. You may have bad memory, a bad disk, somehow a corrupted system, or broken code in your API. Are you compiled flat (with NCGDIRECT)? In that case your program could write to those files. You might try recompiling your program so it talks to texisdnt.exe, and see if that stops the problems.

Hey, thought I'd give you an update.

I reinstalled Texis, and rebuilt the database. It now seems that the only problems I get are the Abend 11 errors. I don't know what they mean, but I think it is the cause of memory leaks I am having running our component in Transaction Server.

The monitor log looks like this:

200 May 6 20:58:18 ABEND signal 11
200 May 6 20:58:18 ABEND signal 11
200 May 6 20:58:18 ABEND signal 11
200 May 6 20:59:20 ABEND signal 11
200 May 6 20:59:20 ABEND signal 11
200 May 6 21:00:32 ABEND signal 11
200 May 6 21:00:32 ABEND signal 11
200 May 6 21:00:50 ABEND signal 11
200 May 6 21:00:50 ABEND signal 11
200 May 6 21:01:30 ABEND signal 11
200 May 6 21:01:30 ABEND signal 11
200 May 6 21:01:32 ABEND signal 11
200 May 6 21:01:32 ABEND signal 11

It appears that every SQL statement that is executed results in this log statement, even when data is returned.

Any help is appreciated.