Replication Error while Configuring Distributor

Hi,
I am trying to setup transactional replication on a database within 1
sql instance. When I try to configure the pulisher/distributor, it errors out
with this message.
"SQL Server Enterprise Manager could not configure 'DZDEV007' as the
distributor for 'DZDEV007'.
Error 14234 : The specified '@.server' in invalid (valid values are returned
by sp_helpserver"
What's going on ? Please help.
TIA
Mohan
Hi Mohan,
The following KB seems to match most of your symptoms although your server
name appear to be too short for the problem occur:
http://support.microsoft.com/default...b;en-us;310639
You may also want to consider some other possibilities such as subtle
comparison issues related to the collation that you are using for your server.
-Raymond
"MO" wrote:

> Hi,
> I am trying to setup transactional replication on a database within 1
> sql instance. When I try to configure the pulisher/distributor, it errors out
> with this message.
> "SQL Server Enterprise Manager could not configure 'DZDEV007' as the
> distributor for 'DZDEV007'.
> Error 14234 : The specified '@.server' in invalid (valid values are returned
> by sp_helpserver"
> What's going on ? Please help.
> TIA
> Mohan

Replication Error in Visual Basic

Hi Group,
I have an SQL Server with a database called support for which I have setup a
merge replication subscription called "support".
On my laptop, I have a support program using MSDE locally to access an exact
copy of the data as the main SQL server has.
Whenenver I try to synchronise using the SQLDistribution activeX control, I
get the following message:
"Cannot create transactional subscription to merge publication "support".
The publication type should either be transactional(0) or snapshot(1) for
this operation."
The trouble is, how I see it, I have to used merged because several clients
would have disconnected data sources and any or all could effectively change
the data.
Any help on this appreciated.
Jim
I think your script is wrong. Could you post it here?
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
|||Hi Hilary,
Thanks for the reply. I figured out I actually needed to use the "merge"
activeX control and not the distribution one. My code is below but I am
still receiving this error:
"The merge process was unable to add the pull subscription from
'JBHOME':'Support:'Support'."
JBHOME being my SQL server, support being the database name and also the
publication name. I have tried various variations on the below code but to
no avail.
-- CODE: --
With SQLMerge
.Publisher = "JBHOME"
.PublisherDatabase = "Support"
.Publication = "Support"
.PublisherSecurityMode = NT_AUTHENTICATION
.Distributor = "JBHOME"
.DistributorSecurityMode = NT_AUTHENTICATION
.Subscriber = "(Local)"
.SubscriberDatabase = "Support"
.SubscriberDatasourceType = SQL_SERVER
.SubscriberSecurityMode = NT_AUTHENTICATION
.SubscriberLogin = "sa"
.SubscriberPassword = "mypassword"
.SubscriptionType = ANONYMOUS
.SynchronizationType = AUTOMATIC
.AddSubscription EXISTING_DATABASE, NONE
.Initialize
.Run
.Terminate
End With
-- END CODE --
Kind Regards
Jim
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:1113405033.118118.312480@.g14g2000cwa.googlegr oups.com...
>I think your script is wrong. Could you post it here?
> --
> 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
>
|||FYI,
What I am attempting to do is have a server with a database on it and be
able for a vb written client program to "merge" update the remote server.
The clients will use MSDE as their disconnected database, and all this will
work over the internet (hopefully!!!)
Jim
"Reapes" <reapesuk-@.hotmail.com> wrote in message
news:xvb7e.85688$Nr5.22780@.fe2.news.blueyonder.co. uk...
> Hi Hilary,
> Thanks for the reply. I figured out I actually needed to use the "merge"
> activeX control and not the distribution one. My code is below but I am
> still receiving this error:
> "The merge process was unable to add the pull subscription from
> 'JBHOME':'Support:'Support'."
> JBHOME being my SQL server, support being the database name and also the
> publication name. I have tried various variations on the below code but to
> no avail.
> -- CODE: --
> With SQLMerge
> .Publisher = "JBHOME"
> .PublisherDatabase = "Support"
> .Publication = "Support"
> .PublisherSecurityMode = NT_AUTHENTICATION
> .Distributor = "JBHOME"
> .DistributorSecurityMode = NT_AUTHENTICATION
> .Subscriber = "(Local)"
> .SubscriberDatabase = "Support"
> .SubscriberDatasourceType = SQL_SERVER
> .SubscriberSecurityMode = NT_AUTHENTICATION
> .SubscriberLogin = "sa"
> .SubscriberPassword = "mypassword"
> .SubscriptionType = ANONYMOUS
> .SynchronizationType = AUTOMATIC
> .AddSubscription EXISTING_DATABASE, NONE
>
> .Initialize
> .Run
> .Terminate
> End With
>
> -- END CODE --
> Kind Regards
> Jim
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:1113405033.118118.312480@.g14g2000cwa.googlegr oups.com...
>

replication error after database update

I have a system where I utilize merge replication between sqlserver2000 and
pocketpc sqlservece 2.0. The setup is very mature, and has been working fine
until I had my customer "refresh" the database with new data. We're still in
the testing phase, and the database I connect to is a copy of their live
one. After the database was restored from a backup of the live database, I
get the following error on the pocketpc when attempting to perform a merge.
Unique indexes and constraints cannot be created on columns that allow null
values
That's as descriptive as the error gets. I have a few questions:
Is there any place either on the server or the pocketpc that I can find a
log with more information. The publication has many articles with many
fields. I can remove one at a time and figure out which one is causing the
problem, but it will take lots of time. I was hoping to find some
information as to which table is causing the problem.
Also I'm having difficulty removing an article from a publication after
subscriptions have been pulled or attempted to be pulled. I've
re-initialized subscriptions, but the articles cannot be removed. What's the
procedure for doing this?
sorry about double post, I got an error message that the first one wasn't
sent!
"mgarner1980" <mgarner@.kbsi.com> wrote in message
news:%23aiSjpAeFHA.3028@.TK2MSFTNGP09.phx.gbl...
> I have a system where I utilize merge replication between sqlserver2000
and
> pocketpc sqlservece 2.0. The setup is very mature, and has been working
fine
> until I had my customer "refresh" the database with new data. We're still
in
> the testing phase, and the database I connect to is a copy of their live
> one. After the database was restored from a backup of the live database, I
> get the following error on the pocketpc when attempting to perform a
merge.
> Unique indexes and constraints cannot be created on columns that allow
null
> values
>
> That's as descriptive as the error gets. I have a few questions:
>
> Is there any place either on the server or the pocketpc that I can find a
> log with more information. The publication has many articles with many
> fields. I can remove one at a time and figure out which one is causing the
> problem, but it will take lots of time. I was hoping to find some
> information as to which table is causing the problem.
>
> Also I'm having difficulty removing an article from a publication after
> subscriptions have been pulled or attempted to be pulled. I've
> re-initialized subscriptions, but the articles cannot be removed. What's
the
> procedure for doing this?
>

Replication error - schema

I am getting the error below trying the 1st merge synch to my laptop. The
laptop has MSDE2000 SP3 on it. I tried this synch right after I setup the
database as a publisher. This is the 1st subscriber I have tried to create.
Can anyone help? Thanks.
David
The schema script
'\\LIFEDEV02\d$\sqldata\MSSQL\ReplData\unc\LIFEDEV 02_MCFIData_MCFIData\20051129091321\vw_BillingDeta ilBalance_1465.sch'
could not be propagated to the subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
------
Unable to replicate a view or function because the referenced objects or
columns are not present on the Subscriber.
(Source: DONAFAYE (Agent); Error number: 0)
------
Invalid object name 'dbo.vw_BillingPaid'.
(Source: DONAFAYE (Data source); Error number: 208)
------
I think that I read somewhere that all objects such as functions, triggers,
procs, etc.. have to be at the subscriber if there is a dependency AND if
they are not in your publication. If the referenced object is not in your
publication then you'll have to add it or manually create it at the
subscriber.
Scott E. Hunley (MCAD)
Measure Twice, Cut Once...
"David" wrote:

> I am getting the error below trying the 1st merge synch to my laptop. The
> laptop has MSDE2000 SP3 on it. I tried this synch right after I setup the
> database as a publisher. This is the 1st subscriber I have tried to create.
> Can anyone help? Thanks.
> David
> The schema script
> '\\LIFEDEV02\d$\sqldata\MSSQL\ReplData\unc\LIFEDEV 02_MCFIData_MCFIData\20051129091321\vw_BillingDeta ilBalance_1465.sch'
> could not be propagated to the subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ------
> Unable to replicate a view or function because the referenced objects or
> columns are not present on the Subscriber.
> (Source: DONAFAYE (Agent); Error number: 0)
> ------
> Invalid object name 'dbo.vw_BillingPaid'.
> (Source: DONAFAYE (Data source); Error number: 208)
> ------
>
>
|||David,
stored procedures use deferred name resolution, so you can get away with
this sort of thing, but in the case of views it doesn't work - you'll need
to have vw_BillingPaid on the subscriber to be able to initialize. You could
drop the subscription, XXX the view into the publication then readd the
subscription. You could alternatively add vw_BillingPaid manually, but this
would have to be done for any other subscribers.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
I'm confused. This is the FIRST subscription I am trying to create. The
view that is referred to DOES exist on the Publication. I do not understand
why I am getting this error.
David
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23fvafr09FHA.912@.TK2MSFTNGP11.phx.gbl...
> David,
> stored procedures use deferred name resolution, so you can get away with
> this sort of thing, but in the case of views it doesn't work - you'll need
> to have vw_BillingPaid on the subscriber to be able to initialize. You
> could drop the subscription, XXX the view into the publication then readd
> the subscription. You could alternatively add vw_BillingPaid manually, but
> this would have to be done for any other subscribers.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Paul,
I also looked at the articles being published and ALL views are selected. I
tried dropping and re-creating the subscription, but it did the same thing
at the exact same place. I once had a similar error problem with DTS on a
different database but never was able to resolve it. I also tried your
suggestion to add the view vw_BillingPaid to the subscriber. I did it with
DTS and exported the view and it went over fine. Then I ran the synch
again, but got the exact same error. This is very frustrating. Any ideas
on what else I can do to make this work? I have 7 laptops to setup as
anonymous subscribers, but can't even get the very 1st one to work. Thanks.
David
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23fvafr09FHA.912@.TK2MSFTNGP11.phx.gbl...
> David,
> stored procedures use deferred name resolution, so you can get away with
> this sort of thing, but in the case of views it doesn't work - you'll need
> to have vw_BillingPaid on the subscriber to be able to initialize. You
> could drop the subscription, XXX the view into the publication then readd
> the subscription. You could alternatively add vw_BillingPaid manually, but
> this would have to be done for any other subscribers.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||David,
I think your dependency information is corrupted. If you add the view to the
subscriber manually and meanwhile drop it from the publication it should be
ok. The current problem is that it is still in the publication and is
therefore being dropped.
Alternatively, run sp_depends on the view that errors to check that the
dependency is not acknowledged by SQL Server. If this shows no dependencies
then refresh the view and run it again to check the dependency is
recognised, and once this is the case, the snapshot article order should be
correct.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||You were right. I dropped the pub and subscriber and dropped and re-created
the 2 views and checked their dependencies. Both now appear ok. Then I
tried publication and the create subscriber again and got error on a
different view. Same error. I will remove and recreate everything again!
Is there any way to check all views at once for corrupt dependencies? (I'm
guessing no). Also, any idea how this could happen to so many views?
David
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:O8FdSaQ%23FHA.3340@.TK2MSFTNGP12.phx.gbl...
> David,
> I think your dependency information is corrupted. If you add the view to
> the subscriber manually and meanwhile drop it from the publication it
> should be ok. The current problem is that it is still in the publication
> and is therefore being dropped.
> Alternatively, run sp_depends on the view that errors to check that the
> dependency is not acknowledged by SQL Server. If this shows no
> dependencies then refresh the view and run it again to check the
> dependency is recognised, and once this is the case, the snapshot article
> order should be correct.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||David,
these links show the sort of thing we're talking about:
http://support.microsoft.com/?id=115333
http://support.microsoft.com/?id=201846
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Transactional\Snapshot replication in SQL2005 (the SQL2005 snapshot agent
specifically) is much more resilient to inaccurate\missing information in
sysdepends or sys.sql_dependencies. For Merge replication users, they have
the capability to specify a custom ordering for the articles in SQL2005 to
overcome these kinds of problems.
-Raymond
"David" <dlchase@.lifetimeinc.com> wrote in message
news:OTAXiyR%23FHA.3804@.TK2MSFTNGP14.phx.gbl...
> You were right. I dropped the pub and subscriber and dropped and
> re-created the 2 views and checked their dependencies. Both now appear
> ok. Then I tried publication and the create subscriber again and got
> error on a different view. Same error. I will remove and recreate
> everything again! Is there any way to check all views at once for corrupt
> dependencies? (I'm guessing no). Also, any idea how this could happen to
> so many views?
> David
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
> news:O8FdSaQ%23FHA.3340@.TK2MSFTNGP12.phx.gbl...
>

Replication Error

I have been trying to setup SQL Server Replication between two SQL Server
2000 SP3 servers.
I have configured the Distributer and publisher on the same SQL Server. I
modified the Publisher Snapshot folder to a non default ie.
\\server\is\Replication\TLIS. Note \\server is a file server within our
network
The SQL Agent Service on both SQL Servers run under a domain account; with
admin rights on the SQL Servers and full control on the Publisher Snapshot
folder.
Questions/Errors:
When creating the subscription i get the following message; which is
probably normal?
SQL Server Enterprise Manager successfully created a pull subscription to
publication 'Merge_Replicate'.
The initial snapshot for publication 'Merge_Replicate' is not available.
This subscription will be initialized after the snapshot is available.
Errors:
I am receiving the following errors when replication executes. The database
objects I am trying to replicate are not replicating.
event log:
Unable to start a DCOM Server: {08B0B2D9-3FB3-11D3-A4DE-00C04F610189}. The
error: "The system cannot find the path specified. "
Happened while starting this command:
C:\PROGRA~1\MICROS~3\80\COM\snapshot.exe -Embedding
Agent logs:
Executed as user: NFPOWER_DOMAIN\SQLboss. Replication-Replication Snapshot
Subsystem:
agent NPBOSSSQL4\NPBOSSSQL4-INTRANETD-Merge_Replicate-1 failed. The system
cannot find the path specified. NOTE: The step was retried the requested
number of times (10) without succeeding. The step failed. [SQLSTATE 42000]
(Error 14151). The step failed.
We are looking at using SQL Replication to support an application we are
currently working on. I would really appreciate your help in resolving this
issue. Thanks in Advance.
Hi Gary, can you try to see if you can manually start
C:\PROGRA~1\MICROS~3\80\COM\snapshot.exe on the distributor machine?
-Raymond
"Gary Murphy" wrote:

> I have been trying to setup SQL Server Replication between two SQL Server
> 2000 SP3 servers.
> I have configured the Distributer and publisher on the same SQL Server. I
> modified the Publisher Snapshot folder to a non default ie.
> \\server\is\Replication\TLIS. Note \\server is a file server within our
> network
> The SQL Agent Service on both SQL Servers run under a domain account; with
> admin rights on the SQL Servers and full control on the Publisher Snapshot
> folder.
> Questions/Errors:
> When creating the subscription i get the following message; which is
> probably normal?
> SQL Server Enterprise Manager successfully created a pull subscription to
> publication 'Merge_Replicate'.
> The initial snapshot for publication 'Merge_Replicate' is not available.
> This subscription will be initialized after the snapshot is available.
> Errors:
> I am receiving the following errors when replication executes. The database
> objects I am trying to replicate are not replicating.
> event log:
> Unable to start a DCOM Server: {08B0B2D9-3FB3-11D3-A4DE-00C04F610189}. The
> error: "The system cannot find the path specified. "
> Happened while starting this command:
> C:\PROGRA~1\MICROS~3\80\COM\snapshot.exe -Embedding
> Agent logs:
> Executed as user: NFPOWER_DOMAIN\SQLboss. Replication-Replication Snapshot
> Subsystem:
> agent NPBOSSSQL4\NPBOSSSQL4-INTRANETD-Merge_Replicate-1 failed. The system
> cannot find the path specified. NOTE: The step was retried the requested
> number of times (10) without succeeding. The step failed. [SQLSTATE 42000]
> (Error 14151). The step failed.
> We are looking at using SQL Replication to support an application we are
> currently working on. I would really appreciate your help in resolving this
> issue. Thanks in Advance.
>
|||HI Raymond,
I tried as you suggested. I logged into the server using the same domain
account that the SQL Agent runs under.
I am assuming you manually start snapshot.exe by just running the
executasble as I tried below:
C:\Program Files\Microsoft SQL Server\80\COM>snapshot.exe -Embedding
C:\Program Files\Microsoft SQL Server\80\COM>echo %errorlevel%
0
C:\Program Files\Microsoft SQL Server\80\COM>replmerg.exe -Embedding
C:\Program Files\Microsoft SQL Server\80\COM>echo %errorlevel%
0
When I setup replication two jobs are setup within sql server server. A
snapshot and merge job. Within each job there are three steps. The first
step of each job (Snapshot Agent startup message, Merge Agent startup
message) starts successfully.
The second step of each job (Run Agent) fails with "The system cannot find
the path specified" error.
1) Job 1 is NPBOSSSQL4\NPBOSSSQL4-INTRANETD-Merge_Replicate-1
steps :
- Snapshot Agent startup message:
sp_MSadd_snapshot_history @.perfmon_increment = 0, @.agent_id = 1,
@.runstatus = 1, @.comments = 'Starting agent.'
- Run Agent:
-Publisher [NPBOSSSQL4\NPBOSSSQL4] -PublisherDB [INTRANETD] -Distributor
[NPBOSSSQL4\NPBOSSSQL4] -Publication [Merge_Replicate] -ReplicationType 2
-DistributorSecurityMode 1
-Detect nonlogged agent shutdown:
sp_MSdetect_nonlogged_shutdown @.subsystem = 'Snapshot', @.agent_id = 1
Fails with error: Executed as user: NFPOWER_DOMAIN\SQLboss.
Replication-Replication Snapshot Subsystem: agent
NPBOSSSQL4\NPBOSSSQL4-INTRANETD-Merge_Replicate-1 failed. The system cannot
find the path specified. NOTE: The step was retried the requested number of
times (10) without succeeding. The step failed. [SQLSTATE 42000] (Error
14151). The step failed.
2) Job 2 is:
NPBOSSSQL4\NPBOSSSQL4-INTRANETD-Merge_Replicate-NPBOSSSQL2\NPBOSSSQL2-2
steps:
- Merge Agent startup message:
sp_MSadd_merge_history @.perfmon_increment = 0, @.agent_id = 2, @.runstatus =
1, @.comments = 'Starting agent.'
- run agent:
-Publisher [NPBOSSSQL4\NPBOSSSQL4] -PublisherDB [INTRANETD] -Publication
[Merge_Replicate] -Subscriber [NPBOSSSQL2\NPBOSSSQL2] -SubscriberDB
[Northwind] -Distributor [NPBOSSSQL4\NPBOSSSQL4] -DistributorSecurityMode 1
- Detect nonlogged agent shutdown:
sp_MSdetect_nonlogged_shutdown @.subsystem = 'Merge', @.agent_id = 2
Fails with error: Executed as user: NFPOWER_DOMAIN\SQLboss.
Replication-agentclassname: agent
NPBOSSSQL4\NPBOSSSQL4-INTRANETD-Merge_Replicate-NPBOSSSQL2\NPBOSSSQL2-2
failed. The system cannot find the path specified. NOTE: The step was
retried the requested number of times (10) without succeeding. The step
failed. [SQLSTATE 42000] (Error 14151). The step failed.
"Raymond Mak [MSFT]" wrote:
[vbcol=seagreen]
> Hi Gary, can you try to see if you can manually start
> C:\PROGRA~1\MICROS~3\80\COM\snapshot.exe on the distributor machine?
> -Raymond
> "Gary Murphy" wrote:
|||Gary, I have the vague suspicion that the 8.3 path that you listed below is
bad. As such it is important that you try running:
C:\PROGRA~1\MICROS~3\80\COM\snapshot.exe
driectly instead of navigating to the 80\com directory and then run the
executables. Once we have determined that the 8.3 path is indeed bad (or
not), we can then try something else accordingly.
-Raymond
"Gary Murphy" wrote:
[vbcol=seagreen]
> HI Raymond,
> I tried as you suggested. I logged into the server using the same domain
> account that the SQL Agent runs under.
> I am assuming you manually start snapshot.exe by just running the
> executasble as I tried below:
> C:\Program Files\Microsoft SQL Server\80\COM>snapshot.exe -Embedding
> C:\Program Files\Microsoft SQL Server\80\COM>echo %errorlevel%
> 0
> C:\Program Files\Microsoft SQL Server\80\COM>replmerg.exe -Embedding
> C:\Program Files\Microsoft SQL Server\80\COM>echo %errorlevel%
> 0
> When I setup replication two jobs are setup within sql server server. A
> snapshot and merge job. Within each job there are three steps. The first
> step of each job (Snapshot Agent startup message, Merge Agent startup
> message) starts successfully.
> The second step of each job (Run Agent) fails with "The system cannot find
> the path specified" error.
> 1) Job 1 is NPBOSSSQL4\NPBOSSSQL4-INTRANETD-Merge_Replicate-1
> steps :
> - Snapshot Agent startup message:
> sp_MSadd_snapshot_history @.perfmon_increment = 0, @.agent_id = 1,
> @.runstatus = 1, @.comments = 'Starting agent.'
> - Run Agent:
> -Publisher [NPBOSSSQL4\NPBOSSSQL4] -PublisherDB [INTRANETD] -Distributor
> [NPBOSSSQL4\NPBOSSSQL4] -Publication [Merge_Replicate] -ReplicationType 2
> -DistributorSecurityMode 1
> -Detect nonlogged agent shutdown:
> sp_MSdetect_nonlogged_shutdown @.subsystem = 'Snapshot', @.agent_id = 1
> Fails with error: Executed as user: NFPOWER_DOMAIN\SQLboss.
> Replication-Replication Snapshot Subsystem: agent
> NPBOSSSQL4\NPBOSSSQL4-INTRANETD-Merge_Replicate-1 failed. The system cannot
> find the path specified. NOTE: The step was retried the requested number of
> times (10) without succeeding. The step failed. [SQLSTATE 42000] (Error
> 14151). The step failed.
> 2) Job 2 is:
> NPBOSSSQL4\NPBOSSSQL4-INTRANETD-Merge_Replicate-NPBOSSSQL2\NPBOSSSQL2-2
> steps:
> - Merge Agent startup message:
> sp_MSadd_merge_history @.perfmon_increment = 0, @.agent_id = 2, @.runstatus =
> 1, @.comments = 'Starting agent.'
> - run agent:
> -Publisher [NPBOSSSQL4\NPBOSSSQL4] -PublisherDB [INTRANETD] -Publication
> [Merge_Replicate] -Subscriber [NPBOSSSQL2\NPBOSSSQL2] -SubscriberDB
> [Northwind] -Distributor [NPBOSSSQL4\NPBOSSSQL4] -DistributorSecurityMode 1
> - Detect nonlogged agent shutdown:
> sp_MSdetect_nonlogged_shutdown @.subsystem = 'Merge', @.agent_id = 2
> Fails with error: Executed as user: NFPOWER_DOMAIN\SQLboss.
> Replication-agentclassname: agent
> NPBOSSSQL4\NPBOSSSQL4-INTRANETD-Merge_Replicate-NPBOSSSQL2\NPBOSSSQL2-2
> failed. The system cannot find the path specified. NOTE: The step was
> retried the requested number of times (10) without succeeding. The step
> failed. [SQLSTATE 42000] (Error 14151). The step failed.
> "Raymond Mak [MSFT]" wrote:
|||Hi Raymond,
Your suspicion is correct the path is bad.
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.
C:\>C:\PROGRA~1\MICROS~3\80\COM\snapshot.exe -Embedding
The system cannot find the path specified.
I changed to the path specified as you will see below it's the incorrect path.
C:\>cd C:\PROGRA~1\MICROS~3
C:\PROGRA~1\MICROS~3>dir
Volume in drive C has no label.
Volume Serial Number is E47F-3E92
Directory of C:\PROGRA~1\MICROS~3
2004/06/29 12:22a <DIR> .
2004/06/29 12:22a <DIR> ..
2004/06/29 12:22a <DIR> Bin
2004/06/29 12:22a <DIR> Data
2004/02/24 12:43p 40,158 DeIsL1.isu
2004/06/29 12:22a <DIR> Help
2004/06/29 12:22a <DIR> Help80
2000/08/05 11:22p 47,815 readme.txt
2004/06/29 12:22a <DIR> Samples
2002/10/20 03:13p 49,152 uninst.dll
2004/02/24 01:10p 182,606 uninst.isu
4 File(s) 319,731 bytes
7 Dir(s) 13,039,251,456 bytes free
I tried setting to other combinations: C:\PROGRA~1\MICROS~1,
C:\PROGRA~1\MICROS~2, C:\PROGRA~1\MICROS~4 and all these give me the wrong
folder as well.
How do I get the replication tools to point at the correct folders i.e
C:\Program Files\Microsoft SQL Server\80\COM.
I searched the registry for snapshot.exe and replmerg.exe and some entries
have the correct path while others don't. It's inconsistent within the
registry.
Thanks Raymond.
"Raymond Mak [MSFT]" wrote:
[vbcol=seagreen]
> Gary, I have the vague suspicion that the 8.3 path that you listed below is
> bad. As such it is important that you try running:
> C:\PROGRA~1\MICROS~3\80\COM\snapshot.exe
> driectly instead of navigating to the 80\com directory and then run the
> executables. Once we have determined that the 8.3 path is indeed bad (or
> not), we can then try something else accordingly.
> -Raymond
> "Gary Murphy" wrote:
|||Hi Gary,
You can repair the path of the replication COM servers by doing the following:
c:\Program Files\Microsoft SQL Server\80\Com>snapshot -RegServer
c:\Program Files\Microsoft SQL Server\80\Com>replmerg -RegServer
c:\Program Files\Microsoft SQL Server\80\Com>distrib -RegServer
c:\Program Files\Microsoft SQL Server\80\Com>logread -RegServer
c:\Program Files\Microsoft SQL Server\80\Com>qrdrsvc -RegServer
It seems kind of strange that the 8.3 path (btw, you can do a dir /x to find
out what the current 8.3 path is) has changed since you first installed SQL
Server. It would be great if you can let us know if you can recall anything
unusual that happened recently on your machine that would have caused such a
change. (accidental renaming of Program Files, Microsoft SQL Server in
explorer ?)
-Raymond
"Gary Murphy" wrote:
[vbcol=seagreen]
> Hi Raymond,
> Your suspicion is correct the path is bad.
> Microsoft Windows 2000 [Version 5.00.2195]
> (C) Copyright 1985-2000 Microsoft Corp.
> C:\>C:\PROGRA~1\MICROS~3\80\COM\snapshot.exe -Embedding
> The system cannot find the path specified.
> I changed to the path specified as you will see below it's the incorrect path.
> C:\>cd C:\PROGRA~1\MICROS~3
> C:\PROGRA~1\MICROS~3>dir
> Volume in drive C has no label.
> Volume Serial Number is E47F-3E92
> Directory of C:\PROGRA~1\MICROS~3
> 2004/06/29 12:22a <DIR> .
> 2004/06/29 12:22a <DIR> ..
> 2004/06/29 12:22a <DIR> Bin
> 2004/06/29 12:22a <DIR> Data
> 2004/02/24 12:43p 40,158 DeIsL1.isu
> 2004/06/29 12:22a <DIR> Help
> 2004/06/29 12:22a <DIR> Help80
> 2000/08/05 11:22p 47,815 readme.txt
> 2004/06/29 12:22a <DIR> Samples
> 2002/10/20 03:13p 49,152 uninst.dll
> 2004/02/24 01:10p 182,606 uninst.isu
> 4 File(s) 319,731 bytes
> 7 Dir(s) 13,039,251,456 bytes free
> I tried setting to other combinations: C:\PROGRA~1\MICROS~1,
> C:\PROGRA~1\MICROS~2, C:\PROGRA~1\MICROS~4 and all these give me the wrong
> folder as well.
> How do I get the replication tools to point at the correct folders i.e
> C:\Program Files\Microsoft SQL Server\80\COM.
> I searched the registry for snapshot.exe and replmerg.exe and some entries
> have the correct path while others don't. It's inconsistent within the
> registry.
> Thanks Raymond.
> "Raymond Mak [MSFT]" wrote:
|||Hi Raymond,
I'm not in the office today (Wednesday) so I will try your fixes on Thursday
and let you know the result. We have a number of SQL Server's that I can
check the 8.3 path on, just for curiosity.
As to why the path has changed I'm not sure. Our SQL Server's are
restricted to admin staff and DBA's so the chances of a folder getting
renamed is low. I am seeing the same type of error on the publisher and
subscriber SQL Servers (two separate servers). We have recently applied MS
updates related to security patches but no SQL Server patches. I will check
with the guys back at the office when I get back to work on Thursday to see
if they have any comments on this issue.
Thanks.
"Raymond Mak [MSFT]" wrote:
[vbcol=seagreen]
> Hi Gary,
> You can repair the path of the replication COM servers by doing the following:
> c:\Program Files\Microsoft SQL Server\80\Com>snapshot -RegServer
> c:\Program Files\Microsoft SQL Server\80\Com>replmerg -RegServer
> c:\Program Files\Microsoft SQL Server\80\Com>distrib -RegServer
> c:\Program Files\Microsoft SQL Server\80\Com>logread -RegServer
> c:\Program Files\Microsoft SQL Server\80\Com>qrdrsvc -RegServer
> It seems kind of strange that the 8.3 path (btw, you can do a dir /x to find
> out what the current 8.3 path is) has changed since you first installed SQL
> Server. It would be great if you can let us know if you can recall anything
> unusual that happened recently on your machine that would have caused such a
> change. (accidental renaming of Program Files, Microsoft SQL Server in
> explorer ?)
> -Raymond
> "Gary Murphy" wrote:
|||Hi Raymond,
I did the dir /x on the servers where I am having the problem. Here is the
result:
As you will see MS SQL Server has a 8.3 path called MI6841~1. Not sure how
it got this name.
I checked 5 other sql servers that we have and the 8.3 path is either
micros~3 or micros~3. I assume these are okay.
2002/01/31 08:08a <DIR> ACCESS~1 Accessories
2004/10/08 04:01p <DIR> COMMON~1 Common Files
2004/06/29 12:21a <DIR> Compaq
2002/01/31 11:40a <DIR> COMPLU~1 ComPlus Applications
2004/07/12 02:00p <DIR> COMPUT~1 ComputerAssociates
2004/06/29 12:21a <DIR> DATADI~1 DataDirect
2004/11/06 09:14a <DIR> INTERN~1 Internet Explorer
2004/06/29 12:22a <DIR> MICROS~3 Microsoft Analysis
Servi
es
2002/01/31 08:08a <DIR> MICROS~2 microsoft frontpage
2004/06/29 12:22a <DIR> MICROS~4 Microsoft Operations
Man
ger 2000
2002/01/31 08:09a <DIR> MICROS~1 Microsoft Script
Debugge
2004/06/29 12:22a <DIR> MI6841~1 Microsoft SQL Server
2004/04/24 11:03a <DIR> NETMEE~1 NetMeeting
2004/10/05 02:34p <DIR> Oracle
2004/11/06 11:33a <DIR> OUTLOO~1 Outlook Express
2004/06/29 12:22a <DIR> RESOUR~1 Resource Kit
2004/12/08 02:54p <DIR> Robocopy
2003/08/03 07:48a <DIR> WINDOW~3 Windows Media Player
2002/02/01 10:50a <DIR> WINDOW~1 Windows NT
0 File(s) 0 bytes
21 Dir(s) 13,038,665,728 bytes free
I ran the executables using the -RegServer command as you instructed and now
replication is working. Thanks alot.
The changes made by running the -RegServer command are permanent? I
wouldn't lose anything on a reboot?
When I was registering executable C:\Program Files\Microsoft SQL
Server\80\COM>qrdrsvc.exe -regserver another screen appeared:
Microsoft SQL Server Replication Queue Reader Agent 8.00.760
Copyright (c) 2000 Microsoft Corporation
Server: NPBOSSSQL4, Database distribution : ODBC Error:SQL Server does not ex
or access denied.
Unable to connect to Local Distributor
Queue Reader aborting
The process finished. Use CTRL+C to close this window.
Replication seems to be working okay now; should I be concerned about "queue
reader aborting"?
I was talking to another DBA here at our office querying about the 8.3
issue. The two servers that I was having replication trouble with were
involved in a test disaster recovery scenerio in 2004. Basically a
production server restore (using tapes) was restored onto a development
server (server I am having replication issues with). After the disaster
restores and tests the development server was restored again back to its
original development state. So it's possible that the 8.3 path changed
during these restores.
Gary.
"Raymond Mak [MSFT]" wrote:
[vbcol=seagreen]
> Hi Gary,
> You can repair the path of the replication COM servers by doing the following:
> c:\Program Files\Microsoft SQL Server\80\Com>snapshot -RegServer
> c:\Program Files\Microsoft SQL Server\80\Com>replmerg -RegServer
> c:\Program Files\Microsoft SQL Server\80\Com>distrib -RegServer
> c:\Program Files\Microsoft SQL Server\80\Com>logread -RegServer
> c:\Program Files\Microsoft SQL Server\80\Com>qrdrsvc -RegServer
> It seems kind of strange that the 8.3 path (btw, you can do a dir /x to find
> out what the current 8.3 path is) has changed since you first installed SQL
> Server. It would be great if you can let us know if you can recall anything
> unusual that happened recently on your machine that would have caused such a
> change. (accidental renaming of Program Files, Microsoft SQL Server in
> explorer ?)
> -Raymond
> "Gary Murphy" wrote:
|||Hi Gary,
The output from qrdrsvc.exe doesn't look right to me although you shouldn't
be affected if you don't have any transactional queued updating subscribers.
The 8.3 filename for "Microsoft SQL Server" does look kind of strange and you
may want to run chkdsk to see if everything is in order. Have you tried
installing SQL2005 on the machine recently? That might sort of explain it but
I am not exactly sure how.
-Raymond
"Gary Murphy" wrote:
[vbcol=seagreen]
> Hi Raymond,
> I did the dir /x on the servers where I am having the problem. Here is the
> result:
> As you will see MS SQL Server has a 8.3 path called MI6841~1. Not sure how
> it got this name.
> I checked 5 other sql servers that we have and the 8.3 path is either
> micros~3 or micros~3. I assume these are okay.
> 2002/01/31 08:08a <DIR> ACCESS~1 Accessories
> 2004/10/08 04:01p <DIR> COMMON~1 Common Files
> 2004/06/29 12:21a <DIR> Compaq
> 2002/01/31 11:40a <DIR> COMPLU~1 ComPlus Applications
> 2004/07/12 02:00p <DIR> COMPUT~1 ComputerAssociates
> 2004/06/29 12:21a <DIR> DATADI~1 DataDirect
> 2004/11/06 09:14a <DIR> INTERN~1 Internet Explorer
> 2004/06/29 12:22a <DIR> MICROS~3 Microsoft Analysis
> Servi
> es
> 2002/01/31 08:08a <DIR> MICROS~2 microsoft frontpage
> 2004/06/29 12:22a <DIR> MICROS~4 Microsoft Operations
> Man
> ger 2000
> 2002/01/31 08:09a <DIR> MICROS~1 Microsoft Script
> Debugge
> 2004/06/29 12:22a <DIR> MI6841~1 Microsoft SQL Server
> 2004/04/24 11:03a <DIR> NETMEE~1 NetMeeting
> 2004/10/05 02:34p <DIR> Oracle
> 2004/11/06 11:33a <DIR> OUTLOO~1 Outlook Express
> 2004/06/29 12:22a <DIR> RESOUR~1 Resource Kit
> 2004/12/08 02:54p <DIR> Robocopy
> 2003/08/03 07:48a <DIR> WINDOW~3 Windows Media Player
> 2002/02/01 10:50a <DIR> WINDOW~1 Windows NT
> 0 File(s) 0 bytes
> 21 Dir(s) 13,038,665,728 bytes free
> I ran the executables using the -RegServer command as you instructed and now
> replication is working. Thanks alot.
> The changes made by running the -RegServer command are permanent? I
> wouldn't lose anything on a reboot?
> When I was registering executable C:\Program Files\Microsoft SQL
> Server\80\COM>qrdrsvc.exe -regserver another screen appeared:
> Microsoft SQL Server Replication Queue Reader Agent 8.00.760
> Copyright (c) 2000 Microsoft Corporation
> Server: NPBOSSSQL4, Database distribution : ODBC Error:SQL Server does not ex
> or access denied.
> Unable to connect to Local Distributor
> Queue Reader aborting
> The process finished. Use CTRL+C to close this window.
> Replication seems to be working okay now; should I be concerned about "queue
> reader aborting"?
> I was talking to another DBA here at our office querying about the 8.3
> issue. The two servers that I was having replication trouble with were
> involved in a test disaster recovery scenerio in 2004. Basically a
> production server restore (using tapes) was restored onto a development
> server (server I am having replication issues with). After the disaster
> restores and tests the development server was restored again back to its
> original development state. So it's possible that the 8.3 path changed
> during these restores.
> Gary.
> "Raymond Mak [MSFT]" wrote:

