Re: solving the problem of spsearch
- From: "callahan" <cacallahan@xxxxxxxxxxxxxxxxxxx>
- Date: Thu, 1 Mar 2007 21:27:30 -0500
Actually, the dcom in question is IIS wamreg (if I'm not mistaken, something
like a class id of 617 something), and if you give the configuration
database access account, and the content database account launch activation
rights for the dcom, and if you do that it solves those errors in the event
viewer.
But I have found that you can have errors with search even after that. And
when I have had the search errors combined with the VSS errors, only a
reboot fixes it. But, a reboot does do the job when nothing does.
-callahan
<jscott@xxxxxxxxxxxxxxxxx> wrote in message
news:1172703724.925067.73420@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Okay - I solved my own issue. I was getting the same Volume Shadow
Copy service (VSS) errors and registry hive errors others have posted
on this site. As I mentioned in my previous post, I was able to get
the service to run if I put my service account into the local machine
administrator's group, so I was fairly certain that this was a
security/permissions related issue.
After a lot of tinkering with COM launch permissions (which didn't
seem to help anything), I set a Failure audit for my service account
on my local drives (both the system root - "C" and my data partition
where I pointed the search indexing). When I tried to launch the
search service, I checked the security log and sure enough, I had a
raft of failure audit events. By going through each one and granting
the appropriate read/write access to the numerous folders I was able
to get the search service to run without error.
I hope this helps someone, and I'm wondering why Microsoft's setup
guide doesn't mention the local machine permissions that are needed
for this to work correctly in a farm configuration with a generic
(i.e. non-administrator) domain account.
On Feb 28, 2:26 pm, jsc...@xxxxxxxxxxxxxxxxx wrote:
I'm having the exact same error as everyone else. Here's my
configuration:
1. WSS 3.0 fresh install
2. Server Farm Environment
3. Using a service account with minimal permissions for the search
service, AppPool, WSS Service identity.
When I grant the service account local machine administer permissions,
the service starts just fine and when I take it out of the local
machine administrator group I won't start, so I know this is a
permissions issue. I think it's something with DCOM launch/activation
permissions but I've set that for every application I can think of.
I'm stumped.
On Feb 2, 12:29 am, "kurt-o" <kurt.hutchin...@xxxxxxxxx> wrote:
Hi All,
I'm having these same issues pretaining to getting the sharepoint 2007
search services running.
Strange enough as it is.... I've gotten this to work on a single
server instance where sharepoint configures/installs mssql. However
when installing on a box with a full sql server 2005 instance I have
problems with the search service.
Does anyone have any updates or some gotchas with doing the "farm"
installation method?
-Kurt
On Jan 17, 3:32 pm, Timo Tapupere wrote:
Hello!
I was having the exact same trouble as everybody else on this thread,
but I found a solution to my problem. I tried all the other solutions
(besides reinstalling) and nothing worked. I also have a sit migrated
from v2 to v3. I simply had to change the Application pool to use
system account in IIS and all my problems were magically solved. No
more annoying messages in event and search is working perfectly. Hope
this helps somebody.
Regards
Timo
EggHeadCafe.com - .NET Developer Portal of
Choicehttp://www.eggheadcafe.com-Hide quoted text -
- Show quoted text -- Hide quoted text -
- Show quoted text -
.
- Follow-Ups:
- Re: solving the problem of spsearch
- From: callahan
- Re: solving the problem of spsearch
- References:
- Re: solving the problem of spsearch
- From: jscott
- Re: solving the problem of spsearch
- Prev by Date: Cannot complete this action error on top level sites?
- Next by Date: WSS 3.0 cannot extract user properties from Active Directory (AD)
- Previous by thread: Re: solving the problem of spsearch
- Next by thread: Re: solving the problem of spsearch
- Index(es):
Relevant Pages
|
