Have you tried re-indexing your site?

support.microsoft.com/default.aspx

Make sure indexing server  can communicate with the front-end server using Netbios traffic. Indexes are being propogated using File Copy

Closure to my problem….

I called Microsoft support and added  the one service  account to all 3 portal servers to local Administrators group to resolve the issue. Windows 2003 SP1 security changes were too tight and it did not work right from the installation instruction that comes with the portal. KB article http://support.microsoft.com/?kbid=555309

i have the service  account in power users group. the only thing that didnt work was that i had to give the account local launch permissions for IISWAMREG in dcom. this is with sps/wss 2003 sp2. i have exactly the same config as you (medium farm).

giving a service account administrative privs is just plain wrong (the unix comes out, yes). Does Andy David, MVP read these groups?

I agreed that is NOT a good thing to do. So if I understand how to down grade it, I will do so.

Yes, I have the sps/wss 2003 SP2 on windows 2003 Sp1.

Can you explain to me how to give that account to IISWAMREG and which server  do I do it on?

(on each index,job,search,web)
start>run>dcomcnfg
expand - component  services>computers>my computer>DCOM Config

find IISWAMREG; right click select properties. under security select edit under "launch and activation permissions". give your sp service  account(application pool) "Allow" to local launch.


my setup (basically from the reccomended setups in the resource kit) is:

2 service accounts and 1 security group

spservice (app pool identity)
spcrawl (crawl account)
SPPSAdmins (security group)

make sure and put both accounts in that group and then under the "set sharepoint administrator group account", type in the security group you created.

No. I don’t  see any DCOM error. I have to try it out and see.