I got transactional replication between two servers , two identical database
(one publusher and one subscriber, distributor is on publisher server),
everything works clear however a few days ago i got on
Replication Monitor --> Publishers --> MyServerName failed icon snapshot
agent, now on path above i have two publication one that i buil transactional
with 3 agents, and one snapshot i don't know how it created.
Also when i trying to remove it i got the following message description
couldn't retrive information about publication, ... .... ... publication
name not found in the TransPublication collection.
Any ideas ? TNX
Message posted via http://www.droptable.com
You have inconsistent meta data in your distribution database. The best way
to fix this is unfortunately to start carefully editing the metadata tables.
Sometimes it is better to live with these phantom messages.
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
"akej via droptable.com" <forum@.droptable.com> wrote in message
news:507682708C7A4@.droptable.com...
> I got transactional replication between two servers , two identical
database
> (one publusher and one subscriber, distributor is on publisher server),
> everything works clear however a few days ago i got on
> Replication Monitor --> Publishers --> MyServerName failed icon
snapshot
> agent, now on path above i have two publication one that i buil
transactional
> with 3 agents, and one snapshot i don't know how it created.
> Also when i trying to remove it i got the following message description
> couldn't retrive information about publication, ... .... ... publication
> name not found in the TransPublication collection.
>
> Any ideas ? TNX
> --
> Message posted via http://www.droptable.com
|||>carefully editing the metadata tables
I don't really understande what does it mean, can u explain me plz?
Message posted via http://www.droptable.com
|||somebody can help me with problem that i experiance
Message posted via http://www.droptable.com
Showing posts with label publisher. Show all posts
Showing posts with label publisher. Show all posts
Friday, March 30, 2012
Friday, March 23, 2012
problems with replication while rolling back nested transactions
Replication appears to be reading rolled back transactions. We are seeing
rows on our subscriber that do not exist on our publisher. The data on the
publisher is what is expected, the rolled back rows appearing on the
subscriber obviously are not.
Here's the basic structure of my two stored procs. They are done this way
because, depending on business rules, I can call the inner proc by itself or
from the outer.
sp_outer
{ basics of the outer
SET IMPLICIT_TRANSACTIONS OFF
Begin Transaction
Save Transaction Group
While more deals
Call sp_inner
{ basics of the inner
SET IMPLICIT_TRANSACTIONS OFF
Begin Transaction
Save Transaction Individual
work...
If Fail ROLLBACK Individual
If Pass COMMIT
}
End
If Any Fail in inner ROLLBACK Group outer
Else COMMIT outer
}
Problem is occuring when outer transaction rolls back. From on the
sqlserver docs "Committing inner transactions is ignored by Microsoft? SQL
Server. The transaction is either committed or rolled back based on the
action taken at the end of the outermost transaction. If the outer
transaction is committed, the inner nested transactions are also committed.
If the outer transaction is rolled back, then all inner transactions are also
rolled back, regardless of whether or not the inner transactions were
individually committed."
Again, what we see on our publisher is as expected. Subscribers having
different rows are the issue.
The chart at the bottom shows different ordering of the rollbacks and
commits and establishes a pattern of the problem occurs with commited
transactions prior to or between two rolled back transactions.
This sure looks like a replication bug as the publisher behaves as expected.
What do you think?
Exists on PublisherExists on Subscriber
Begin Outer
Rollback InnerNoNo
Commit InnerNoYes
Commit InnerNoYes
Rollback InnerNoNo
Rollback Outer
Begin Outer
Commit InnerNoYes
Rollback InnerNoNo
Commit InnerNoYes
Rollback InnerNoNo
Rollback Outer
Begin Outer
Rollback InnerNoNo
Commit InnerNoYes
Rollback InnerNoNo
Commit InnerNoNo
Rollback Outer
Begin Outer
Rollback InnerNoNo
Rollback InnerNoNo
Commit InnerNoNo
Commit InnerNoNo
Rollback Outer
Begin Outer
Commit InnerNoNo
Commit InnerNoNo
Commit InnerNoNo
Rollback InnerNoNo
Rollback Outer
Begin Outer
Rollback InnerNoNo
Commit InnerNoNo
Commit InnerNoNo
Commit InnerNoNo
Rollback Outer
TPerry,
I admire your methodicalness (if this is a proper word) and agree that this
looks confusing
If we compare
> Begin Outer
> Rollback Inner No No
> Commit Inner No Yes
> Commit Inner No Yes
> Rollback Inner No No
> Rollback Outer
and
> Begin Outer
> Rollback Inner No No
> Commit Inner No No
> Commit Inner No No
> Commit Inner No No
> Rollback Outer
Why should the first and second commits should be different? Interesting!
I can't test all this right now, but one thing I did test in the past was
that setting the transaction isolation level as serializable and setting
xact_abort on before running the transactions altered the behaviour; if code
in a stored procedure was rolled back on the publisher, it wasn't sent to
the subscriber. Please can you test your scenario under these conditions to
see if this fixes your issue.
Rgds,
Paul Ibison (SQL Server MVP)
[vbcol=seagreen]
|||If a transaction is logged, it will be replicated.
If the transaction is not committed the log reader can't read it, and hence
it will not be replicated.
If you can isolate a sequence of transactions that cause this phenomena you
could use sp_browsereplcmds to see if they make it to the distribution
database. If so they will be replicated.
It sounds like to me there is a logical error somewhere in your proc.
"tperry" <tperry@.discussions.microsoft.com> wrote in message
news:D2DF5BE8-66E0-45E6-891D-DD61BD23EBD3@.microsoft.com...
> Replication appears to be reading rolled back transactions. We are seeing
> rows on our subscriber that do not exist on our publisher. The data on
> the
> publisher is what is expected, the rolled back rows appearing on the
> subscriber obviously are not.
> Here's the basic structure of my two stored procs. They are done this way
> because, depending on business rules, I can call the inner proc by itself
> or
> from the outer.
> sp_outer
> { basics of the outer
> SET IMPLICIT_TRANSACTIONS OFF
> Begin Transaction
> Save Transaction Group
> While more deals
> Call sp_inner
> { basics of the inner
> SET IMPLICIT_TRANSACTIONS OFF
> Begin Transaction
> Save Transaction Individual
> work...
> If Fail ROLLBACK Individual
> If Pass COMMIT
> }
> End
> If Any Fail in inner ROLLBACK Group outer
> Else COMMIT outer
> }
> Problem is occuring when outer transaction rolls back. From on the
> sqlserver docs "Committing inner transactions is ignored by Microsoft?
> SQL
> Server. The transaction is either committed or rolled back based on the
> action taken at the end of the outermost transaction. If the outer
> transaction is committed, the inner nested transactions are also
> committed.
> If the outer transaction is rolled back, then all inner transactions are
> also
> rolled back, regardless of whether or not the inner transactions were
> individually committed."
> Again, what we see on our publisher is as expected. Subscribers having
> different rows are the issue.
> The chart at the bottom shows different ordering of the rollbacks and
> commits and establishes a pattern of the problem occurs with commited
> transactions prior to or between two rolled back transactions.
> This sure looks like a replication bug as the publisher behaves as
> expected.
> What do you think?
>
> Exists on Publisher Exists on Subscriber
> Begin Outer
> Rollback Inner No No
> Commit Inner No Yes
> Commit Inner No Yes
> Rollback Inner No No
> Rollback Outer
> Begin Outer
> Commit Inner No Yes
> Rollback Inner No No
> Commit Inner No Yes
> Rollback Inner No No
> Rollback Outer
> Begin Outer
> Rollback Inner No No
> Commit Inner No Yes
> Rollback Inner No No
> Commit Inner No No
> Rollback Outer
> Begin Outer
> Rollback Inner No No
> Rollback Inner No No
> Commit Inner No No
> Commit Inner No No
> Rollback Outer
> Begin Outer
> Commit Inner No No
> Commit Inner No No
> Commit Inner No No
> Rollback Inner No No
> Rollback Outer
> Begin Outer
> Rollback Inner No No
> Commit Inner No No
> Commit Inner No No
> Commit Inner No No
> Rollback Outer
>
rows on our subscriber that do not exist on our publisher. The data on the
publisher is what is expected, the rolled back rows appearing on the
subscriber obviously are not.
Here's the basic structure of my two stored procs. They are done this way
because, depending on business rules, I can call the inner proc by itself or
from the outer.
sp_outer
{ basics of the outer
SET IMPLICIT_TRANSACTIONS OFF
Begin Transaction
Save Transaction Group
While more deals
Call sp_inner
{ basics of the inner
SET IMPLICIT_TRANSACTIONS OFF
Begin Transaction
Save Transaction Individual
work...
If Fail ROLLBACK Individual
If Pass COMMIT
}
End
If Any Fail in inner ROLLBACK Group outer
Else COMMIT outer
}
Problem is occuring when outer transaction rolls back. From on the
sqlserver docs "Committing inner transactions is ignored by Microsoft? SQL
Server. The transaction is either committed or rolled back based on the
action taken at the end of the outermost transaction. If the outer
transaction is committed, the inner nested transactions are also committed.
If the outer transaction is rolled back, then all inner transactions are also
rolled back, regardless of whether or not the inner transactions were
individually committed."
Again, what we see on our publisher is as expected. Subscribers having
different rows are the issue.
The chart at the bottom shows different ordering of the rollbacks and
commits and establishes a pattern of the problem occurs with commited
transactions prior to or between two rolled back transactions.
This sure looks like a replication bug as the publisher behaves as expected.
What do you think?
Exists on PublisherExists on Subscriber
Begin Outer
Rollback InnerNoNo
Commit InnerNoYes
Commit InnerNoYes
Rollback InnerNoNo
Rollback Outer
Begin Outer
Commit InnerNoYes
Rollback InnerNoNo
Commit InnerNoYes
Rollback InnerNoNo
Rollback Outer
Begin Outer
Rollback InnerNoNo
Commit InnerNoYes
Rollback InnerNoNo
Commit InnerNoNo
Rollback Outer
Begin Outer
Rollback InnerNoNo
Rollback InnerNoNo
Commit InnerNoNo
Commit InnerNoNo
Rollback Outer
Begin Outer
Commit InnerNoNo
Commit InnerNoNo
Commit InnerNoNo
Rollback InnerNoNo
Rollback Outer
Begin Outer
Rollback InnerNoNo
Commit InnerNoNo
Commit InnerNoNo
Commit InnerNoNo
Rollback Outer
TPerry,
I admire your methodicalness (if this is a proper word) and agree that this
looks confusing
If we compare
> Begin Outer
> Rollback Inner No No
> Commit Inner No Yes
> Commit Inner No Yes
> Rollback Inner No No
> Rollback Outer
and
> Begin Outer
> Rollback Inner No No
> Commit Inner No No
> Commit Inner No No
> Commit Inner No No
> Rollback Outer
Why should the first and second commits should be different? Interesting!
I can't test all this right now, but one thing I did test in the past was
that setting the transaction isolation level as serializable and setting
xact_abort on before running the transactions altered the behaviour; if code
in a stored procedure was rolled back on the publisher, it wasn't sent to
the subscriber. Please can you test your scenario under these conditions to
see if this fixes your issue.
Rgds,
Paul Ibison (SQL Server MVP)
[vbcol=seagreen]
|||If a transaction is logged, it will be replicated.
If the transaction is not committed the log reader can't read it, and hence
it will not be replicated.
If you can isolate a sequence of transactions that cause this phenomena you
could use sp_browsereplcmds to see if they make it to the distribution
database. If so they will be replicated.
It sounds like to me there is a logical error somewhere in your proc.
"tperry" <tperry@.discussions.microsoft.com> wrote in message
news:D2DF5BE8-66E0-45E6-891D-DD61BD23EBD3@.microsoft.com...
> Replication appears to be reading rolled back transactions. We are seeing
> rows on our subscriber that do not exist on our publisher. The data on
> the
> publisher is what is expected, the rolled back rows appearing on the
> subscriber obviously are not.
> Here's the basic structure of my two stored procs. They are done this way
> because, depending on business rules, I can call the inner proc by itself
> or
> from the outer.
> sp_outer
> { basics of the outer
> SET IMPLICIT_TRANSACTIONS OFF
> Begin Transaction
> Save Transaction Group
> While more deals
> Call sp_inner
> { basics of the inner
> SET IMPLICIT_TRANSACTIONS OFF
> Begin Transaction
> Save Transaction Individual
> work...
> If Fail ROLLBACK Individual
> If Pass COMMIT
> }
> End
> If Any Fail in inner ROLLBACK Group outer
> Else COMMIT outer
> }
> Problem is occuring when outer transaction rolls back. From on the
> sqlserver docs "Committing inner transactions is ignored by Microsoft?
> SQL
> Server. The transaction is either committed or rolled back based on the
> action taken at the end of the outermost transaction. If the outer
> transaction is committed, the inner nested transactions are also
> committed.
> If the outer transaction is rolled back, then all inner transactions are
> also
> rolled back, regardless of whether or not the inner transactions were
> individually committed."
> Again, what we see on our publisher is as expected. Subscribers having
> different rows are the issue.
> The chart at the bottom shows different ordering of the rollbacks and
> commits and establishes a pattern of the problem occurs with commited
> transactions prior to or between two rolled back transactions.
> This sure looks like a replication bug as the publisher behaves as
> expected.
> What do you think?
>
> Exists on Publisher Exists on Subscriber
> Begin Outer
> Rollback Inner No No
> Commit Inner No Yes
> Commit Inner No Yes
> Rollback Inner No No
> Rollback Outer
> Begin Outer
> Commit Inner No Yes
> Rollback Inner No No
> Commit Inner No Yes
> Rollback Inner No No
> Rollback Outer
> Begin Outer
> Rollback Inner No No
> Commit Inner No Yes
> Rollback Inner No No
> Commit Inner No No
> Rollback Outer
> Begin Outer
> Rollback Inner No No
> Rollback Inner No No
> Commit Inner No No
> Commit Inner No No
> Rollback Outer
> Begin Outer
> Commit Inner No No
> Commit Inner No No
> Commit Inner No No
> Rollback Inner No No
> Rollback Outer
> Begin Outer
> Rollback Inner No No
> Commit Inner No No
> Commit Inner No No
> Commit Inner No No
> Rollback Outer
>
Tuesday, March 20, 2012
problems with merge replicaton.
Hi, I have installed sql server 2000 sp 3 on a publisher/distributor. I
have about 6 merge replication configured whith pull subscription. Four
of them are ok but one give me this error.
The process could not deliver the snapshot to the Subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
---
The process could not bulk copy into table
'"dbo"."sysmergesubsetfilters"'.
(Source: SCENALMSQL (Agent); Error number: 20037)
---
Unable to open BCP host data-file
(Source: ODBC SQL Server Driver (ODBC); Error number: 0)
---
and the other one give me this error:
You must rerun snapshot because current snapshot files are obsolete.
(Source: Merge Replication Provider (Agent); Error number: -2147201021)
Both are configured on the same subscriptor.
I guess that could be the versions of sql server, i execute the select
@.@.version sentence on both servers and this are the results:
publisher/distributor: Microsoft SQL Server 2000 - 8.00.760
Subscriptor. Microsoft SQL Server 2000 - 8.00.818
However, I have configured the same scenario of replication in servers
whith the same configuration.
How could i resolve this problem?
thanks a lot for your help.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
For the 1st error, you may be running into the issue described in KB
article: FIX: Compressed Snapshot CAB Does Not Contain All Necessary Files
- ID: 318075 (available at http://support.microsoft.com)
For the second (snapshot obsolete message) this means we are trying to
apply a snapshot whose files are obsolete (older than the retention
period), you need to rerun the snapshot agent to create up to date snapshot
files.
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
have about 6 merge replication configured whith pull subscription. Four
of them are ok but one give me this error.
The process could not deliver the snapshot to the Subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
---
The process could not bulk copy into table
'"dbo"."sysmergesubsetfilters"'.
(Source: SCENALMSQL (Agent); Error number: 20037)
---
Unable to open BCP host data-file
(Source: ODBC SQL Server Driver (ODBC); Error number: 0)
---
and the other one give me this error:
You must rerun snapshot because current snapshot files are obsolete.
(Source: Merge Replication Provider (Agent); Error number: -2147201021)
Both are configured on the same subscriptor.
I guess that could be the versions of sql server, i execute the select
@.@.version sentence on both servers and this are the results:
publisher/distributor: Microsoft SQL Server 2000 - 8.00.760
Subscriptor. Microsoft SQL Server 2000 - 8.00.818
However, I have configured the same scenario of replication in servers
whith the same configuration.
How could i resolve this problem?
thanks a lot for your help.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
For the 1st error, you may be running into the issue described in KB
article: FIX: Compressed Snapshot CAB Does Not Contain All Necessary Files
- ID: 318075 (available at http://support.microsoft.com)
For the second (snapshot obsolete message) this means we are trying to
apply a snapshot whose files are obsolete (older than the retention
period), you need to rerun the snapshot agent to create up to date snapshot
files.
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
problems with merge replication and server subcriber
Hi,
I'm trying to setup a replication topologie with a publisher, a server
subscriber (push-subcription) and a client subscriber (pull-subcription).
First I setup the publication and a push-subscription for the server
subcriber.
This replication works fine. Data and schema changes are replicated and I
can apply new snapshots to the subscriber any time.
Just at the moment, when I define the (re)publication on the server
subscriber every attempt to apply a new snapshot to the Server subscriber,
the merge-agent fails with the error :
Source: Merge replication provider
Number: -2147200965
Message: The merge agent fails to cleanup the subscription for
'GO-ON-DC1\SQL2005ONDC':'TestReplikation:'TestPublikation '
Category:SQLSERVER
Source: ZANDER\GOONDEV2005
Number: 245
Message: Error converting the nvarchar-Value
'MSmerge_view_logical_record_11282001' to int-Datatype.
Above message is not literal, I translated it form german, but I hope it
will help any way. By the way, sorry for my english ;-[
I hope any one can help me, i have no idee whats going wrong.
Regards
Jan
This looks like a bug. Can we get your publication script and table schema
to see if we can repro it?
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
"Jan" <Jan@.discussions.microsoft.com> wrote in message
news:76CD7085-2418-4147-B907-AF94720330D5@.microsoft.com...
> Hi,
> I'm trying to setup a replication topologie with a publisher, a server
> subscriber (push-subcription) and a client subscriber (pull-subcription).
> First I setup the publication and a push-subscription for the server
> subcriber.
> This replication works fine. Data and schema changes are replicated and I
> can apply new snapshots to the subscriber any time.
> Just at the moment, when I define the (re)publication on the server
> subscriber every attempt to apply a new snapshot to the Server
> subscriber,
> the merge-agent fails with the error :
> Source: Merge replication provider
> Number: -2147200965
> Message: The merge agent fails to cleanup the subscription for
> 'GO-ON-DC1\SQL2005ONDC':'TestReplikation:'TestPublikation '
> Category:SQLSERVER
> Source: ZANDER\GOONDEV2005
> Number: 245
> Message: Error converting the nvarchar-Value
> 'MSmerge_view_logical_record_11282001' to int-Datatype.
> Above message is not literal, I translated it form german, but I hope it
> will help any way. By the way, sorry for my english ;-[
> I hope any one can help me, i have no idee whats going wrong.
> Regards
> Jan
|||Jan,
this entry from Raymond Mak looks as though it could be related :
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=55550&SiteID=1
although it applies to a different merge view. Apart from that, I agree with
Hilary - let's see if we can repro.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Hi Hilary, hi Paul,
thanks for your immediate response.
I am new to the newsgroup. Do I have a posibility to upload files, except of
pasting it into this message?
I stored the scripts on http://www.go-on-software.de/replication/ .
Thre are 4 scripts:
1-Create-Tables-On-Publisher.sql
2-Setup-Publisher.sql
3-Create-DB-on-ServerSub.sql
4-Setup-Re-Publication-on-ServerSub.sql
the first two scrpts are executed at the publisher
the 3rd script is executed at the server subscriber
after the snapshot-agent and the merge-agent finshed
the 4th script re-publish the new database
At this time I haven't added any client subscriber.
To get the Error I create a new Snapshot (on the publisher) and mark the
server subsriber for reinitialisation. After this the merge-agent fails with
the described error message.
Thanks and
Kindest Regards
Jan
"Hilary Cotter" wrote:
> This looks like a bug. Can we get your publication script and table schema
> to see if we can repro it?
> --
> 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
>
> "Jan" <Jan@.discussions.microsoft.com> wrote in message
> news:76CD7085-2418-4147-B907-AF94720330D5@.microsoft.com...
>
>
|||Hi Jan - I click on the hyperlinks but there isn't a file behind it.
Cheers,
Paul
|||Hi Paul,
sorry... my web server doesn't support files with .SQL extensions.
I renamed all to ".txt" and added an zip-file including the 4 scripts.
This time I tested it on stage.
Regards
Jan
"Paul Ibison" wrote:
> Hi Jan - I click on the hyperlinks but there isn't a file behind it.
> Cheers,
> Paul
>
>
|||Hi Paul,
have you got the scripts now? (from http://www.go-on-software.de/replication/)
and
have you found time to run the script and could you repro the error?
I would be happy about any feedback.
Kindest Regards
Jan
|||Jan - it is taking me too long to reformat to get the scripts to work
Pls can you post them up in formatted form?
Rgds,
Paul Ibison
|||Hi Paul, I am ashamed, sorry once again.
I now converted the files to ANSI, so the will be displayed in the browser
with CR.
Alternatively you can download the zip-file, which includes the 4 scripts.
Redards Jan
|||Jan,
I now have it set up and working fine. Did you have a problem with the
original setup or was there a subsequent problem caused by a change made?
It may or may not be relevant, but I probably can't mimic your environment
exactly as I am using no sp1 or sp2 at the moment - our servers have just
been rebuilt and will have the sps applied later on this month.
Rgds,
Paul Ibison
I'm trying to setup a replication topologie with a publisher, a server
subscriber (push-subcription) and a client subscriber (pull-subcription).
First I setup the publication and a push-subscription for the server
subcriber.
This replication works fine. Data and schema changes are replicated and I
can apply new snapshots to the subscriber any time.
Just at the moment, when I define the (re)publication on the server
subscriber every attempt to apply a new snapshot to the Server subscriber,
the merge-agent fails with the error :
Source: Merge replication provider
Number: -2147200965
Message: The merge agent fails to cleanup the subscription for
'GO-ON-DC1\SQL2005ONDC':'TestReplikation:'TestPublikation '
Category:SQLSERVER
Source: ZANDER\GOONDEV2005
Number: 245
Message: Error converting the nvarchar-Value
'MSmerge_view_logical_record_11282001' to int-Datatype.
Above message is not literal, I translated it form german, but I hope it
will help any way. By the way, sorry for my english ;-[
I hope any one can help me, i have no idee whats going wrong.
Regards
Jan
This looks like a bug. Can we get your publication script and table schema
to see if we can repro it?
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
"Jan" <Jan@.discussions.microsoft.com> wrote in message
news:76CD7085-2418-4147-B907-AF94720330D5@.microsoft.com...
> Hi,
> I'm trying to setup a replication topologie with a publisher, a server
> subscriber (push-subcription) and a client subscriber (pull-subcription).
> First I setup the publication and a push-subscription for the server
> subcriber.
> This replication works fine. Data and schema changes are replicated and I
> can apply new snapshots to the subscriber any time.
> Just at the moment, when I define the (re)publication on the server
> subscriber every attempt to apply a new snapshot to the Server
> subscriber,
> the merge-agent fails with the error :
> Source: Merge replication provider
> Number: -2147200965
> Message: The merge agent fails to cleanup the subscription for
> 'GO-ON-DC1\SQL2005ONDC':'TestReplikation:'TestPublikation '
> Category:SQLSERVER
> Source: ZANDER\GOONDEV2005
> Number: 245
> Message: Error converting the nvarchar-Value
> 'MSmerge_view_logical_record_11282001' to int-Datatype.
> Above message is not literal, I translated it form german, but I hope it
> will help any way. By the way, sorry for my english ;-[
> I hope any one can help me, i have no idee whats going wrong.
> Regards
> Jan
|||Jan,
this entry from Raymond Mak looks as though it could be related :
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=55550&SiteID=1
although it applies to a different merge view. Apart from that, I agree with
Hilary - let's see if we can repro.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Hi Hilary, hi Paul,
thanks for your immediate response.
I am new to the newsgroup. Do I have a posibility to upload files, except of
pasting it into this message?
I stored the scripts on http://www.go-on-software.de/replication/ .
Thre are 4 scripts:
1-Create-Tables-On-Publisher.sql
2-Setup-Publisher.sql
3-Create-DB-on-ServerSub.sql
4-Setup-Re-Publication-on-ServerSub.sql
the first two scrpts are executed at the publisher
the 3rd script is executed at the server subscriber
after the snapshot-agent and the merge-agent finshed
the 4th script re-publish the new database
At this time I haven't added any client subscriber.
To get the Error I create a new Snapshot (on the publisher) and mark the
server subsriber for reinitialisation. After this the merge-agent fails with
the described error message.
Thanks and
Kindest Regards
Jan
"Hilary Cotter" wrote:
> This looks like a bug. Can we get your publication script and table schema
> to see if we can repro it?
> --
> 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
>
> "Jan" <Jan@.discussions.microsoft.com> wrote in message
> news:76CD7085-2418-4147-B907-AF94720330D5@.microsoft.com...
>
>
|||Hi Jan - I click on the hyperlinks but there isn't a file behind it.
Cheers,
Paul
|||Hi Paul,
sorry... my web server doesn't support files with .SQL extensions.
I renamed all to ".txt" and added an zip-file including the 4 scripts.
This time I tested it on stage.
Regards
Jan
"Paul Ibison" wrote:
> Hi Jan - I click on the hyperlinks but there isn't a file behind it.
> Cheers,
> Paul
>
>
|||Hi Paul,
have you got the scripts now? (from http://www.go-on-software.de/replication/)
and
have you found time to run the script and could you repro the error?
I would be happy about any feedback.
Kindest Regards
Jan
|||Jan - it is taking me too long to reformat to get the scripts to work
Pls can you post them up in formatted form?
Rgds,
Paul Ibison
|||Hi Paul, I am ashamed, sorry once again.
I now converted the files to ANSI, so the will be displayed in the browser
with CR.
Alternatively you can download the zip-file, which includes the 4 scripts.
Redards Jan
|||Jan,
I now have it set up and working fine. Did you have a problem with the
original setup or was there a subsequent problem caused by a change made?
It may or may not be relevant, but I probably can't mimic your environment
exactly as I am using no sp1 or sp2 at the moment - our servers have just
been rebuilt and will have the sps applied later on this month.
Rgds,
Paul Ibison
Saturday, February 25, 2012
Problems with bidirectional transactional replication
Hi, I have a four servers in bidirectional transactional replication
(publisher, publicator and subscriber), the problem is when I to be activate
the subscription with one server, the transactional process in the client
application (.Net) fails and send me an error.
Please post up full error message and how you are activating the
subscription...
Rgds,
Paul Ibison
|||OK.
The message is "Cannot find to member name "System.SqlClient.SqlError
server"" in the application client. I disabled the subscription and the error
is vanish.
"Paul Ibison" wrote:
> Please post up full error message and how you are activating the
> subscription...
> Rgds,
> Paul Ibison
>
(publisher, publicator and subscriber), the problem is when I to be activate
the subscription with one server, the transactional process in the client
application (.Net) fails and send me an error.
Please post up full error message and how you are activating the
subscription...
Rgds,
Paul Ibison
|||OK.
The message is "Cannot find to member name "System.SqlClient.SqlError
server"" in the application client. I disabled the subscription and the error
is vanish.
"Paul Ibison" wrote:
> Please post up full error message and how you are activating the
> subscription...
> Rgds,
> Paul Ibison
>
Subscribe to:
Posts (Atom)