Re: Merge Agent error number 53 for replication

From: Hilary Cotter (hilaryk_at_att.net)
Date: 03/12/04 

Date: Fri, 12 Mar 2004 08:07:50 -0500

I take it you have moved to using SQL Server Standard security in your
enabled subscriber.

Is this account in the PAL for the publication. Right click on your
publication in the publication database, select publication properties, and
go to Publication Access List. The account you are using must be in the
server administrator role on the subscriber, and in the dbo role on the
publication database. It also must be present in the PAL.

Also verify that the password you are using is correct. To do this, go to
Tools-Replication-Configure Publishers, Distributors, Subscribers, click on
the Subscribers tab, and locate your Subscriber. Then click on the browse
button to the right of your Subscribers, and then in the Use SQL Server
Authentication enter the correct information.

"Joe Mine" <huytuanattpgdotcomdotau> wrote in message
news:OeNZV$$BEHA.1588@tk2msftngp13.phx.gbl...
> Now I even got error no: 1326
>
>
> The schema script
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_Northwind_NorthwindMercuryPub1\20040
> 311181629\snapshot.pre' could not be propagated to the subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> -------------------------------------------------------------------------- 

--
> -----------------------------------
> The process could not read file
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_Northwind_NorthwindMercuryPub1\20040
> 311181629\snapshot.pre' due to OS error 1326.
> (Source: ECSWEB (Agent); Error number: 0)
> --------------------------------------------------------------------------
--
> -----------------------------------
> Logon failure: unknown user name or bad password.
> (Source:  (OS); Error number: 1326)
> --------------------------------------------------------------------------
--
> -----------------------------------
>
> "Joe Mine" <huytuanattpgdotcomdotau> wrote in message
> news:#8btBY#BEHA.3784@TK2MSFTNGP10.phx.gbl...
> > Hilary,
> >          I just ran the select working_directory on the Distributor and
> this
> > is the results:
> > working_directory
> >
> > \\Mercury\REPLDATA
> >
> > \\Mercury\REPLDATA
> >
> > \\Mercury\REPLDATA
> >
> > \\MERCURY\G$\Program Files\Microsoft SQL Server\MSSQL$MERCURY\ReplData
> >
> >
> >
> > Yes I can net use * \\Mercury \REPLDATA   and navigate to the
snapshot.pre
> > file.
> >
> > Regards
> >
> >
> >
> >
> > "Hilary Cotter" <hilaryk@att.net> wrote in message
> > news:uPeVrH#BEHA.2404@TK2MSFTNGP11.phx.gbl...
> > > notice the unc path is completly wrong.
> > >
> > >
> >
>
\\Mercury\REPLDATA\unc\MERCURY$MERCURY_Northwind_NorthwindMercuryPub1\200403
> > > 11181629\
> > > its the dollar sign which I think is messing you up.
> > >
> > > can you run run a net use * \\Mercury\REPLDATA on your subscriber and
> see
> > if
> > > you can map this drive. Then try to navigate upwards to the
snapshot.pre
> > > file?
> > >
> > > Also if you could run this on your publisher/distributor and report
back
> > > here with what you get it will be helpful
> > >
> > > select working_directory from msdb.dbo.MSdistpublishers
> > >
> > >
> > > "Joe Mine" <huytuanattpgdotcomdotau> wrote in message
> > > news:#ONwfV3BEHA.576@TK2MSFTNGP11.phx.gbl...
> > > > Hi, I am trying to setup replication between 2 SQL Servers across
> > > > non-trusted domains(2 different domains). I am able to successfully
> > > > registered both SQL servers in either domains. But I still cannot
> access
> > > the
> > > > snapshot folder in the Distributor/Publisher domain from the
> subscriber
> > > > domain.
> > > > * I've create the same SQL login: SQLAdmin and use this SQL
> > authentication
> > > > on both the distributor and subscriber to interact with each other.
> They
> > > can
> > > > access each other fine, accept the subscriber cannot access the
> snapshot
> > > > folder on the distributor.
> > > > * I've given the Snapshot folder UNC path and Administrative share
the
> > > > everyone permission.
> > > > ********
> > > > I've read these Microsoft documents already:
> > > > Q321822 - Replicate between computers running SQL Server in
> Non-Trusted
> > > > Domains or Across the Internet.
> > > > Q240688 - Replication Subscribers Unable to Synchronize with Pull
> > > > Subscription.
> > > >
> > > > Objective: I cannot create a pass-through account because the
> > Distributor
> > > is
> > > > installed upon a Win2k Domain controller (with active directory),
but
> I
> > > have
> > > > use SQL authentication on both SQL Server, but it still cannot
access
> > the
> > > > snapshot folder. All I need is for the subscriber to access the
> snapshot
> > > > folder. What do I need to do? Please list the steps, thanks...
> > > >
> > > >
> > > > *********************************************
> > > > The schema script
> > > >
> > >
> >
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_Northwind_NorthwindMercuryPub1\20040
> > > > 311181629\snapshot.pre' could not be propagated to the subscriber.
> > > > ****************************
> > > >
> > > > The schema script
> > > >
> > >
> >
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_Northwind_NorthwindMercuryPub1\20040
> > > > 311181629\snapshot.pre' could not be propagated to the subscriber.
> > > >
> > > > (Source: Merge Replication Provider (Agent); Error
> number: -2147201001)
> > > >
> > >
> >
>
> --------------------------------------------------------------------------
> > > --
> > > > -----------------------------------
> > > >
> > > > The process could not read file
> > > >
> > >
> >
>
'\\Mercury\REPLDATA\unc\MERCURY$MERCURY_Northwind_NorthwindMercuryPub1\20040
> > > > 311181629\snapshot.pre' due to OS error 53.
> > > >
> > > > (Source: ECSWEB (Agent); Error number: 0)
> > > >
> > >
> >
>
> --------------------------------------------------------------------------
> > > --
> > > > -----------------------------------
> > > >
> > > > The network path was not found.
> > > >
> > > > (Source: (OS); Error number: 53)
> > > >
> > >
> >
>
> --------------------------------------------------------------------------
> > > --
> > > > -----------------------------------
> > > >
> > > > *************************
> > > >
> > > > The schema script '\\MERCURY\G$\Program Files\Microsoft SQL
> > > >
> > >
> >
>
Server\MSSQL$MERCURY\ReplData\unc\MERCURY$MERCURY_Northwind_NorthwindMercury
> > > > Pub1\20040306225703\snapshot.pre' could not be propagated to the
> > > subscriber.
> > > >
> > > > *************************
> > > >
> > > > The schema script '\\MERCURY\G$\Program Files\Microsoft SQL
> > > >
> > >
> >
>
Server\MSSQL$MERCURY\ReplData\unc\MERCURY$MERCURY_Northwind_NorthwindMercury
> > > > Pub1\20040306225703\snapshot.pre' could not be propagated to the
> > > subscriber.
> > > >
> > > > (Source: Merge Replication Provider (Agent); Error
> number: -2147201001)
> > > >
> > >
> >
>
> --------------------------------------------------------------------------
> > > --
> > > > -----------------------------------
> > > >
> > > > The process could not read file '\\MERCURY\G$\Program
Files\Microsoft
> > SQL
> > > >
> > >
> >
>
Server\MSSQL$MERCURY\ReplData\unc\MERCURY$MERCURY_Northwind_NorthwindMercury
> > > > Pub1\20040306225703\snapshot.pre' due to OS error 53.
> > > >
> > > > (Source: ECSWEB (Agent); Error number: 0)
> > > >
> > >
> >
>
> --------------------------------------------------------------------------
> > > --
> > > > -----------------------------------
> > > >
> > > > The network path was not found.
> > > >
> > > > (Source: (OS); Error number: 53)
> > > >
> > >
> >
>
> --------------------------------------------------------------------------
> > > --
> > > > -----------------------------------
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>