Re: Need help urgently - Replication ERROR 18456

Can you set up the sql server agent on both boxes to use the same domain
account and add it to the local administrators group on each box then see if
this helps.
Cheers,
Paul Ibison



<war_wheelan@xxxxxxxxx> wrote in message
news:1127221547.595236.97980@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>I have been trying to get replication working for a month now with no
> luck. I have tried all of the suggestions to fix 'ERROR 18456' and
> none have worked.
>
> Most of the suggestions talk about enabling mixed mode authentication.
> The server has always been in mixed mode and I can login to query
> analyzer with either the Windows or SQL accounts. I have also tried
> adding the login to the db_Creators role for the db and changing the
> account which runs the distribution agent amongst other things.
>
> BACKGROUND
>
> Replication was working correctly until I detached and copied the db to
> another server so that they would be identical. The other server is
> the destination of replication. I GENERATED A SQL SCRIPT OF THE
> REPLICATION SETUP BEFORE DETACHING THE DB. After syncing up the two
> dbs, I re-enabled replication. It worked replication was re-enabled
> with all of the appropriate tables, but the distribution agent couldn't
> login in to the subscribers (There are two). The account listed in the
> error has system admin rights to the server and db. I can login
> manually to either subscriber with my SQL or Windows accounts.
>
> At this point, I disabled replication and decided to set it up from
> scratch. I received the same error this time while setting up
> replication so it failed with the now infamous ERROR 18456.
>
> CAN SOMEONE PLEASE HELP ME UNDERSTAND THIS BETTER. I know that agents
> control replication and I have tried to change the accounts which these
> run under.
>
> LASTLY, WHEN I SETUP REPLICATION FROM SCRATCH I RECEIVE THE ERROR 18456
> FOR AN ACCOUNT THAT I WASN'T LOGGED IN UNDER. THE ACCOUNT IN QUESTION
> IS A MEMBER OF THE DB_OWNER ROLE FOR THE DB AS IS MINE.
>
> CAN SOMEONE PROVIDE ME WITH A TROUBLESHOOTING METHODOLOGY TO ATTEMPT TO
> RESOLVE THIS PROBLEM?
>


.

Relevant Pages

  • Re: Different Directory Information Trees
    ... I think that was a DC account password issue that I have since cleaned up. ... I noticed some NTDS Replication 1955 and 1083 errors that come together. ... Weird side-effect I also noticed was that I can no longer launch the Active Directory related Management tools from my workstation unless I use the Active Directory Management MMC. ... I noticed a lot if DNS 4015 errors on the server it appears that the DNS or Active Directory is "busy". ...
    (microsoft.public.windows.server.active_directory)
  • Re: Active directory connector replication between 2 domains
    ... > account with service account admin rights. ... >> General tab? ... >>> I am having a problem with ADC replication between my Ex 5.5 directory ... >>> have the ADC running and one Exchange server 2003 installed. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Error at parameter 93 during datastream processing of paramete
    ... the distribution agent fails with the message. ... Message: Replication-Replication Distribution Subsystem: agent ... Source: ODBC SQL Server Driver ... > pack/hotfix level on each of the servers involved in this replication setup? ...
    (microsoft.public.sqlserver.replication)
  • Re: Publishers disappeared from under replication monitor
    ... Basically the only database on the server being replicated suddenly had 'no' ... This seemed like some kind of corruption in the database. ... The next day we set up transactional replication again (Yes, ... > distribution agent name you can get a condition like this. ...
    (microsoft.public.sqlserver.replication)
  • Re: Swing didnt Swing - Help!!
    ... TEMP DC or the Final Box when Replication is occurring it will not complete and your problem will occur. ... I used my>> laptop ... >> which is a member of the "orginal" domain server and connected it to>> the ... >> is down or utherwise unavailable, or because your computer account>> was ...
    (microsoft.public.windows.server.sbs)
Loading