Thanks Alan! I was able to get things resolved. I don't know why, but the Hummingbird UI is toast on my server, so I was forced to utilize the command line app.
It turned out that the issue was a "News Flash" item that was in there from a couple of years back. It seemed to be corrupted in some way (I couldn't tell how/why). I removed every item from the published folder. I then triggered the index check for that folder. I then placed the published docs back in small batches. Each time running the index. I did this till it failed. I then went through the failed bunch until I found the offending document and DELTED it! Once I did that, the rest went in as nice as could be. Now everything is indexing just fine. I suspect that the corrupted doc may have been playing havoc with some other items... Now if I could just figure out why the UI is hosed! Take care! Warren On Fri, Apr 2, 2010 at 10:35 AM, Alan Blake <alan_knowly...@yahoo.com>wrote: > ** > Hummingbird has a UI where you can go in and unprotect and delete the > tables if needed and then the rebuild should be able to build the entire > index over from scratch. The URL is typically http://<server>:8666/ssadmin > > > Alan Blake > Knowlysis > > --- On *Thu, 4/1/10, Warren Baltimore <warrenbaltim...@gmail.com>* wrote: > > > From: Warren Baltimore <warrenbaltim...@gmail.com> > Subject: KMX problems > To: arslist@ARSLIST.ORG > Date: Thursday, April 1, 2010, 3:47 PM > > ** > Folks, I am blindly trying to fix a problem with my Knowledge base. > > First off... > > KB is running on a Windows 2000 server. It is KMX 5.4 (I think). Running > on Hummingbird 5.4. It's normally very quiet and I don't need to do > anything, but.... > > I followed the instructions to update the indexes (Killed KMS Indexing > Service and IIS). > > Ran the Update scripts > > Brought everything back and....My helpdesk complained that it was even > worse! They were right. The thing was fried. > > So, I ran kms_Rebuild.bat. > > This seemed to clean things up BUT none of the published KB's are > available! I went back and took a look, and whenever the Published index > attempts to build, it comes back with an error: > > > *C:\Program Files\ar system\apps\kms\bin\Indexing>execsql > c:\progra~1\arsyst~1\ap > ps\kms\bin\indexing\up.txt* > > *validate index published validate table; > execsql: execute failed* > > *SQLSTATE: 80913, Native error: 0, error text > [Hummingbird][SearchServer]Table is protected* > ***** > > > *C:\Program Files\ar system\apps\kms\bin\Indexing>pause > Press any key to continue . . .* > Now, I've tried everything I can think of but no luck. I have even tried > adding "unprotect table Published;" to the Update_Published.bat script > without any luck. The other update scripts run fine. Just not the > published.... > > -- > Warren R. Baltimore II > Remedy Developer > 410-533-5367 > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ > > > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ > -- Warren R. Baltimore II Remedy Developer 410-533-5367 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
