Showing posts with label publications. Show all posts
Showing posts with label publications. Show all posts

Friday, March 30, 2012

Merge sinchronization problem

Hi there.

I have big problem with SQL2005 merge sinchronization from single subscriber. This problem reveals itself on one database publications (it worked till today fine) but not others. Sincronization job writes to histrory :

The merge process was unable to create a new generation at the 'Subscriber'. Troubleshoot by restarting the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200994).

This message can be found in sincronization status after 30 minutes idle with status

Upload changes to publisher

During this time the replication agent job locks another one. I think subscriber can not upload changes from subscriber, which have accumulated them since sinchronization failure start.

How can I log verbose history to file?

Will be appreciate for help.

Here is the info how to logging...

How to enable replication agents for logging to output files in SQL Server

http://support.microsoft.com/kb/312292

|||Did you ever find a solution to the problem. I have had the same error on a couple of different subscribers and the verbose logging does not show where the problem is!

?

Thanks

Stuart

|||

I am also experiencing similar problems.

In my case, we are using pull subscriptions from 24 different subscribers all to one published database. Distributor is same as publisher.

No answers yet, but we're getting MS help on it -- sort of. Very difficult to track down without being able to get useful data, and getting useful data is proving to be difficult.

Merge sinchronization problem

Hi there.

I have big problem with SQL2005 merge sinchronization from single subscriber. This problem reveals itself on one database publications (it worked till today fine) but not others. Sincronization job writes to histrory :

The merge process was unable to create a new generation at the 'Subscriber'. Troubleshoot by restarting the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200994).

This message can be found in sincronization status after 30 minutes idle with status

Upload changes to publisher

During this time the replication agent job locks another one. I think subscriber can not upload changes from subscriber, which have accumulated them since sinchronization failure start.

How can I log verbose history to file?

Will be appreciate for help.

Here is the info how to logging...

How to enable replication agents for logging to output files in SQL Server

http://support.microsoft.com/kb/312292

|||Did you ever find a solution to the problem. I have had the same error on a couple of different subscribers and the verbose logging does not show where the problem is!

?

Thanks

Stuart

|||

I am also experiencing similar problems.

In my case, we are using pull subscriptions from 24 different subscribers all to one published database. Distributor is same as publisher.

No answers yet, but we're getting MS help on it -- sort of. Very difficult to track down without being able to get useful data, and getting useful data is proving to be difficult.

Wednesday, March 28, 2012

Merge Replication with different Service Packs

I have a Win 2003 server with SQL 2000 SP3 that is publisher and distributor for several merge replication publications. Subscribers are a mixture of SQL 2000 (running SP3 and SP4) and MSDE. I've run into a problem in creating publications that is fixed in SP4 but for various reasons I can't update all of the subscribers that are running SP3. I don't expect any issues updating just my server but will I have any issues running SP4 on my server and SP3 on the subscribers?

Thanks for the help.

GaryI have not experienced any issues related to mis-matched service packs in my development environment. On the other hand, I have not yet deployed to full scale production.

Regards,

hmscottsql

Monday, March 26, 2012

Merge Replication 'wait' issues

Hello,
I have created 3 merge publications on my server. I notice
that when I right click and try to view the properties of
the publication, SQL takes a long time to pull up the
properties of the publication.
Any ideas on how to make this 'wait' time less or why this
occurs?
Thanks,
niv
Niv,
a few things to try to narrow it down:
when you run sp_helpmergepublication does it also take a long time? How about sp_helpmergearticle? How many records are there in sysmergepublications and sysmergesubscriptions? Are things generally slow in EM? If it is just the merge publications, what oc
curs if you open another EM and look at the current activity windows - any evidence of blocking?
HTH,
Paul Ibison
|||Paul,
Tried both those procedures and it returned very fast.
Looks like it may have been another issue. I can get into
the properties quickly now... hmm. weird..
Anyhow,
I am in need of some advice in regards to the best
replication option to select when making changes to
triggers, views, sprocs.
I tried this at one point but I think I choose drop and
recreate.. needless to say.. this was not good
I await your reply.
niv

