HELP! Issue creating subscription

We have been creating the initial subscriptions the same way for years
(sp_addmergepullsubscription_agent). Our FTP server is the same as well.
Yesterday I ran into a strange situation on one client (3 subscribers to one
database at 3 different locations, 2 with the same ISP). Each have SQL
Server 2005 Developer's Editon.
As soon as the process to connect to our FTP and download the snapshot we
get the following error:
************************************************** *******
Error messages:
The schema script '' could not be propagated to the subscriber. (Source:
MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
Get help: http://help/MSSQL_REPL-2147201001
The process could not retrieve file
'OURSERVER_CLIENT_DBNAME_CLIENT_DBNAME\20071105123 250\snapshot.cab' from the
FTP site '11.222.33.44'. (Source:
MSSQL_REPL, Error number: MSSQL_REPL20033) Get help:
http://help/MSSQL_REPL20033
200 Type set to I.
500 Invalid PORT Command.
500 'LPRT 6,16,0,0,0,0,0,0,0,0,80,173,6,0,0,0,0,0,2,4,208': command not
understood
(Source: MSSQL_REPL, Error number: MSSQL_REPL12003)
************************************************** ******
I used the exact same procedure on their publication as if I was one for
their locations and it worked fine. We do this at least twice every week for
new clients or when the subscription has to be recreated and have never had
this issue.
We turned off the firewalls and set the router to DMZ. Same problem. I
turned on verbose logging and did not get any additional information.
To work-around I downloaded the snapshot manually, changed the snapshot
location to the subscriber's local drive and it created the subscriptions.
When it finished I changed the snapshot path back to FTP and re-ran the
snapshot agent to see if it would continue to sync. Thankfully it does at
least for now.
The same issued happened again today on our other server. Both are SQL
Server 2005 SP2.
Anybody know what is causing this?
Thank you in advance!
when I ping 111.222.33.44 the ping request times out. I think this is your
problem;)
When I examine your logs it looks like the ftp command was not correctly
formatted:
500 Invalid PORT Command.
500 'LPRT 6,16,0,0,0,0,0,0,0,0,80,173,6,0,0,0,0,0,2,4,208': command not
understood
Can you check your ftp logs to see what ftp command SQL Server was issuing?
The ftp logs might also give you some clues as to what actually occured and
what the problem is.
RelevantNoise.com - dedicated to mining blogs for business intelligence.
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
"RichardD" <RichardD@.discussions.microsoft.com> wrote in message
news:5B0C5E4D-9529-4EFC-97B5-5748558B4399@.microsoft.com...
> We have been creating the initial subscriptions the same way for years
> (sp_addmergepullsubscription_agent). Our FTP server is the same as well.
> Yesterday I ran into a strange situation on one client (3 subscribers to
> one
> database at 3 different locations, 2 with the same ISP). Each have SQL
> Server 2005 Developer's Editon.
> As soon as the process to connect to our FTP and download the snapshot we
> get the following error:
> ************************************************** *******
> Error messages:
> The schema script '' could not be propagated to the subscriber. (Source:
> MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
> Get help: http://help/MSSQL_REPL-2147201001
> The process could not retrieve file
> 'OURSERVER_CLIENT_DBNAME_CLIENT_DBNAME\20071105123 250\snapshot.cab' from
> the
> FTP site '11.222.33.44'. (Source:
> MSSQL_REPL, Error number: MSSQL_REPL20033) Get help:
> http://help/MSSQL_REPL20033
> 200 Type set to I.
> 500 Invalid PORT Command.
> 500 'LPRT 6,16,0,0,0,0,0,0,0,0,80,173,6,0,0,0,0,0,2,4,208': command not
> understood
> (Source: MSSQL_REPL, Error number: MSSQL_REPL12003)
> ************************************************** ******
> I used the exact same procedure on their publication as if I was one for
> their locations and it worked fine. We do this at least twice every week
> for
> new clients or when the subscription has to be recreated and have never
> had
> this issue.
> We turned off the firewalls and set the router to DMZ. Same problem. I
> turned on verbose logging and did not get any additional information.
> To work-around I downloaded the snapshot manually, changed the snapshot
> location to the subscriber's local drive and it created the subscriptions.
> When it finished I changed the snapshot path back to FTP and re-ran the
> snapshot agent to see if it would continue to sync. Thankfully it does at
> least for now.
> The same issued happened again today on our other server. Both are SQL
> Server 2005 SP2.
> Anybody know what is causing this?
> Thank you in advance!
>
|||The actual IP is working. ;)
So far this has only happened to 2 clients. Others that have been done
before AND after have not had this issue. All clients use the same FTP
Server but each of the these 2 snapshots that failed are on a different
server. The others that worked after these failed are on the same server as
one of the failing clients.
In the event view we did see this message but have not yet tried using the
uncompressed snapshot.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 14151
Date: 11/7/2007
Time: 7:13:13 AM
User: HOSTING\sql-int05
Computer: OURSQLSERVER
Description:
Replication-Replication Snapshot Subsystem: agent
OURSQLSERVER-ClientName_DBName-ClientName_DBName-5 failed. The replication
agent had encountered an exception.
Source: Replication
Exception Type: Microsoft.SqlServer.Replication.FciException
Exception Message: The replication agent had encountered a file compression
(cabinet) library error while calling 'FCIF
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 47 37 00 00 12 00 00 00 G7.....
0008: 0e 00 00 00 49 00 4e 00 ...I.N.
0010: 54 00 45 00 52 00 41 00 T.E.R.A.
0018: 43 00 54 00 49 00 56 00 C.T.I.V.
0020: 45 00 30 00 35 00 00 00 E.0.5...
0028: 0d 00 00 00 64 00 69 00 ...d.i.
0030: 73 00 74 00 72 00 69 00 s.t.r.i.
0038: 62 00 75 00 74 00 69 00 b.u.t.i.
0040: 6f 00 6e 00 00 00 o.n...
I will look for the FTP logs and see if there is anything in those as well.
Thanks!
"Hilary Cotter" wrote:

> when I ping 111.222.33.44 the ping request times out. I think this is your
> problem;)
> When I examine your logs it looks like the ftp command was not correctly
> formatted:
> 500 Invalid PORT Command.
> 500 'LPRT 6,16,0,0,0,0,0,0,0,0,80,173,6,0,0,0,0,0,2,4,208': command not
> understood
> Can you check your ftp logs to see what ftp command SQL Server was issuing?
> The ftp logs might also give you some clues as to what actually occured and
> what the problem is.
>
> --
> RelevantNoise.com - dedicated to mining blogs for business intelligence.
> 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
> "RichardD" <RichardD@.discussions.microsoft.com> wrote in message
> news:5B0C5E4D-9529-4EFC-97B5-5748558B4399@.microsoft.com...
>
>