After running a bunch of Windows Updates, when Microsoft Search starts, getting errors ESE 494, 454, Indexer 9000, 7037, 7010 and search is broken.
Hello, new Technet Subscriber and first time poster!I've got an odd exchange 2003 issue that I can't get to the bottom of.This started this weekend after some Microsoft Updates. Now on server startup, I'm getting a bunch of errors and the search can't connect to the full text indexes (meaning that clients cant search.I'm getting the following:-----------------------Source: ESEType: ErrorCategory: Logging/RecoveryEvent ID: 494ExchangeServer_METIS (3188) ExchangeServer_METIS: Database recovery failed with error -1216 because it encountered references to a database, 'C:\Program Files\Exchsrvr\ExchangeServer_METIS\ExchangeServer_METIS.edb', which is no longer present. The database was not brought to a Clean Shutdown state before it was removed (or possibly moved or renamed). The database engine will not permit recovery to complete for this instance until the missing database is re-instated. If the database is truly no longer available and no longer required, procedures for recovering from this error are available in the Microsoft Knowledge Base or by following the "more information" link at the bottom of this message. ---------------------Source: ESEType: ErrorCategory: Logging/RecoveryEvent ID: 454ExchangeServer_METIS (3188) ExchangeServer_METIS: Database recovery/restore failed with unexpected error -1216.---------------------Source: Microsoft SearchType: ErrorCategory: Search ServiceEvent ID: 9000The Microsoft Search service is unable to open the Jet property store. Error: .---------------------Source: Microsoft SearchType: ErrorCategory: IndexerEvent ID: 7037The Property Store failed to initialize. Error: 8004111e - The Indexer failed to update or access information because of a database error. Stop and restart the Search service. If errors continue, reset the catalog and rebuild the index. In some cases, it may be necessary to delete and recreate the catalog. .---------------------Source: Microsoft SearchType: ErrorCategory: IndexerEvent ID: 7010The project cannot be initialized. Error: 8004111e - The Indexer failed to update or access information because of a database error. Stop and restart the Search service. If errors continue, reset the catalog and rebuild the index. In some cases, it may be necessary to delete and recreate the catalog. .---------------------I get a couple of the Indexer errors with different full-text indexes that are on the server.Reading through the errors, I would think that one of my EDBs is corrupt and not mounted. The thing is that all four of the stores (3 Mailbox stores and 1 public folder) are up and accessible. THe users just can't search. Also The EDBs are all stored on F:\Exchsrvr\MDBDATA not on the c:\. On the c:\ drive is a store that is the one indicated in the logs, but isn't this the default store that is created when you install exchange? I deleted this one...Any ideas on how to get search working again? I've tried hitting up the MS links in the logs (no go on the suggestions) and googling.I did run the ESE on the C:\Program Files\Exchsrvr\ExchangeServer_METIS\ExchangeServer_METIS.edb database with the /mu switch and it said that the DB was clean.Thanks
May 19th, 2009 8:13pm

Hello,Stop the Microsoft Search,Delete fulltext index on public folder store and mailbox store.re-build the fulltext index on both the stores.Arun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3
Free Windows Admin Tool Kit Click here and download it now
May 19th, 2009 11:16pm

You can do it with help of pre-build scripts available in script directory to identify catalog... How to Rebuild the Full-Text Index Catalog http://technet.microsoft.com/en-us/library/aa995966.aspxAmit Tank | MVP Exchange Server | MCITP: EMA, MCSA: M | http://ExchangeShare.WordPress.com
May 20th, 2009 6:09am

Oops Amit,The KB is for E2k7 :)here is the KB for creating fulltext indexing after following my previous instruction.Configure Full-Text Indexing on Mailbox Stores in Exchange 2003http://support.microsoft.com/default.aspx/kb/822932Arun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3
Free Windows Admin Tool Kit Click here and download it now
May 20th, 2009 6:27am

