Trying to solve a verity problem

Anyone seen this error when attempting to do verity searches? "The collection you specified does not exists or is not registered with the ColdFusion Search Service." The collection is definitely there, 100% sure. It's in CF Admin but I can't optimise the index as it bombs out with the same error. I've tried creating the index using CF admin and then updating the index from my code. It allows me to build the index no problem but when I try to search it bombs out. If anyone has any suggestions I would be most grateful because I've been researching this for 2 days and am getting nowhere :( "Help me Obi Wan Kenobi, you're my only hope" :)

----- Excess quoted text cut - see Original Post for more ----- Your sad devotion to that ancient Jedi religion has not helped you conjure up the missing index, or given you enough clairvoyance to find the Verity problem. OK, with that out of the way - I've run into similar problems with Verity when specific documents were indexed. To work through those problems, I had to index documents one-by-one to identify the problem document. This is one reason why I don't use Verity any more. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ http://training.figleaf.com/ Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on GSA Schedule, and provides the highest caliber vendor-authorized instruction at our training centers, online, or onsite.

> -----Original Message----- > Your sad devotion to that ancient Jedi religion has not helped you conjure up > the missing index, or given you enough clairvoyance to find the Verity problem. ROFLMAO, thanks for that, made me smile :) > OK, with that out of the way - I've run into similar problems with Verity when > specific documents were indexed. To work through those problems, I had to > index documents one-by-one to identify the problem document. This is one > reason why I don't use Verity any more. I'm not indexing documents, it's a query based index and when I run the part of the script with the cfindex tag it works without any problem:   <cfindex action="UPDATE"            collection="testCollection"            key="id"            type="CUSTOM"            title="title"            query="get"            body="title,descr"            custom1="descr"            language="English"> We recently moved the site to a new server at a new hosting company but they've already reinstalled Verity once and it's still not working right. Indexing no problem, searching big problem. Didn't have this issue on our old server... Do you think maybe indexing smaller sections of data might help with testing? Like index 10 rows at a time or something? -= Ed

----- Excess quoted text cut - see Original Post for more ----- I never had a problem indexing database content with Verity. I suspect you may have something else going on. Try creating a new collection, indexing one document into it, then seeing if that collection is searchable. You might also look at using the command-line tools to see if you can query the index from them. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ http://training.figleaf.com/ Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on GSA Schedule, and provides the highest caliber vendor-authorized instruction at our training centers, online, or onsite.

I wasn't seeing this before but I just tried to create a new collection in CF Admin and got this error: Unable to create collection testDocs. Unable to register collection testdocs. An error occurred while registering the collection with the K2 Search server: com.verity.api.administration.ConfigurationException: Failed to find configuration key. (-6005) But when I look in the list of collections in CFAdmin I see the collection. Maybe verity just needs to be reinstalled completely again. > > I'm not indexing documents, it's a query based index and when I run > > the part of the script with the cfindex tag it works without any problem: ----- Excess quoted text cut - see Original Post for more ----- right. ----- Excess quoted text cut - see Original Post for more ----- may > have something else going on. Try creating a new collection, indexing one > document into it, then seeing if that collection is searchable. You might also > look at using the command-line tools to see if you can query the index from > them. > > Dave Watts, CTO, Fig Leaf Software > http://www.figleaf.com/ > http://training.figleaf.com/ > > Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on GSA Schedule, > and provides the highest caliber vendor-authorized instruction at our training ----- Excess quoted text cut - see Original Post for more -----

Check that the k2 server is actually running. Regards Russ Michaels On Jul 3, 2012 2:44 PM, "Edward Chanter" <firewall@cc.uk.com> wrote: ----- Excess quoted text cut - see Original Post for more -----

Seems to be: When I run ./cfsearch start it says there is already a k2admin process running > -----Original Message----- > Check that the k2 server is actually running. >

Has this machine beem upgraded from previous version, might explain why you have 2 conflicting processes Regards Russ Michaels On Jul 3, 2012 4:25 PM, "Edward Chanter" <firewall@cc.uk.com> wrote: ----- Excess quoted text cut - see Original Post for more -----

AFAIK it's a fresh install of CF08.01 on a brand new VPS instance, but I can check with our hosting company tomorrow. > -----Original Message----- > Has this machine beem upgraded from previous version, might explain why you > have 2 conflicting processes >