Viewing 2 posts - 1 through 2 (of 2 total)
Here it is:
restricted0
status1
task1
replication frequency0
synchronization method3
immediate_sync0
enabled_for_internet0
allow_push1
allow_pull1
allow_anonymous0
independent_agent1
immediate_sync_ready0
allow_sync_tran0
autogen_sync_procs0
retention0
has subscription1
allow_queued_tran0
snapshot_in_defaultfolder0
pre_snapshot_scriptNULL
post_snapshot_scriptNULL
compress_snapshot0
ftp_addressNULL
ftp_port21
ftp_subdirectoryNULL
ftp_loginanonymous
allow_dts0
allow_subscription_copy0
centralized_conflictsNULL
conflict_retention14
conflict_policyNULL
queue_typeNULL
backward_comp_level40
publish_to_AD0
allow_initialize_from_backup0
replicate_ddl1
enabled_for_p2p0
publish_local_changes_only0
enabled_for_het_sub0
enabled_for_p2p_conflictdetection0
originator_idNULL
p2p_continue_onconflict0
allow_partition_switch0
replicate_partition_switch0
Do you see anything that would cause that?
And is there a way to list all articles set to be snapshotted next time the stapshot agent...
August 1, 2013 at 6:44 am
Both immediate_sync and allow_anonymous are already false, but I still see all articles sometimes (not always) being snapshotted.
Any other suggestions?
Thanks.
July 31, 2013 at 5:15 pm
Viewing 2 posts - 1 through 2 (of 2 total)