Having Exchange 2003 SP2 in environment frequently getting event log error as follows. How to find this particular message and cleanup from database. Error 0xfffffbd3 occurred on message 1-5B86690 during a background cleanup on database "SG1\CDE". Regards, Ganesh, MCTS, MCP, ITILV2

I think "isinteg" might help (to correct the problem, or to show additional symptoms and information for the problem) http://support.microsoft.com/kb/182081/en-us

What is the command for fixing one information store on different drive? Also i am getting these events. Event id : 1173, Error 0x6bb deleting unused restricted view from folder 1-272B15 on database "SG3\NoPurge". Microsoft Exchange Information Store will try to delete the view again at the next maintenance interval. Event id : 1025, An error occurred on database "SG1\CDE". Function name or description of problem: EcGenerateNDR: Error: 0xfffff9bf Event id: 1022, Logon Failure on database "SG1\AB" - Windows 2000 account NSKNK\sannamareddy; mailbox /O=org_name/OU=bstsksrs01/cn=Recipients/cn=snamareddy. Error: -1097 , Error 0xfffffbd3 occurred while cleaning up background folder 1-778F3FF on database "SG1\FGHIJ".  I am gettting above mentioned event also on this, will this isinteg will fix all these issues. Regards, Ganesh, MCTS, MCP, ITILV2

"Isininteg" will ask you which store/database to fix. See this picture http://www.msexchange.org/img/upl/image0241109064642025.jpg but in your case, it is better to use parameter "alltests" >isinteg -s server -fix -test alltests

Hi GaneshKumar Anand, For Event ID 1173 about “Error 0x6bb”, we can just ignore it. you can know more detail form this document: Event 1173 is logged in the Application event log in Exchange Server 2003 http://support.microsoft.com/kb/913126 From your other information, this may your database has logical corruption, you can follow DimiterS’s suggestion, run Isiniteg on the database to fix the logical corruption. Thanks, Evan

Hi GaneshKumar Anand, For Event ID 1173 about “Error 0x6bb”, we can just ignore it. you can know more detail form this document: Event 1173 is logged in the Application event log in Exchange Server 2003 http://support.microsoft.com/kb/913126 From your other information, this may your database has logical corruption, you can follow DimiterS’s suggestion, run Isiniteg on the database to fix the logical corruption. Thanks, Evan

Thanks! i appreciate that.Regards, Ganesh, MCTS, MCP, ITILV2