Synchronise using FTP for Snapshot Location Fails - Merge Replication 
Author Message
 Synchronise using FTP for Snapshot Location Fails - Merge Replication

When creating a subscription to a merge publication and specifying an FTP
server as the snapshot location, we are getting these errors:

"The server name or address could not be resolved"

"The process could not connect to FTP site
'??????????????????????????????????????????????????????????????' using port
21."

The second message is copied straight from the agent history window. The
server name specified in the publication is the IP address of the server but
it appears to be corrupted in the message. Not sure if the message reflects
the server that the merge agent is trying to connect to or not. I hope not.

It is possible to FTP to this IP from the subscriber using the FTP client,
so connectivity and access rights are there. If we copy the snaphot files
over to the subscriber manually and then pick them up in the snapshot
location when creating the subscription, everything works fine.

Any ideas why the FTP process is not working?



Sun, 12 Sep 2004 10:46:21 GMT
 Synchronise using FTP for Snapshot Location Fails - Merge Replication

I take it your server name is not
'??????????????????????????????????????????????????????????????'

When I try to diagnose FTP errors I look in the ftp log - typically in
c:\winnt\system32\logfiles  You may have to enable ftp logging to get this
to work.  If you have enabled ftp logging (which is the default) and there
is not msftpsvc directory this means that no one has tried to logon to your
ftp server yet.  However you should be able look at the log and see the
subscriber logon and retrieve the ftp files.

If you see no activity this means that the subscriber never got to your ftp
site.  You then have to go to the subscriber and try to ftp to the publisher
and try to diagnose from here.  You may need to use a hosts file to hardcode
a hostname to ip address to get the name resolved correctly.  You can also
try to ping the hostname of the publisher by ip and name.

Are you using anonymous subscribers, BTW?


Quote:
> When creating a subscription to a merge publication and specifying an FTP
> server as the snapshot location, we are getting these errors:

> "The server name or address could not be resolved"

> "The process could not connect to FTP site
> '??????????????????????????????????????????????????????????????' using
port
> 21."

> The second message is copied straight from the agent history window. The
> server name specified in the publication is the IP address of the server
but
> it appears to be corrupted in the message. Not sure if the message
reflects
> the server that the merge agent is trying to connect to or not. I hope
not.

> It is possible to FTP to this IP from the subscriber using the FTP client,
> so connectivity and access rights are there. If we copy the snaphot files
> over to the subscriber manually and then pick them up in the snapshot
> location when creating the subscription, everything works fine.

> Any ideas why the FTP process is not working?



Sun, 12 Sep 2004 11:54:51 GMT
 Synchronise using FTP for Snapshot Location Fails - Merge Replication

Quote:

> '??????????????????????????????????????????????????????????????'

No it isn't, in fact I have specified the IP address of the FTP server when
creating the publication. Actually, the string of '?' chars was put there by
the News client. The actual message that I copied from the Agent History
window was a bunch of unprintable characters, which show up as boxes, and
some arabic-looking characters. Whatever, it's not my server name.

I know that FTP is working between the subscriber. I can open an FTP
connection to my server, using the same IP that I gave during the
publication setup. I can log in using the same user id and password, and I
can see and download the snaphot files. The problem is that the subscription
agent can't and I don't know why. The fact that the server name in the
message is garbage makes me suspect that it is being corrupted, either
during the publication creation step, or during the transfer of the
subscription details.

Thanks for the suggestion. I guess it is worth investigating whether or not
my FTP server is receiving anything. I suppose we could also try monitoring
at the subscriber end to see what server it is actually trying to connect
to.

Yes, we are using anonymous subscribers.

Cheers.



Sun, 12 Sep 2004 13:17:40 GMT
 Synchronise using FTP for Snapshot Location Fails - Merge Replication
I was kidding about the server name:).

Sounds like it could be a path issue then.  Run sql agent
for your job with the OutputVerboseLevel 2 Output
c:\temp\sql.out

to see what it says.

Quote:
>-----Original Message-----

name is not
>> '???????????????????????????????????????????????????????
???????'

>No it isn't, in fact I have specified the IP address of
the FTP server when
>creating the publication. Actually, the string of '?'

chars was put there by
Quote:
>the News client. The actual message that I copied from
the Agent History
>window was a bunch of unprintable characters, which show
up as boxes, and
>some arabic-looking characters. Whatever, it's not my
server name.

>I know that FTP is working between the subscriber. I can
open an FTP
>connection to my server, using the same IP that I gave
during the
>publication setup. I can log in using the same user id
and password, and I
>can see and download the snaphot files. The problem is

that the subscription
Quote:
>agent can't and I don't know why. The fact that the
server name in the
>message is garbage makes me suspect that it is being
corrupted, either
>during the publication creation step, or during the
transfer of the
>subscription details.

>Thanks for the suggestion. I guess it is worth

investigating whether or not
Quote:
>my FTP server is receiving anything. I suppose we could
also try monitoring
>at the subscriber end to see what server it is actually
trying to connect
>to.

>Yes, we are using anonymous subscribers.

>Cheers.

>.



Sun, 12 Sep 2004 21:40:40 GMT
 Synchronise using FTP for Snapshot Location Fails - Merge Replication
We were able to solve this problem by applying SP2 to all the
subscribers/publisher.


Quote:
> When creating a subscription to a merge publication and specifying an FTP
> server as the snapshot location, we are getting these errors:

> "The server name or address could not be resolved"

> "The process could not connect to FTP site
> '??????????????????????????????????????????????????????????????' using
port
> 21."

> The second message is copied straight from the agent history window. The
> server name specified in the publication is the IP address of the server
but
> it appears to be corrupted in the message. Not sure if the message
reflects
> the server that the merge agent is trying to connect to or not. I hope
not.

> It is possible to FTP to this IP from the subscriber using the FTP client,
> so connectivity and access rights are there. If we copy the snaphot files
> over to the subscriber manually and then pick them up in the snapshot
> location when creating the subscription, everything works fine.

> Any ideas why the FTP process is not working?



Tue, 14 Sep 2004 01:51:00 GMT
 
 [ 5 post ] 

 Relevant Pages 

1. Merge Replication with ftp fails after adding A New Merge Article

2. snapshot ftp delivery error in merge replication

3. Merge Replication: Snapshot creation fails

4. Merge Replication Snapshot job fails

5. Merge Replication - SNAPSHOT agent fails with sa login

6. Error 20033, Pull merge replication using FTP

7. merge replication using ftp

8. Cant initialize pull subscriptions using ftp in Merge Replication

9. ftp snapshot to a new location

10. ftp'ing snapshot to new location

11. SQL2000 MERGE/FTP snapshot

12. FTP Merge snapshot failure


 
Powered by phpBB® Forum Software