sql server replication:
Make sure 1) your account you are pulling with from the subscriber is in the PAL on the publication 2) the PAL account is also in the dbo_role in the distribution database, or the account you are using to connect to the distributor is in the dbo_role distribution database 3) make sure the NT account you are using for FTP has read and list files and folders permission on the root of your virtual directory of the ftp site. 4) enable replication agent logging to see exactly what the error is Here is a guide to replicating over the internet which may help. http://www.dbazine.com/sql/sql-articles/cotter4 -- Hilary Cotter Director of Text Mining and Database Strategy RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. 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 [quoted text, click to view] "Damien" <Damien_The_Unbeliever@hotmail.com> wrote in message news:1151488848.925166.150570@m73g2000cwd.googlegroups.com... > 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 >
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
[quoted text, click to view] 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
Don't see what you're looking for? Try a search.
|