IDX_SETS errors (AREV Specific)
At 10 SEP 1999 06:04:28PM David Plass wrote:
I have been following the many discussions regarding these errors, but I can't seem to find a direct correlation to the problems that we are having with one of our clients.
The error:
] FS445———————————
] IDX_SETS function 1 returned error code -9773
] FS448———————————
] Fatal Internal Error
] ]
Environment:
Windows95 clients with NT Service 1.5 using AREV 3.12 application.
The error occurs extremely sporatically when they utilize one part of our application. Unfortunately, that one part is a batch function that allows them to set up multiple jobs to run sequentially. I've looked at the code and just don't see anything that should be causing these errors, but I also don't feel comfortable with my level of expertise in examining the code.
I'm becoming convinced that the problem is between AREV and Windows95, because we can localize the application, using the Non-Networking driver (and moving the application to a local drive, of course), and still get the error (eventually). We are continuing to test it, and will be shifting efforts to an NT box, to see if that helps at all, but to be honest, I'm at a loss.
We are willing to entertain proposals from consultants on those who think they can figure this problem out for us. If you are interested and have the necessary qualifications, please email David Plass at dplass@scc.com. Thanks.
At 10 SEP 1999 09:17PM Barry Stevens wrote:
Between the running of each job setup the following r/basic commands.
flush
garbagecollect
Barry
At 14 SEP 1999 08:54AM David Plass wrote:
Thank you for the feedback.
We did have the code in there, but the lines were in the opposite order, and, according to some research of the AREV documentation done, the order you presented is the correct order. We will make the change and continue testing.
Thanks again.
At 11 OCT 1999 03:23PM David Plass wrote:
We reversed the lines of code, and it seemed to work, but there's a catch. The system we set up to test on was local, and the fix eliminated the error from this environment, but when we went back to a NT Server with the NT Service and a Win95 client, the IDX_SETS error returned.
We did, however, begin testing on a WinNT workstation, and the problems do not seem to be occuring.
Does anyone have insight into this?