Replication does detect Mirrored Source Fail Over

I'm trying setup a proof of concept for a client but I’m having issues with mirroring and replication.

With the help of http://technet.microsoft.com/en-us/library/ms151799.aspx I’ve done the following..

The setup is as follows, I have several instances of SQL Server

A+B are mirrored with each other, with A being the principle and B the mirror

C is the distributor

E is subscribes to A, with parameters for PublicationFailoverPartner set to B

The mirroring between A+B works fine, I can manually fail each and the databases keep in step.

Without testing the mirroring failover, the replication between A+C+E also works.

However when I test the mirror to failover between A+B no transactions are replicated though to E. The publication moves from A to B in the Server Management Studio.

The logs state that the log reader agent can not gain access to A, however nothing is recorded regarding any attempts to contact B. In the replication monitor the error message

"The concurrent snapshot for publication ABCXYZ is not available because it has not been fully generated of the Log Reader Agent is not running to activate it. If generation of the concurrent snapshot was interrupted, the Spapshot Agent for the publica..." (cut off).

"the process could not execute 'sp_replcmds' on 'A'

I have checked that the SQL Server Agents are running on all agents,

I have checked that that server B is set at the PublisherFailoverPartner on server C agent configuration, I'm now at a lost as to what is wrong,

Any help or suggestions are greatly appreciated.

