I was adviced to turn Logging on to spot the problem with the consistantly
failing Merge Replication
Below is the end of the log. I you need the entire log I will add it
Percent Complete: 31
select * from "dbo"."tblUser" where 1 = 2
Bulk copying data into table 'tblSolsFeeEarner'
[9/30/2006 9:26:01 PM]LEEDSSERVER.MRN.LOCAL\MRNLEEDS.MRN1: select * from
"dbo"."tblUser" where 1 = 2
Percent Complete: 32
The process could not deliver the snapshot to the Subscriber.Bulk copying
data into table 'tblStaff'
Percent Complete: 33
[9/30/2006 9:26:01 PM]SERVER\SERVER1.MRN1: {call sp_reinitmergesubscription
(N'MRN1_rep', N'LEEDSSERVER.MRN.LOCAL\MRNLEEDS', N'MRN1', 'FALSE')}
Bulk copying data into table 'tblTeam'
Percent Complete: 34
Bulk copying data into table 'tblTeamMembers'
Percent Complete: 35
Bulk copying data into table 'tblTest'
Percent Complete: 36
Bulk copying data into table 'tblUser'
Reinitialized subscription to publication 'MRN1_rep' at subscriber
'LEEDSSERVER.MRN.LOCAL\MRNLEEDS:MRN1'Percent Complete: 0
The subscription has been marked for reinitialization. Reinitialization will
occur the next time you synchronize this subscription.
Percent Complete: 0
The process could not deliver the snapshot to the Subscriber.
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147201001
Message: The process could not deliver the snapshot to the Subscriber.
Percent Complete: 0
Category:AGENT
Source: LEEDSSERVER.MRN.LOCAL\MRNLEEDS
Number: 20037
Message: The process could not bulk copy into table
'"dbo"."MSmerge_contents"'.
Percent Complete: 0
Category:SQLSERVER
Source: LEEDSSERVER.MRN.LOCAL\MRNLEEDS
Number: 11
Message: General network error. Check your network documentation.
Disconnecting from Subscriber 'LEEDSSERVER.MRN.LOCAL\MRNLEEDS'
Disconnecting from Subscriber 'LEEDSSERVER.MRN.LOCAL\MRNLEEDS'
Disconnecting from Publisher 'SERVER\SERVER1'
Disconnecting from Publisher 'SERVER\SERVER1'
Disconnecting from Distributor 'SERVER\SERVER1'
Microsoft SQL Server Merge Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent:
SERVER\SERVER1-MRN1-MRN1_rep-LEEDSSERVER.MRN.LOCAL-12
It appears that your network connection has failed in the middle of your
snapshot deployment. Restart your merge agent and it should progress further
or complete the next time.
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
"Samuel Shulman" <samuel.shulman@.ntlworld.com> wrote in message
news:%23JqkyKN5GHA.1252@.TK2MSFTNGP04.phx.gbl...
>I was adviced to turn Logging on to spot the problem with the consistantly
>failing Merge Replication
> Below is the end of the log. I you need the entire log I will add it
> Percent Complete: 31
> select * from "dbo"."tblUser" where 1 = 2
> Bulk copying data into table 'tblSolsFeeEarner'
> [9/30/2006 9:26:01 PM]LEEDSSERVER.MRN.LOCAL\MRNLEEDS.MRN1: select * from
> "dbo"."tblUser" where 1 = 2
> Percent Complete: 32
> The process could not deliver the snapshot to the Subscriber.Bulk copying
> data into table 'tblStaff'
> Percent Complete: 33
> [9/30/2006 9:26:01 PM]SERVER\SERVER1.MRN1: {call
> sp_reinitmergesubscription (N'MRN1_rep',
> N'LEEDSSERVER.MRN.LOCAL\MRNLEEDS', N'MRN1', 'FALSE')}
> Bulk copying data into table 'tblTeam'
> Percent Complete: 34
> Bulk copying data into table 'tblTeamMembers'
> Percent Complete: 35
> Bulk copying data into table 'tblTest'
> Percent Complete: 36
> Bulk copying data into table 'tblUser'
> Reinitialized subscription to publication 'MRN1_rep' at subscriber
> 'LEEDSSERVER.MRN.LOCAL\MRNLEEDS:MRN1'Percent Complete: 0
> The subscription has been marked for reinitialization. Reinitialization
> will occur the next time you synchronize this subscription.
> Percent Complete: 0
> The process could not deliver the snapshot to the Subscriber.
> Percent Complete: 0
> Category:NULL
> Source: Merge Replication Provider
> Number: -2147201001
> Message: The process could not deliver the snapshot to the Subscriber.
> Percent Complete: 0
> Category:AGENT
> Source: LEEDSSERVER.MRN.LOCAL\MRNLEEDS
> Number: 20037
> Message: The process could not bulk copy into table
> '"dbo"."MSmerge_contents"'.
> Percent Complete: 0
> Category:SQLSERVER
> Source: LEEDSSERVER.MRN.LOCAL\MRNLEEDS
> Number: 11
> Message: General network error. Check your network documentation.
> Disconnecting from Subscriber 'LEEDSSERVER.MRN.LOCAL\MRNLEEDS'
> Disconnecting from Subscriber 'LEEDSSERVER.MRN.LOCAL\MRNLEEDS'
> Disconnecting from Publisher 'SERVER\SERVER1'
> Disconnecting from Publisher 'SERVER\SERVER1'
> Disconnecting from Distributor 'SERVER\SERVER1'
> Microsoft SQL Server Merge Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent:
> SERVER\SERVER1-MRN1-MRN1_rep-LEEDSSERVER.MRN.LOCAL-12
>
|||That is what is happening for days
Is it possibly because it is over VPN?
I did set the time out to 1000. Is it not enough?
This is the script of the Run Agent step:
-Publisher [SERVER\SERVER1] -PublisherDB [MRN1] -Publication
[MRN1_rep] -Subscriber [LEEDSSERVER.MRN.LOCAL\MRNLEEDS] -SubscriberDB
[MRN1] -Distributor [SERVER\SERVER1] -DistributorSecurityMode 1
-QueryTimeout 1000 -Output
C:\ShmuelShulman\OUTPUTFILE1.txt -Outputverboselevel 2
Thank you for your help,
Samuel
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uyDqc9N5GHA.3836@.TK2MSFTNGP06.phx.gbl...
> It appears that your network connection has failed in the middle of your
> snapshot deployment. Restart your merge agent and it should progress
> further or complete the next time.
> --
> 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
> "Samuel Shulman" <samuel.shulman@.ntlworld.com> wrote in message
> news:%23JqkyKN5GHA.1252@.TK2MSFTNGP04.phx.gbl...
>
|||run this script, it will tell you if there is a network hiccup and when
between your publisher and subscriber.
Save this as keepalive.sql on your publisher.
WHILE 1<>2
BEGIN
SELECT GETDATE()
WAITFOR DELAY '00:00:01'
END
GO
Here is the batch file that I use to run this script:
osql -S yourSubscriberName -E -i c:\keepalive.sql -n
date /t
time /t
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"Samuel Shulman" <samuel.shulman@.ntlworld.com> wrote in message
news:%23knLfHO5GHA.3308@.TK2MSFTNGP04.phx.gbl...
> That is what is happening for days
> Is it possibly because it is over VPN?
> I did set the time out to 1000. Is it not enough?
> This is the script of the Run Agent step:
> -Publisher [SERVER\SERVER1] -PublisherDB [MRN1] -Publication
> [MRN1_rep] -Subscriber [LEEDSSERVER.MRN.LOCAL\MRNLEEDS] -SubscriberDB
> [MRN1] -Distributor [SERVER\SERVER1] -DistributorSecurityMode 1
> -QueryTimeout 1000 -Output
> C:\ShmuelShulman\OUTPUTFILE1.txt -Outputverboselevel 2
>
> Thank you for your help,
> Samuel
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:uyDqc9N5GHA.3836@.TK2MSFTNGP06.phx.gbl...
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment