Merge SQL 7 to 2000 problem

I am having a problem running a merge replication between
a SQL 7 publisher/distributor and a SQL 2000 subscriber
(push). After the subscription is initialized, the agent
fails with the error "The process could not query row
metadata at the Subscriber." The error details
says "Could not find stored procedure ''." A clip from
the log is below. This same merge replication works fine
from SQL 7 to SQL 7, but fails to SQL 2000. I have tried
2 different SQL 2k boxes with the same error.
The replication job logs in using SQL Server
authentication. Account is system administrator and dbo
on subscriber. Distributor runs under sa. Both Servers
are at latest SP levels. KB search has turned up no help.
Thanks for any ideas!
~~~~~~~~~~~~~~~~~~snip~~~~~~~~~~~~~~~~~~~
Percent Complete: 55
Processing article 'RequestStatusHistory'
Repl Agent Status: 3
chrs4.ITWorkRequest: {call sp_MSenumcolumns (?,?)}
chrs4.ITWorkRequest: {call sp_MSenumchanges(?,?,?,?,?)}
CHHIST.ITWorkRequest: {call sp_MSgetrowmetadata
(?,?,?,?,?,?,?)}{call sp_MSgetrowmetadata(?,?,?,?,?,?,?)}
{call sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}
Percent Complete: 0
The process could not query row metadata at the
Subscriber.
Repl Agent Status: 6
Percent Complete: 0
Category:COMMAND
Source: Failed Command
Number:
Message: {call sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call
sp_MSgetrowmetadata(?,?,?,?,?,?,?)}{call sp_M
Repl Agent Status: 3
Percent Complete: 0
Category:SQLSERVER
Source: CHHIST
Number: 2812
Message: Could not find stored procedure ''.
Repl Agent Status: 3
Could not find stored procedure ''.
Disconnecting from Publisher 'chrs4'
Disconnecting from Subscriber 'CHHIST'
Disconnecting from Publisher 'chrs4'
Disconnecting from Distributor 'chrs4'
George,
this is not a supported configuration. For merge replication, a SQL 7.0
publisher can only publish to a SQL 7.0 Subscriber.
Rgds,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
Thanks for the reply. I read the "...Different Versions"
article in books online, but obviously scanned too
quickly. I see the limitation now for merge, but not for
snap and trans. You might help out "Nick Horrocks" with
an answer to his thread "Unable to create Merge
subscription".
George

>--Original Message--
>George,
>this is not a supported configuration. For merge
replication, a SQL 7.0
>publisher can only publish to a SQL 7.0 Subscriber.
>Rgds,
>Paul Ibison
>(recommended sql server 2000 replication book:
>http://www.nwsu.com/0974973602p.html)
>
>.
>
|||Thanks for the prompt - have posted to Nick as well.
Rgds,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

>--Original Message--
>Paul,
>Thanks for the reply. I read the "...Different Versions"
>article in books online, but obviously scanned too
>quickly. I see the limitation now for merge, but not for
>snap and trans. You might help out "Nick Horrocks" with
>an answer to his thread "Unable to create Merge
>subscription".
>George
>
>replication, a SQL 7.0
>.
>

Merge Snapshot execution does not create any BCP files for data tables.

Good Day,
After running Merge Snapshot Subscription Job No BCP files are created
for the data tables:
here is my code for the Merge Articles:
Dim lbResult As Boolean
Dim lobjMArt As MergeArticle2
Dim lbHasIdentity As Boolean
Set lobjMArt = New MergeArticle2
lobjMArt.Name = asTableName
lobjMArt.SourceObjectName = asTableName
lobjMArt.SourceObjectOwner = "dbo"
UpdateLog "CreationScriptOptions Default Value is: " &
lobjMArt.CreationScriptOptions
If abHasIdentity Then
lobjMArt.AutoIdentityRange = True
lobjMArt.PublisherIdentityRangeSize = 1000000
lobjMArt.SubscriberIdentityRangeSize = 1000000
lobjMArt.IdentityRangeThreshold = 85
End If
pobjSQLDMOMerge.MergeArticles.Add lobjMArt
Set lobjMArt = Nothing
lbResult = True
The Job History Shows:
bulk copying snapshot data for article [TableName] (0 rows).
This is shown for all tables. 90 % of my tables contain records. For
Example the Patient Table has 675 records.
What am i Missing?
Thanks In Advance.
Brian
The agent just ran and created the bcp files.
The agent is scheduled to run @. 12:00 am. Why did it work through
scheduled execution and not through code.
Am I missing something from this code:
Dim lbResult As Boolean
Dim lsErrSource As String
Dim lsJobID As String
Dim liX As Long
Dim lobjDis As SQLDMO.Distributor2
Dim lobjDisPubs As SQLDMO.DistributionPublishers
Dim lobjDisPub As SQLDMO.DistributionPublication2
Dim lobjJobs As SQLDMO.Jobs
Dim lobjJob As SQLDMO.Job
Dim loJobHis As SQLDMO.JobHistoryFilter
Dim loQR As SQLDMO.QueryResults2
Dim liY As Integer 'Rows
UpdateLog "Refresh Snapshot Function"
'===Load an Default Vars
lsErrSource = "clsPublisher.RefreshSnapShot"
'===Parse the Connection String:
If ParseConnectionString(asConnect) Then
If ConnectToServer() Then
'pobjSQLServer now equals the Sever object.
'We need to get a copy of the Publication DB.
Set lobjDis = pobjSQLServer.Replication.Distributor
Set lobjDisPubs = lobjDis.DistributionPublishers
'Set lobjDisPub =
lobjDis.DistributionPublishers(psPubServer).Distri butionPublications.Item("Promise:Promise")
Set lobjDisPub =
lobjDisPubs(psPubServer).DistributionPublications. Item(1)
UpdateLog ("DisPub Name: " &
lobjDisPubs(psPubServer).DistributionPublications. Item(1).Name)
lsJobID = lobjDisPub.SnapshotJobID
psJobName = lobjDisPub.SnapshotAgent
Set lobjDisPub = Nothing
Set lobjDisPubs = Nothing
Set lobjDis = Nothing
Set lobjJobs = pobjSQLServer.JobServer.Jobs
'Get the Job to Start it.
UpdateLog ("Job Info: ID:" & lsJobID & " Name: " &
psJobName)
Call SaveSetting("Horizon Healthware Inc", "Promise",
"ReplicationJobName", psJobName)
Set lobjJob = lobjJobs.Item(psJobName)
UpdateLog ("Job: Starting Job.")
lobjJob.Invoke
liX = 0
lobjJob.Refresh
Do While lobjJob.CurrentRunStatus <>
SQLDMOJobExecution_Idle
liX = liX + 1
If liX = 200000 Then
lobjJob.Refresh
DoEvents
liX = 0
End If
Loop
' loJobHis.JobName = asJobName
' loJobHis.OldestFirst = False
'
' Set loQR =
pobjSQLServer.JobServer.EnumJobHistory(loJobHis)
'
' liX = 1
'
'
' For liX = 1 To loQR.Columns
' 'UpdateLog ("Job History ColumnName :" &
loQR.ColumnName(liX) & " Value:" & loQR.GetColumnString(1, liX))
'
' Next
Set loQR = Nothing
Set loJobHis = Nothing
Set lobjJob = Nothing
Set lobjJobs = Nothing
Call DisconnectFromServer
lbResult = True
Else
Err.Raise hhwErrorNum.lErrUnableToConnectToServer,
lsErrSource, ptErrorDesc.sErrParsingConnectionString
End If
Else
lbResult = False
Err.Raise hhwErrorNum.lErrParsingConnectionString, lsErrSource,
ptErrorDesc.sErrUnableToConnectToServer
End If
Thanks
Brian
sql

Merge reversed

Running Win 2000 & SQL 2000
I have a merge publication/subscription (rows are
filtered by location), replicating data between 16
servers (15 remote location & a main office). When data
is changed at the a remote location, the changes gets
propagated to the main office, but at some point, the
change gets reversed.
Any idea what is causing this?
Larry,
when you say it gets reversed, do you mena the row is deleted from the
subscriber? This could be caused if you are partitioning data and a row has
been added on a subscriber which doesn't accord with its filter.
HTH,
Paul Ibison
|||Look in the conflict table, for the article, on the publisher. This might
give you a clue as to what is going on.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Paul,
No the row is not deleted, but changed back to its
original state, prior to being updated at the
subscriber. This happens sporadically, but is causing
MAJOR problems.
Larry...
|||Rand,
There is nothing in the conflict tables for any article
in the publication.
Larry...
|||I saw your reply to Rand and if both filtering and conflicts are ruled out
(and no user on the publisher is altering the data!) then this is very
strange. I'd use profiler or an audit trigger to capture what is going on.
HTH,
Paul Ibison
|||Thanks Paul...will do.
|||Does the MSmerge_history table on the distributor offer any reason why
the updates were not applied?
Reinout Hillmann
SQL Server Product Unit
This posting is provided "AS IS" with no warranties, and confers no rights.
anonymous@.discussions.microsoft.com wrote:
> Rand,
> There is nothing in the conflict tables for any article
> in the publication.
> Larry...
>

Merge Replication Synchronization Manager

Hi,
after upgrading a client within a Merger Replication scenario from MSDE2000A
to SQL Express SP1 the subscription is no longer listed within the
synchronisation manager.
How to register the subscription within Synchronization Manager?
(I know it is possible within Management Studio but I need to automate this
process).
Thanks in advance,
Thomas
have you tried to pull it again in WSM?
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
"ThoHot00" <ThoHot00@.discussions.microsoft.com> wrote in message
news:F36273CF-38BA-4A7C-A373-CB96CCDE37E4@.microsoft.com...
> Hi,
> after upgrading a client within a Merger Replication scenario from
> MSDE2000A
> to SQL Express SP1 the subscription is no longer listed within the
> synchronisation manager.
> How to register the subscription within Synchronization Manager?
> (I know it is possible within Management Studio but I need to automate
> this
> process).
> Thanks in advance,
> Thomas
|||Hi Hilary,
I haven't tried to pull it again within WSM. I would need to reregister it
within WSM, but since this upgrade occurs within a software upgrade I do not
have access to all client machines and I need a solution that I can integrate
into an installer package.
The subscription registration can still be found under
HKLM\Software\Microsoft\Microsoft SQL Server\80\Replication\Subscriptions\...
If I copy this entry to HKLM\Software\Microsoft\Microsoft SQL
Server\90\Replication\Subscriptions\... the subscription shows up in WSM and
works fine. I'm a little bit worried about the fact that within this key is
entry called subid. When I regenerate this entry using "Management Studio"
the subid is different and there is one additional entry called WebSync.
WebSync is always 0 in our case but I don't have a clue where the changed
subid comes from. If I call sp_helpmergepullsubscription it still shows the
"old" subid.
Greetings,
Thomas
"Hilary Cotter" wrote:

> have you tried to pull it again in WSM?
> --
> 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
> "ThoHot00" <ThoHot00@.discussions.microsoft.com> wrote in message
> news:F36273CF-38BA-4A7C-A373-CB96CCDE37E4@.microsoft.com...
>
>

Merge replication subscription error with proxy

Ok, perhaps I'm a moron.. believe me, I'd be glad to admit it if I
could just get this fixed.
We're trying to merge replicate data via https, we have installed the
CA certificate and can connect to the replisapi.dll through IE. I used
the following script to generate the subscription:
DECLARE @.publication AS sysname;
DECLARE @.publisher AS sysname;
DECLARE @.publicationDB AS sysname;
DECLARE @.websyncurl AS sysname;
DECLARE @.login AS sysname;
DECLARE @.password AS nvarchar(512);
SET @.publication = N'tables';
SET @.publisher = N'server';
SET @.publicationDB = N'database';
SET @.websyncurl = 'https://webserver/WebSync';
SET @.login = N'websql\user';
Set @.password = N'pass';
USE [LocalDB]
EXEC sp_addmergepullsubscription
@.publisher = @.publisher,
@.publication = @.publication,
@.publisher_db = @.publicationDB,
@.subscriber_type = N'anonymous';
EXEC sp_addmergepullsubscription_agent
@.publisher = @.publisher,
@.publisher_db = @.publicationDB,
@.publication = @.publication,
@.distributor = @.publisher,
@.job_login = @.login,
@.job_password = @.password,
@.use_web_sync = 1,
@.internet_url = @.websyncurl,
@.internet_login = @.login,
@.internet_password = @.password,
@.enabled_for_syncmgr = 'true';
GO
This creates the subscription locally but gives me the error
"websql\user not a valid Windows account". I tried changing the
job_login & job_password to a local account and the subscription was
added without errors. When I go to start the syncronization I get the
error: "The system cannot find the file specified." The underlying
error here is with the proxy. For some reason when it tries to connect
it isn't passing the proper credentials or something.
Anyway, any I'd appreciate any help or direction. If I find out what's
wrong I'll go ahead and post it.
JC
That's because it is creating the agent at the subscriber and when doing so,
you are specifying an account of websql\user which does not exist on the
subscriber. If you change this to a local account and then try to
synchronize, you will get security errors, because the SID of the local
account you set it to does not have a valid scope outside of the local
machine. The job login and password can be a local account and it dosn't
affect anything. However, take a look at the other credential. You are
setting the synchronization context to websql\user and that account, since
it doesn't exist on the local machine can't generate the file which is used
to synch via https. (The more accurate error message would be user doesn't
exist or access denied.)
I don't have a system setup to be able to configure https synchronization
right now. I've done this before and your issue is with the security
context. I just can't remember what I did before to fix this particular
error.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
<jbzcooper@.gmail.com> wrote in message
news:1138315588.689076.326990@.g14g2000cwa.googlegr oups.com...
> Ok, perhaps I'm a moron.. believe me, I'd be glad to admit it if I
> could just get this fixed.
> We're trying to merge replicate data via https, we have installed the
> CA certificate and can connect to the replisapi.dll through IE. I used
> the following script to generate the subscription:
> DECLARE @.publication AS sysname;
> DECLARE @.publisher AS sysname;
> DECLARE @.publicationDB AS sysname;
> DECLARE @.websyncurl AS sysname;
> DECLARE @.login AS sysname;
> DECLARE @.password AS nvarchar(512);
> SET @.publication = N'tables';
> SET @.publisher = N'server';
> SET @.publicationDB = N'database';
> SET @.websyncurl = 'https://webserver/WebSync';
> SET @.login = N'websql\user';
> Set @.password = N'pass';
> USE [LocalDB]
> EXEC sp_addmergepullsubscription
> @.publisher = @.publisher,
> @.publication = @.publication,
> @.publisher_db = @.publicationDB,
> @.subscriber_type = N'anonymous';
> EXEC sp_addmergepullsubscription_agent
> @.publisher = @.publisher,
> @.publisher_db = @.publicationDB,
> @.publication = @.publication,
> @.distributor = @.publisher,
> @.job_login = @.login,
> @.job_password = @.password,
> @.use_web_sync = 1,
> @.internet_url = @.websyncurl,
> @.internet_login = @.login,
> @.internet_password = @.password,
> @.enabled_for_syncmgr = 'true';
> GO
> This creates the subscription locally but gives me the error
> "websql\user not a valid Windows account". I tried changing the
> job_login & job_password to a local account and the subscription was
> added without errors. When I go to start the syncronization I get the
> error: "The system cannot find the file specified." The underlying
> error here is with the proxy. For some reason when it tries to connect
> it isn't passing the proper credentials or something.
> Anyway, any I'd appreciate any help or direction. If I find out what's
> wrong I'll go ahead and post it.
> JC
>
|||Mike,
Appreciate the reply and you are correct. I split the credentials into
two, one for the machine and one for the web. This brought up a second
error which I pondered for some time until a colleage suggested I look
at the security permissions for the login. I tried several things but
this is what I was doing when I got it to work:
0. Ensure that windows account SQL run under has proper authority to
execute job
1. Log into windows using the windows account SQL is using
2. Log into SQL using Windows Authentication
3. Execute the above script (after adding a second set of credentials
for the job)
4. Run replication
Some of the above steps may not be necessary.. it just worked for me.
HTH someone else.. man, I was in a bad spot.
JC

Merge replication reinitialization deleted all data

Hello,

When I reinitialized a subscription from SQL2005 db (publisher) to a SQL 2000 DB (Subscriber) and had the Upload changes before reinitialization turned on, the data from the SQL 2000 db didn't get uploaded. This resulted in a loss of 2 days worth of data.

Does anyone have any idea if there's anywhere that data is kept. (unfortunately a series of errors caused our backups to not be running on the 2000 db either).

Thank You

Bob

sorry, your data is gone. I also find it hard to believe your data didn't get uploaded - how did you indicate you wanted the data uploaded? Was this reinitialized from the UI?|||

Yes it was from the UI and the box marked "Upload data before reinitialization" was checked.

|||

I could not reproduce the problem.

I tried push and pull SQL 200 subscriptions from a SQL 2005 publication/pulisher.

Could you give me more details on what kind of subscription you have and the SP of SQL you are running on both the servers?

Also can you continue to reproduce this? If so, some more details and some steps would be of help.

Merge Replication Recovery

Hi,
Had merge replication set up between two servers. with push subscription.
For various reasons the replication stopped running for a few days and now
we have different data at both sites.
Does anybody have a series of steps to get this back up and running other
than the following.
1. Create new db at subscriber.
2. Publish to this new sunscriber from existing publication.
3. Piece in missing data from offline subscriber.(data inserted at
subscriber since merge stopped).
Any other suggestions?
You should be able to synchronize to get things back up, provided you
haven't exceeded the retention period - the publication retention value is
used to determine when subscriptions that have not synchronized within the
retention period should expire and it is set to 14 days by default. If this
is not an option, then I'd use Redgate'd DataCompare to generate the change
script to be applied at the publisher then reinitialize the subscriber.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||run a validation to determine how out of sync you are. Run the merge agent
until it completes. Chances are you will be in sync after it runs.
The problem with trying to enter the data manually or through applets like
DataCompare is that when you enter this data on the subscriber to try to
sync it
it will raise all sorts of conflicts when you run the merge agent, and
they will be kicked back and you will be returned the state you where in
before.
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
|||Fair point, but I was recommending using the RedGate change script at the
publisher and subsequently reinitializing the subscriber. It's not very
sophisticated and the data size might make it unattractive, but it should
work.
Rgds,
Paul
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:opso0n92xurj9kur@.hcottter-lap.ap.org...
> run a validation to determine how out of sync you are. Run the merge agent
> until it completes. Chances are you will be in sync after it runs.
> The problem with trying to enter the data manually or through applets like
> DataCompare is that when you enter this data on the subscriber to try to
> sync it
> it will raise all sorts of conflicts when you run the merge agent, and
> they will be kicked back and you will be returned the state you where in
> before.
> --
> 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
|||Thanks for all the suggestions guys. The replicationanswers website is very
informative. Just a quick question Hilary you mentioned run a validation,
what exactly did you mean by that? write my own routine.
Just for info we did get the snapshot reapplied to the subscription but the
data changes at the subscriber did not get applied, despite being well
within the retention period so we had to maunally rebuild the data.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:eh4LsOdPFHA.2748@.TK2MSFTNGP09.phx.gbl...
> Fair point, but I was recommending using the RedGate change script at the
> publisher and subsequently reinitializing the subscriber. It's not very
> sophisticated and the data size might make it unattractive, but it should
> work.
> Rgds,
> Paul
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:opso0n92xurj9kur@.hcottter-lap.ap.org...
>
|||if your subscription is a global subscription you should be able to
synchronize!
MB wrote:
> Thanks for all the suggestions guys. The replicationanswers website
is very
> informative. Just a quick question Hilary you mentioned run a
validation,
> what exactly did you mean by that? write my own routine.
> Just for info we did get the snapshot reapplied to the subscription
but the
> data changes at the subscriber did not get applied, despite being
well[vbcol=seagreen]
> within the retention period so we had to maunally rebuild the data.
>
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
> news:eh4LsOdPFHA.2748@.TK2MSFTNGP09.phx.gbl...
at the[vbcol=seagreen]
very[vbcol=seagreen]
should[vbcol=seagreen]
merge[vbcol=seagreen]
runs.[vbcol=seagreen]
applets[vbcol=seagreen]
subscriber to[vbcol=seagreen]
and[vbcol=seagreen]
where in[vbcol=seagreen]

Merge Replication Pull Subscription Error

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 between al
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 created a new pull subscription and I noticed that the subscriber is downloading changes from the publisher (new rows or changes made on other subscribers) but is not uploading new info back to the publisher.

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.

merge replication partition options

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...
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 metedata cleanup error

Hi,

We have a merge subscription which is reporting the following error at the subscriber:

The Merge Agent failed after detecting the retention-based metadata cleanup has deleted metadata at the Publisher for changes not yet set to the Subscriber. You must reinitalize the subscription (without upload)

I'm a bit confused about this - there have been no changes made at the publisher - why would we be getting this message?

thanks
Bruce

The data changes that the merge agent is referring to are the metadata contained in the merge tables MSmerge_contents, MSmerge_tombstone, MSmerge_genhistory. Periodically this data needs to be purged otherwise it starts to impact performance.

If the retention period is passed the subscription will expire as the meta data will be removed. You will need to reinitialize the subscription. Here is some more information about setting the retention period.

http://msdn2.microsoft.com/en-us/library(d=robot)/ms151188.aspx

Thanks

Nabila Lacey

Merge replication issue - The subscription to publication is invalid

I am trying to configure a merge replication of publication with 151 table-articles over 128 kbps line via proxy (Win XP, WinProxy), which is used for connection to internet as well.
The whole snapshot runs well, all the data are pumped to the subscriber and all dri, trg etc. scripts are executed without problem, but instead of the message "No data needed to be merged" comes out this error message:

Last Command: {call sp_MSgetreplicainfo(?,?,?,?,?,?,?)}

The subscription to publication 'Katalog' is invalid.
(Source: Merge Replication Provider (Agent); Error number: -2147201019)
--------------------------
General network error. Check your network documentation.
(Source: FANTOM (Data source); Error number: 11)
--------------------------

When I try to replicate the small Northwind database, everything works fine, no errors. When I try to replicate only a few tables from my big database, everything works fine.

Thank you very much for any ideas.The problem is probably in WinProxy. When comunicating without Proxy everything goes OK.|||Hi,

I had seen your psting and asking your help.

How do I use the FTP option in Merge Replication

I am using Merge Replication on SqlServer 2000 with SP2 and MDAC2.7 loaded on my system.
My database version is 8.00.534 on Windows2000 Advancedserver.

Both Publisher and Subscriber are running with same versions.

I created a publication and I created a pull subscription using internet.
I want the subscriber machine to access the Publisher
machine via ftp and get the Snapshot and do
Synchronization.

I had setup the following parameters at the Publisher side
for the publication.

1.Generate snapshots in the following location as

\\myservername\D$\Microsoft SQL Server\MSSQL\REPLDATA\ftp which is UNC shared with full access.

2.Checked - Subscribers can access this folder using FTP

ftpservername -myservername
port-21

Login-Anonymous, no password

3.At subscriber side I had setup SnapshotLocation property as
Download the folder using File Transfer Protocol - checked

I get the following errors at Synchronization time
After configuring subscriber for merge replication i am getting staus as succeeded at the subscriber.

when performing data modifications I am getting following errors during synchronisation time.

Errors

Category:NULL
Source: Merge Replication Provider
Number: -2147201001
Message: The schema script '' could not be propagated to the subscriber.

Category:AGENT
Source: SRVH
Number: 0
Message: The process could not connect to FTP site 'HERITAGEAMERICA' using port 21.

Category:OS
Source:
Number: 12007
Message: The server name or address could not be resolved

The schema script '' could not be propagated to the subscriber. The step failed.

Microsoft conformed this is a bug and that details are
Question number is Q318592.
BUG #: 356652 (SHILOH_BUGS) BUG #: 356652 (SHILOH_BUGS)

Microsoft confirmed that this is a bug when we use different versions check with the Question in microsoft site in fixes.

I am getting same error for same versions also.

Can anyone help me on how to use FTP for accessing
Snapshots?

Thanks|||Hello,

I have not any experience with using FTP for merge replication over internet, we are using VPN connection to the server on port 1433.
But as far as I understood, you do not get the error message when transferring a snapshot but at the moment, when the distributor needs to propagate data changes between publisher and subscriber.
I suppose it is important when do you get the error message: whether on the very beginning of applying the snapshot or at the end.
Also would be useful to check, whether the FTP connection is reliable (proxies, switches etc.).

Caruso|||Hi

May be you can help me wit a minor problem in Merge replication. I am trying to perform merge replication on two SQL Server 2000 databases on Windows Nt 4.0 platform using TCP/IP and FTp. Have set everything in Publication and Subscriber for FTp and the subscriber can connect to publisher.

I am getting the followiing error message afetr running replmerg.exe withh all required parameters for FTP.

Microsoft SQL Server Merge Agent 8.00.194
Copyright (c) 2000 Microsoft Corporation

Connecting to Subscriber 'RAJ'
Connecting to Distributor 'VTPL'
Initializing
Connecting to Publisher 'VTPL'
Retrieving publication information
Retrieving subscription information
Snapshot files will be downloaded via ftp
Connecting to ftp site 'VTPL'
The subscription has been marked for reinitialization. Reinitialization will occur the next time you synchronize this subscription.
The schema script '\\VTPL\C$\Program Files\Microsoft SQL Server\MSSQL\ReplData\ftp\VTPL_Caryaire_F2\2003010 7120306\RightMain_1.sch' could not be propagated to the subscriber.
Category:NULL
Source: Merge Replication Provider
Number: -2147201001
Message: The schema script '\\VTPL\C$\Program Files\Microsoft SQL Server\MSSQL\ReplData\ftp\VTPL_Caryaire_F2\2003010 7120306\RightMain_1.sch' could not be propagated to the subscriber.
Category:AGENT
Source: VTPL
Number: 0
Message: The process could not retrieve file 'VTPL_Caryaire_F2\20030107120306\RightMain_1.sch' from the FTP site 'VTPL'.
Category:OS
Source:
Number: 12003
Message: 200 Type set to I.
200 PORT command successful.
550 VTPL_Caryaire_F2\20030107120306\RightMain_1.sch: The system cannot find the path specified.
550 VTPL_Caryaire_F2\20030107120306\RightMain_1.sch: The system cannot find the path specified.

The process finished. Use CTRL+C to close this window.

I am desparately in need of a solution. Can anyone help me out?

Thanks and regards,
Anamika|||Hi,

Anamika, first thing I would like you to do is check the verison of SQL server 2000. Merge Replication module has some problems. It have been fixed in the SQL server SP3. It is essential to apply this pack on SQL server.

Secondly you need to check ftp settings. your ftp service or root directory of ftp is not configured properly. Due to this you are getting "The process could not retrieve file 'VTPL_Caryaire_F2\20030107120306\RightMain_1.sch' from the FTP site 'VTPL'. "VTPL_Caryaire_F2" parent folder should be root of ftp site.
Details are available in windows or in IIS about ftp configuration.

Merge Replication Issue

Hi,
My Merge replication setup for a particular table has 1 subscriber and
muliple publishers. Each publisher will push the subscription to the
subscriber.
However, I am encountering some issues with this setup.
Findings:
Any record inserted/deleted/updated in either Publisher 1 or Publisher 2
will be reflected in Subscriber.
Any record inserted/deleted/updated in Subscriber will be reflected in
Publisher 1 and Publisher 2.
Issue:
Any record replicated in Subscriber from one publisher is NOT reflected in
the other publisher (e.g. Insert new record in Publisher 1, inserted record
gets replicated in Subscriber but does not insert this new record in
Publisher 2, vice versa)
I will like to find out if there is any setting or consideration that I need
to make with regards to my merge replication setup, in order to allow changes
made in any of the publisher to be replicated in the subscriber and then
reflected in other publishers.
Will definitely appreciate any of your inputs and advice.
Thanks In Advanace,
Roy Tan
Had made changes to my configuration. I have a single publisher and multiple
subscribers and everything seems to work fine. I am just wondering when do we
actually apply a "single subscriber and multiple publisher" scenario.
"Roy Tan" wrote:

> Hi,
> My Merge replication setup for a particular table has 1 subscriber and
> muliple publishers. Each publisher will push the subscription to the
> subscriber.
> However, I am encountering some issues with this setup.
> Findings:
> Any record inserted/deleted/updated in either Publisher 1 or Publisher 2
> will be reflected in Subscriber.
> Any record inserted/deleted/updated in Subscriber will be reflected in
> Publisher 1 and Publisher 2.
> Issue:
> Any record replicated in Subscriber from one publisher is NOT reflected in
> the other publisher (e.g. Insert new record in Publisher 1, inserted record
> gets replicated in Subscriber but does not insert this new record in
> Publisher 2, vice versa)
> I will like to find out if there is any setting or consideration that I need
> to make with regards to my merge replication setup, in order to allow changes
> made in any of the publisher to be replicated in the subscriber and then
> reflected in other publishers.
> Will definitely appreciate any of your inputs and advice.
> --
> Thanks In Advanace,
> Roy Tan

Merge replication failure

After working for about 30 minutes (delivering the snapshot) the replication
failed
I checked the Session details of the subscription and I found Action Message
saying the 'The process could not deliver the snapshot to the Subscriber.'
In the error information under Data Source I found the following message
'General network error. Check your network documentation.'
Checking the network log I got the following message: SQL Server Scheduled
Job 'SERVER\SERVER1-MRN1-MRN1_rep-XYZSERVER.ABC.LOCAL-12'
(0x97E3EAE1F1106144B16C808A6492CB9C) - Status: Failed - Invoked on:
2006-09-28 20:23:00 - Message: The job failed. The Job was invoked by
Schedule 35 (Replication agent schedule.). The last step to run was step 3
(Detect nonlogged agent shutdown.).
Any clue?
Samuel
Samuel,
what happens if you restart the agent - normally this'll solve a network
outage.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||It happens consistantly during the initial stage when the entire database
was replicated
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:uN7b$g84GHA.1188@.TK2MSFTNGP05.phx.gbl...
> Samuel,
> what happens if you restart the agent - normally this'll solve a network
> outage.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
|||Samuel,
I'd enable logging to see if this gets more info
(http://support.microsoft.com/?id=312292), especially if the failure is at
the same point each time. Otherwise I'd look at monitoring the network for
outages - network connectivity problems.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

Merge replication fails

Hi all,
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.

Merge replication error??

Error: 29045--
Error: 0--The validity period of subscription went out. It is necessary to
re-initialize.
Error: 0--Subscription for 'SanyoMB_CE’publication is invalid.
Context:
Firstly, when I synchronized the above mentioned error occurs.
Although we carry out synchronization again, the same error occurs.
However, after 10 minutes, we carry out synchronization the third time, that
error does not occur, it runs normally.
What is the reason which make this error occur?
The reason you get this error is that your subscriber is off line for a
longer period than what you specified in the retention period or your
history retention period. Make sure both these values match and are set to a
reasonable level.
The reason you got the "Subscription for 'SanyoMB_CE'publication is invalid"
message is because your snapshot had not been created or had not finished
creation yet.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Mai Thoa" <MaiThoa@.discussions.microsoft.com> wrote in message
news:9708BCE3-39F6-4F85-92D4-58A1E41E69B4@.microsoft.com...
> Error: 29045--
> Error: 0--The validity period of subscription went out. It is necessary
to
> re-initialize.
> Error: 0--Subscription for 'SanyoMB_CE'publication is invalid.
> Context:
> Firstly, when I synchronized the above mentioned error occurs.
> Although we carry out synchronization again, the same error occurs.
> However, after 10 minutes, we carry out synchronization the third time,
that
> error does not occur, it runs normally.
> What is the reason which make this error occur?
>
|||Thanks for your quick respone.
Can I ask you why after the error "Error: 0--The validity period of
subscription went out. It is necessary tore-initialize." occurred 10 minutes
, and I carried out the third synchorization, it run normally?
I did not restart the agent, neither reinitialized the subscription.
"Hilary Cotter" wrote:

> The reason you get this error is that your subscriber is off line for a
> longer period than what you specified in the retention period or your
> history retention period. Make sure both these values match and are set to a
> reasonable level.
> The reason you got the "Subscription for 'SanyoMB_CE'publication is invalid"
> message is because your snapshot had not been created or had not finished
> creation yet.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> "Mai Thoa" <MaiThoa@.discussions.microsoft.com> wrote in message
> news:9708BCE3-39F6-4F85-92D4-58A1E41E69B4@.microsoft.com...
> to
> that
>
>
|||I am not sure why this is? Is this for anonymous subscribers?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Mai Thoa" <MaiThoa@.discussions.microsoft.com> wrote in message
news:7A33F4E1-B57D-4F53-9B9F-3E0AF5BFC60C@.microsoft.com...
> Thanks for your quick respone.
> Can I ask you why after the error "Error: 0--The validity period of
> subscription went out. It is necessary tore-initialize." occurred 10
minutes[vbcol=seagreen]
> , and I carried out the third synchorization, it run normally?
> I did not restart the agent, neither reinitialized the subscription.
> "Hilary Cotter" wrote:
to a[vbcol=seagreen]
invalid"[vbcol=seagreen]
finished[vbcol=seagreen]
It is necessary[vbcol=seagreen]
time,[vbcol=seagreen]
|||Yes, that's right, It is subscription of anonymous subscriber.
Can you help me?
"Hilary Cotter" wrote:

> I am not sure why this is? Is this for anonymous subscribers?
> --

merge replication error - could not find stored procedure ''.

Hi
I have a client which has a merge subscription - anonymous ftp
When synchronising we see the following error message at the publisher:
Error Message:
The merge process could not retrieve column information for table
'dbo.Transfer'.
(Source: Merge Replication Provider (Agent); Error number: -2147201016)
------
Could not find stored procedure ''.
(Source: LOUISEPC (Data source); Error number: 2812)
------
What does this mean ?
Thanks
Bruce
does this help?
http://support.microsoft.com/default...b;en-us;308743
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
"Bruce Baker" <bruceb@.ardex.com.au> wrote in message
news:%23DHMBbVrFHA.1168@.TK2MSFTNGP10.phx.gbl...
> Hi
> I have a client which has a merge subscription - anonymous ftp
> When synchronising we see the following error message at the publisher:
> Error Message:
> The merge process could not retrieve column information for table
> 'dbo.Transfer'.
> (Source: Merge Replication Provider (Agent); Error number: -2147201016)
> ----
--
> Could not find stored procedure ''.
> (Source: LOUISEPC (Data source); Error number: 2812)
> ----
--
>
> What does this mean ?
> Thanks
> Bruce
>
>
|||Not really - it was working - for some reason the procs for the table are
missing from the sysmergearticles table.
Any bright ideas on repopulating that table ? Wonder what else is bung....
Thanks
Bruce
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%233tiAZprFHA.1252@.TK2MSFTNGP09.phx.gbl...
> does this help?
> http://support.microsoft.com/default...b;en-us;308743
> --
> 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
> "Bruce Baker" <bruceb@.ardex.com.au> wrote in message
> news:%23DHMBbVrFHA.1168@.TK2MSFTNGP10.phx.gbl...
> --
> --
>
|||You can manually populate these tables with the correct procs. It will be
somewhat difficult to figure out what these procs names should be. You will
have to open these procs to find out which underlying tables they populate
and go from there.
You are best in the long run to drop the subscribers, and then re deploy
them.
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
"Bruce Baker" <bruceb@.newsgroups.nospam> wrote in message
news:OiBu4NurFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Not really - it was working - for some reason the procs for the table are
> missing from the sysmergearticles table.
> Any bright ideas on repopulating that table ? Wonder what else is
bung....[vbcol=seagreen]
> Thanks
> Bruce
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%233tiAZprFHA.1252@.TK2MSFTNGP09.phx.gbl...
-[vbcol=seagreen]
-
>

Merge Replication Error

Hi,
I'm getting this error on trying to setup a push Merge subscription.
The Merge Process could not initialize the subscription
{call sp_MSmergesubscribedb *;true') }
Invalid column name 'maxversion_at_cleanup'
Invalid column name 'published_in_tran_pub'
The system tables for the merge replication could not be created
successfully.
The push Merge subscription does work with two other SQL Servers. When
reviewing the table schemas, both columns are located in the
sysmergearticles table on the publisher yet neither exists on the
subscriber. Also, the creation date for the system table (sysmergearticles)
on the subscriber is over a year old. I think these are older merge system
tables that were used previously.
Anyone know how to correct this issue or is there a "safe" way to delete the
sytem tables for merge replication and push the subscription out again.
Also, which merge system tables should I delete.
I did add the two new columns to the table on the subscriber but then got
the error message that the publication was invalid. After removing the
columns things went back to the orriginal error message.
Any help is greatly appreciated!
Thanks
Jerry
Jerry,
please check that you have the latest service pack on each computer on your
replication setup.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

merge replication error

Hi,

We have an HTTPS merge publication which has been working fine, but all of a sudden the subscription for a subscriber is failing with the following message at the publisher:

Error messages: The process could not read the request message due to OS error
10054. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147014842) Get help:
http://help/MSSQL_REPL-2147014842 The format of a message during Web
synchronization was invalid. Ensure that replication components are properly
configured at the Web server. (Source: MSSQL_REPL, Error number: MSSQL_REPL-
2147199374) Get help: http://help/MSSQL_REPL-2147199374 The subscription to
publication 'yarraman main' could not be verified. Ensure that all Merge Agent
command line parameters are specified correctly and that the subscription is
correctly configured. If the Publisher no longer has information about this
subscription, drop and recreate the subscription. (Source: MSSQL_REPL, Error
number: MSSQL_REPL-2147201019) Get help: http://help/MSSQL_REPL-2147201019

We have 2 subscribers to this publication and it is working fine for the other subscriber..

Help !

thanks
Bruce

Well

We rebooted their ADSL router and all is now working - strange - given the other subscriber on the same network was working fine. Who knows !

Thanks
bruce

Merge Replication Error

Hello,
I have a publiction on my development box using SQL Server 2005 developer
edition. I created a subscription for my test box, sitting next to me,
intialized and synchronized with the subscriber. I also have SQL Server
Express installed on my development box. I created a subscription for this
server and tried to initialize and sychronize with that subscriber. However,
the subscription never appears in that servers Local Subscriptions list.
The SQL Server Agent is running under a domain account that we use for
replication and this account has the neccessary permissions on each
subcribers machines including my dev box. However, I get the error:
The job failed. Unable to determine if the owner (domain\username) of job
MachineName\SQL2005-Weed-WeedMerge-MachineName\SQLEXPRESS-14 has server
access (reason: Could not obtain information about Windows NT group/user
'domain\username', error code 0xea. [SQLSTATE 42000] (Error 15404) The
statement has been terminated. [SQLSTATE 01000] (Error 3621)).
When I view the job history.
Can anyone help me with this?
S
Just changing the job owner to sa should do it.
Cheers,
Paul Ibison
|||You might also want to consider using a SQL account for the merge agent.
relevantNoise - 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
"SAL" <SAL_@.NoNo.com> wrote in message
news:OunlT8o3HHA.5184@.TK2MSFTNGP02.phx.gbl...
> Hello,
> I have a publiction on my development box using SQL Server 2005 developer
> edition. I created a subscription for my test box, sitting next to me,
> intialized and synchronized with the subscriber. I also have SQL Server
> Express installed on my development box. I created a subscription for this
> server and tried to initialize and sychronize with that subscriber.
> However, the subscription never appears in that servers Local
> Subscriptions list.
> The SQL Server Agent is running under a domain account that we use for
> replication and this account has the neccessary permissions on each
> subcribers machines including my dev box. However, I get the error:
> The job failed. Unable to determine if the owner (domain\username) of job
> MachineName\SQL2005-Weed-WeedMerge-MachineName\SQLEXPRESS-14 has server
> access (reason: Could not obtain information about Windows NT group/user
> 'domain\username', error code 0xea. [SQLSTATE 42000] (Error 15404) The
> statement has been terminated. [SQLSTATE 01000] (Error 3621)).
> When I view the job history.
> Can anyone help me with this?
> S
>
|||Hi Paul,
I did try that but what finally worked was changing the account that SQL
Server runs under to the account that it couldn't determine if it had access
rights.
So, event though the owner of the job was the domain replication account,
SQL Server Express was running under a different account and the job was
actually running under my acccount. I change SQL Server Expresses log on
account to me and it started working. This only seemed to be a problem on my
dev server for some reason.
Thanks again.
S
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:75E0428A-BF72-4E1E-B428-76743E99AEA5@.microsoft.com...
> Just changing the job owner to sa should do it.
> Cheers,
> Paul Ibison
>