Oops Amit,The KB is for E2k7 :)here is the KB for creating fulltext indexing after following my previous instruction.Configure Full-Text Indexing on Mailbox Stores in Exchange 2003http://support.microsoft.com/default.aspx/kb/822932 Arun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3 Oh yeh, I missed to see version in question... Thanks...Amit Tank | MVP Exchange Server | MCITP: EMA, MCSA: M | http://ExchangeShare.WordPress.com
May 20th, 2009 6:29am

Sorry not to reply sooner, I was out for an extended holiday. I have begun working on this and will update as soon as I can. Thanks
Free Windows Admin Tool Kit Click here and download it now
May 26th, 2009 8:39pm

Well that was fast.. hit another roadblock. When trying to delete the full text indexes in ESM, the console would lock up. I found this blog post: http://msexchangeteam.com/archive/2005/02/23/379032.aspx I followed the instructions there to manually delete the full text index, but when I then go back to ESM and right click the store to create the full-text index, I get the message: ----------------------------- "The Indexer failed to update or access information because of a database error. Stop and restart the Search Service. If errors continue, reset the catalog and rebuild the index. In some cases, it may be necessary to delete and recreate the catalog. Facility: MSSearch.EmbeddedGatherMgr.1 ID no: 8004111e Exchange System manager ------------------------------ This message occurs with errors in the Application log. ----------------------------- ----------------------- Source: ESE Type: Error Category: Logging/Recovery Event ID: 494 ExchangeServer_METIS (3188) ExchangeServer_METIS: Database recovery failed with error -1216 because it encountered references to a database, 'C:\Program Files\Exchsrvr\ExchangeServer_METIS\ExchangeServer_METIS.edb', which is no longer present. The database was not brought to a Clean Shutdown state before it was removed (or possibly moved or renamed). The database engine will not permit recovery to complete for this instance until the missing database is re-instated. If the database is truly no longer available and no longer required, procedures for recovering from this error are available in the Microsoft Knowledge Base or by following the "more information" link at the bottom of this message. --------------------- Source: ESE Type: Error Category: Logging/Recovery Event ID: 454 ExchangeServer_METIS (3188) ExchangeServer_METIS: Database recovery/restore failed with unexpected error -1216. --------------------- Source: Microsoft Search Type: Error Category: Search Service Event ID: 9000 The Microsoft Search service is unable to open the Jet property store. Error: . ---------------------
May 26th, 2009 9:09pm

Any more ideas?Thanks
Free Windows Admin Tool Kit Click here and download it now
May 27th, 2009 11:28pm

Hi, 1. Would you please let me know whether you have attempted to remove all the Indexes of the databases on the server?2. If yes, please attempt folloiwng method to troubleshoot the issue:a. Stop MSSearch Serviceb. Move following files to a temporary folder:In folder: C:\Program Files\Exchsrv\ExchangeServer_%COMPUTERNAME%, Please moved the following files mss.chk, mss.log, ExchangeServer_servername.edb, res1.log, and res2.log to a temporary folder.c. Restart MSSearch Service and check the result. Mike
June 1st, 2009 6:55pm

Hi Mike, I did remove all of the indexes, but I had to do it manually with the help of this post: http://msexchangeteam.com/archive/2005/02/23/379032.aspxThen I was able tosolved this issue this morning by moving those files. that was exactly the problem. After that, when I tried to recreate the index it went fine.I'm assuming that the MSS* files are related to the search indexing?Thanks
Free Windows Admin Tool Kit Click here and download it now
June 1st, 2009 10:42pm

Hi, Thanks for your repsonse. I am glad to know that the issue could be solved after moving the files in ExchangeServer_ComputerName folder. According to the event 494: ExchangeServer_METIS (3188) ExchangeServer_METIS: Database recovery failed with error -1216 because it encountered references to a database, 'C:\Program Files\Exchsrvr\ExchangeServer_METIS\ExchangeServer_METIS.edb', which is no longer present.I would like to explain that the issue may occur if ExchangeServer_METIS.edb file corrupted or missed, after moving all the above files, a new database file will be generated. Mike
June 2nd, 2009 6:06am

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

Other recent topics Other recent topics