>--Original Message--
>Niv,
>a few things to try to narrow it down:
>when you run sp_helpmergepublication does it also take a
long time? How about sp_helpmergearticle? How many records
are there in sysmergepublications and
sysmergesubscriptions? Are things generally slow in EM? If
it is just the merge publications, what occurs if you open
another EM and look at the current activity windows - any
evidence of blocking?
>HTH,
>Paul Ibison
>.
>
|||Niv,
glad it's working.
You mention "Changes to triggers, views, sprocs" - are these objects created by SQL Server as part of the replication setup, or are they user objects. If the former, I would advise against altering, although in the case of a recent poster I mentioned edit
ing the triggers, but this was a specific business scenario.
If they are user objects then you might replicate the views and sprocs as separate articles. Triggers are more difficult, and you can use sp_addscriptexec if you are using transactional replication but if not then scripting changes and using linked server
s may be considered.
HTH,
Paul Ibison

Merge Replication trigger count

Hi,
I have Merge Replication ( Articles x,y) with Publications at 4 Sites and a
Central Subscriber. All the Merge Agents are running with property
-exchangetype 2 parameter
Article x have 12 triggers (4 for insert, 4 delete and 4 updates) which
looks OK ( 1 set for each publication) but article y has only 3 triggers(1
insert, i update and 1 delete). I am getting invalid following erros in the
conflict viewer:
1. The row was updated at 'SINDEV21.NewCase' but could not be updated at
'SINDEV20.NewCase'. Invalid object name
'ctsv_CAB6F215FE394ECAB4CE7DD56BD4B1B8'.
2. The row was updated at 'SINDEV21.NewCase' but could not be updated at
'SINDEV20.NewCase'. Unable to synchronize the row because the row was updated
by a different process outside of replication.
You need to reinitialize this subscription and resend your data. It looks
like your replication metadata is out of sync.
Hilary Cotter
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
"Vikas Kohli" <VikasKohli@.discussions.microsoft.com> wrote in message
news:7DC1A948-B930-45A1-ACFF-BB88246FBC16@.microsoft.com...
> Hi,
> I have Merge Replication ( Articles x,y) with Publications at 4 Sites and
a
> Central Subscriber. All the Merge Agents are running with property
> -exchangetype 2 parameter
> Article x have 12 triggers (4 for insert, 4 delete and 4 updates) which
> looks OK ( 1 set for each publication) but article y has only 3 triggers(1
> insert, i update and 1 delete). I am getting invalid following erros in
the
> conflict viewer:
> 1. The row was updated at 'SINDEV21.NewCase' but could not be updated at
> 'SINDEV20.NewCase'. Invalid object name
> 'ctsv_CAB6F215FE394ECAB4CE7DD56BD4B1B8'.
> 2. The row was updated at 'SINDEV21.NewCase' but could not be updated at
> 'SINDEV20.NewCase'. Unable to synchronize the row because the row was
updated
> by a different process outside of replication.
|||When I had first configured this, everything was OK. However to carry a
schema change activity, I had dropped all the subscriptions and Publications,
dropped all the replication procedures, triggers manually wherever required
and reconfigure the Replication again after the schema change. It has started
giving error after then.I have tried removing replication a number of times
but each time same problem.
Also please let me know what should be the normal count of Triggers at the
Central Subscriber, is it 12 or 4?
"Hilary Cotter" wrote:

> You need to reinitialize this subscription and resend your data. It looks
> like your replication metadata is out of sync.
> --
> Hilary Cotter
> 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
> "Vikas Kohli" <VikasKohli@.discussions.microsoft.com> wrote in message
> news:7DC1A948-B930-45A1-ACFF-BB88246FBC16@.microsoft.com...
> a
> the
> updated
>
>
|||Just to add more...
I cant reinitialize the Replication since the Data volume is huge and I
can't send that accross WAN. I have to use the property 'do not initialize
Schema or data' when I add subscription.
"Vikas Kohli" wrote:
[vbcol=seagreen]
> When I had first configured this, everything was OK. However to carry a
> schema change activity, I had dropped all the subscriptions and Publications,
> dropped all the replication procedures, triggers manually wherever required
> and reconfigure the Replication again after the schema change. It has started
> giving error after then.I have tried removing replication a number of times
> but each time same problem.
> Also please let me know what should be the normal count of Triggers at the
> Central Subscriber, is it 12 or 4?
> "Hilary Cotter" wrote:
|||Hi,
Any help in this matter will be appreciated as we are encountering lot of
issues due to this
Vikas Kohli
"Vikas Kohli" wrote:
[vbcol=seagreen]
> Just to add more...
> I cant reinitialize the Replication since the Data volume is huge and I
> can't send that accross WAN. I have to use the property 'do not initialize
> Schema or data' when I add subscription.
> "Vikas Kohli" wrote:

Wednesday, March 21, 2012

Merge Replication Problems

Hi all,
I have a problem by using GPRS in a merge replication.
I have an SQL Servers with 4 publications, these publication have horizontal
filtering, and they have about 20 Articles each of them. I need the
horizontal filtering because the client databases (client laptops use MSDE)
only needs to have the required data.
If I run the replication by using the office network, all of then works
fine. But my problem is by running the replication using GPRS. I have lot of
problems because the connection is broken although there isn't data to be
merged.
Thanks in advance
If the network error is a problem causing the merge agent to fail, then you
can force it to restart: the last step in the merge job should be to return
to step one if it fails.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi Paul,
Automatically is retrying the agent execution, Exactly the error is "General
network error", it seems the connection with distributor is broken when there
is data to be downloaded.
There is any guide to optimize correctly a publication.
I also have change the replication schema, I have configurated an
intermediate database to obtain the required data by a client, and after i
have configurated this database as publiser to send the data to the client
without filters, but when I try to send this data to the client the
replication log says "there isn't data to be downloaded". It is possible to
configure this topology? or it is an erroneus design?
Topology:
ServerDB (publisher) --> Inter.DB (Subscriber/Publisher) --> clientDB
(Subscriber)
Thanks.
|||Please, could anybody help me?
Thanks
|||For the unreliable agent, apart from creating the loop I
referred to earlier, you could change the merge agent's
profile properties to
optimize for an unreliable link - eg reduce
the '...GenerationsPerBatch'
counters.
For the topology, this is vaible and is referred to as
republishing. If you're having issues with it, then
perhaps go down the alternative synchronization partners
route.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I have tried to configured the new topology:
ServerDB (publisher) --> Inter.DB (Subscriber/Publisher) --> clientDB
(Subscriber)
But always after I execute the subscription at ClientDB, it says "no data to
be merged", but i have modified data in the Serverdb that has been merged to
the InterDB. I don't understand why. Any idea?
Thanks.
|||OK - I just set this up in the office and it worked fine.
Perhaps you have been put off by the message 'No data
needed to be merged'? This message is the last one to be
recorded and is displayed even when the data has indeed
been merged. Please right-click the merge agent for the
clientDB subscription and examine its history to
determine if the changes really went over.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I have checked the job history, but no data has been trasfered. I have open
tables, but there isn't data.
|||Please can you script it out - the table schema and the 2
publications and subscribers and post it up and I'll take
a look some time tomorrow.
Rgds,
Paul Ibison
|||Table:
CREATE TABLE [dbo].[MST_MANDANTE] (
[ID_CODMANDANTE] [varchar] (3) COLLATE Modern_Spanish_CI_AS NOT NULL ,
[TXT_DESCRIPCION] [varchar] (20) COLLATE Modern_Spanish_CI_AS NULL ,
[ID_CONTROL] uniqueidentifier ROWGUIDCOL NOT NULL
) ON [PRIMARY]
GO
Publication ServerDB:
-- Enabling the replication database
use master
GO
exec sp_replicationdboption @.dbname = N'SFAservidor', @.optname = N'merge
publish', @.value = N'true'
GO
use [SFAservidor]
GO
-- Adding the merge publication
exec sp_addmergepublication @.publication = N'SFAservidorMandante',
@.description = N'Merge publication of SFAservidor database from Publisher
PCSAC02.', @.retention = 14, @.sync_mode = N'native', @.allow_push = N'true',
@.allow_pull = N'true', @.allow_anonymous = N'false', @.enabled_for_internet =
N'false', @.centralized_conflicts = N'true', @.dynamic_filters = N'false',
@.snapshot_in_defaultfolder = N'false', @.alt_snapshot_folder = N'd:\snapshot',
@.compress_snapshot = N'false', @.ftp_port = 21, @.ftp_login = N'anonymous',
@.conflict_retention = 14, @.keep_partition_changes = N'false',
@.allow_subscription_copy = N'false', @.allow_synctoalternate = N'false',
@.add_to_active_directory = N'false', @.max_concurrent_merge = 0,
@.max_concurrent_dynamic_snapshots = 0
exec sp_addpublication_snapshot @.publication =
N'SFAservidorMandante',@.frequency_type = 4, @.frequency_interval = 1,
@.frequency_relative_interval = 1, @.frequency_recurrence_factor = 0,
@.frequency_subday = 1, @.frequency_subday_interval = 5, @.active_start_date =
0, @.active_end_date = 0, @.active_start_time_of_day = 500,
@.active_end_time_of_day = 235959, @.snapshot_job_name =
N'PCSAC02-SFAservidor-SFAservidorMandante-21'
GO
exec sp_grant_publication_access @.publication = N'SFAservidorMandante',
@.login = N'BUILTIN\Administradores'
GO
exec sp_grant_publication_access @.publication = N'SFAservidorMandante',
@.login = N'distributor_admin'
GO
exec sp_grant_publication_access @.publication = N'SFAservidorMandante',
@.login = N'sa'
GO
-- Adding the merge articles
exec sp_addmergearticle @.publication = N'SFAservidorMandante', @.article =
N'MST_MANDANTE', @.source_owner = N'dbo', @.source_object = N'MST_MANDANTE',
@.type = N'table', @.description = null, @.column_tracking = N'true',
@.pre_creation_cmd = N'drop', @.creation_script = null, @.schema_option =
0x000000000000CFF1, @.article_resolver = null, @.subset_filterclause = null,
@.vertical_partition = N'false', @.destination_owner = N'dbo',
@.auto_identity_range = N'false', @.verify_resolver_signature = 0,
@.allow_interactive_resolver = N'false', @.fast_multicol_updateproc = N'true',
@.check_permissions = 0
GO
Publication InterDB:
-- Enabling the replication database
use master
GO
exec sp_replicationdboption @.dbname = N'SFAInt', @.optname = N'merge
publish', @.value = N'true'
GO
use [SFAInt]
GO
-- Adding the merge publication
exec sp_addmergepublication @.publication = N'SFAIntMandante', @.description =
N'Merge publication of SFAInt database from Publisher PCSAC02.', @.retention =
14, @.sync_mode = N'native', @.allow_push = N'true', @.allow_pull = N'true',
@.allow_anonymous = N'false', @.enabled_for_internet = N'false',
@.centralized_conflicts = N'true', @.dynamic_filters = N'false',
@.snapshot_in_defaultfolder = N'false', @.alt_snapshot_folder = N'd:\snapshot',
@.compress_snapshot = N'false', @.ftp_port = 21, @.ftp_login = N'anonymous',
@.conflict_retention = 14, @.keep_partition_changes = N'false',
@.allow_subscription_copy = N'false', @.allow_synctoalternate = N'false',
@.add_to_active_directory = N'false', @.max_concurrent_merge = 0,
@.max_concurrent_dynamic_snapshots = 0
exec sp_addpublication_snapshot @.publication =
N'SFAIntMandante',@.frequency_type = 8, @.frequency_interval = 64,
@.frequency_relative_interval = 0, @.frequency_recurrence_factor = 1,
@.frequency_subday = 1, @.frequency_subday_interval = 0, @.active_start_date =
0, @.active_end_date = 0, @.active_start_time_of_day = 5000,
@.active_end_time_of_day = 0, @.snapshot_job_name =
N'PCSAC02-SFAInt-SFAIntMandante-27'
GO
exec sp_grant_publication_access @.publication = N'SFAIntMandante', @.login =
N'BUILTIN\Administradores'
GO
exec sp_grant_publication_access @.publication = N'SFAIntMandante', @.login =
N'distributor_admin'
GO
exec sp_grant_publication_access @.publication = N'SFAIntMandante', @.login =
N'sa'
GO
-- Adding the merge articles
exec sp_addmergearticle @.publication = N'SFAIntMandante', @.article =
N'MST_MANDANTE', @.source_owner = N'dbo', @.source_object = N'MST_MANDANTE',
@.type = N'table', @.description = null, @.column_tracking = N'true',
@.pre_creation_cmd = N'drop', @.creation_script = null, @.schema_option =
0x000000000000CFF1, @.article_resolver = null, @.subset_filterclause = null,
@.vertical_partition = N'false', @.destination_owner = N'dbo',
@.auto_identity_range = N'false', @.verify_resolver_signature = 0,
@.allow_interactive_resolver = N'false', @.fast_multicol_updateproc = N'true',
@.check_permissions = 0
GO
Subscription InterDB:
-- Adding the merge pull subscription: PCSAC02:SFAservidor:SFAservidorMandante
/****** Begin: Script to be run at Subscriber: PCSAC02 ******/
use [SFAInt]
GO
exec sp_addmergepullsubscription @.publication = N'SFAservidorMandante',
@.publisher = N'PCSAC02', @.publisher_db = N'SFAservidor', @.subscriber_type =
N'global', @.subscription_priority = 75.000000, @.sync_type = N'none',
@.description = N'Merge publication of SFAservidor database from Publisher
PCSAC02.'
exec sp_addmergepullsubscription_agent @.publisher = N'PCSAC02',
@.publisher_db = N'SFAservidor', @.publication = N'SFAservidorMandante',
@.distributor = N'PCSAC02', @.subscriber_security_mode = 1,
@.publisher_security_mode = 1, @.distributor_security_mode = 1, @.frequency_type
= 4, @.frequency_interval = 1, @.frequency_relative_interval = 1,
@.frequency_recurrence_factor = 0, @.frequency_subday = 8,
@.frequency_subday_interval = 1, @.active_start_date = 0, @.active_end_date = 0,
@.active_start_time_of_day = 0, @.active_end_time_of_day = 235959,
@.enabled_for_syncmgr = N'true', @.alt_snapshot_folder = N'\\pcsac02\snapshot',
@.use_ftp = N'false', @.use_interactive_resolver = N'false', @.offloadagent =
N'false'
GO
/****** End: Script to be run at Subscriber: PCSAC02 ******/
/****** Begin: Script to be run at Publisher: PCSAC02 ******/
use [SFAservidor]
GO
exec sp_addmergesubscription @.publication = N'SFAservidorMandante',
@.subscriber = N'PCSAC02', @.subscriber_db = N'SFAInt', @.subscription_type =
N'pull', @.subscriber_type = N'global', @.subscription_priority = 75.000000,
@.sync_type = N'none'
GO
/****** End: Script to be run at Publisher: PCSAC02 ******/
Subscription ClienDB:
-- Adding the merge pull subscription: PCSAC02:SFAInt:SFAIntMandante
/****** Begin: Script to be run at Subscriber: PCSAC02 ******/
use [sfacliente]
GO
exec sp_addmergepullsubscription @.publication = N'SFAIntMandante',
@.publisher = N'PCSAC02', @.publisher_db = N'SFAInt', @.subscriber_type =
N'local', @.subscription_priority = 0.000000, @.sync_type = N'none',
@.description = N'Merge publication of SFAInt database from Publisher PCSAC02.'
exec sp_addmergepullsubscription_agent @.publisher = N'PCSAC02',
@.publisher_db = N'SFAInt', @.publication = N'SFAIntMandante', @.distributor =
N'PCSAC02', @.subscriber_security_mode = 1, @.publisher_security_mode = 1,
@.distributor_security_mode = 1, @.frequency_type = 4, @.frequency_interval = 1,
@.frequency_relative_interval = 1, @.frequency_recurrence_factor = 0,
@.frequency_subday = 8, @.frequency_subday_interval = 1, @.active_start_date =
0, @.active_end_date = 0, @.active_start_time_of_day = 0,
@.active_end_time_of_day = 235959, @.enabled_for_syncmgr = N'true',
@.alt_snapshot_folder = N'\\pcsac02\snapshot', @.use_ftp = N'false',
@.use_interactive_resolver = N'false', @.offloadagent = N'false'
GO
/****** End: Script to be run at Subscriber: PCSAC02 ******/
/****** Begin: Script to be run at Publisher: PCSAC02 ******/
use [SFAInt]
GO
exec sp_addmergesubscription @.publication = N'SFAIntMandante', @.subscriber =
N'PCSAC02', @.subscriber_db = N'sfacliente', @.subscription_type = N'pull',
@.subscriber_type = N'local', @.subscription_priority = 0.000000, @.sync_type =
N'none'
GO
/****** End: Script to be run at Publisher: PCSAC02 ******/

