Replication Architecture question - Pull subscriptions on a SQL cluster...

Greetings:

I am working on a replication setup using transactional replication using with pull subscriptions and a separate distributor. The pull subscriptions are located on a SQL cluster using the virtual SQL Server name as the subscriber; when the box fails over, we get an error of missing replication.dlls. Researching further, we found that replication only works on one node of the subscriber.

Any ideas on what we did wrong in the setup?

Thanks,

Lee Everest

www.texas2oo.com/sqlblog

can you check the c:\program files\Microsoft Sql Server\80\com folder to see if the dll's exist there? If not try to copy and register them on the failing node.|||

We could do that, but i'm afraid that after I try to install one, several (or dozens) of others might show up missing, meaning that we didn't install it properly in the first place. The specific error that we get is:

Cannot load the DLL replsetoriginator extended procedure, or one of the DLLs it references. Reason: 126(The specified module could not be found.). The step failed.

I have no idea which DLL this function is located but could probably find out.

|||This is a missing or corrupt dll. When I have encountered these in SQL FTS clusters I have had to copy the dll's to the failed not and reregister them.|||So you are saying that the setup is correct, and that if the box fails over replication should pick right back up?|||

A friend of mine responded, below. Apparently replication shouldn’t miss a beat if failover occurs:

Never had this issue before. We are running 4 node clusters (active/active/active/passive) here and we have never had that issue. I'm going to guess it goes back to the install of SQL. I would just copy any missing dll from one node to the other. It sounds like SQL is looking for them so I think you should be safe just to copy them over.

Any thoughts?

|||That depends on the programming mechanism. Sometimes they need to be registered and sometimes they don't. It these dll's contain com compoents they will be, if not a simple file copy will work.

Replication Architecture question - Pull subscriptions on a SQL cluster...

Greetings:

I am working on a replication setup using transactional replication using with pull subscriptions and a separate distributor. The pull subscriptions are located on a SQL cluster using the virtual SQL Server name as the subscriber; when the box fails over, we get an error of missing replication.dlls. Researching further, we found that replication only works on one node of the subscriber.

Any ideas on what we did wrong in the setup?

Thanks,

Lee Everest

www.texas2oo.com/sqlblog

can you check the c:\program files\Microsoft Sql Server\80\com folder to see if the dll's exist there? If not try to copy and register them on the failing node.|||

We could do that, but i'm afraid that after I try to install one, several (or dozens) of others might show up missing, meaning that we didn't install it properly in the first place. The specific error that we get is:

Cannot load the DLL replsetoriginator extended procedure, or one of the DLLs it references. Reason: 126(The specified module could not be found.). The step failed.

I have no idea which DLL this function is located but could probably find out.

|||This is a missing or corrupt dll. When I have encountered these in SQL FTS clusters I have had to copy the dll's to the failed not and reregister them.|||So you are saying that the setup is correct, and that if the box fails over replication should pick right back up?|||

A friend of mine responded, below. Apparently replication shouldn’t miss a beat if failover occurs:

Never had this issue before. We are running 4 node clusters (active/active/active/passive) here and we have never had that issue. I'm going to guess it goes back to the install of SQL. I would just copy any missing dll from one node to the other. It sounds like SQL is looking for them so I think you should be safe just to copy them over.

Any thoughts?

|||That depends on the programming mechanism. Sometimes they need to be registered and sometimes they don't. It these dll's contain com compoents they will be, if not a simple file copy will work.

Replication -- subscriber job history does not appear on SQL server 2005 Subscriber from S

Hi Everyone,
I have a small issue in looking at the the subscription's job history
(transaction history) on SQL Server 2005 subscriber subscribed to a
SQL Server 2000 publication.
We have the following environments set up and running and all the
Windows and SQL servers service packed to the latest. We are using
transactional replication with all pull subscriptions.
-----
Replication Publisher: SQL server 2000 Standard Edition(on Windows
2003 Server)
both publisher and distributor run on the same machine.
-----
Replication Subscriber: SQL server 2000 Standard Edition(on Windows
2000 Server)
both publisher and distributor run on the same machine.
-----
When I look on the subscriber SQL server 2000, in the subscription's
job history, a message (row) for each transaction (or one row for upto
a group of 100 transactions) is written along with start-up messages
for the job and any error messages.
But when we set up the subscriptions on SQL server 2005 from same
publication, as below
-----
Subscriber: SQL server 2005 Standard Edition(on Windows 2003 Server)
both publisher and distributor run on the same machine.
-----
the replication works fine but the job history is not consistent
between 2000 and 2005 subscribers. When I look on SQL server 2005
subscription's job history, no rows are written for the transactions,
but only messages are logged for job start-ups and any error messages.
Did anyone notice this behaviour?
Is there any way we can configure so all the transaction messages
appear in subscription's job history in SQL Server 2005.
Regards
Raj Chidipudi
On 6 Aug, 14:03, Raj Chidipudi <chidip...@.gmail.com> wrote:
> Hi Everyone,
> I have a small issue in looking at the the subscription's job history
> (transaction history) on SQL Server 2005 subscriber subscribed to a
> SQL Server 2000 publication.
> We have the following environments set up and running and all the
> Windows and SQL servers service packed to the latest. We are using
> transactional replication with all pull subscriptions.
> ----X--
> Replication Publisher: SQL server 2000 Standard Edition(on Windows
> 2003 Server)
> both publisher and distributor run on the same machine.
> ----X--
> Replication Subscriber: SQL server 2000 Standard Edition(on Windows
> 2000 Server)
> both publisher and distributor run on the same machine.
> ----X--
> When I look on the subscriber SQL server 2000, in the subscription's
> job history, a message (row) for each transaction (or one row for upto
> a group of 100 transactions) is written along with start-up messages
> for the job and any error messages.
> But when we set up the subscriptions on SQL server 2005 from same
> publication, as below
> ----X--
> Subscriber: SQL server 2005 Standard Edition(on Windows 2003 Server)
> both publisher and distributor run on the same machine.
> ----X--
> the replication works fine but the job history is not consistent
> between 2000 and 2005 subscribers. When I look on SQL server 2005
> subscription's job history, no rows are written for the transactions,
> but only messages are logged for job start-ups and any error messages.
> Did anyone notice this behaviour?
> Is there any way we can configure so all the transaction messages
> appear in subscription's job history in SQL Server 2005.
> Regards
> Raj Chidipudi
Resolved the issue by editing job used to run the subscription on the
subscriber.
Just suffixed this "-HistoryVerboseLevel [3] -OutputVerboseLevel [2]"
at the end of the command in the only job step.
But i must admit it needed a bit of digging-in few things.
Raj Chidipudi

