Friday, March 30, 2012
Merge Rpl. Pull from subscriber access denied problem
I have set up one laptop as the Distributer/Publisher. Went through the
wizard and set up a Publication also, used Pubs. Then registered another
remote laptop that I can see via the network, and it can see me. I went
through the wizard again and set up a Push to that laptop. Said it ran good,
and I can see the tables on the remote laptop now.
I deleted the Push and keep trying to create a Pull at the other laptop,
(subscriber). The wizard sets it up, but when it Starts Syncronizing, it
immediately gets the big Red X.
The error said The schema script
'\\ACER\ReplShare\ReplData\unc\ACER_pubs_pubs_arti cles\20050928212317\stores_1.sch' could not be propagated to the subscriber.
I can see this share from both ends. I have read a ton about the accounts
the agent has to run under in the last 12 hours, but can't see what I am
doing wrong.
Is there a trick here?
Thanks.
Steve,
try logging on to the subscriber laptop using the same account that the sql
server agent uses as a service account. The see if you can browse to the
snapshot folder
\\ACER\ReplShare\ReplData\unc\ACER_pubs_pubs_artic les\20050928212317. If you
can, see if you can copy the contents of this directory locally. I'm
guessing that the first part won't be possible due to permission
restrictions, but please post back with your results.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
I had tried some other things prior to being able to read your response.
Here is what I have done that is now working.
I set up new SQL users on both Publisher/Dist. and Subscriber, giving them
the proper roles. I then set up a new Windows login on each box, "Bob", of
type admin. I then changed both the MSSQLSERVICE and SQLAGENTSERVICE on each
to run under "Bob". When it asks for logon credintials for the subscriber, I
use the sa, when it asks for the publisher, I use the new SQL user I had set
up. Probably may have been able to use that for the subscriber instead of
the sa, don't know.
I have tried so many things since yesterday afternoon, I am a little unsure
as to what actually solved it. From all I read over night, having the two
service run under "Bob" was needed.
Thank you for the response,
Steve
"Paul Ibison" wrote:
> Steve,
> try logging on to the subscriber laptop using the same account that the sql
> server agent uses as a service account. The see if you can browse to the
> snapshot folder
> \\ACER\ReplShare\ReplData\unc\ACER_pubs_pubs_artic les\20050928212317. If you
> can, see if you can copy the contents of this directory locally. I'm
> guessing that the first part won't be possible due to permission
> restrictions, but please post back with your results.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||This is OK - what you've set up is known as pass-through authentication.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Is there a better or more preferred method? We have one laptop that acts as
the publisher/distributor, and two other laptops that will be subscribers.
They run over a wireless network. The two subscribers will be able to
initial pull merge replications.
Thanks,
Steve
"Paul Ibison" wrote:
> This is OK - what you've set up is known as pass-through authentication.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Steve,
are the laptops all on the same domain? If so, you could use a domain
account, which is given rights to the distributor's working folder. If not,
it's either pass-through, FTP, backup and restore or alternative snapshot
locations.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
sql
Wednesday, March 28, 2012
merge replication with pull subscriber(compress snapshot)
I am trying to implement merge publication with compress snapshot, copy it
to the subscriber,
create a pull subscriber with the alternate folder(where the snapshot was
copied to)
and then run the agent for synchronization (first time).
i get error that the table in the publication does not exist in the
subscriber database.
It seems that the agent ignores the snapshot and it tries to just merge the
changes between publisher and subscriber.
when i create the table manually at the subscriber with the rowguid column,
it does not fail but it stills does not aplly the snapshot.
if i update/insert new row and run the agent it does merge the changes.
am i missing a crucial step in the process that causes that problem?
Thanks in advance
Daniel
daniel
Please can you post up the error message in its entirety. I suspect that it
is related to a script missing. Also, please try not using the CAB file
method. If you need to compress the snapshot, zip it up and unzip on the
subscriber (I only say this because I've never tested using an alternative
folder with a CAB file).
Paul Ibison
|||Hi and thank u for the replying.
When i start the agent for the first time i get the following error:
"Table 't3' does not exist in the Subscriber database."
At the log i can see that he does try to get the snapshot from alternate
folder:
" Snapshot will be applied from the alternate folder ..."
thanks in advance
Daniel
daniel
"Paul Ibison" wrote:
> Please can you post up the error message in its entirety. I suspect that it
> is related to a script missing. Also, please try not using the CAB file
> method. If you need to compress the snapshot, zip it up and unzip on the
> subscriber (I only say this because I've never tested using an alternative
> folder with a CAB file).
> Paul Ibison
|||Interesting - if you enable full logging is there more info? Also, are you
using the uncompressed snapshot files (if not please try this way also)? In
the snapshot files do you see the table creation script for t3?
(the alternative to this investigation if you like is to do a nosync
initialization).
Paul Ibison
|||Hi Paul
Yes there is a script for table creation.
I tried to use the uncompressed and i got the same error.
How do i do the no sync initialization?
daniel
"Paul Ibison" wrote:
> Interesting - if you enable full logging is there more info? Also, are you
> using the uncompressed snapshot files (if not please try this way also)? In
> the snapshot files do you see the table creation script for t3?
> (the alternative to this investigation if you like is to do a nosync
> initialization).
> Paul Ibison
|||Please have a look here. It largely applies to transactional, but mostly the
same info applies: http://www.replicationanswers.com/NoSyncInitializations.asp
HTH,
Paul Ibison
Monday, March 26, 2012
Merge Replication Topology
Is it possible to have three publishers who also subscribe to
publications from each other? All are pull subscriptions participating
in merge replication. The physical design is represented by a triangle.
My understanding of the suppported replication topology precludes such
a design - is this the case?
Paul
Hey Paul,
Triangle, or Peer To Peer Topologies are not supported in SQL2000.
You can 'fake' it with some heavy duty partitioning if you need to.
Take a peek at SQL2005 for that kind of functionality out of the box.
Donna Lambert
"Waterfall" wrote:
> Hi everyone,
> Is it possible to have three publishers who also subscribe to
> publications from each other? All are pull subscriptions participating
> in merge replication. The physical design is represented by a triangle.
> My understanding of the suppported replication topology precludes such
> a design - is this the case?
> Paul
>
|||Thanks Donna. It is good to know that SQL2005 will support peer-to-peer
replication topology.
I have another question. Is it possible to replicate to a table
containing an identity column and a natural key using merge or
transactional replication, where the identity values are not preserved?
Paul
*** Sent via Developersdex http://www.codecomments.com ***
Friday, March 23, 2012
Merge replication real-time monitoring
So far I used merge ActiveX control to start and monitor pull merge
subscription within C# client application. Due to fact that some subscriber
machines are rather slow and publication is relatively complex (lots of join
filters etc.), I want to offload processing to distributor. Some subscribers
often report "The process is running and is waiting for a response from one of
the backend connections".
Since I cannot control offloading with ActiveX (because it starts process on
local subscriber, or I am missing something here?), I would like to
use -Offload, start agent using msdb..sp_start_job on subscriber and monitor
replication progress by directly reading distributor's
distribution..MSmerge_history.
My questions are:
- is there better approach to accomplish same goal (e.g. .NET Remoting?)
- how to get "percentage complete" (agent outputs it if -OutputVerboseLevel 2
is used, but how to get it from subscriber?)
Links with more detailed info on replication would also be nice :-)
Thanks,
Tom
for percentage complete have a look at the status event.
The replication ActiveX controls do not support the full range of properties
that the SQL DMO replication objects support. IIRC the offloadagent
parameter is ignored in the merge ActiveX control.
"Tom" <tomislav.hrvoic.rimuv.dis@.inet.hr> wrote in message
news:%23ouVBHUJEHA.2660@.TK2MSFTNGP09.phx.gbl...
> Hi,
> So far I used merge ActiveX control to start and monitor pull merge
> subscription within C# client application. Due to fact that some
subscriber
> machines are rather slow and publication is relatively complex (lots of
join
> filters etc.), I want to offload processing to distributor. Some
subscribers
> often report "The process is running and is waiting for a response from
one of
> the backend connections".
> Since I cannot control offloading with ActiveX (because it starts process
on
> local subscriber, or I am missing something here?), I would like to
> use -Offload, start agent using msdb..sp_start_job on subscriber and
monitor
> replication progress by directly reading distributor's
> distribution..MSmerge_history.
> My questions are:
> - is there better approach to accomplish same goal (e.g. .NET Remoting?)
> - how to get "percentage complete" (agent outputs it
if -OutputVerboseLevel 2
> is used, but how to get it from subscriber?)
> Links with more detailed info on replication would also be nice :-)
> Thanks,
> Tom
>
sql
Wednesday, March 21, 2012
Merge Replication Pull Subscription Error
l subscribers and the publisher.
When I try to run a pull subscription scenario the replication will fail. I think that the snapshot agent is failing because of some type of security problem. I get the error:
“SQL Server Agent could not access the replication agent. Use the DCOMCNFG utility to confirm that the SQL Server Agent Windows account has permissions to launch the replication agent. The step failed.”
The server is using windows authentication and has the sp3a on it. Again, when I run the replication using push subscribers it works. When I change it to pull subscribers, I get the error.
Any advice is greatly appreciated,
Phil
Are you using remove agent activation?
If so, you must use your Publisher, Susbcriber, or Distributor as the location of your remote agent.
If not, someone has messed with where your merge.exe program is running.
open up DCOMCnfg, locate Microsoft SQL Server Replication Merge Agent 8.0. click on properties Verify in the location tab, that the program runs locally, in the security tab, click on edit for launch permissions. Make sure the everyone group has special
access.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
-- Phil wrote: --
I have replication scenario using SQL SERVER 2000 as the Distributor/Publisher and multiple MSDE databases as the subscribers. When I set up the scenario to use push subscriptions the replication seems to work well. All changes flow correctly betwe
en all subscribers and the publisher.
When I try to run a pull subscription scenario the replication will fail. I think that the snapshot agent is failing because of some type of security problem. I get the error:
“SQL Server Agent could not access the replication agent. Use the DCOMCNFG utility to confirm that the SQL Server Agent Windows account has permissions to launch the replication agent. The step failed.”
The server is using windows authentication and has the sp3a on it. Again, when I run the replication using push subscribers it works. When I change it to pull subscribers, I get the error.
Any advice is greatly appreciated,
Phil
sql
Merge Replication problem....
I have been working with this type of replication for a year now and never have any problem like this.
- The job succeeded always. but no changes are uploaded to the susbsciber.
- Checking the merge agent history has 0 on inserts, deletes and updates on the susbcriber.
- Publisher is running the same merge replication with other 42 subscribers without problems.
- Windows 2000 Server (sp4) , Sql 2000 (sp3)
- Sanpshot size is 12 Gigas , I don't want or can't affort to copy again the snapshot.
Thank you for your help.
:(Does your distribution database have the transactions that have not been applied to the Subscriber? If not, you have no option but to apply a snapshot - how you do that is dependent on what is missing and what is available. You can roll-your-own snapshot.
Test a dummy insert on your Publisher and see what happens from Distribution to Subscription(s). It appears something is not running correctly on the Subscriber, and checking the Distributor will help you determine that.
Finally, you may want to create a job that alerts when the difference between the date of the most recently inserted row in your most active article and GetDate() is > n hours.|||Thank you for your suggestions.
I described my problem incorrectly above in saying that I could upload my new data to the subscriber.
The problem is that one of my 42 subscribers is receiving all and any changers that any of the 42 subscriber makes, but it does not sent it's new info to the publsher.
So, it could receive changes but not send any upward.
Sorry, for the confusion.|||My suggestions still apply - just work from the Subscriber back to the Publisher. Use whatever Distributor that Subscriber is using to communicate Updates back to the Publisher to see where the problem is.|||If you find that any changes at the subscriber are not 'taking' i.e. they get overwritten from the publisher even when there are no changes to those particular records anywhere else, then you should check that you have set the subscription priority appropriately and not just left it as 'use publisher as proxy'. I speak from experience.
Monday, March 19, 2012
merge replication partition options
SQL Server 2005 -> Merge pull subscription via HTTPS
Tables:
1) StudioType (Id [tinyint] PK, Name [nvarchar])
2) Studio (Id [int] PK, StudioTypeId [tinyint] FK, ComputerName [nvarchar]...)
3) etc
Remarks:
I have a single parametrized filter (for the entire database) on article
Studio like so -> ComputerName=HOST_NAME().
@.partition_option for Studio is obviously 3.
I have a join filter between Studio and StudioType like so:
@.filtername = N'StudioTypes_Studios', @.join_articlename = N'Studios',
@.join_filterclause = N'[StudioTypes].[Id] = [Studios].[StudioTypeId]',
@.join_unique_key = 0
Basically I have multiple Studios that belong to the same StudioType
Question:
Which @.partition_option can/should I use on article StudioType?
I know 0 works, but can I use 2 instead?
In order to save you guys some time searching, this page should contain all
the info required:
http://technet.microsoft.com/en-us/library/ms152478.aspx
But I have a problem undestanding whether the join filter creates
overlapping or nonoverlapping partitions...
Also, could somebody answer this question as well:
Does the following - "The Subscriber cannot update columns referenced in a
parameterized filter." - also apply to columns used in joins or does it only
apply to the parametrized filter column (ComputerName)?
I'm guessing not...
Ok, I figured out that I can't use partition_option 2, because the rows are
indeed overlapping.
So I can only use partition_option either 0 or 1.
But it would still be nice if somebody can answer the last question in my
post...
"mommi" wrote:
> Setup:
> SQL Server 2005 -> Merge pull subscription via HTTPS
> Tables:
> 1) StudioType (Id [tinyint] PK, Name [nvarchar])
> 2) Studio (Id [int] PK, StudioTypeId [tinyint] FK, ComputerName [nvarchar]...)
> 3) etc
> Remarks:
> I have a single parametrized filter (for the entire database) on article
> Studio like so -> ComputerName=HOST_NAME().
> @.partition_option for Studio is obviously 3.
> I have a join filter between Studio and StudioType like so:
> @.filtername = N'StudioTypes_Studios', @.join_articlename = N'Studios',
> @.join_filterclause = N'[StudioTypes].[Id] = [Studios].[StudioTypeId]',
> @.join_unique_key = 0
> Basically I have multiple Studios that belong to the same StudioType
> Question:
> Which @.partition_option can/should I use on article StudioType?
> I know 0 works, but can I use 2 instead?
>
> In order to save you guys some time searching, this page should contain all
> the info required:
> http://technet.microsoft.com/en-us/library/ms152478.aspx
> But I have a problem undestanding whether the join filter creates
> overlapping or nonoverlapping partitions...
> Also, could somebody answer this question as well:
> Does the following - "The Subscriber cannot update columns referenced in a
> parameterized filter." - also apply to columns used in joins or does it only
> apply to the parametrized filter column (ComputerName)?
> I'm guessing not...
Merge Replication over internet Problem: Couldn't propagate schema to the subscriber.
I am implementing Pull merge replication over internet, I have a sql
server which I have set as Publishe/Distributor and MSDE which I have
set a subscriber. I have a sample Database FTP_REPL which I have
published. whenever I try to run merge Agent it succssfully connects
to the publisher, Distributor,but it gives error "The schema script
<ScriptName> could not be propagated to the subscriber".
Plz anyone help me to resolve this problem.
Locate your agent, right click on it, select agent properties, and ensure
the job owner is sa. Then restart your agent.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Ruchir" <ruchirdhar@.gmail.com> wrote in message
news:88216eb7.0501100407.d4c3f56@.posting.google.co m...
> Hello All,
> I am implementing Pull merge replication over internet, I have a sql
> server which I have set as Publishe/Distributor and MSDE which I have
> set a subscriber. I have a sample Database FTP_REPL which I have
> published. whenever I try to run merge Agent it succssfully connects
> to the publisher, Distributor,but it gives error "The schema script
> <ScriptName> could not be propagated to the subscriber".
> Plz anyone help me to resolve this problem.
Merge replication not working (Push or Pull)
So I tried a push subscription. This gets me a little further, it creates the snapshot in the subs DB, but then the merge agent fails with the following error.
The subscription to publication 'pubs_customer_test' is invalid.
(Source: Merge Replication Provider (Agent); Error number: -2147201019)
------
The remote server is not defined as a subscription server.
(Source: BBLABCW03 (Data source); Error number: 14010)
------
Please help. Thanks.After creating a pull subscription to a transactional Publication, the status
of the pull subscription in the Database -> Pull Subscription Folder will
never change from the default of 'Never Started'
The job and the Pull Subscription Agent will show history for the agent, but
the status does not change in this view.
The problem is that the name of the job is greater than 100 characters, and is
trying to be placed into a temporary table that only allows 100 characters for
the job name.
SELECT job_id
FROM msdb.dbo.sysjobs
WHERE (name = N'SQL02-MyProj-DBReplication-SQL01-RptDB-D3E11F67-B38E-4DE4-82AE-9A3358B902AF')
-- Get job ID
-- Run below command with the job id as input
sp_MSenum_replication_job @.job_id = '388BFC85-BB28-434F-A7AE-77EEBB1A3C8B'
-- If you see this error, then you may need to reduce the -- job description name to resolve this issue
Server: Msg 8152, Level 16, State 6, Procedure sp_help_jobhistory, Line 91
String or binary data would be truncated.
NOTE: Then name of the job is a automatically concatenated by SQL of the
Publishing Server Name + Publishing Database + Publication Name + Subscribing Server + Subscribing Database.
Friday, March 9, 2012
Merge replication ignores some records
i use merge replication as pull, in replication data including some image
data.
Few records are just ignored and they do not appear in subscriber database,
what i can do to make the databases fully synchronized?
Mndr
How are you inserting the image data? If you are using the WRITETEXT and
UPDATETEXT, you will have to create a trigger that will update the row for
merge replication to pick up these changes/updates.
Also are you doing any form of filtering? Sometimes you filters will not
resolve correctly.
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
"Malgorzata Ndreu" <mndreu@.maritweb.com> wrote in message
news:uj%23CXFhLFHA.3512@.TK2MSFTNGP15.phx.gbl...
> Pls advise,
> i use merge replication as pull, in replication data including some image
> data.
> Few records are just ignored and they do not appear in subscriber
database,
> what i can do to make the databases fully synchronized?
> Mndr
>
|||We have this same issue but belive it is related to snapshot creation every
night. If a user downloads a new snapshot and fails to syncronize before a
new snapshot is created, the changes to the database between snapshots will
not replicate to the to the user. What causes this?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OVLbUsiLFHA.2648@.TK2MSFTNGP14.phx.gbl...
> How are you inserting the image data? If you are using the WRITETEXT and
> UPDATETEXT, you will have to create a trigger that will update the row for
> merge replication to pick up these changes/updates.
> Also are you doing any form of filtering? Sometimes you filters will not
> resolve correctly.
> --
> 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
> "Malgorzata Ndreu" <mndreu@.maritweb.com> wrote in message
> news:uj%23CXFhLFHA.3512@.TK2MSFTNGP15.phx.gbl...
> database,
>
|||The snapshot might be created each night, but it will only be sent to
subscribers who are new or who require an reinitialization. It is unlikely
that this is your problem.
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
"Fast Eddie" <e@.bellsouth.net> wrote in message
news:52o0e.74802$%Y4.50101@.bignews6.bellsouth.net. ..
> We have this same issue but belive it is related to snapshot creation
every
> night. If a user downloads a new snapshot and fails to syncronize before
a
> new snapshot is created, the changes to the database between snapshots
will[vbcol=seagreen]
> not replicate to the to the user. What causes this?
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:OVLbUsiLFHA.2648@.TK2MSFTNGP14.phx.gbl...
for[vbcol=seagreen]
image
>
merge replication generation problem
publisher and distributor: SQL Server 2005 X64 build 2221
clients are SQL Express builld 2047
We have 3 of our clients that received the following error at the end
of a merge.
SessionStatistics:
============================
UploadInserts:4
DownloadInserts:1748
DownloadUpdates:67
DownloadDeletes:15
SchemaChanges:1
ChangeDeliveryTime:64sec
SchemaChangeandBulkInsertTime:26sec
DeliveryRate:28.66rows/sec
TotalSessionDuration:368sec
================================================== ===========
2007-04-1823:50:38.669 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.
Since that time, they recieve the same error message at the beginning
of every merge attempt and fail immediately:
2007-04-1900:28:06.672 The merge process was unable to create a new
generation at the 'Subscriber'...
We have marked for re-init, but they get the above message prior and
fail, before ever doing a re-init.
Has anyone seen this? Have any suggestions what to look for/at?
TIA,
jg
Hi,
I am having the same problems with Merge Replication, did you find a solution?
Cheers
Pieter
"johng@.garrisonenterprises.net" wrote:
> Merge Replication Web Sync - Pull subscriptions
> publisher and distributor: SQL Server 2005 X64 build 2221
> clients are SQL Express builld 2047
> We have 3 of our clients that received the following error at the end
> of a merge.
> SessionStatistics:
> ============================
> UploadInserts:4
> DownloadInserts:1748
> DownloadUpdates:67
> DownloadDeletes:15
> SchemaChanges:1
> ChangeDeliveryTime:64sec
> SchemaChangeandBulkInsertTime:26sec
> DeliveryRate:28.66rows/sec
> TotalSessionDuration:368sec
> ================================================== ===========
> 2007-04-1823:50:38.669 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.
>
> Since that time, they recieve the same error message at the beginning
> of every merge attempt and fail immediately:
> 2007-04-1900:28:06.672 The merge process was unable to create a new
> generation at the 'Subscriber'...
>
> We have marked for re-init, but they get the above message prior and
> fail, before ever doing a re-init.
> Has anyone seen this? Have any suggestions what to look for/at?
> TIA,
> jg
>
Merge replication fails
Finally snapshot is generated.
Then i create a pull subscription (i am using merge replication). But after executing 193 actions it gives following error
Line 1: Incorrect syntax near 'No_'
Details are as follow.
1. The subscription has been marked for reinitialization. Reinitialization will occur the next time you synchronize this subscription.
2. Category:SQLSERVER
Source: IM66\WM_MSDE
Number: 170
Message: Line 1: Incorrect syntax near 'No_'.
3. Category:NULL
Source: Merge Replication Provider
Number: -2147201001
Message: The process could not deliver the snapshot to the Subscriber.
4. Line 1: Incorrect syntax near 'No_'. The step failed.
Please Help.
Do i need to create a snapshot again? ( It takes almost 2-3 hours to create a snapshot of 995 articles).
Hi,
Is this SQL 2000 or SQL 2005?
Do you have any tables like %No_%?
Are there any special characters in this name?
Can you narrow down which table is it failing on?|||
It's SQL 2000.
There are lots many table having No_ as primary key.
Above history i have taken from Job History.
From where can i get the exact table name?
When i right click on merge agent and click on Error Details , i see following info.
Category Source Number
Data Source Subscriber Name 170
Agent Merge Replication Provider -2147201001
Please help.
|||995 articles is certainly a large publication. Are they all table articles, or are some of the stored procedures, views, functions, etc.?I recomment you split this into two publications, one for just schema objects (stored procedures, views, functions, etc.) and one for table articles. This way if you change a stored procedure, it'll be much easier to propogate it to all the subscribers by reinit'ing just that one publication with schema objects, as opposed to a single publication with 995 objects.
and vice versa, if you need to reinit due to a change in a table article, then you don't have to spend valuable time regenerating bcp files, scripts, etc. for all 995 objects, just for that subset.|||
Can you query table MSmerge_history in distribution database and see if there are more details leading up to the failure? WHen applying the snapshot, it might tell you what file it's trying to apply. If you open that file, you may be able to see the TSQL that's failing.
If the history table doesn't tell you anything, can you change the -HistoryVerboseLevel from 1 to 2, as well as pipe the output of the merge agent to a file by using -Output "c:\somefilename.txt". If you open up your merge agent profile, you can add or modify these parameters. THen rerun the merge agent.
Is this SQL Server 2000 Sp4?
|||They are all table articles. I have not included schema objects yet.Actually i am trying to implement replication for navision. I am using Microsoft Business Solution Navision (With sql option).
|||
I have SQL Server 2000 with Sp4.
On the distributor side there is no Msmerge_history, instead Msmerge_genhistory is there. I opened it but is contains data which gives information regarding snapshot generation.
Then i created a new merge agent profile. with -Historyverboselevel set to 2. where can i find -Output property. There is no such property in agent's profile.
Please help.
|||You have to add the parameter to the existing profile, or you can create your own custom profile. Just add -Output "<some file name>". If you still need help with this, please reference: http://msdn2.microsoft.com/en-us/library/ms221382.Wednesday, March 7, 2012
merge replication error
I,m trying to pull a suscription for the first time so I create the database
when I create the suscription but I'm getting this error.
could not be propagated to the subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
Unable to replicate a view or function because the referenced objects or
columns are not present on the Subscriber.
(Source: SQLServer (Agent); Error number: 0)
Invalid object name 'dbo.Clients'.
(Source: SQLServer (Data source); Error number: 208)
Invalid object name 'dbo.EmailJobReports'.
(Source: SQLServer (Data source); Error number: 208)
Invalid object name 'dbo.EmailLinks'.
(Source: SQLServer (Data source); Error number: 208)
Invalid object name 'dbo.Employees'.
(Source: SQLServer (Data source); Error number: 208)
Why is not creating this tables?
Tks in advance for you help..
Johnny
Tks Paul,
I will put my views in a separate publication.
Johnny
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:044401c4d7c8$5d17d310$a601280a@.phx.gbl...
> JFB,
> on SQL Server 2005 you can specify the article processing
> order, but not on SQL Server 2000. To avoid this type of
> issue, you could put the views into a separate
> publication or use sp_addscriptexec to send over
> separately (not forgetting the permissions though).
> Rgds,
> Paul Ibison
>
|||Are these object present on the subscriber? Are these objects part of your
publication?
If they are not present on your subcsriber and are not part of your
publication you will have to manually script them out and deploy them to
your subscriber. Possibly by using sp_addscriptexec if all of your
subscriptions were deployed using a UNC.
you could also use a pre snapshot script to deploy these objects.
If they are not present on your subscriber and are part of your publication
they are not being created in the correct order.
Replication does order the article creation scripts correctly, however it
depends on sysdepends on the publisher which can be inacurate. Your best
option again is a pre snapshot command containing a script which will
precreate these objects for you.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"JFB" <jfb@.newSQL.com> wrote in message
news:OyqGUZ81EHA.3820@.TK2MSFTNGP11.phx.gbl...
> Hi All,
> I,m trying to pull a suscription for the first time so I create the
> database when I create the suscription but I'm getting this error.
> could not be propagated to the subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ----
> Unable to replicate a view or function because the referenced objects or
> columns are not present on the Subscriber.
> (Source: SQLServer (Agent); Error number: 0)
> ----
> Invalid object name 'dbo.Clients'.
> (Source: SQLServer (Data source); Error number: 208)
> ----
> Invalid object name 'dbo.EmailJobReports'.
> (Source: SQLServer (Data source); Error number: 208)
> ----
> Invalid object name 'dbo.EmailLinks'.
> (Source: SQLServer (Data source); Error number: 208)
> ----
> Invalid object name 'dbo.Employees'.
> (Source: SQLServer (Data source); Error number: 208)
> ----
> Why is not creating this tables?
> Tks in advance for you help..
> Johnny
>
|||Tks for reply Hilary,
These objects are not in the suscriber and are part of the publication.
How can i create it in the correct order?
can you show me how to use a pre snapshot command?
Sorry but I'm new in replication.
Also Paul tell me that I can include the views in a different publication,
because I soon I get out the views the replication works but of course my
database is not complete.
Tks again
Johnny
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OhWVHs81EHA.3504@.TK2MSFTNGP12.phx.gbl...
> Are these object present on the subscriber? Are these objects part of your
> publication?
> If they are not present on your subcsriber and are not part of your
> publication you will have to manually script them out and deploy them to
> your subscriber. Possibly by using sp_addscriptexec if all of your
> subscriptions were deployed using a UNC.
> you could also use a pre snapshot script to deploy these objects.
> If they are not present on your subscriber and are part of your
> publication they are not being created in the correct order.
> Replication does order the article creation scripts correctly, however it
> depends on sysdepends on the publisher which can be inacurate. Your best
> option again is a pre snapshot command containing a script which will
> precreate these objects for you.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> Now available for purchase at:
> http://www.nwsu.com/0974973602.html
> "JFB" <jfb@.newSQL.com> wrote in message
> news:OyqGUZ81EHA.3820@.TK2MSFTNGP11.phx.gbl...
>
|||Note that in my case I don't have inter-view
dependencies, so this is possible. If you have views that
query other views, then the same issue may arise. In that
case you'll need to consider sp_addscriptexec.
Rgds,
Paul Ibison
|||Tks for u reply Paul,
How can I use sp_addscriptexec in my snapshot or publication?
You know I'm new and I dont know how to use this... I create the script for
the views in a sql file..
Regards
Johnny
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:082701c4d865$fbb42440$a601280a@.phx.gbl...
> Note that in my case I don't have inter-view
> dependencies, so this is possible. If you have views that
> query other views, then the same issue may arise. In that
> case you'll need to consider sp_addscriptexec.
> Rgds,
> Paul Ibison
>
|||The details are in BOL
(http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/tsqlref/ts_sp_repl_6qzn.asp). It isn't
really added to the publication, but is a way of using
the replication 'plumbing' to run a script (using osql).
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)