Pls do not duplicate

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1958649&SiteID=1

|||

Sorry about this Deepak, I had duplicated this as I though I had lost my original post, it was just in anothor forum,

appologies for being a Topic Hog

Replication Disrupting Other Access

We have setup merge replication on a production server/database that
is also used for our web applications. We need the replication for
disconnected computing using an MSDE database. The replication works
exceptionally well, however, we had to publish ID ranges on the tables
so that data could be merged with the server correctly. This has
caused a problem with our web based applications. Once the end of the
ID range is reached, our other applications cannot insert data into
the tables without resetting the ranges or removing replication.
Has anyone else seen this problem? If so, is there a good work-around
to allow both entities to co-exist using the same database? We would
like to avoid adding a significant amount of code/scripts to manage
this automatically. Would we be better off to use a snapshot method
of replication and insert data directly from that?
Thanks for any suggestions you may have.
Dan Broomall
Dan,
there are 2 ways I can think of:
you can use large ranges - so large in fact that no new ranges are required,
or you can select to manually manage the ranges and select a simple
algorithm that ensures there is never any overlap between publisher and
subscriber(s). EG if you have a publisher and a single subscriber, the
publisher could have a seed of 1 and increment of 2 while the subscriber has
a seed of 2 and increment of 2 - the publisher has odd identity values and
the subscriber evens.
HTH,
Paul Ibison