Monday, March 12, 2012

merge replication issue

Hi all,
Setup: SQL2K (Enterprise) [SQLSVR1] in Network 1 - 2 publications (merge
for tables that data changes in often, and snapshot for stuff that is
batched after a few months) - there are a number of MSDE subscribers to
these publications in this network.
The same setup is in Network 2 [SQLSVR2].
SQLSVR2 subscribes to the SQLSVR1 publications, and re-publishes them for
Network 2 MSDE subscribers.
I have an app that works on the local msde installations - any changes to
a specific database is then replicated.
Everything works great in Network 1.
On Network 2, I tried to insert into a specific table and I get a
"Invalid object name 'ctsv_EEF98A7665F64374A3C47E6A3D87155E'." error ?
Other tables do not appear to be effected ?
I read a post that appear to suggest security context in setting up the
publications ? - the publications security context is a sql user, and the
distribution folder is shared so that all users in the network can read
and write to it
(http://groups.google.com/groups?hl=e...3DN%26tab%3Dwg)
Any information on helping me resolve this would be useful.
tia,
Best Regards,
Ranjeet.
how did you deploy the problem subscriber?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"ranjeet" <not-telling> wrote in message
news:opsemtjwu6v8so89@.athwalrt40.castlewood.co.uk. ..
> Hi all,
> Setup: SQL2K (Enterprise) [SQLSVR1] in Network 1 - 2 publications (merge
> for tables that data changes in often, and snapshot for stuff that is
> batched after a few months) - there are a number of MSDE subscribers to
> these publications in this network.
> The same setup is in Network 2 [SQLSVR2].
> SQLSVR2 subscribes to the SQLSVR1 publications, and re-publishes them for
> Network 2 MSDE subscribers.
> I have an app that works on the local msde installations - any changes to
> a specific database is then replicated.
> Everything works great in Network 1.
> On Network 2, I tried to insert into a specific table and I get a
> "Invalid object name 'ctsv_EEF98A7665F64374A3C47E6A3D87155E'." error ?
> Other tables do not appear to be effected ?
> I read a post that appear to suggest security context in setting up the
> publications ? - the publications security context is a sql user, and the
> distribution folder is shared so that all users in the network can read
> and write to it
>
(http://groups.google.com/groups?hl=e...32G%23zQRJBHA.
388%40tkmsftngp02&rnum=1&prev=/groups%3Fq%3Dinvalid%2520object%2520name%2520
%27tsvw_%26hl%3Den%26lr%3D%26ie%3DUTF-8%26sa%3DN%26tab%3Dwg)
> Any information on helping me resolve this would be useful.
> tia,
> Best Regards,
> Ranjeet.
|||used enterprise manager logged on as a user in network 1 (registered the
subscriber in EM, and clicked through to add pull subscription to SQLSVR2
in network 2).
the subscriber and publisher were part of network 2.
|||when you start getting messages like this telling you you have missing
views, or the merge agent expects a different view than the one present on
your subscriber, you have inconsistent replication metadata.
While it is entirely possible to hack your way through the triggers and
adjust them for the views the merge agent expects to use, you are better off
to redeploy your subscriber.
I'm still not exactly sure how you deployed your subscribers. The way to do
it is to create a publication on SQLSRV1, and deploy a subscription to
SQLSRV2. After the subscription is deployed to SQLSRV2, you then create
your publication on SQLSRV2 and deploy the subscriptions to the MSDE
subscribers.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"ranjeet" <not-telling> wrote in message
news:opsem0kgrgv8so89@.athwalrt40.castlewood.co.uk. ..
> used enterprise manager logged on as a user in network 1 (registered the
> subscriber in EM, and clicked through to add pull subscription to SQLSVR2
> in network 2).
> the subscriber and publisher were part of network 2.
|||Hi Hillary,
thanks for the info.
My deployment was as you described.
I am now rebuilding the subscriptions and publications for network 2 and
SQLSVR2 in the hope that this fixes this most frustrating problem. I am
in the fortunate position that my users are not yet ready to go live in
network 2 (phew!).
I will update this post with my results incase it is ever useful to anyone.
thanks again,
Ranjeet.
|||recreating the server subscription and publications resolved this problem.
thanks again for your help hilary.
Ranjeet.