verity

[Schreck, Tom]

I'm getting the following error message with verity:

Error occurred in tag CFSEARCH 
Internal Error: VDKSessionNew failed

Error Code: -125
The error occurred while processing an element with a general identifier of
(CFSEARCH), occupying document position (112:2) to (116:2).

Does anyone know what a VDKSessionNew is?  Also, it seems like verity is
causing a memory leak because CF will completely freeze up every 4 to 5
hours on our production site.  After we stop and restart CF, the site and
the search functionality works fine.  The production server has MS's Index
Server.  The failure seems to match up time wise with a failure in the
application log of qperf.dll, part of the Index Server.  I cannot say if the
failure cascades to a failure of verity or if the reverse is true, the
verity failure kills qperf.dll.  Is qperf.dll associated with verity?
Should we not use Index Server and verity on the same server?  We've
extensively tested the site on a seperate server and did not have any of
these issues. 
Attached are 2 file snippets: 1 for how I'm creating the indexes
(verityIndex.cfm) and the other for how I'm calling the
results(verityResults.cfm)
Thanks - 

Tom Schreck
[EMAIL PROTECTED]
817-252-4900

I have not failed. I've just found 10,000 ways that won't work. 
- Thomas Edison 

 <<VerityIndex.cfm>>  <<VerityResults.cfm>> 

VerityIndex.cfm
Description: Binary data

VerityResults.cfm
Description: Binary data