Replication complete event on publisher

I would like to setup transactional replication so that when the publisher
finishes sending data out, a .NET 2.0 app is run. Is there an event I can
grab onto, or would I have to set a trigger up on a system table?
Add it to the final job step of your merge or distribution agent.
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
"Rono" <Rono@.discussions.microsoft.com> wrote in message
news:E31B4A0E-4F1A-420C-AADC-AC39EB76C738@.microsoft.com...
>I would like to setup transactional replication so that when the publisher
> finishes sending data out, a .NET 2.0 app is run. Is there an event I can
> grab onto, or would I have to set a trigger up on a system table?
|||In your distribution agent job there are 3 steps. The second one - "Run
agent" does the real work. In the Advanced tab there is workflow defined so
that when this step completes, the job quits, while if it fails, the job
goes to the next step. So, you'll need another step to be added to call your
app, and ensure that the workflow is such that the step 4 is arrived at on
success of step 2.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

Replication Chain Problem

Is it possible to setup a merge replication chain where you have a Head
Office (HO) which is a publisher to a Region Office (RO) subscriber which is
a publisher to a Store Office (SO) subscriber where the data travels both
directions fully? eg. HO<->RO<->SO.
From testing, it appears that if data is changed at the SO, then it only
gets merged to the RO, not the HO as well.
Do anyone know what needs to be done to get it also merged to the HO as well?
this should work. As long as all the downstream subscribers have a lower
priority than the upstream publisher/subscriber the data should move as you
desire. You might want to check to make sure that the missing data isn't
logged in the conflict tables.
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
"Cheval" <Cheval@.discussions.microsoft.com> wrote in message
news:8D8A9DE5-B207-4CF2-997C-5BD65A3EDD01@.microsoft.com...
> Is it possible to setup a merge replication chain where you have a Head
> Office (HO) which is a publisher to a Region Office (RO) subscriber which
> is
> a publisher to a Store Office (SO) subscriber where the data travels both
> directions fully? eg. HO<->RO<->SO.
> From testing, it appears that if data is changed at the SO, then it only
> gets merged to the RO, not the HO as well.
> Do anyone know what needs to be done to get it also merged to the HO as
> well?
|||No issues. I've built these as deep as 16 levels with data flowing in both
directions.
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.
"Cheval" <Cheval@.discussions.microsoft.com> wrote in message
news:8D8A9DE5-B207-4CF2-997C-5BD65A3EDD01@.microsoft.com...
> Is it possible to setup a merge replication chain where you have a Head
> Office (HO) which is a publisher to a Region Office (RO) subscriber which
> is
> a publisher to a Store Office (SO) subscriber where the data travels both
> directions fully? eg. HO<->RO<->SO.
> From testing, it appears that if data is changed at the SO, then it only
> gets merged to the RO, not the HO as well.
> Do anyone know what needs to be done to get it also merged to the HO as
> well?

Replication between SQL2000 and SQL2005

I have a distributor setup on SQL Server 2005 (9.0.3042) and am trying to create a publication on SQL Server 2000 (8.0.2040) which receives the following error in my production environment:

Msg 8526, Level 16, State 2, Procedure sp_addpublication, Line 802

Cannot go remote while the session is enlisted in a distributed transaction that has an active savepoint.

The interesting part of this equation is that I was able to get this to work without error in my DEV (development) environment and well as my QAT (test) environment. This end result was that my distributor was SQL 2005, my publisher was SQL 2000 and my pull subscriber was SQL 2005. I have been diligently comparing our production environment to my other environment and have yet to find differences.

Has anyone else seen an error similiar to this? Any insight would be appreciated.

Thanks in advance,

Max

http://support.microsoft.com/kb/295027

HTH

Vishal

|||I'm having the same problem, and it's persisting even after setting the 8599 trace on. Were you able to get yours to work? If so, how?
sql

Replication between SQL server and SQL express ??

Dear all,
I try to setup a replication between a database TEST on a server myServer
into an SQL express database myDB on a Vista office PC machine.
For that I define my SQL server to be a publisher of my database TEST and
then on my Client PC under sqL express I define a new subscription by
selection my SQL server as the publisher. Setup goes fine until it try the
firts initialisation with the only mesage initialisation failed..
What do I have to verify ?
If on my SQL server dtabase I want to publish table EVENT, does that table
need to be already created in my SQL express before initialisation or it will
created automaticaly ?
Which permission type should be use from both side... ? for time beeing I
was using 'sa'
thnaks for help
rergards
serge
Replication will create the table for you. There is no need for you to
pre-create it. Can you enable logging so we can see where replication is
failing.
Use this link to enable it.
http://support.microsoft.com/kb/312292
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
"calderara" <calderara@.discussions.microsoft.com> wrote in message
news:AEDF7E8F-8D58-488E-A3B0-DDCD38575CCF@.microsoft.com...
> Dear all,
> I try to setup a replication between a database TEST on a server myServer
> into an SQL express database myDB on a Vista office PC machine.
> For that I define my SQL server to be a publisher of my database TEST and
> then on my Client PC under sqL express I define a new subscription by
> selection my SQL server as the publisher. Setup goes fine until it try the
> firts initialisation with the only mesage initialisation failed..
> What do I have to verify ?
> If on my SQL server dtabase I want to publish table EVENT, does that table
> need to be already created in my SQL express before initialisation or it
> will
> created automaticaly ?
> Which permission type should be use from both side... ? for time beeing I
> was using 'sa'
> thnaks for help
> rergards
> serge
|||OK I will try to setup thge login...
Just for you to know that I have use the snaphot method for replication and
when I use the replication monitor and press th re iintialize menu...it goes
from status running to status fail retry initializing after a while and of
course my table is not created on my client machine.
Any rigths to verify on my client machine under EXPRES 2005 for the
receiving database ?
regards
"Hilary Cotter" wrote:

> Replication will create the table for you. There is no need for you to
> pre-create it. Can you enable logging so we can see where replication is
> failing.
> Use this link to enable it.
> http://support.microsoft.com/kb/312292
> --
> 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
>
> "calderara" <calderara@.discussions.microsoft.com> wrote in message
> news:AEDF7E8F-8D58-488E-A3B0-DDCD38575CCF@.microsoft.com...
>
>
|||I have generated the log file.
I can paste the whol content here ?
What I have noticed if I read properly is that the sanphot seems to work ok
as when starting the agent I get status complete succesfully.I think the
problem come from the time it needs to copy the snapshot to the Client SQL
express 2005 database...
:-(
"Hilary Cotter" wrote:

> Replication will create the table for you. There is no need for you to
> pre-create it. Can you enable logging so we can see where replication is
> failing.
> Use this link to enable it.
> http://support.microsoft.com/kb/312292
> --
> 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
>
> "calderara" <calderara@.discussions.microsoft.com> wrote in message
> news:AEDF7E8F-8D58-488E-A3B0-DDCD38575CCF@.microsoft.com...
>
>
|||Yes, please post the whole thing here. It sounds like you might have done
this for the snapshot agent. You may need to do this for the
merge/distribution agent as well.
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
"calderara" <calderara@.discussions.microsoft.com> wrote in message
news:3243F73C-43DF-458A-837D-615F57DF16D4@.microsoft.com...[vbcol=seagreen]
>I have generated the log file.
> I can paste the whol content here ?
> What I have noticed if I read properly is that the sanphot seems to work
> ok
> as when starting the agent I get status complete succesfully.I think the
> problem come from the time it needs to copy the snapshot to the Client SQL
> express 2005 database...
> :-(
>
> "Hilary Cotter" wrote:
|||Thanks for your prompt reply..
Where can I find the merge/replication agent ? in my list where I have doen
previous steps I have seen only the snapshot agent ?
regards
serge
"Hilary Cotter" wrote:

> Yes, please post the whole thing here. It sounds like you might have done
> this for the snapshot agent. You may need to do this for the
> merge/distribution agent as well.
> --
> 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
>
> "calderara" <calderara@.discussions.microsoft.com> wrote in message
> news:3243F73C-43DF-458A-837D-615F57DF16D4@.microsoft.com...
>
>
|||Hi hilary,
Here is below the file output requested for the type : "Replication
snapshot" part 1
================================================
2007-03-21 14:42:57.75
2007-03-21 14:42:57.75 Microsoft (R) SQL Server Snapshot Agent
2007-03-21 14:42:57.75 [Assembly Version = 9.0.242.0, File Version =
9.00.1399.00]
2007-03-21 14:42:57.75 Copyright (C) 1988-2005 Microsoft Corporation. All
rights reserved.
2007-03-21 14:42:57.75 The timestamps prepended to the output lines are
expressed in terms of UTC time.
2007-03-21 14:42:57.75 User-specified agent parameter values:
2007-03-21 14:42:57.75 ---
2007-03-21 14:42:57.75 -Publisher NOMOS-SRVR
2007-03-21 14:42:57.75 -PublisherDB TEST
2007-03-21 14:42:57.75 -Publication TestPublication
2007-03-21 14:42:57.75 -Distributor NOMOS-SRVR
2007-03-21 14:42:57.75 -DistributorSecurityMode 1
2007-03-21 14:42:57.75 -Output d:\output.txt
2007-03-21 14:42:57.75 -OutputVerboseLevel 2
2007-03-21 14:42:57.75 -XJOBID 0x88F5D8DDCAC5174B953F14E7691E823B
2007-03-21 14:42:57.75 ---
2007-03-21 14:42:57.75 Connecting to Distributor 'NOMOS-SRVR'
2007-03-21 14:42:57.96
2007-03-21 14:42:57.96 SQL Command dump
2007-03-21 14:42:57.96 ================
2007-03-21 14:42:57.96 Server: NOMOS-SRVR
2007-03-21 14:42:57.96 Database: master
2007-03-21 14:42:57.96 Command Text: sp_helpdistpublisher
2007-03-21 14:42:57.96 Parameters:
2007-03-21 14:42:57.96 @.publisher = NOMOS-SRVR
2007-03-21 14:42:57.96
2007-03-21 14:42:57.96 SQL Command dump
2007-03-21 14:42:57.96 ================
2007-03-21 14:42:57.96 Server: NOMOS-SRVR
2007-03-21 14:42:57.96 Database: distribution
2007-03-21 14:42:57.96 Command Text: select 'id' = convert(int, srvid) from
master..sysservers where upper(srvname) = upper(N'NOMOS-SRVR')
2007-03-21 14:42:57.96 Parameters:
2007-03-21 14:42:57.96
2007-03-21 14:42:57.96 SQL Command dump
2007-03-21 14:42:57.96 ================
2007-03-21 14:42:57.96 Server: NOMOS-SRVR
2007-03-21 14:42:57.96 Database: distribution
2007-03-21 14:42:57.96 Command Text: sp_MShelp_snapshot_agentid
2007-03-21 14:42:57.96 Parameters:
2007-03-21 14:42:57.96 @.publisher_id = 0
2007-03-21 14:42:57.96 @.publisher_db = TEST
2007-03-21 14:42:57.96 @.publication = TestPublication
2007-03-21 14:42:57.96 @.job_id = System.Byte[]
2007-03-21 14:42:57.96
2007-03-21 14:42:57.96 SQL Command dump
2007-03-21 14:42:57.96 ================
2007-03-21 14:42:57.96 Server: NOMOS-SRVR
2007-03-21 14:42:57.96 Database: distribution
2007-03-21 14:42:57.96 Command Text: sp_MShelp_snapshot_agent
2007-03-21 14:42:57.96 Parameters:
2007-03-21 14:42:57.96 @.agent_id = 1
2007-03-21 14:42:57.98
2007-03-21 14:42:57.98 SQL Command dump
2007-03-21 14:42:57.98 ================
2007-03-21 14:42:57.98 Server: NOMOS-SRVR
2007-03-21 14:42:57.98 Database: distribution
2007-03-21 14:42:57.98 Command Text: sp_MShelp_profile
2007-03-21 14:42:57.98 Parameters:
2007-03-21 14:42:57.98 @.agent_id = 1
2007-03-21 14:42:57.98 @.agent_type = 1
2007-03-21 14:42:57.98 @.profile_name =
2007-03-21 14:42:57.98 Parameter values obtained from agent profile:
2007-03-21 14:42:57.98 ---
2007-03-21 14:42:57.98 -BcpBatchSize 100000
2007-03-21 14:42:57.98 -HistoryVerboseLevel 2
2007-03-21 14:42:57.98 -LoginTimeout 15
2007-03-21 14:42:57.98 -QueryTimeout 1800
2007-03-21 14:42:57.98 ---
2007-03-21 14:42:58.00 Connecting to Publisher 'NOMOS-SRVR'
2007-03-21 14:42:58.03
2007-03-21 14:42:58.03 SQL Command dump
2007-03-21 14:42:58.03 ================
2007-03-21 14:42:58.03 Server: NOMOS-SRVR
2007-03-21 14:42:58.03 Database: TEST
2007-03-21 14:42:58.03 Command Text: use master
2007-03-21 14:42:58.03 select isnull(convert(int, value_in_use), 0) from
master.sys.configurations where lower(name) = 'smo and dmo xps'
2007-03-21 14:42:58.03 use [TEST]
2007-03-21 14:42:58.03 Parameters:
2007-03-21 14:42:58.04
2007-03-21 14:42:58.04 SQL Command dump
2007-03-21 14:42:58.04 ================
2007-03-21 14:42:58.04 Server: NOMOS-SRVR
2007-03-21 14:42:58.04 Database: TEST
2007-03-21 14:42:58.04 Command Text: use [TEST]
2007-03-21 14:42:58.04 select publishingservername(), convert(int,
compatibility_level) from sys.databases where name = @.database_name
2007-03-21 14:42:58.04 Parameters:
2007-03-21 14:42:58.04 @.database_name = TEST
2007-03-21 14:42:58.04 Publisher database compatibility level is set to 80.
2007-03-21 14:42:58.04
2007-03-21 14:42:58.04 SQL Command dump
2007-03-21 14:42:58.04 ================
2007-03-21 14:42:58.04 Server: NOMOS-SRVR
2007-03-21 14:42:58.04 Database: TEST
2007-03-21 14:42:58.04 Command Text: select convert(int,
isnull(is_member('db_owner'),0))
2007-03-21 14:42:58.04 Parameters:
2007-03-21 14:42:58.04
2007-03-21 14:42:58.04 SQL Command dump
2007-03-21 14:42:58.04 ================
2007-03-21 14:42:58.04 Server: NOMOS-SRVR
2007-03-21 14:42:58.04 Database: TEST
2007-03-21 14:42:58.04 Command Text:
2007-03-21 14:42:58.04 declare @.retcode int
2007-03-21 14:42:58.04 exec @.retcode = sys.sp_getapplock @.Resource =
N'NOMOS-SRVR-TEST-TestPublication-1',
2007-03-21 14:42:58.04 @.LockMode =
N'Exclusive',
2007-03-21 14:42:58.04 @.LockOwner =
N'Session',
2007-03-21 14:42:58.04 @.LockTimeout = 0,
2007-03-21 14:42:58.04 @.DbPrincipal =
N'db_owner'
2007-03-21 14:42:58.04 if @.retcode < 0 raiserror(21036, 16, -1, 'snapshot')
2007-03-21 14:42:58.04 Parameters:
2007-03-21 14:42:58.04 Retrieving publication and article information from
the publisher database 'NOMOS-SRVR.TEST'
2007-03-21 14:42:58.04
2007-03-21 14:42:58.04 SQL Command dump
2007-03-21 14:42:58.04 ================
2007-03-21 14:42:58.04 Server: NOMOS-SRVR
2007-03-21 14:42:58.04 Database: TEST
2007-03-21 14:42:58.04 Command Text: sp_helppublication
2007-03-21 14:42:58.04 Parameters:
2007-03-21 14:42:58.04 @.publication = TestPublication
2007-03-21 14:42:58.04
2007-03-21 14:42:58.04 SQL Command dump
2007-03-21 14:42:58.04 ================
2007-03-21 14:42:58.04 Server: NOMOS-SRVR
2007-03-21 14:42:58.04 Database: TEST
2007-03-21 14:42:58.04 Command Text: if
object_id('sys.sp_checkinvalidivarticle') < 0 exec sp_checkinvalidivarticle
@.mode, @.publication
2007-03-21 14:42:58.04 Parameters:
2007-03-21 14:42:58.04 @.mode = 1
2007-03-21 14:42:58.04 @.publication = TestPublication
2007-03-21 14:42:58.04
2007-03-21 14:42:58.04 SQL Command dump
2007-03-21 14:42:58.04 ================
2007-03-21 14:42:58.04 Server: NOMOS-SRVR
2007-03-21 14:42:58.04 Database: TEST
2007-03-21 14:42:58.04 Command Text: declare @.ftp_password nvarchar(524)
select @.ftp_password = ftp_password from dbo.syspublications where name =
N'TestPublication' if object_id('sys.fn_repldecryptver4', 'FN') is not null
begin select sys.fn_repldecryptver4(@.ftp_password) end else begin select
@.ftp_password end
2007-03-21 14:42:58.04 Parameters:
2007-03-21 14:42:58.04
2007-03-21 14:42:58.04 SQL Command dump
2007-03-21 14:42:58.04 ================
2007-03-21 14:42:58.04 Server: NOMOS-SRVR
2007-03-21 14:42:58.04 Database: TEST
2007-03-21 14:42:58.04 Command Text: SET TRANSACTION ISOLATION LEVEL READ
COMMITTED;BEGIN TRANSACTION
2007-03-21 14:42:58.04 Parameters:
2007-03-21 14:42:58.04
2007-03-21 14:42:58.04 SQL Command dump
2007-03-21 14:42:58.04 ================
2007-03-21 14:42:58.04 Server: NOMOS-SRVR
2007-03-21 14:42:58.04 Database: TEST
2007-03-21 14:42:58.04 Command Text: sp_MSestimatesnapshotworkload
2007-03-21 14:42:58.04 Parameters:
2007-03-21 14:42:58.04 @.publication = TestPublication
2007-03-21 14:42:58.06
2007-03-21 14:42:58.06 SQL Command dump
2007-03-21 14:42:58.06 ================
2007-03-21 14:42:58.06 Server: NOMOS-SRVR
2007-03-21 14:42:58.06 Database: TEST
2007-03-21 14:42:58.06 Command Text: COMMIT TRANSACTION
2007-03-21 14:42:58.06 Parameters:
2007-03-21 14:42:58.06
2007-03-21 14:42:58.06 SQL Command dump
2007-03-21 14:42:58.06 ================
2007-03-21 14:42:58.06 Server: NOMOS-SRVR
2007-03-21 14:42:58.06 Database: TEST
2007-03-21 14:42:58.06 Command Text: SET TRANSACTION ISOLATION LEVEL READ
COMMITTED;BEGIN TRANSACTION
2007-03-21 14:42:58.06 Parameters:
2007-03-21 14:42:58.06
2007-03-21 14:42:58.06 SQL Command dump
2007-03-21 14:42:58.06 ================
2007-03-21 14:42:58.06 Server: NOMOS-SRVR
2007-03-21 14:42:58.06 Database: TEST
2007-03-21 14:42:58.06 Command Text: exec sys.sp_getapplock @.Resource =
@.publication, @.LockMode = N'Shared', @.LockOwner = N'Session', @.DbPrincipal =
N'db_owner'
2007-03-21 14:42:58.06 select 'article id' = art.artid,
2007-03-21 14:42:58.06 'article name' = art.name,
2007-03-21 14:42:58.06 'base object' = null,
2007-03-21 14:42:58.06 'destination_object' =
art.dest_table,
2007-03-21 14:42:58.06 'synchronization object' =
object_name(art.sync_objid),
2007-03-21 14:42:58.06 'type' = case when
objectproperty(art.objid, 'IsSchemaBound') = 1 and art.type <> 0x80 then
0x0100 | convert(smallint, art.type) else art.type end,
2007-03-21 14:42:58.06 'status' = art.status,
2007-03-21 14:42:58.06 'filter' = null,
2007-03-21 14:42:58.06 'description' = null,
2007-03-21 14:42:58.06 'insert_command' = art.ins_cmd,
2007-03-21 14:42:58.06 'update_command' = art.upd_cmd,
2007-03-21 14:42:58.06 'delete_command' = art.del_cmd,
2007-03-21 14:42:58.06 'creation script path' =
art.creation_script,
2007-03-21 14:42:58.06 'vertical partition' =
convert(bit, case when (art.type & 1) <> 1 or
2007-03-21 14:42:58.06
not exists (select *
2007-03-21 14:42:58.06
from sys.columns cols
2007-03-21 14:42:58.06
where cols.object_id = art.objid
2007-03-21 14:42:58.06
and not ((art.status & 32)=32 and
cols.system_type_id = 189)
2007-03-21 14:42:58.06
and cols.column_id not in (select artcols.colid
2007-03-21 14:42:58.06
from
dbo.sysarticlecolumns artcols
2007-03-21 14:42:58.06
where artcols.artid =
art.artid)) then 0
2007-03-21 14:42:58.06 else 1 end),
2007-03-21 14:42:58.06 'pre_creation_cmd' =
art.pre_creation_cmd,
2007-03-21 14:42:58.06 'filter_clause' =
art.filter_clause,
2007-03-21 14:42:58.06 'schema_option' =
art.schema_option,
2007-03-21 14:42:58.06 'dest_owner' =
art.dest_owner,
2007-03-21 14:42:58.06 'source_owner' =
schema_name(convert(int, objectpropertyex(art.objid, 'SchemaId'))),
2007-03-21 14:42:58.06 'unqua_source_object' =
object_name(art.objid),
2007-03-21 14:42:58.06 'sync_object_owner' =
schema_name(convert(int, objectpropertyex(art.sync_objid, 'SchemaId'))),
2007-03-21 14:42:58.06 'unqualified_sync_object' =
object_name(art.sync_objid),
2007-03-21 14:42:58.06 'filter_owner' = null,
2007-03-21 14:42:58.06 'unqua_filter' = null,
2007-03-21 14:42:58.06 'auto_identity_range' = null,
2007-03-21 14:42:58.06 'publisher_identity_range' = null,
2007-03-21 14:42:58.06 'identity_range' = null,
2007-03-21 14:42:58.06 'threshold' = null,
2007-03-21 14:42:58.06 'identityrangemanagementoption' = null,
2007-03-21 14:42:58.06 'fire_triggers_on_snapshot' =
convert(bit, art.fire_triggers_on_snapshot)
2007-03-21 14:42:58.06 from dbo.sysextendedarticlesview art
2007-03-21 14:42:58.06 inner join dbo.syspublications pub
2007-03-21 14:42:58.06 on art.pubid = pub.pubid
2007-03-21 14:42:58.06 where pub.name = @.publication
2007-03-21 14:42:58.06 Parameters:
2007-03-21 14:42:58.06 @.publication = TestPublication
2007-03-21 14:42:58.06
2007-03-21 14:42:58.06 SQL Command dump
2007-03-21 14:42:58.06 ================
2007-03-21 14:42:58.06 Server: NOMOS-SRVR
2007-03-21 14:42:58.06 Database: TEST
2007-03-21 14:42:58.06 Command Text: COMMIT TRANSACTION
2007-03-21 14:42:58.06 Parameters:
2007-03-21 14:42:58.07
2007-03-21 14:42:58.07 SQL Command dump
2007-03-21 14:42:58.07 ================
2007-03-21 14:42:58.07 Server: NOMOS-SRVR
2007-03-21 14:42:58.07 Database: TEST
2007-03-21 14:42:58.07 Command Text: sys.sp_MSget_load_hint
2007-03-21 14:42:58.07 Parameters:
2007-03-21 14:42:58.07 @.qualified_source_object_name = [dbo].[STATE]
2007-03-21 14:42:58.07 @.qualified_sync_object_name =
[dbo].[syncobj_0x3737313837413543]
2007-03-21 14:42:58.07 @.primary_key_only = False
2007-03-21 14:42:58.07 @.is_vertically_partitioned = False
2007-03-21 14:42:58.07
2007-03-21 14:42:58.07 SQL Command dump
2007-03-21 14:42:58.07 ================
2007-03-21 14:42:58.07 Server: NOMOS-SRVR
2007-03-21 14:42:58.07 Database: TEST
2007-03-21 14:42:58.07 Command Text:
2007-03-21 14:42:58.07 set nocount on
2007-03-21 14:42:58.07 declare @.source_object_id int
2007-03-21 14:42:58.07 declare @.sync_object_id int
2007-03-21 14:42:58.07
2007-03-21 14:42:58.07 set @.source_object_id =
object_id(quotename(@.source_object_schema) + N'.' +
quotename(@.source_object_name))
2007-03-21 14:42:58.07 set @.sync_object_id =
object_id(quotename(@.sync_object_schema) + N'.' +
quotename(@.sync_object_name))
2007-03-21 14:42:58.07
2007-03-21 14:42:58.07 declare @.partitioning_column sysname
2007-03-21 14:42:58.07 declare @.partitioning_column_type sysname
2007-03-21 14:42:58.07 declare @.qualified_source_object_name nvarchar(600)
2007-03-21 14:42:58.07 declare @.partitioning_column_collation sysname
2007-03-21 14:42:58.07 declare @.partitioning_index_name sysname
2007-03-21 14:42:58.07
2007-03-21 14:42:58.07 set @.qualified_source_object_name =
quotename(@.source_object_schema) + N'.' + quotename(@.source_object_name)
2007-03-21 14:42:58.07 set @.partitioning_column = null
2007-03-21 14:42:58.07 set @.partitioning_column_type = null
2007-03-21 14:42:58.07 set @.partitioning_index_name = null
2007-03-21 14:42:58.07
2007-03-21 14:42:58.07 select @.partitioning_column = sc.name,
2007-03-21 14:42:58.07 @.partitioning_column_type = st.name,
2007-03-21 14:42:58.07 @.partitioning_column_collation =
sc.collation,
2007-03-21 14:42:58.07 @.partitioning_index_name = si.name
2007-03-21 14:42:58.07 from sysindexes si
2007-03-21 14:42:58.07 inner join syscolumns sc
2007-03-21 14:42:58.07 on index_col(@.qualified_source_object_name,
si.indid, 1) = sc.name
2007-03-21 14:42:58.07 inner join systypes st
2007-03-21 14:42:58.07 on sc.xtype = st.xusertype
2007-03-21 14:42:58.07 where si.id = @.source_object_id
2007-03-21 14:42:58.07 and sc.id = @.sync_object_id
2007-03-21 14:42:58.07 and si.indid = 1
2007-03-21 14:42:58.07 and st.name in (N'uniqueidentifier', N'bit',
N'tinyint', N'smallint', N'int', N'smalldatetime', N'real', N'money',
N'datetime', N'float', N'bit', N'decimal', N'numeric', N'smallmoney',
N'bigint', N'varbinary', N'varchar', N'binary', N'char', N'timestamp',
N'nvarchar', N'nchar')
2007-03-21 14:42:58.07 and (@.use_primary_key_only = 0 or si.status &
2048 = 2048)
2007-03-21 14:42:58.07
2007-03-21 14:42:58.07 if @.partitioning_column is not null
2007-03-21 14:42:58.07 begin
2007-03-21 14:42:58.07 select @.partitioning_index_name,
@.partitioning_column, @.partitioning_column_type,
@.partitioning_column_collation
2007-03-21 14:42:58.07 dbcc
show_statistics(@.qualified_source_object_name, @.partitioning_index_name)
2007-03-21 14:42:58.07 end
2007-03-21 14:42:58.07 Parameters:
2007-03-21 14:42:58.07 @.source_object_name = STATE
2007-03-21 14:42:58.07 @.source_object_schema = dbo
2007-03-21 14:42:58.07 @.sync_object_name = syncobj_0x3737313837413543
2007-03-21 14:42:58.07 @.sync_object_schema = dbo
2007-03-21 14:42:58.07 @.use_primary_key_only = 0
2007-03-21 14:42:58.09
2007-03-21 14:42:58.09 SQL Command dump
2007-03-21 14:42:58.09 ================
2007-03-21 14:42:58.09 Server: NOMOS-SRVR
2007-03-21 14:42:58.09 Database: TEST
2007-03-21 14:42:58.09 Command Text: SET TRANSACTION ISOLATION LEVEL READ
COMMITTED;BEGIN TRANSACTION
2007-03-21 14:42:58.09 Parameters:
2007-03-21 14:42:58.09
2007-03-21 14:42:58.09 SQL Command dump
2007-03-21 14:42:58.09 ================
2007-03-21 14:42:58.09 Server: NOMOS-SRVR
2007-03-21 14:42:58.09 Database: TEST
2007-03-21 14:42:58.09 Command Text: update dbo.syssubscriptions with
(ROWLOCK READPAST) set status = status where artid in (select artid from
dbo.sysarticles arts inner join dbo.syspublications pubs on arts.pubid =
pubs.pubid where pubs.name = @.publication)
2007-03-21 14:42:58.09 Parameters:
2007-03-21 14:42:58.09 @.publication = TestPublication
2007-03-21 14:42:58.09 [0%] Locking published tables while generating the
snapshot
2007-03-21 14:42:58.09
2007-03-21 14:42:58.09 SQL Command dump
2007-03-21 14:42:58.09 ================
2007-03-21 14:42:58.09 Server: NOMOS-SRVR
2007-03-21 14:42:58.09 Database: TEST
2007-03-21 14:42:58.09 Command Text: SELECT * FROM [dbo].[STATE] WITH
(TABLOCK HOLDLOCK) WHERE 1 = 2
2007-03-21 14:42:58.09 Parameters:
2007-03-21 14:42:58.15 [0%] Bulk copying snapshot data for article 'STATE'
2007-03-21 14:42:58.18 [0%] Bulk copied snapshot data for article 'STATE' (4
rows).
2007-03-21 14:42:58.73
2007-03-21 14:42:58.73 SQL Command dump
2007-03-21 14:42:58.73 ================
2007-03-21 14:42:58.73 Server: NOMOS-SRVR
2007-03-21 14:42:58.73 Database: TEST
2007-03-21 14:42:58.73 Command Text: select count_big(*) from sys.tables
2007-03-21 14:42:58.73 Parameters:
2007-03-21 14:42:58.75 [7%] Pre-loading meta-data of all tables in the
publisher database for scripting
2007-03-21 14:42:59.64 [7%] Sorting article objects in the proper creation
order
2007-03-21 14:42:59.70
2007-03-21 14:42:59.70 SQL Command dump
2007-03-21 14:42:59.70 ================
2007-03-21 14:42:59.70 Server: NOMOS-SRVR
2007-03-21 14:42:59.70 Database: TEST
2007-03-21 14:42:59.70 Command Text:
2007-03-21 14:42:59.70 select distinct
2007-03-21 14:42:59.70 'name' = so.name,
2007-03-21 14:42:59.70 'schema' = schema_name(so.schema_id),
2007-03-21 14:42:59.70 'type' = rtrim(so.type)
2007-03-21 14:42:59.70 from sys.objects so
2007-03-21 14:42:59.70 inner join sys.sql_dependencies sd
2007-03-21 14:42:59.70 on so.object_id = sd.referenced_major_id
2007-03-21 14:42:59.70 where sd.object_id = object_id(@.qualified_name)
2007-03-21 14:42:59.70 and sd.object_id <> sd.referenced_major_id
2007-03-21 14:42:59.70 and upper(rtrim(so.type)) in ('U', 'P', 'PC', 'V',
'FN', 'TF', 'IF', 'FS', 'FT', 'AF', 'SN')
2007-03-21 14:42:59.70
2007-03-21 14:42:59.70 Parameters:
2007-03-21 14:42:59.70 @.qualified_name = [dbo].[STATE]
2007-03-21 14:42:59.71 [7%] Customizing object for scripting based on
article 'STATE'
2007-03-21 14:42:59.71 [7%] Resolving duplicate object names among
replicated objects
2007-03-21 14:42:59.84 [7%] Analyzing foreign key references among article
objects in the publication
2007-03-21 14:42:59.84 [7%] Analyzing external references of all replicated
check and default constraints
2007-03-21 14:42:59.84 [7%] Analyzing dependencies on non-article objects
2007-03-21 14:42:59.84 [7%] Generating schema scripts for article 'STATE'
2007-03-21 14:42:59.95
2007-03-21 14:42:59.95 SQL Command dump
2007-03-21 14:42:59.95 ================
2007-03-21 14:42:59.95 Server: NOMOS-SRVR
2007-03-21 14:42:59.95 Database: TEST
2007-03-21 14:42:59.95 Command Text: sp_scriptsubconflicttable
2007-03-21 14:42:59.95 Parameters:
2007-03-21 14:42:59.95 @.publication = TestPublication
2007-03-21 14:42:59.95 @.article = STATE
2007-03-21 14:42:59.95 [61%] Processing system pre-snapshot script
2007-03-21 14:42:59.96
2007-03-21 14:42:59.96 SQL Command dump
2007-03-21 14:42:59.96 ================
2007-03-21 14:42:59.96 Server: NOMOS-SRVR
2007-03-21 14:42:59.96 Database: TEST
2007-03-21 14:42:59.96 Command Text: declare @.lsn binary(10) exec
sp_replincrementlsn @.lsn OUTPUT select @.lsn
2007-03-21 14:42:59.96 Parameters:
2007-03-21 14:42:59.96
2007-03-21 14:42:59.96 SQL Command dump
2007-03-21 14:42:59.96 ================
2007-03-21 14:42:59.96 Server: NOMOS-SRVR
2007-03-21 14:42:59.96 Database: TEST
2007-03-21 14:42:59.96 Command Text: sp_MSactivate_auto_sub
2007-03-21 14:42:59.96 Parameters:
2007-03-21 14:42:59.96 @.publication = TestPublication
2007-03-21 14:42:59.96 @.article = %
2007-03-21 14:42:59.96 @.status = active
2007-03-21 14:42:59.96 @.skipobjectactivation = 1
2007-03-21 14:42:59.98
2007-03-21 14:42:59.98 SQL Command dump
2007-03-21 14:42:59.98 ================
2007-03-21 14:42:59.98 Server: NOMOS-SRVR
2007-03-21 14:42:59.98 Database: distribution
2007-03-21 14:42:59.98 Command Text: SET TRANSACTION ISOLATION LEVEL READ
COMMITTED;BEGIN TRANSACTION
2007-03-21 14:42:59.98 Parameters:
2007-03-21 14:42:59.98
2007-03-21 14:42:59.98 SQL Command dump
2007-03-21 14:42:59.98 ================
2007-03-21 14:42:59.98 Server: NOMOS-SRVR
2007-03-21 14:42:59.98 Database: distribution
2007-03-21 14:42:59.98 Command Text: sp_MSget_new_xact_seqno
2007-03-21 14:42:59.98 Parameters:
2007-03-21 14:42:59.98 @.publisher_id = 0
2007-03-21 14:42:59.98 @.publisher_db = TEST
2007-03-21 14:42:59.98 @.len = 14
2007-03-21 14:42:59.98 [61%] Posting snapshot commands into the distribution
database
2007-03-21 14:42:59.98
2007-03-21 14:42:59.98 SQL Command dump
2007-03-21 14:42:59.98 ================
2007-03-21 14:42:59.98 Server: NOMOS-SRVR
2007-03-21 14:42:59.98 Database: distribution
2007-03-21 14:42:59.98 Command Text: sp_MSadd_repl_command
2007-03-21 14:42:59.98 Parameters:
2007-03-21 14:42:59.98 @.publisher_id = 0
2007-03-21 14:42:59.98 @.publisher_db = TEST
2007-03-21 14:42:59.98 @.type = -2147483598
2007-03-21 14:42:59.98 @.article_id = 1
2007-03-21 14:42:59.98 @.xact_id = System.Byte[]
2007-03-21 14:42:59.98 @.xact_seqno = SqlBinary(14)
2007-03-21 14:42:59.98 @.command_id = 1
2007-03-21 14:42:59.98 @.partial_command = False
2007-03-21 14:42:59.98 @.command = System.Byte[]
2007-03-21 14:42:59.98
2007-03-21 14:42:59.98 SQL Command dump
2007-03-21 14:42:59.98 ================
2007-03-21 14:42:59.98 Server: NOMOS-SRVR
2007-03-21 14:42:59.98 Database: distribution
2007-03-21 14:42:59.98 Command Text: sp_MSadd_repl_command
2007-03-21 14:42:59.98 Parameters:
2007-03-21 14:42:59.98 @.publisher_id = 0
2007-03-21 14:42:59.98 @.publisher_db = TEST
2007-03-21 14:42:59.98 @.type = -2147483597
2007-03-21 14:42:59.98 @.article_id = 1
2007-03-21 14:42:59.98 @.xact_id = System.Byte[]
2007-03-21 14:42:59.98 @.xact_seqno = SqlBinary(14)
2007-03-21 14:42:59.98 @.command_id = 2
2007-03-21 14:42:59.98 @.partial_command = False
2007-03-21 14:42:59.98 @.command = System.Byte[]
2007-03-21 14:42:59.98
2007-03-21 14:42:59.98 SQL Command dump
2007-03-21 14:42:59.98 ================
2007-03-21 14:42:59.98 Server: NOMOS-SRVR
2007-03-21 14:42:59.98 Database: distribution
2007-03-21 14:42:59.98 Command Text: sp_MSadd_repl_command
2007-03-21 14:42:59.98 Parameters:
2007-03-21 14:42:59.98 @.publisher_id = 0
2007-03-21 14:42:59.98 @.publisher_db = TEST
2007-03-21 14:42:59.98 @.type = -2147483641
2007-03-21 14:42:59.98 @.article_id = 0
2007-03-21 14:42:59.98 @.xact_id = System.Byte[]
2007-03-21 14:42:59.98 @.xact_seqno = SqlBinary(14)
2007-03-21 14:42:59.98 @.command_id = 3
2007-03-21 14:42:59.98 @.partial_command = False
2007-03-21 14:42:59.98 @.command = System.Byte[]
2007-03-21 14:42:59.98
2007-03-21 14:42:59.98 SQL Command dump
2007-03-21 14:42:59.98 ================
2007-03-21 14:42:59.98 Server: NOMOS-SRVR
2007-03-21 14:42:59.98 Database: distribution
2007-03-21 14:42:59.98 Command Text: sp_MSadd_repl_command
2007-03-21 14:42:59.98 Parameters:
2007-03-21 14:42:59.98 @.publisher_id = 0
2007-03-21 14:42:59.98 @.publisher_db = TEST
2007-03-21 14:42:59.98 @.type = -2147483588
2007-03-21 14:42:59.98 @.article_id = 1
2007-03-21 14:42:59.98 @.xact_id = System.Byte[]
2007-03-21 14:42:59.98 @.xact_seqno = SqlBinary(14)
2007-03-21 14:42:59.98 @.command_id = 4
2007-03-21 14:42:59.98 @.partial_command = False
2007-03-21 14:42:59.98 @.command = System.Byte[]
2007-03-21 14:43:00.00
2007-03-21 14:43:00.00 SQL Command dump
2007-03-21 14:43:00.00 ================
2007-03-21 14:43:00.00 Server: NOMOS-SRVR
2007-03-21 14:43:00.00 Database: distribution
2007-03-21 14:43:00.00 Command Text: sp_MSadd_repl_command
2007-03-21 14:43:00.00 Parameters:
2007-03-21 14:43:00.00 @.publisher_id = 0
2007-03-21 14:43:00.00 @.publisher_db = TEST
2007-03-21 14:43:00.00 @.type = -2147483646
2007-03-21 14:43:00.00 @.article_id = 1
2007-03-21 14:43:00.00 @.xact_id = System.Byte[]
2007-03-21 14:43:00.00 @.xact_seqno = SqlBinary(14)
2007-03-21 14:43:00.00 @.command_id = 5
2007-03-21 14:43:00.00 @.partial_command = False
2007-03-21 14:43:00.00 @.command = System.Byte[]
2007-03-21 14:43:00.00 [61%] Inserted schema command for article 'STATE'
into the distribution database
2007-03-21 14:43:00.00
2007-03-21 14:43:00.00 SQL Command dump
2007-03-21 14:43:00.00 ================
2007-03-21 14:43:00.00 Server: NOMOS-SRVR
2007-03-21 14:43:00.00 Database: distribution
2007-03-21 14:43:00.00 Command Text: sp_MSadd_repl_command
Amything inside ?
"Hilary Cotter" wrote:

> Yes, please post the whole thing here. It sounds like you might have done
> this for the snapshot agent. You may need to do this for the
> merge/distribution agent as well.
> --
> 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
>
> "calderara" <calderara@.discussions.microsoft.com> wrote in message
> news:3243F73C-43DF-458A-837D-615F57DF16D4@.microsoft.com...
>
>
|||Here is is the next part of the file :
================================
2007-03-21 14:43:00.00 Parameters:
2007-03-21 14:43:00.00 @.publisher_id = 0
2007-03-21 14:43:00.00 @.publisher_db = TEST
2007-03-21 14:43:00.00 @.type = -2147483546
2007-03-21 14:43:00.00 @.article_id = 1
2007-03-21 14:43:00.00 @.xact_id = System.Byte[]
2007-03-21 14:43:00.00 @.xact_seqno = SqlBinary(14)
2007-03-21 14:43:00.00 @.command_id = 6
2007-03-21 14:43:00.00 @.partial_command = False
2007-03-21 14:43:00.00 @.command = System.Byte[]
2007-03-21 14:43:00.00
2007-03-21 14:43:00.00 SQL Command dump
2007-03-21 14:43:00.00 ================
2007-03-21 14:43:00.00 Server: NOMOS-SRVR
2007-03-21 14:43:00.00 Database: distribution
2007-03-21 14:43:00.00 Command Text: sp_MSadd_repl_command
2007-03-21 14:43:00.00 Parameters:
2007-03-21 14:43:00.00 @.publisher_id = 0
2007-03-21 14:43:00.00 @.publisher_db = TEST
2007-03-21 14:43:00.00 @.type = -2147483646
2007-03-21 14:43:00.00 @.article_id = 1
2007-03-21 14:43:00.00 @.xact_id = System.Byte[]
2007-03-21 14:43:00.00 @.xact_seqno = SqlBinary(14)
2007-03-21 14:43:00.00 @.command_id = 7
2007-03-21 14:43:00.00 @.partial_command = False
2007-03-21 14:43:00.00 @.command = System.Byte[]
2007-03-21 14:43:00.00 [61%] Inserted index creation command for article
'STATE' into the distribution database.
2007-03-21 14:43:00.00
2007-03-21 14:43:00.00 SQL Command dump
2007-03-21 14:43:00.00 ================
2007-03-21 14:43:00.00 Server: NOMOS-SRVR
2007-03-21 14:43:00.00 Database: distribution
2007-03-21 14:43:00.00 Command Text: sp_MSadd_repl_command
2007-03-21 14:43:00.00 Parameters:
2007-03-21 14:43:00.00 @.publisher_id = 0
2007-03-21 14:43:00.00 @.publisher_db = TEST
2007-03-21 14:43:00.00 @.type = -2147483645
2007-03-21 14:43:00.00 @.article_id = 1
2007-03-21 14:43:00.00 @.xact_id = System.Byte[]
2007-03-21 14:43:00.00 @.xact_seqno = SqlBinary(14)
2007-03-21 14:43:00.00 @.command_id = 8
2007-03-21 14:43:00.00 @.partial_command = False
2007-03-21 14:43:00.00 @.command = System.Byte[]
2007-03-21 14:43:00.00 [61%] Inserted bcp command for article 'STATE' into
the distribution database.
2007-03-21 14:43:00.00
2007-03-21 14:43:00.00 SQL Command dump
2007-03-21 14:43:00.00 ================
2007-03-21 14:43:00.00 Server: NOMOS-SRVR
2007-03-21 14:43:00.00 Database: TEST
2007-03-21 14:43:00.00 Command Text: sp_MSget_synctran_commands
2007-03-21 14:43:00.00 Parameters:
2007-03-21 14:43:00.00 @.publication = TestPublication
2007-03-21 14:43:00.01
2007-03-21 14:43:00.01 SQL Command dump
2007-03-21 14:43:00.01 ================
2007-03-21 14:43:00.01 Server: NOMOS-SRVR
2007-03-21 14:43:00.01 Database: distribution
2007-03-21 14:43:00.01 Command Text: sp_MSadd_repl_command
2007-03-21 14:43:00.01 Parameters:
2007-03-21 14:43:00.01 @.publisher_id = 0
2007-03-21 14:43:00.01 @.publisher_db = TEST
2007-03-21 14:43:00.01 @.type = -2147483596
2007-03-21 14:43:00.01 @.article_id = 1
2007-03-21 14:43:00.01 @.xact_id = System.Byte[]
2007-03-21 14:43:00.01 @.xact_seqno = SqlBinary(14)
2007-03-21 14:43:00.01 @.command_id = 9
2007-03-21 14:43:00.01 @.partial_command = False
2007-03-21 14:43:00.01 @.command = System.Byte[]
2007-03-21 14:43:00.01
2007-03-21 14:43:00.01 SQL Command dump
2007-03-21 14:43:00.01 ================
2007-03-21 14:43:00.01 Server: NOMOS-SRVR
2007-03-21 14:43:00.01 Database: distribution
2007-03-21 14:43:00.01 Command Text: sp_MSlock_auto_sub
2007-03-21 14:43:00.01 Parameters:
2007-03-21 14:43:00.01 @.publisher_id = 0
2007-03-21 14:43:00.01 @.publisher_db = TEST
2007-03-21 14:43:00.01 @.publication = TestPublication
2007-03-21 14:43:00.01 @.reset = 1
2007-03-21 14:43:00.01
2007-03-21 14:43:00.01 SQL Command dump
2007-03-21 14:43:00.01 ================
2007-03-21 14:43:00.01 Server: NOMOS-SRVR
2007-03-21 14:43:00.01 Database: distribution
2007-03-21 14:43:00.01 Command Text: sp_MSset_snapshot_xact_seqno
2007-03-21 14:43:00.01 Parameters:
2007-03-21 14:43:00.01 @.publisher_id = 0
2007-03-21 14:43:00.01 @.publisher_db = TEST
2007-03-21 14:43:00.01 @.article_id = 1
2007-03-21 14:43:00.01 @.xact_seqno = SqlBinary(14)
2007-03-21 14:43:00.01 @.reset = 1
2007-03-21 14:43:00.01 @.publisher_seqno = SqlBinary(10)
2007-03-21 14:43:00.01 @.ss_cplt_seqno = Null
2007-03-21 14:43:00.01
2007-03-21 14:43:00.01 SQL Command dump
2007-03-21 14:43:00.01 ================
2007-03-21 14:43:00.01 Server: NOMOS-SRVR
2007-03-21 14:43:00.01 Database: distribution
2007-03-21 14:43:00.01 Command Text: sp_MSdist_activate_auto_sub
2007-03-21 14:43:00.01 Parameters:
2007-03-21 14:43:00.01 @.publisher_id = 0
2007-03-21 14:43:00.01 @.publisher_db = TEST
2007-03-21 14:43:00.01 @.article_id = 1
2007-03-21 14:43:00.01
2007-03-21 14:43:00.01 SQL Command dump
2007-03-21 14:43:00.01 ================
2007-03-21 14:43:00.01 Server: NOMOS-SRVR
2007-03-21 14:43:00.01 Database: distribution
2007-03-21 14:43:00.01 Command Text: COMMIT TRANSACTION
2007-03-21 14:43:00.01 Parameters:
2007-03-21 14:43:00.01
2007-03-21 14:43:00.01 SQL Command dump
2007-03-21 14:43:00.01 ================
2007-03-21 14:43:00.01 Server: NOMOS-SRVR
2007-03-21 14:43:00.01 Database: TEST
2007-03-21 14:43:00.01 Command Text: COMMIT TRANSACTION
2007-03-21 14:43:00.01 Parameters:
2007-03-21 14:43:00.03 [100%] A snapshot of 1 article(s) was generated.
2007-03-21 14:43:00.03 *************************** Performance Statistics
****************************
2007-03-21 14:43:00.03 Overall snapshot generation time (seconds): 2,05
2007-03-21 14:43:00.03 Total number of rows bulk-copied from published
objects: 4
2007-03-21 14:43:00.03 Time spent generating schema scripts (seconds): 1,59
2007-03-21 14:43:00.03 Time spent pre-loading database objects for scripting
(seconds): 1,44
2007-03-21 14:43:00.03 Time spent analyzing article object dependencies
(seconds): 0,05
2007-03-21 14:43:00.03 Time spent customizing article objects for scripting
(seconds): 0,00
2007-03-21 14:43:00.03 Time spent resolving duplicate object names
(seconds): 0,00
2007-03-21 14:43:00.03 Time spent analyzing foreign key references
(seconds): 0,00
2007-03-21 14:43:00.03 Time spent analyzing check and default constraint
references (seconds): 0,00
2007-03-21 14:43:00.03 Time spent analyzing non-article object dependencies
(seconds): 0,00
2007-03-21 14:43:00.03 Time spent preparing snapshot generation (seconds):
0,11
2007-03-21 14:43:00.03 Time spent bulk copying data (seconds): 0,09
2007-03-21 14:43:00.03 Time spent copying/compressing generated file
(seconds): 0,00
2007-03-21 14:43:00.03 Time spent posting snapshot commands (seconds): 0,06
2007-03-21 14:43:00.03
************************************************** *****************************
2007-03-21 14:43:00.04
2007-03-21 14:43:00.04 SQL Command dump
2007-03-21 14:43:00.04 ================
2007-03-21 14:43:00.04 Server: NOMOS-SRVR
2007-03-21 14:43:00.04 Database: TEST
2007-03-21 14:43:00.04 Command Text: sys.sp_releaseapplock
2007-03-21 14:43:00.04 Parameters:
2007-03-21 14:43:00.04 @.Resource = NOMOS-SRVR-TEST-TestPublication-1
2007-03-21 14:43:00.04 @.LockOwner = Session
2007-03-21 14:43:00.04 @.DbPrincipal = db_owner
================================================== ===
"Hilary Cotter" wrote:

> Yes, please post the whole thing here. It sounds like you might have done
> this for the snapshot agent. You may need to do this for the
> merge/distribution agent as well.
> --
> 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
>
> "calderara" <calderara@.discussions.microsoft.com> wrote in message
> news:3243F73C-43DF-458A-837D-615F57DF16D4@.microsoft.com...
>
>

Replication between MSDE and SQL Server 2000

I got a corporate machine has SQL Server 2000 installed. And a laptop has
MSDE installed. Is this complicated to setup a 2 way replication in SQL
Server 2000 Enterprise Manager?
Not at all. The MSDE can't be set up as a transactional publisher, and most
people set up the MSDE as a subscriber because of the topology they're using
anyway. Apart from that it's pretty straightforward. Configuration of MSDE
on a separate bix when you can't connect to it using EM can be more
difficult though.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Use merge replication for bi-directional replication. Merge also works with
MSDE.
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
"Man Utd" <alanpltseNOSPAM@.yahoo.com.au> wrote in message
news:%23decwk1FGHA.376@.TK2MSFTNGP12.phx.gbl...
>I got a corporate machine has SQL Server 2000 installed. And a laptop has
> MSDE installed. Is this complicated to setup a 2 way replication in SQL
> Server 2000 Enterprise Manager?
>
|||Hi Hilary,
Could you tell me where can I get the detailed steps to set up the
replication process between the SQL Server 2000 and the laptop MSDE ?
As I am investigating the database to do this project, MSDE is an option,
and Firebird is another but I can only find some trial version of components
which have some limitations.
The reason why I need to do the replication is the sales persons bring the
laptop on site and then back to office hook up to the corporate sever
database and the replication can be done on demand or by schedule. So it
depends on if I can experiment that SQL Server 2000 and MSDE is a good
combination, the project will use this combination, otherwise, Firebird or
MySQL.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uFv4DO2FGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Use merge replication for bi-directional replication. Merge also works
with
> MSDE.
> --
> 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
> "Man Utd" <alanpltseNOSPAM@.yahoo.com.au> wrote in message
> news:%23decwk1FGHA.376@.TK2MSFTNGP12.phx.gbl...
>

replication between MS Access and SQL Server

Does anyone know the correct procedure to setup a pull relationship from MS Access to a SQL database and vice versa?http://vyaskn.tripod.com/repl_ans5.htm#sqljetsub for information.
And refer to books online

Replication between 7.0 and 2005

Is it true that merge replication between SQL7.0 and 2005 is not supported?
I would like to setup SQL2005 as a publisher and distributor and SQL7.0 as a
subscriber.
Can someone confirm that please...
Other options in that case would be to use transactional replication or to
upgrade 7.0 to 2000 and then use merge replication.
Tom
Hi Tom,
Merge Replication in SQL Server 2005 does indeed support SQL 2005
distributor and SQL 2005 publisher with SQL 70 subscribers.
You'll want to check out the following topic in SQL Server 2005 BOL:
"Using Multiple Versions of SQL Server in a Replication Topology"
Hope this helps,
Tom
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tom" wrote:

> Is it true that merge replication between SQL7.0 and 2005 is not supported?
> I would like to setup SQL2005 as a publisher and distributor and SQL7.0 as a
> subscriber.
> Can someone confirm that please...
> Other options in that case would be to use transactional replication or to
> upgrade 7.0 to 2000 and then use merge replication.
> Tom
>
>

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.