Replication

Mssql 2005 - Mssql2000
I try to create a "Transactional publication with updatable subscriptions:"
But I can see that all tables cet an added colunm "msrepl_tran_version"
Is it possible to replicate 2-way that wil not add this column
(msrepl_tran_version)?
What will happen if I set up "Transactional publication" in both Database.
ie. both is a Publisher and Subscriber at a same time?
The data that will be updated and inserted will newer confilct in our
environment. (The Software we use manage this.)
Roger Nygrd
Ask IT
Roger,
these links should help you set up bi-directional transactional replication:
http://support.microsoft.com/default...b;en-us;820675
http://msdn.microsoft.com/library/de...lsamp_3ve6.asp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||It works well. You don't need this msrepl_tran_version column. Please see
this script for an example of it.
http://www.indexserverfaq.com/bidireproscript.sql or
http://www.indexserverfaq.com/Mike1.sql
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
"Roger Nygrd" <roger@.askit.no> wrote in message
news:11surfla2d9svab@.corp.supernews.com...
> Mssql 2005 - Mssql2000
> I try to create a "Transactional publication with updatable
> subscriptions:"
> But I can see that all tables cet an added colunm "msrepl_tran_version"
> Is it possible to replicate 2-way that wil not add this column
> (msrepl_tran_version)?
> What will happen if I set up "Transactional publication" in both Database.
> ie. both is a Publisher and Subscriber at a same time?
> The data that will be updated and inserted will newer confilct in our
> environment. (The Software we use manage this.)
> Roger Nygrd
> Ask IT
>
>

Replication

Hello,
Whats's the utility / advantages of the "Transactional publication with
updatable subscriptions"
thanks for your help!!!
nico
"pralnico" <pralnico@.discussions.microsoft.com> wrote in message
news:1C221973-1029-4380-8C24-A8C55817567F@.microsoft.com...
> Hello,
> Whats's the utility / advantages of the "Transactional publication with
> updatable subscriptions"
> thanks for your help!!!
>
Transactional replication starts with a snapshot. Thereafter only the
changes are replicated (which will typically mean less network traffic /
more frequent updates / less latency between different copies of the
database).
Updateable subscriptions means that the destination servers (subscribers)
can update the data on their own SQL Servers. SQL server will update it
locally and at the same time on the Publisher database, so that the changes
can then be replicated out to the other subscribers. This is done via a
distributed transaction.
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.775 / Virus Database: 522 - Release Date: 08/10/2004

Replication

Hello,
Whats's the utility / advantages of the "Transactional publication with
updatable subscriptions"
thanks for your help!!!
nico"pralnico" <pralnico@.discussions.microsoft.com> wrote in message
news:1C221973-1029-4380-8C24-A8C55817567F@.microsoft.com...
> Hello,
> Whats's the utility / advantages of the "Transactional publication with
> updatable subscriptions"
> thanks for your help!!!
>
Transactional replication starts with a snapshot. Thereafter only the
changes are replicated (which will typically mean less network traffic /
more frequent updates / less latency between different copies of the
database).
Updateable subscriptions means that the destination servers (subscribers)
can update the data on their own SQL Servers. SQL server will update it
locally and at the same time on the Publisher database, so that the changes
can then be replicated out to the other subscribers. This is done via a
distributed transaction.
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.775 / Virus Database: 522 - Release Date: 08/10/2004

Replication

Hello,
Whats's the utility / advantages of the "Transactional publication with
updatable subscriptions"
thanks for your help!!!
nico"pralnico" <pralnico@.discussions.microsoft.com> wrote in message
news:1C221973-1029-4380-8C24-A8C55817567F@.microsoft.com...
> Hello,
> Whats's the utility / advantages of the "Transactional publication with
> updatable subscriptions"
> thanks for your help!!!
>
Transactional replication starts with a snapshot. Thereafter only the
changes are replicated (which will typically mean less network traffic /
more frequent updates / less latency between different copies of the
database).
Updateable subscriptions means that the destination servers (subscribers)
can update the data on their own SQL Servers. SQL server will update it
locally and at the same time on the Publisher database, so that the changes
can then be replicated out to the other subscribers. This is done via a
distributed transaction.
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.775 / Virus Database: 522 - Release Date: 08/10/2004