Hi Paul, Thanks for shedding some light on this. Could you please explain a little further as to what is required to be done. I read the kb and its talking about resetting the index.
I just wanted to confirm the steps as I really don't want to stuff up the live solution, as all hell will break loose. Regards, Trent Allday TAD Solutions | P: (03) 9018 9040 | F: (03) 9769 7561 | M: 0418 745 253 | W: TadSolutions.com.au From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Culmsee Sent: Tuesday, 22 July 2008 3:49 PM To: listserver@ozMOSS.com Subject: RE: [OzMOSS] RE: MOSS Search Sorry guys I haven't been following this thread until now, but as soon as saw "stuck on crawling" it made me think of a recent problem I had with SQLSP1, maintenance plans and corrupt indexes http://www.cleverworkarounds.com/2008/07/09/office-server-search-memory-leak-and-stuck-on-crawling/ Also check the personalisation service permissions of the crawler account in the SSP. I've seen this stick because the crawler can't access the user profile store. Hope that helps Paul From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Trent Allday Sent: Tuesday, 22 July 2008 1:39 PM To: listserver@ozMOSS.com Subject: RE: [OzMOSS] RE: MOSS Search Yeah correct. SQL is own its own machine. Web server on own machine. AD on own machine. All on same network and domain. My test env is on one env (nice easy :)). Regards, Trent ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com
