FogBugz Technical Support

A forum for technical support discussion related to Fogbugz.
The current FogBugz Knowledge Base can be found at http://help.fogcreek.com/fogbugz.

Posts by Fog Creek Employees are marked:

Documentation
Release Notes
Network Status

Getting Full Text Index error

I'm getting full text index error below for every case I want open now:

File:  /CFullTextIndexer.asp 
Line:  1178 
Browser:  Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Media Center PC 3.0; .NET CLR 1.0.3705) 
Number:  0x80131600 
Column:  -1 
OS Version:  Microsoft Windows Server 2003 R2 5.2.3790 
Database:  Microsoft SQL Server 
CLR Versions:  1033|v1.0.3705|v1.1.4322|v2.0.50727|v3.0 
QueryString:  pgx=EV&ixBug=14753&= 
URL:  /default.asp 
Content Length:  0 
Time:  12/11/2007 8:54:37 AM 

I use SQL2005 and somehow cannot find the full text catalog to rebuild it...

Please help?
Serge Baranovsky Send private email
Tuesday, December 11, 2007
 
 
It appears the FogBugz full text catalog disappeared in my setup. I have re-created it according to http://www.fogcreek.com/FogBugz/KB/dbsetup/FullTextSearch.html - that did not help...

Any ideas?
Serge Baranovsky Send private email
Tuesday, December 11, 2007
 
 
You should remove te full text index you created.  It's not necessary in FogBugz 6.


What version of 6.0 are you running?  If it's not the latest (6.0.39) please upgrade.
Michael H. Pryor Send private email
Tuesday, December 11, 2007
 
 
Deleted the manually created index.

I'm running 6.0.27

Can you please tell me how the latest will help this issue if I was running the 6.0.27 for a couple of months just fine?
Serge Baranovsky Send private email
Tuesday, December 11, 2007
 
 
We fixed some bugs.  You can view all the release notes here:
http://www.fogcreek.com/FogBugz/KB/indexWindows6.html#relnotes

But there was a bug that you are experiencing that we fixed in one of the minor updates.
Michael H. Pryor Send private email
Tuesday, December 11, 2007
 
 
Upgraded to 6.0.39 - didn't help. Still getting the error above...

There was a message during the upgrade Setup - "A License for the PowerTCP SecurePop Component was not found on this machine" - is this related in any way? I assume FogBugz may've not setup properly this during the upgrade...

And another error FogBugz has been warning me about on Dec 3rd (didn't look at it earlier):

========================================================
The Fog Creek Maintenance Service has reported an error. - Delete


12/3/2007 1:00 AM (GMT-08:00): Failed to update the search index: -2146232832 - Cannot find ixIndexFile
  at FogUtil.Database.IndexFile.LoadNewKey()
  at FogUtil.Database.ActiveRecord.Commit()
  at FogUtil.Database.IndexFile.LoadByPrefixAndFilename(String sPrefix, String sFilename, Int32 ixGeneration, Boolean fCommit)
  at FogUtil.Database.IndexFile..ctor(DatabaseSupport oConnectionSrc, String sPrefix, String sFilename, Int32 ixGeneration)
  at FogUtil.Database.IndexFileFactory.CreateFile(String sPrefix, String sFilename)
  at FogUtil.Search.Index.CreateFile(String name)
  at FogUtil.Search.Store.Directory.FogUtil.Search.Interfaces.DirectoryState.CreateFile(String name)
  at FogUtil.Search.Store.Directory.CreateFile(String name)
  at FogUtil.Search.Store.Directory.CreateOutput(String name)
  at Lucene.Net.Util.BitVector.Write(Directory d, String name)
  at Lucene.Net.Index.SegmentReader.DoCommit()
  at Lucene.Net.Index.IndexReader.Commit()
  at Lucene.Net.Index.MultiReader.DoCommit()
  at Lucene.Net.Index.IndexReader.AnonymousClassWith1.DoBody()
  at Lucene.Net.Store.Lock.With.Run()
  at Lucene.Net.Index.IndexReader.Commit()
  at Lucene.Net.Index.IndexReader.Close()
  at FogUtil.Search.Index.InternalCommit.RunTransaction()
  at FogUtil.Search.Index.TransactedWith.DoBody()
  at Lucene.Net.Store.Lock.With.Run()
  at FogUtil.Search.Index.CommitChanges()
========================================================

What do I do next?
Serge Baranovsky Send private email
Tuesday, December 11, 2007
 
 
I've opened a case with one of our developers to help track this down.
Michael H. Pryor Send private email
Tuesday, December 11, 2007
 
 
Any update on this?

I'm still down - cannot get back to any of my customers... :(

Anything I could try? Any troubleshooting I can help with at this point? Can I re-register the PowerTCP components somehow?
Serge Baranovsky Send private email
Thursday, December 13, 2007
 
 
You can reregister the PowerTCP stuff by simply clicking Settings->Site and then just hit OK at the bottom.

While you're in the Site Settings, check the search tab and see if you can reset the search index if that fixes the problem... or does it come back soon after that?
Michael H. Pryor Send private email
Thursday, December 13, 2007
 
 
Resetting the index did the trick, thank you. We are back up again. Will keep it in mind next time. I keep discovering new 6.0 features :)

Thanks again!
Serge Baranovsky Send private email
Thursday, December 13, 2007
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
 
Powered by FogBugz Bug Tracking and Evidence-Based Scheduling.