Re: Merge/FTP schema propogation failure

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Damien wrote:
Hi Guys,

Trying to fathom out my replication issues...

Got two boxes running SQL Server 2000, reporting version 8.00.2162.
Trying to set up Merge replication between them, using FTP.
Publisher/Distributor is Windows 2000, Subscriber is Windows 2003.

SQL Server and the Agent are both running under the same domain account
on both machines. (Both machines being in the same domain). There are
no firewalls between them.

When I try to create the subscription, and start synchronisation, the
agent times out on the ftp connection, and eventually fails, reporting
"The schema script '' could not be propogated to the subscriber". There
is also a hint in the ftp failure message that this could be due to IE
being configured for dial-up. I'm not sure whether that warning is
*telling* me that IE IS configured for dial-up, or if it's just
suggesting a vaguely possible cause.

Creating a subscription from another machine (also in the same Domain,
no firewalls, sql running as local system, agent running as a different
domain user (who is sa on both boxes)), under windows XP, succeeds, so
I think the publication is set up right. Manually FTPing from the
Windows 2003 box, using the correct username and password, works, to
the point where I can download all of the snapshot files.

Examining the FTP logs on the publisher, the subscription attempt isn't
even getting across to it.

Hopefully the above is enough for someone to come up with a suggestion
for what to look at next. I've tried running the subscription agent
under an sa user (on both machines), as the user account under which
the services are running, and as the sa itself. In all cases, the error
is the same.

As a side note, I tried setting the Merge Agent location to Distributor
rather than subscriber, and received an error concerning a null
connection. Don't know if this is in any way related though - I'm just
floundering now.

Whilst I could set up a fully trusted, non anonymous subscription while
we're doing this development work, the final configuration includes a
firewall in the middle, and the subscriber being out of the domain.
Strangely, we already have a working Merge/FTP replication set up on
the live servers, and it works fine.

Well, enough rambling, can anyone point me in the right direction?

Damien

After a few false alleys, we logged onto the box, using the domain user
account which the services run under, and attempted to FTP to the
publisher server. It worked, and the replication now can succesfully
reach the FTP server (even after we've logged out again). This does
confuse me, since that's normally the solution for problems like NTLM
double-hops, which shouldn't be involved in computer name lookups/FTP.
But it seems to have sorted it. For how long, that's another
question...

Damien

.



Relevant Pages

  • Re: Host Name Change and Replication
    ... the msdb.sysjobs did still contain PDB01 as the server originator and this caused the 14274 error about the MSX. ... I then added accountName user to the Security folder again, reenabled replication, and then made sure each agent was using the accountName and tested the replication. ... Unfortunately on DGP09 and TDB10 in their> subscription folder each had a push subscription pointing to PDB01 which no> longer exsists. ...
    (microsoft.public.sqlserver.server)
  • NT Group user not in PAL, error in Snapshot Agent log
    ... We are using merge replication from a SQL Server 2008 server to SQL ... subscription whose credentials are a user in that NT group, ...
    (microsoft.public.sqlserver.replication)
  • Re: Web Replication
    ... You can use any type of replication with ftp. ... Director of Text Mining and Database Strategy ... Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.replication)
  • Re: Suspended Merge Replication Job
    ... that's not the error message. ... Management> SQL Server Agent> Jobs). ... This isn't the subscription as shown ... through the Replication Monitor. ...
    (microsoft.public.sqlserver.replication)
  • Re: attaching subscription database woes
    ... Run SQL Server agent under a local admin account on the subscriber. ... Looking for a SQL Server replication book? ... My plan is to ship copies of a subscription ...
    (microsoft.public.sqlserver.replication)