Hi Doug,


This seems to be a somewhat common Verity error, outside of ColdFusion even:
http://www.google.com/search?q=%22Error+%23+-2%22++Error+E3-0005
<BLOCKED::http://www.google.com/search?q=>
&num=100&hl=en&lr=&ie=UTF-8&c2coff=1&safe=off&filter=0


Maybe you could try my custom tag CF_MKVDK to generate a verity mkvdk log
file.  The log might have more information with details since there is a
highly verbose logging option built into mkvdk, and ColdFusion normally
doesn't make use of that option.


Description:  
http://www.talkingtree.com/blog/index.cfm?data=""> <BLOCKED::http://www.talkingtree.com/blog/index.cfm?data=""


Custom Tag and pre-made test files to index:
http://www.talkingtree.com/downloads/index.cfm?item=mkvdk%5Fgood%5Ftest%2Ezi
p
<BLOCKED::http://www.talkingtree.com/downloads/index.cfm?item=mkvdk_good_tes
t.zip>


Custom Tag with caller demo:
http://www.talkingtree.com/downloads/index.cfm?item=mkvdk%2Ezip
<BLOCKED::http://www.talkingtree.com/downloads/index.cfm?item=mkvdk.zip>


Also, the custom tag will write a bulk file and shell script to the /tmp
directory.  You can run the shell script manually from the command line to
run mkvdk outside of ColdFusion to see if you get the same error message or
not.


If this is a "custom" collection built from a query then my tag won't help.
Its only for file based collections.  


HTH,
Steven Erat

  _____  

From: Doug James [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 29, 2004 1:16 PM
To: CF-Talk
Subject: verity error help

We are using RedHat AS2.1 and we have just migrated to 6.1MX. I received
a note from a user that they got a verity error message. "An error
occurred while performing an operation in the Search Engine native
library. ...CFIndexTagException: Error # -2 Error E3-0005 ...Attach:
/opt/coldfusionmx/verity/collections/myColl/custom is not a directory..."

Can some please shed a bit of light on what it all means?

Thanks for the help.

Doug
  _____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to