((MXECHO))

Before I explain the difference before the clean and dirty states of an Exchange database we should explain how

I have noticed a lot of questions come up regarding the severity of the 8275 error on an Exchange 2003 Server.

Event Type: Error
Event Source: MSExchangeFBPublish
Event Category: General
Event ID: 8275
Date: <date>
Time: <time>
User: N/A
Computer: <server>
Description:
SchedulePlusFreeBusy folder could not be opened for duplicate message deletion on virtual machine <server name>. The error number is 0×80040115.
For more information, click http://www.microsoft.com/contentredirect.asp.

This error normally can be resolved by restarting the System Attendant, if this error is being logged on a cluster failing over to the other node (and then back if desired) would also resolve the error.

Keep in mind that restarting the SA will restart your Information Store service as well so you should schedule this during a maintenance window.

I have a few posts coming on Exchange 2007 Search, but in the mean time I am posting a gathering of links from around the Microsoft Net. These links are a good beginning to understanding Exchange 2007 Search. If you are interested in Exchange 2007 Search and Content Indexing, this list should help you get familiarized.

How to Diagnose Exchange Search Issues - http://technet.microsoft.com/en-us/library/bb123701(EXCHG.80).aspx?track=cc_exchange_sync

How to Disable or Enable Exchange Search - http://technet.microsoft.com/en-us/library/aa996416.aspx

How to Rebuild the Full-Text Index Catalog - http://technet.microsoft.com/en-us/library/aa995966(EXCHG.80).aspx

Indexing Exchange Server 2007 Public Folders - http://blogs.msdn.com/enterprisesearch/archive/2008/06/06/indexing-exchange-server-2007-public-folders.aspx

Managing Exchange Search - http://technet.microsoft.com/en-us/library/aa998289.aspx

Understanding Client Throttling - http://technet.microsoft.com/en-us/library/cc540454.aspx

Understanding Exchange Search - http://technet.microsoft.com/en-us/library/bb232132(EXCHG.80).aspx

Exchange Search FAQ - http://www.exchangeninjas.com/ExchangeSearchFAQ

Exchange Server 2007 Cross Mailbox Search using Export-mailbox - http://msexchangeteam.com/archive/2006/12/18/431934.aspx

The new Search in Exchange Server 2007 - http://msexchangeteam.com/archive/2006/10/11/429163.aspx

944516 How to register Filter Pack IFilters with Exchange Server 2007 - http://support.microsoft.com/default.aspx?scid=kb;EN-US;944516

945077 The Outlook Web Access search function does not work for some users in Exchange 2007 - http://support.microsoft.com/default.aspx?scid=kb;EN-US;945077

When you look up another users Free Busy you may see ////// hash marks. Many Administrators know these hash marks, they can sometimes be frustrating. But, before immediately thinking you have a problem with Free Busy, it is important to know some, valid reasons for seeing these hash marks //////

For example, lets say there is a free busy message in the public folder but no meetings are scheduled in the calendar. You may see hash marks, not just a blank schedule when looking up the user. Below are the different mailbox/client scenarios and what they produce in this type of situation.

Free Busy message exists in Public Folder, but no meetings are scheduled during the clients publishing period (generally 2 months)

MB = Mailbox, CL = Client

MB Exchange 2003 with CL Outlook 2003 or 2007 = ////////////

MB Exchange 2007 with CL Outlook 2007 = <nothing>

MB Exchane 2007 with Outlook 2003 = /////////////

So you can see the only time we will actually see a blank calendar when there are no appointments or meetings scheduled in the users calendar is when we are using Outlook 2007 and Exchange 2007. Otherwise if the users calendar is blank for the entire publishing period we would see hash marks.

So, easy test. Next time you are fighting a ////// Free Busy battle, see if posting a meeting to the users calendar has any affect. Remember to give the entry time to publish and replicate if using multiple Public Folder Shed + Free Busy replicas.

Mail store will not mount, in Exchange System Manager you see an Internal Processing error with error ID c1041724. You also notice an error in the application log, 9518 with error code 0xfffffddc.

How do you find out what is wrong?

First, you need to make sense of the error codes. If you have not used err.exe before, this is a perfect time to become familiar. Download this tool from Microsoft