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

Maintenance Service has reported an error

Fogbugz has reported the following error:

10/29/2008 1:00 AM (GMT+11:00): The Fog Creek Maintenance Service has reported an error. (424) Microsoft VBScript runtime error: Object required

Should I ignore it?
Darren Munt Send private email
Wednesday, October 29, 2008
 
 
See if there are any rows in your TrainingRequest table.  If there are, go ahead and delete them.

-Michael
Michael H. Pryor Send private email
Wednesday, October 29, 2008
 
 
I checked that table but it had no records.

I seem to be getting different errors every day now. This morning I got this:

6/11/2008 1:54 AM (GMT+11:00): The Fog Creek Maintenance Service has reported an error. (-2146232832) FogUtil.Search: Timeout expired
  at System.Data.OleDb.OleDbConnectionInternal..ctor(OleDbConnectionString constr, OleDbConnection connection)
  at System.Data.OleDb.OleDbConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject)
  at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
  at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
  at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
  at System.Data.OleDb.OleDbConnection.Open()
  at FogUtil.Database.Connection.Open()
  at FogUtil.Database.Command.ExecuteNonQuery()
  at FogUtil.Database.ActiveRecord.Commit()
  at FogUtil.Database.IndexFile.LoadByPrefixAndFilename(String sPrefix, String sFilename, Int32 ixGeneration, Boolean fCommit)
  at FogUtil.Database.IndexFile.LoadByPrefixAndFilename(String sPrefix, String sFilename, Int32 ixGeneration)
  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.Index.FieldInfos.Write(Directory d, String name)
  at Lucene.Net.Index.SegmentMerger.MergeFields()
  at Lucene.Net.Index.SegmentMerger.Merge()
  at FogUtil.Search.Index.InternalOptimize.RunTransaction()
  at FogUtil.Search.Index.TransactedWith.DoBody()
  at Lucene.Net.Store.Lock.With.Run()
  at FogUtil.Search.Index.Optimize()

It indicates a SQL time out, but we're not getting them when using the system generally. I've had a look in the SQL Server logs for activity around the time of the reported error but there doesn't seem to be any. Our maintenance schedules all run in the early evening rather than early morning.

Any where I can look to work out what's going wrong?
Darren Munt Send private email
Wednesday, November 5, 2008
 
 
Can you try re-running the register.bat that you find in the Accessories directory?
Rich Armstrong Send private email
Thursday, November 6, 2008
 
 

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.