Thanks,
This was the solution to the problem I coped with a few
weeks ago.
I thought the problem was that port 1433 was not open at
the publisher/originating side (for incoming traffic), so
we opened it a few days ago for certain IP's, but we had
the same result (not valid subscription).
Thanks again.
>-----Original Message-----
>Glad to be able to help.
>--------------------
>| Subject: Re: Merge Replication - Invalid Subscriptions
>| Date: Sat, 21 Jul 2001 18:02:23 -0500
>|
><Snip of Header Stuff>
>|
>| Thanks Much all
>|
>| I used the LMHOSTS local file of each NT machine and it
worked like a
>| charm!!
>|
>| Thanks again!
>| Mike
>|
>|
>|
in message
>| > Mike,
>| >
>| > Vijayts is correct. Use the SQL client Network
utility on your
>publisher
>| > to define an alias for the server on the DMZ.
Register that server as a
>| > subscriber and then push your subscription.
>| >
>| > John Gose
>| > MCDBA
>| > Microsoft SQL Server Support
>| >
>| > --------------------
>| > | Subject: Re: Merge Replication - Invalid
Subscriptions
>| > | Date: Wed, 18 Jul 2001 11:49:40 -0700
>| > |
>| > <Snip of Header Stuff>
>| > |
>| > | The subscription server is defined with the
servername but the
>| replication
>| > | agent is trying to connect with IP address. (To be
precise, the IP
>| > address
>| > | is not defined in the sysservers of the publisher
database)
>| > | This is the problem. Instead of adding the IP
address to sysservers
>of
>| > | publisher , I suggest that you make an alias with
cliconfg.exe or
>| lmhosts
>| > | type mapping between subscriber name and IP
address so that the
>| > replication
>| > | agent knows only about the server name rather than
IP address.
>| > |
>| > |
>| > | > Greetings List,
>| > | >
>| > | > I hope somebody can help me out here... here's my
situtation.
>| > | >
>| > | > SS2K on 2 machines, on on DMZ one on Internal.
Both have
>connectivity
>| to
>| > | > each other on 1433
>| > | >
>| > | > Internal is the distributor and the publisher. A
push subscription
>is
>| > set
>| > | up
>| > | > to send data from Internal to DMZ
>| > | >
>| > | > I have the standard setup going and when I create
the push
>| subscription
>| > it
>| > | > runs the snapshot agent just fine,
>| > | > transports and imports the snapshot.. then when
it looks like it
>works
>| > OK
>| > | > the Merge Agent says:
>| > | >
>| > | > The subscription to publication 'V3ReplDEV' is
invalid.
>| > | >
>| > | > Error Text:
>| > | >
>| > | > The subscription to publication 'V3ReplDEV' is
invalid.
>| > | > (Source: Merge Replication Provider (Agent); Error
>| number: -2147201019)
>| > | >
>| >
>----------------------------------------------------------
----------------
>| > | --
>| > | > -----------------------------------
>| > | > The remote server is not defined as a
subscription server.
Quote:>| > | > (Source: XXX.XXX.XXX.XXX (Data source); Error
number: 14010)
>| > | >
>| >
>----------------------------------------------------------
----------------
>| > | --
>| > | > -----------------------------------
>| > | >
>| > | > So every time I run the merge agent after this it
repeats the same
>| > process
>| > | > (my bulk insering a new snapshot)
>| > | >
>| > | > I have created another subscription on the same
internal machine to
Quote:>a
>| > | local
>| > | > database. That subscription works
>| > | > fine so I think there is a permissions issue.
Unfortunatly, I really
Quote:>| > don't
>| > | > know what permissions would be causing
>| > | > the problem.. If anyone can help I would greatly
appreciate it!
>| > | >
>| > | > Thanks Much!
>| > | > Mike Fredrick
>| > | >
>| > | >
>| > |
>| > |
>| > |
>| >
>|
>|
>|
>.