What's wrong with indexing on my Exchange 2003 server? - TechRepublic
Question
March 13, 2007 at 10:08 PM
derek369

What’s wrong with indexing on my Exchange 2003 server?

by derek369 . Updated 19 years, 4 months ago

I am having problem with Indexing on my Exchange server 2003. As a result of
this, Outlook users are unable to search items. Attached below are event logs and
indexing status generated by executing MSSearch_Admin.vbs tool.
The event log suggest to reset or recreate catalog. I do not know how.
Anyone could help me out? Thanks in Advance.

Derek LIU

—— Windows Application Event Logs —–

Event Type: Error
Event Source: Microsoft Search
Event Category: Indexer
Event ID: 7037
Date: 12/03/2007
Time: 10:30:59 PM
User: N/A
Computer: GPKPSREX01
Description:
The 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. .

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Microsoft Search
Event Category: Indexer
Event ID: 7039
Date: 12/03/2007
Time: 10:30:59 PM
User: N/A
Computer: GPKPSREX01
Description:
The Content Index for project
cannot be loaded. 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. .

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Microsoft Search
Event Category: Search Service
Event ID: 9000
Date: 12/03/2007
Time: 10:30:59 PM
User: N/A
Computer: GPKPSREX01
Description:
The Microsoft Search service is unable to open the Jet property store.
Error: |???3?w.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Microsoft Search
Event Category: Indexer
Event ID: 7010
Date: 12/03/2007
Time: 10:30:59 PM
User: N/A
Computer: GPKPSREX01
Description:
The 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. .

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 494
Date: 12/03/2007
Time: 10:30:59 PM
User: N/A
Computer: GPKPSREX01
Description:
ExchangeServer_GPKPSREX01 (3628) ExchangeServer_GPKPSREX01: Database
recovery failed with error -1216 because it encountered references to a
database, ‘C:\Program
Files\Exchsrvr\ExchangeServer_GPKPSREX01\ExchangeServer_GPKPSREX01.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.

For more information, click http://www.microsoft.com/contentredirect.asp.

Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 454
Date: 12/03/2007
Time: 10:30:59 PM
User: N/A
Computer: GPKPSREX01
Description:
ExchangeServer_GPKPSREX01 (3628) ExchangeServer_GPKPSREX01: Database
recovery/restore failed with unexpected error -1216.

For more information, click http://www.microsoft.com/contentredirect.asp.

—– Indexing Status generated by MSSearch_Admin.vbs —–

Index Name: pub75BA818F

Index Name pub75BA818F
Exchange Store Public Folder Store (GPKPSREX01)
State Initializing
Documents Indexed 0
Size 0 MB
Last Build Date 4/12/2006 10:31:50 PM
Available for Searching FALSE
Working Directory D:\GPKPSREX01_SG1\FTI2
Gatherer Logs C:\Program Files\Exchsrvr\ExchangeServer_GPKPSREX01\GatherLogs
Start Addresses
\\.\BackOfficeStorage\pqp.local\Public Folders

Index Errors Count 1
Index Errors
Problem: The Start Address URL “\\.\BackOfficeStorage\pqp.local\Public
Folders” is incorrect. The correct Start Address URL is:
“\\.\BackOfficeStorage\\Public Folders”.
Resolution: Run the script “MSSearch_Admin.vbs” specifing the ACTION “FIXUP”
and any additional parameters to correct the Start Address.

Index Name: priv29C202F3

Index Name priv29C202F3
Exchange Store Admin Store (GPKPSREX01)
State Initializing
Documents Indexed 0
Size 0 MB
Last Build Date 5/12/2006 10:00:04 PM
Available for Searching FALSE
Working Directory D:\GPKPSREX01_SG1\FTI1
Gatherer Logs C:\Program Files\Exchsrvr\ExchangeServer_GPKPSREX01\GatherLogs
Start Addresses
\\.\BackOfficeStorage\pqp.local\MBX?MDBName=CN=Mailbox Store
(GPKPSREX01),CN=GPKPSREX01_SG1,CN=InformationStore,CN=GPKPSREX01,CN=Servers,CN=First
Administrative Group,CN=Administrative Groups,CN=Geoff Penney,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=pqp,DC=local

Index Errors Count 1
Index Errors
Problem: The Start Address URL
“\\.\BackOfficeStorage\pqp.local\MBX?MDBName=CN=Mailbox Store
(GPKPSREX01),CN=GPKPSREX01_SG1,CN=InformationStore,CN=GPKPSREX01,CN=Servers,CN=First
Administrative Group,CN=Administrative Groups,CN=Geoff Penney,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=pqp,DC=local” is incorrect. The
correct Start Address URL is:
“\\.\BackOfficeStorage\pqp.local\MBX?MDBName=CN=Admin Store
(GPKPSREX01),CN=GPKPSREX01_SG1,CN=InformationStore,CN=GPKPSREX01,CN=Servers,CN=First
Administrative Group,CN=Administrative Groups,CN=Geoff Penney,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=pqp,DC=local”.
Resolution: Run the script “MSSearch_Admin.vbs” specifing the ACTION “FIXUP”
and any additional parameters to correct the Start Address.

This discussion is locked

All Comments