A couple of users on the same Exchange 2007 SP2 database are having issues with search function in both Outlook and OWA. Was going to try the steps here http://technet.microsoft.com/en-us/library/aa995966(EXCHG.80).aspx using the resetsearchindex.ps1 script. I've tried this on a test server we run and am unclear about a few things. 1. Can this be run during the day or should it be weeknight only? 2. How long will this take to run on a 150GB database roughly? I understand that users won't be able to search until the catalog rebuild is complete, so are we looking at 10 mins, 10 hours etc? I have no idea. 3. Any risk associated with this? 4. When I run on the test server, I keep getting prompted - "do you want to delete various Catalog-Dataxxxxx" files. Do I just select YES TO ALL? Otherwise I have no idea how many times I need to press the Y button. Thanks for any help.

You should follow the technet instructions and run this after hours. Make sure you have logging turned down for things like logons. You should also consider installing the various filter packs they have for Office and Adobe. We have done this on many production databases without any issues.

On Mon, 4 Apr 2011 20:55:38 +0000, Wyclef1 wrote: >A couple of users on the same Exchange 2007 SP2 database are having issues with search function in both Outlook and OWA. > >Was going to try the steps here http://technet.microsoft.com/en-us/library/aa995966(EXCHG.80).aspx using the resetsearchindex.ps1 script. > >I've tried this on a test server we run and am unclear about a few things. If you don't mind using the manual process it's not hard. Stop the service, delete the catalog directory, start the service. >1. Can this be run during the day or should it be weeknight only? You can. >2. How long will this take to run on a 150GB database roughly? I understand that users won't be able to search until the catalog rebuild is complete, so are we looking at 10 mins, 10 hours etc? I have no idea. That depends on the database and whether or not you have the filter pack installed (so attachments can be indexed, too). It might take 10 minutes. It might take 30. I don't think it'll take ten hours, though. Whether the on-line search is used depends on the client. OWA will use it. Outlook might use it, but it depends on the Outlook version, the operating system, if Outlook is working in cached mode, and whether Windows Desktop Search is installed and running. >3. Any risk associated with this? Not much. >4. When I run on the test server, I keep getting prompted - "do you want to delete various Catalog-Dataxxxxx" files. Do I just select YES TO ALL? Otherwise I have no idea how many times I need to press the Y button. That's why I use the manual process. :-) --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

1. run it in off hours, your users will appriciate it. 2. Depends on processor, storage, connectivity, etc. Think about it, churning through 150GB in 8K chunks while you recalculate and write a variable length index file (5-10% of the database size or 7.5 to 15GB). It's going to take several hours most likely. John

a couple of hours is what have seen in real life. but it is dependant of how beefy your hardware and disksystem is. lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com

Thanks all. I see there is a way re-index the database, but I assume there isn't a way to recreate the catalog only for a specific user/users? Also, if there is an issue with the catalog for one database, wouldn't this mean that they can't search anyway online, so it wouldn't make a difference if we did run this in daylight hours?

Thanks all. I see there is a way re-index the database, but I assume there isn't a way to recreate the catalog only for a specific user/users?

Hi, · “1. Can this be run during the day or should it be weeknight only?” It will affect OWA and Outlook on line model experience. In Cached Exchange Mode, Outlook uses Windows Search, rebuilt CI will not affect client experience. So you could do it during day or not. 2. How long will this take to run on a 150GB database roughly? I understand that users won't be able to search until the catalog rebuild is complete, so are we looking at 10 mins, 10 hours etc? I have no idea. I also don’t know how long it will cost. But you can rebuilt CI based database. Once rebuilt CI for a database 3. Any risk associated with this? Your indexing catalogs are located within the same folder as database. C:\Program files\Microsoft\Exchange server\mailbox\First storage group If you have multiple databases homed within the single folder , you may find more than one Catalogs created. After backing up the catalogs file, there will not any risk. 4. When I run on the test server, I keep getting prompted - "do you want to delete various Catalog-Dataxxxxx" files. Do I just select YES TO ALL? Otherwise I have no idea how many times I need to press the Y button. From the warning message “delete various Catalog-Dataxxxxx”, I think you just need to press “Y” same times as the number of database.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks All. Jerome, as regards your comment here: "In Cached Exchange Mode, Outlook uses Windows Search, rebuilt CI will not affect client experience. So you could do it during day or not." Are you saying that when a client is in Online Outlook/OWA mode, they are using Exchange search, but when they are in cached mode, they are using a local technology (Windows Search) to search Outlook?

yes. that 's right.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.