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:
Showing posts with label distributer. Show all posts
Showing posts with label distributer. Show all posts
Wednesday, March 28, 2012
Friday, March 23, 2012
replication conflict error.. how to add datas to publisher ....
Hi..
I have configured publisher, distributer,subscriber... and tried to replicate it... it has done successfully...
When i try to add datas to the publisher ... it says
"conflict error"
can you please tell me how to check the replication is successfull or not.
and i want to add datas to publisher so that it should frequently updated in subscriber...
You should start by reading Books Online topic "How Merge Replication Detects and Resolves Conflicts". You can also read Replication topics about merge replication in general to get a better undestanding about how it works and how it's best used.sqlWednesday, March 7, 2012
Replication
I have Publisher, distributer and subscriber which is SQL 2000. I have built
a new Subscriber with Win2003 and SQL 2005 and wanted to replace the old
subscriber which was SQL 2000. I would like to avoid doing a snapshot to the
new server.
My question can I tell SQL 2000 to DO not do a snapshot as long as the two
Databases are in sync or do I have to reinitialize the snapshot.
The old (Subscriber) name and the New (Subscriber) name are not the same
Here is my plan
1-Verify all transactions have been distributed before deleting replication
Lunch a SQL Server Enterprise manager on OWSQL Server
Expand SQL Server Agent folder, and expand Jobs folder
Right -Click Distribution Clean up Job: Distribution job,
click start the job
Wait for completion.
To Verify all transaction have been distributed to SYMPHONYPROD, Execute the
following T-SQL statements using query analyzer in the distribution Database
and the result should return 0.
Select count (*) AS MSrepl_commands FROM Distribution WITH (nolock)
Select count (*) AS MSrepl_transactios from Distribution WITH (nolock)
2-Delete Publications in OWSQL
Delete all five OWSQL related publications as follows:
Launch a SQQL Server Enterprise Manger on OWSQL Server
Expand the replication folder and then expand publications folder.
Delete
JDESYM: JDE_production
JDESYM_Archive:JDE_Production
JDESYM_F4211: JDE_production
JDESYM_F554101B: JDE_production
JDESYM_Others: JDE_production
3-Recreate the Publications point to the new Subscriber and start the
distribution agent
Do a no-sync subscription.
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
<msnews.microsoft.com> wrote in message
news:uq9rORgqHHA.1204@.TK2MSFTNGP04.phx.gbl...
>I have Publisher, distributer and subscriber which is SQL 2000. I have
>built a new Subscriber with Win2003 and SQL 2005 and wanted to replace the
>old subscriber which was SQL 2000. I would like to avoid doing a snapshot
>to the new server.
> My question can I tell SQL 2000 to DO not do a snapshot as long as the two
> Databases are in sync or do I have to reinitialize the snapshot.
> The old (Subscriber) name and the New (Subscriber) name are not the same
>
> Here is my plan
>
> 1-Verify all transactions have been distributed before deleting
> replication
> Lunch a SQL Server Enterprise manager on OWSQL Server
> Expand SQL Server Agent folder, and expand Jobs folder
> Right -Click Distribution Clean up Job: Distribution job,
> click start the job
> Wait for completion.
> To Verify all transaction have been distributed to SYMPHONYPROD, Execute
> the following T-SQL statements using query analyzer in the distribution
> Database and the result should return 0.
> Select count (*) AS MSrepl_commands FROM Distribution WITH (nolock)
> Select count (*) AS MSrepl_transactios from Distribution WITH (nolock)
>
> 2-Delete Publications in OWSQL
> Delete all five OWSQL related publications as follows:
> Launch a SQQL Server Enterprise Manger on OWSQL Server
> Expand the replication folder and then expand publications folder.
> Delete
> JDESYM: JDE_production
> JDESYM_Archive:JDE_Production
> JDESYM_F4211: JDE_production
> JDESYM_F554101B: JDE_production
> JDESYM_Others: JDE_production
>
>
> 3-Recreate the Publications point to the new Subscriber and start the
> distribution agent
>
a new Subscriber with Win2003 and SQL 2005 and wanted to replace the old
subscriber which was SQL 2000. I would like to avoid doing a snapshot to the
new server.
My question can I tell SQL 2000 to DO not do a snapshot as long as the two
Databases are in sync or do I have to reinitialize the snapshot.
The old (Subscriber) name and the New (Subscriber) name are not the same
Here is my plan
1-Verify all transactions have been distributed before deleting replication
Lunch a SQL Server Enterprise manager on OWSQL Server
Expand SQL Server Agent folder, and expand Jobs folder
Right -Click Distribution Clean up Job: Distribution job,
click start the job
Wait for completion.
To Verify all transaction have been distributed to SYMPHONYPROD, Execute the
following T-SQL statements using query analyzer in the distribution Database
and the result should return 0.
Select count (*) AS MSrepl_commands FROM Distribution WITH (nolock)
Select count (*) AS MSrepl_transactios from Distribution WITH (nolock)
2-Delete Publications in OWSQL
Delete all five OWSQL related publications as follows:
Launch a SQQL Server Enterprise Manger on OWSQL Server
Expand the replication folder and then expand publications folder.
Delete
JDESYM: JDE_production
JDESYM_Archive:JDE_Production
JDESYM_F4211: JDE_production
JDESYM_F554101B: JDE_production
JDESYM_Others: JDE_production
3-Recreate the Publications point to the new Subscriber and start the
distribution agent
Do a no-sync subscription.
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
<msnews.microsoft.com> wrote in message
news:uq9rORgqHHA.1204@.TK2MSFTNGP04.phx.gbl...
>I have Publisher, distributer and subscriber which is SQL 2000. I have
>built a new Subscriber with Win2003 and SQL 2005 and wanted to replace the
>old subscriber which was SQL 2000. I would like to avoid doing a snapshot
>to the new server.
> My question can I tell SQL 2000 to DO not do a snapshot as long as the two
> Databases are in sync or do I have to reinitialize the snapshot.
> The old (Subscriber) name and the New (Subscriber) name are not the same
>
> Here is my plan
>
> 1-Verify all transactions have been distributed before deleting
> replication
> Lunch a SQL Server Enterprise manager on OWSQL Server
> Expand SQL Server Agent folder, and expand Jobs folder
> Right -Click Distribution Clean up Job: Distribution job,
> click start the job
> Wait for completion.
> To Verify all transaction have been distributed to SYMPHONYPROD, Execute
> the following T-SQL statements using query analyzer in the distribution
> Database and the result should return 0.
> Select count (*) AS MSrepl_commands FROM Distribution WITH (nolock)
> Select count (*) AS MSrepl_transactios from Distribution WITH (nolock)
>
> 2-Delete Publications in OWSQL
> Delete all five OWSQL related publications as follows:
> Launch a SQQL Server Enterprise Manger on OWSQL Server
> Expand the replication folder and then expand publications folder.
> Delete
> JDESYM: JDE_production
> JDESYM_Archive:JDE_Production
> JDESYM_F4211: JDE_production
> JDESYM_F554101B: JDE_production
> JDESYM_Others: JDE_production
>
>
> 3-Recreate the Publications point to the new Subscriber and start the
> distribution agent
>
Subscribe to:
Posts (Atom)