"eAW" <anwang@mailcity.com> wrote in message
news:OEcQRrAtFHA.2076@TK2MSFTNGP14.phx.gbl...
> We used to use pure continuous Transactional Replication to replicate our
> data with no problems. Due to business requirements change, we need to
> update data at subscriber occasionally.
>
> After the publication and push subscriptions were set up successfully, we
> can replicate data from publisher to subscribers without any problems.
> However, we receive the following error message when tring to update the
> data at subscriber.
>
> Server: Msg 18456, Level 14, State 1, Line 4
> Login failed for user 'sa'.
>
> Anybody knows where is the error from. All agents are started successfully
> and the user is not 'sa'.
>
> Regards,
>
>

"Hilary Cotter" <hilary.cotter@gmail.com> wrote in message
news:e5JLLWBtFHA.1168@TK2MSFTNGP11.phx.gbl...
> http://support.microsoft.com/default.aspx?scid=kb;en-us;320773
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "eAW" <anwang@mailcity.com> wrote in message
> news:OEcQRrAtFHA.2076@TK2MSFTNGP14.phx.gbl...
> > We used to use pure continuous Transactional Replication to replicate
our
> > data with no problems. Due to business requirements change, we need to
> > update data at subscriber occasionally.
> >
> > After the publication and push subscriptions were set up successfully,
we
> > can replicate data from publisher to subscribers without any problems.
> > However, we receive the following error message when tring to update the
> > data at subscriber.
> >
> > Server: Msg 18456, Level 14, State 1, Line 4
> > Login failed for user 'sa'.
> >
> > Anybody knows where is the error from. All agents are started
successfully
> > and the user is not 'sa'.
> >
> > Regards,
> >
> >
>
>