Groups | Blog | Home
all groups > sql server replication > august 2005 >

sql server replication : Problem with Merge Replication sp_MSsetlastsentgen


Ian Cox
8/11/2005 12:00:00 AM
I am getting the following the error trying to synchronise a subscriber
using merge replication.
The schema script 'exec dbo.sp_MSsetlastsentgen
'299424F6-B38D-4CE7-840E-B941925A7F2D','485','5FC5F1FA-F9EF-4207-9560-06CF70
304024'' could not be propagated to the subscriber.

I have seen the knowledge base article that suggests getting SP3,
unfortunately I already have SP3

Does anyone have any ideas how I can get this working?

Regards
Ian

v-rxwang NO[at]SPAM online.microsoft.com
8/12/2005 10:04:30 AM
Hi Ian,

Can you post the detailed text of the error message? This is important to
get a clue of what has happened. In addition, please provide detailed
information of your replication scenario as mentioned in the following
article:

INF: Information that PSS needs to troubleshoot SQL Server replication
http://support.microsoft.com/?id=315642

Also I recommend that you install SQL2K SP4 to see if the issue still
exists.

Sincerely,

William Wang
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.


This posting is provided "AS IS" with no warranties, and confers no rights.
Ian Cox
8/15/2005 1:12:52 PM
I have completely rebuilt our replication and it seems to be working now.
Not sure what the problem was.
Replication in SQL server does still seem a bit flaky to me. Or maybe its
just me

Anyway, thanks for the response

Cheers
Ian

[quoted text, click to view]

v-rxwang NO[at]SPAM online.microsoft.com
8/16/2005 5:30:45 AM
I'm glad to hear that the problem has gone after rebuilding the
replication. Replication issue are usually very complex. Sometimes
rebuilding replication from scratch is the most efficient way, but this
will vary by the situation and urgency for resolution.

As part of any recovery strategy, it's recommended that we always keep a
current script of our replication settings in a safe location.

Sincerely,

William Wang
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

This posting is provided "AS IS" with no warranties, and confers no rights.
Paul Ibison
8/16/2005 9:31:51 AM
Continuing from William's advice, if anyone is interested in a simple way of
achieving this, have a look at this script which can be run in a DTS job:

'**********************************************************************
' Visual Basic ActiveX Script
'************************************************************************

Function Main()

Dim objDMO
Dim objReplication
Dim fso
Dim tf

Set objDMO = CreateObject("SQLDMO.SQLServer")
Set fso = CreateObject("Scripting.FileSystemObject")

objDMO.LoginSecure = True
objDMO.Connect "crazyfrog"
Set objReplication = objDMO.Replication

Set fso = CreateObject("Scripting.FileSystemObject")
Set tf = fso.CreateTextFile("c:\testfile.txt", True)

tf.Write objReplication.Script(1048576)
tf.Close

Main = DTSTaskExecResult_Success

End Function

(http://www.replicationanswers.com/Script7.asp)

Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Ian Cox
8/16/2005 12:49:51 PM
thanks Guys. Thats good advice.
I'm going to try out the script William sent. Looks like a good website too

Cheers
Ian


[quoted text, click to view]

v-rxwang NO[at]SPAM online.microsoft.com
8/17/2005 9:34:25 AM
Thanks Paul.

Sincerely,

William Wang
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

This posting is provided "AS IS" with no warranties, and confers no rights.
AddThis Social Bookmark Button