Re: Re-installing SP4

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi Daryl,

For exe COM servers, you just need run the executable with the /UnRegServer
parameter followed by running it with the /RegServer parameter, e.g.
snapshot.exe /UnRegServer&snapshot.exe /RegServer. For dll COM components in
the 80\COM directory, you just need to run regsvr32 /u followed by regsvr32
on it, e.g. regsvr32 /u replagnt.dll&regsvr32 replagnt.dll.

-Raymond
"DJ" <DJ@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FAA6361C-AB9E-468F-B998-212EB2EE18A9@xxxxxxxxxxxxxxxx
> 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'm guessing the problem was probably caused by running SP4 with an account ... I will try unregistering the components with the service account but what is ... > guids are improperly ACL'd w.r.t. to your SQL Server Agent account. ...
    (microsoft.public.sqlserver.replication)
  • Re: Browsing for Publication error message
    ... what is going on with the description you gave previously but I would guess that the subscriber SQL Server Agent service account was somehow added to the publication access list of the publication on the DMZ. ... select from the MSpublication_access table in the distribution database and see if the account for your Subscriber's SQL Server Agent service account shows up. ...
    (microsoft.public.sqlserver.replication)
  • Re: Problems with SQL Srv. Agent and Proxy Account
    ... Windows Account. ... SQL Server Agent, try adding this account to the local ... >Password verification of the 'SQLAgentCmdExec' proxy ...
    (microsoft.public.sqlserver.security)
  • Re: Distributor SQLSERVERAgent Account
    ... your subscriber's sql server agent should be running ... under the same account as the publisher's SQL Server agent, ... that is part of the local admin group on the publisher. ... If this is not possible the SQL Server agent account on the subscriber ...
    (microsoft.public.sqlserver.replication)
  • Re: Problems with SQL Srv. Agent and Proxy Account
    ... You need to go to the General Tab of the SQL Server Agent ... >I have tried with both the sa account and with Use Windows ...
    (microsoft.public.sqlserver.security)