RE: Re-installing SP4

Thanks for the reply Raymond

I'm guessing the problem was probably caused by running SP4 with an account
with lower permissions.

I will try unregistering the components with the service account but what is
the command / what do I un-register?

I'll let you know the outcome.

Many Thanks again

Daryl

"Raymond Mak [MSFT]" wrote:

> Hi Daryl,
>
> The most important thing to check first is whether the replication Interface
> guids are improperly ACL'd w.r.t. to your SQL Server Agent account. If so,
> you may need to un-register and then re-register the replication components
> under a high privileged account just so the ACLs on the replication guids are
> refreshed. You can, of course, manually update the ACLs also. However, I am
> guessing that you want a cleaner approach so you are wondering if an SP4
> reinstall will work. My take is that since we don't fully understand why the
> problem happened in the first place, a reinstall may lead you to the same
> problem with a slight risk of aggravating other parts of the system (well, I
> am chicken :). As to why the ACLing problem happened in the first place, I do
> have the following semi-educated guesses:
>
> 1) SP4 setup could not retrieve information for the SQL Server Agent service
> account and so cannot add it to the ACLs of the replication component reg
> keys. This may be a domain issue if SQL Server Agent service account is a
> domain account or the account running SP4 setup simply doesn't have enough
> privilege to enumerate the Agent service account information.
> 2) The SQL Server Agent service account was changed outside of Enterprise
> Manager after SP4 install.
>
> I can be completely wrong above but in any case, it would be tremendously
> useful if you can let us know of anything unusual when you first set up SP4.
>
> Thanks much.
>
> -Raymond
>
> "DJ" wrote:
>
> > I posted a week or so ago about replication breaking after I installed SP4.
> >
> > Raymond Mak queried about the login account I used and suggested registering
> > the dll's.
> >
> > I did this but to no avail. I was wondering if I could re-run the SP4
> > install using the SQL Server account and if I need to do anything first.
> > i.e. can I rerun it straight away on a server already with SP4?
> >
> > As the agents work from the command line, I'm sure the problem is dll / DCom
> > related but I'm not sure how to trace this further.
> >
> > Any suggestions would be appreciated.
> >
> > Thanks!
> >
> >
> >
.

Relevant Pages

  • Re: Re-installing SP4
    ... > I will try unregistering the components with the service account but what ... >> guessing that you want a cleaner approach so you are wondering if an SP4 ... >> 1) SP4 setup could not retrieve information for the SQL Server Agent ... >> privilege to enumerate the Agent service account information. ...
    (microsoft.public.sqlserver.replication)
  • Re: Error 0x800A0046
    ... This bit sounds exactly like the issue I'm having on a W2K server SP4. ... Little icon appearing, click it, it disappears, only to come back ... domain account. ...
    (microsoft.public.windowsupdate)
  • Re: SP4 and n-2 password protection?
    ... DC from SP3 and a win2K server. ... account was locked out. ... Win2k SP4 DC in Native mode with Exchange 2K ...
    (microsoft.public.win2000.security)
  • Re: Re-installing SP4
    ... agent (using the loacal admin account) but I still get the same error. ... There was nothing unusual when I first ran SP4, ... >>> guids are improperly ACL'd w.r.t. to your SQL Server Agent account. ... >>> privilege to enumerate the Agent service account information. ...
    (microsoft.public.sqlserver.replication)
  • RE: LogonUser Error -1314 on Window2000
    ... Is this Win2000 SP4? ... have you tried to grant the "impersonate a ... user" privilege to the ASP.NET account? ... I also granted the "Act as part of the operating system" privilege to the ...
    (microsoft.public.dotnet.framework.aspnet.security)