Re: Merge Agent error number 53 for replication

From: Joe Mine (huytuanattpgdotcomdotau)
Date: 03/12/04

  • Next message: Sabri AKIN: "RE: Stopping sqlserver" 
    Date: Fri, 12 Mar 2004 18:01:22 +1100

    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)
    > > >
    > >
    >
    > --------------------------------------------------------------------------
    > > --
    > > > -----------------------------------
    > > >
    > > >
    > > >
    > >
    > >
    >
    >

  • Next message: Sabri AKIN: "RE: Stopping sqlserver"

    Relevant Pages

    • Re: trans replication of large tables...
      ... Yes, but I tend not to use the snapshot agent to generate the data, and the ... and put the tables into the subscriber by manual methods like ... How to setup the ?UseInprocLoader on the distributor agent so it don?t ...
      (microsoft.public.sqlserver.replication)
    • RE: Merge pull subscription -- Applying snapshot from alternate UN
      ... In one line my objective is to apply the initial snapshot from the CD or UNC ... Even if the subscriber needs to connect to web server to get some ... Using RMO to create the subscription and start the merge agent ... Microsoft Online Community Support ...
      (microsoft.public.sqlserver.replication)
    • Re: Snapshot agent job roles
      ... merge and not transactional/snapshot replication. ... you'll have a merge agent at the subscriber for a pull subscription. ... controls the propagation of the snapshot when the initialization takes place, ...
      (microsoft.public.sqlserver.replication)
    • Re: Adding a primary key to a subscribed SQL 2000 table
      ... You need to include the include DRI option in your table articles snapshot ... You can't really do this in a deployed environment without re-initializing. ... and manually create PKs on the subscriber tables, ... Looking for a SQL Server replication book? ...
      (microsoft.public.sqlserver.replication)
    • Re: Snapshot or merge replcation propagation problem
      ... Your publisher is unable to connect to your subscriber. ... In SQL 2000 to make this change expand the replication folder, ... merge agents folder, locate your merge agent, right click on it select agent ... Looking for a SQL Server replication book? ...
      (microsoft.public.sqlserver.replication)
    • Quantcast