Verity: 1, Me: -1705

coldfusion (This post is more than 2 years old.)

I love Verity, really, I do. But something strange happened today. A site which has been using Verity for ages (well, since CFMX7) suddenly reported an odd error today:

Collection (status code): theCollectionNameHere (-1705)

Of course, I already had a script that did a purse/reindex. So I ran that, and immediately the search began working again. Anyone else seen this before?

Hire Me!

I'm currently looking for my next role in developer evangelism and advocacy. I have a long history of helping companies work with developers and love to write, create demos, and present at conferences. You can find my resume to learn more and drop me an email (raymondcamden@gmail.com) to reach out.

Support this Content!

If you like this content, please consider supporting me. You can become a Patron, visit my Amazon wishlist, or buy me a coffee! Any support helps!

Want to get a copy of every new post? Use the form below to sign up for my newsletter.

Archived Comments

Comment 1 by Simon Horwith posted on 4/5/2006 at 6:55 PM

I assume you meant "purge"? I didn't know it was possible to "purse" a Verity collection ;)
I've seen Verity flake out on occasion - but no, I've never seen that exact error.

Comment 2 by Raymond Camden posted on 4/5/2006 at 6:59 PM

Oops. Um, yeah, thats purge. ;)

Comment 3 by Daniel Daugherty posted on 4/5/2006 at 7:55 PM

Been a long time since I worked with verity but in CF4.5 I had a site that would have to be purged and reindex from time to time. The cause was searches happening while large indexs were occuring. So I added locking around the index and search actions. Not sure if this is still and issue or not in CFMX7

Comment 4 by Raymond Camden posted on 4/5/2006 at 7:58 PM

From what I know, locking is absolutely -not- needed in CFMX7 now.

Comment 5 by Sami Hoda posted on 4/5/2006 at 8:09 PM

Ray,

Known problem.

See here:

http://software.groupbrowse...
http://groups.google.com/gr...
http://groups.google.com/gr...

Sami

Comment 6 by Adam Cameron posted on 4/5/2006 at 11:32 PM

Hi Ray.
Re your comment re locking... very interesting.

What happens if you kick off a long <cfindex> process, and then - shortly afterwards - kick it off again in a separate request (a Verity race condition, if you will).

I guess I could test this, but maybe you already know?

It's good news, anyhow.

--
Adam

Comment 7 by Raymond Camden posted on 4/6/2006 at 12:01 AM

Again, from what I've heard by my sources, you just don't need to worry about it. I haven't tested this yet, but I'm not seeing any locking issues. THis bug was the first oneI've run into so far.

Comment 8 by Toby Reiter posted on 8/9/2006 at 2:41 AM

Ray-
I'm getting the same error on one of our collections. I'd be REALLY interested in knowing if you've learned anything else about this.

We get this error pretty consistently, however.

Thanks,
Toby

Comment 9 by Raymond Camden posted on 8/9/2006 at 5:49 PM

Sorry Toby, but it never happaned again.

Comment 10 by Rich Sloan posted on 10/27/2007 at 12:11 AM

Hi Ray,

Did you ever figure out what is causing this issue? I am consistently having this issue on a couple of collections and can not find any resources on a resolution.

Thanks,

Rich

Comment 11 by Raymond Camden posted on 10/27/2007 at 12:22 AM

Nope. :(

Comment 12 by Rich Sloan posted on 10/27/2007 at 12:45 AM

Thanks Ray. I think I may need to start looking at your Lucene library if I can't figure this out. The only thing i did find is an old post that said to change the language to englishx. I have tried that and I am waiting for the collection to finish indexing. I'll post here if I find an answer or the englishx fixes it.

Rich

Comment 13 by Kevin Penny posted on 12/10/2008 at 9:53 PM

Yup - Just saw it in production this morning:

Steps to fix it:

Executed a 'delete' and then a 'create' on the index.
And repopulated the collection with data.

We've had numerous problems with Verity - and are even running under an unreleased patch that Adobe did for us for another issue where you ask for one collection data, and receive another's.

Good luck

Comment 14 by David McGuigan posted on 5/3/2010 at 7:39 PM

Just had this happen out of nowhere today on some sites that had been running fine for months/years.

Deleting the indexes and recreating them didn't work with a fun new error. Has no one found a good solution to this yet? So far it looks like we'll be reinstalling the Verity stuff and recreating all of the indexes afterwards. Which takes forev.

Comment 15 by Kevin Penny posted on 5/3/2010 at 11:54 PM

If you have a lot of records or a lot of collections - I'd recommend starting to get OFF Verity as soon as possible - the problem will only get worse - my recommendation is to use Solr instead - even if you have to roll your own implementation w/o cf9.

Comment 16 by David McGuigan posted on 5/3/2010 at 11:56 PM

Strangely, killing the verity service ( it wouldn't restart ) and starting it back up completely fixed the issues.

Comment 17 by Raymond Camden posted on 5/4/2010 at 12:11 AM

I'll ditto Kevin. Solr is the future for CF.

Comment 18 by Rodion Bykov posted on 7/5/2010 at 4:35 PM

Was getting -1705 error from Verity after failed 'Optimize' action and when folder permissions were incorrectly set. Thinking about moving to Solr anyway.

Comment 19 by James posted on 11/23/2011 at 12:44 AM

This was frustrating me for a long time, no matter what I did I was getting the (-1705). Then I recreated the collection in cf admin and chose English (Advanced) for the language and it worked!