Cheers Matthew, I've already done the directory security checks. What would your approach be to raise the "trust of that location"?
I've checked all the event logs for Application, Security and System and there's nothing there. The Hive logs on each machine don't elaborate much either, basically logs that the web service throws a soap exception of the same error, but even with verbose turned on nothing else coming through :-( 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 Matthew Cosier Sent: Friday, 24 October 2008 12:43 PM To: [email protected] Subject: RE: [OzMOSS] Configure an indexer in SSP: "The path for the index location is not valid" Strange - maybe it's a CAS related issue, sure its not throwing a security exception internally? Might be worth raising the trust of that location. Other than that - not sure. ACLs would have been my other guess....but you say the security is fine? Might be worth just ensuring that the crawler account has read/write perms on that directory anyway (or refresh the perms for the crawler + app pool accounts). m -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeremy Thake Sent: Friday, 24 October 2008 1:43 PM To: [email protected] 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
