FYI, when the client rebuilt the farm using default install location and did exactly the same steps apart from that. They could create the indexer fine.
I didn't get a chance for them to try a UNC path (internal Microsoft recommendation) as they'd already rolled back their environments to pre-moss install. Might have a go at a PoC to prove this if I get time! Jeremy Thake Readify | Senior Consultant Perth | WA 6000 | Australia M: +61 400 767 022 | E: [EMAIL PROTECTED] | W: www.readify.net | B: www.made4the.net -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeremy Thake Sent: Friday, 24 October 2008 3:34 PM To: listserver@ozMOSS.com Subject: [OzMOSS] RE: Configure an indexer in SSP: "The path for the index location is not valid" Yes, this worked only when we set it to the central admin server, not the second app server. Jeremy Thake Readify | Senior Consultant Perth | WA 6000 | Australia M: +61 400 767 022 | E: [EMAIL PROTECTED] | W: www.readify.net | B: www.made4the.net -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Nemtsev Sent: Friday, 24 October 2008 2:46 PM To: listserver@ozMOSS.com Subject: [OzMOSS] RE: Configure an indexer in SSP: "The path for the index location is not valid" Did you try to use stsadm to set the indexer path manually? Michael Nemtsev | WSS MCTS, MS MVP Readify B: http://msmvps.com/blogs/laflour/ T: +61 424 184 978 E: [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeremy Thake Sent: Friday, October 24, 2008 1:43 PM To: listserver@ozMOSS.com Subject: [OzMOSS] Configure an indexer in SSP: "The path for the index location is not valid" A client is getting an error when trying to configure an indexer in an SSP. "The path for the index location is not valid" If I create the indexer on the central administration server it works fine, but if I try and create it on the second app server that is allocated the 'Office SharePoint Server Search' service to it throws this error. The path I am configuring it to exists on both servers and the security permissions are the same. I googled the error and only one real suggestion came up which was that someone had this issue when MOSS was installed not in the default location. I checked, and the client had installed it on 'D:\SharePoint Server 2007\12.0'. Their Dev environment doesn't have a second app server, so the indexer role is on central admin and runs fine. It appears to be because the indexer is on a machine other than central admin! BTW - This has all been done via the Central Admin UI. Has anyone else had any experience with installing MOSS in the not default location? or any issues with creating an indexer on a separate server to Central Admin? Cheers, Jeremy Thake Readify | Senior Consultant Perth | WA 6005 | Australia M: +61 400 767 022 | E: [EMAIL PROTECTED] | W: www.readify.net | B: www.made4the.net ------------------------------------------------------------------- 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 ------------------------------------------------------------------- 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
