We try to perform replication. We configured our server for
replication. Steps that we followed:
1) Create Publishing and distribution wizard
2) Create Publication wizard
3) Create Pull subscription wizard
We did not meet any errors until while doing them. But at the end of
the process in the replication monitor red cross signs (As seen in
http://stx.cs.deu.edu.tr/~zbektas/er.JPG ) on the publishers and
subscribers and their status seem as "failed". Why?
We can not start the SQL agent because of "the service did not start
due to a logon failure" error. Is this error related with our
replication failure?
Zafer,
SQL Server Replication infrastructure involves many things including a series of jobs which are scheduled and run by the SQL Server Agent. So, if your agent is stopped, replication won't work. Try changing the SQL Server Agent service to use the same doma
in account as your SQL Server Service and then restart it, and then run the Replication Agents.
Regards,
Paul Ibison
|||This is likely your problem. Locate your SQL Server agent and ensure it is
running with a valid account and password.
"zafer" <zaferbektas2000@.yahoo.com> wrote in message
news:c71dc7b.0404020741.2519351e@.posting.google.co m...
> We try to perform replication. We configured our server for
> replication. Steps that we followed:
> 1) Create Publishing and distribution wizard
> 2) Create Publication wizard
> 3) Create Pull subscription wizard
> We did not meet any errors until while doing them. But at the end of
> the process in the replication monitor red cross signs (As seen in
> http://stx.cs.deu.edu.tr/~zbektas/er.JPG ) on the publishers and
> subscribers and their status seem as "failed". Why?
> We can not start the SQL agent because of "the service did not start
> due to a logon failure" error. Is this error related with our
> replication failure?
Showing posts with label configured. Show all posts
Showing posts with label configured. Show all posts
Friday, March 30, 2012
Wednesday, March 28, 2012
replication error
Hi,
I have configured transactional replication with one publisher and one subscriber.
after completion of schema and bcp operation , it has given message as "posting commands into the distribution database" after that timedout expired .
Now the error message is
"The concurrent snapshot for publication 'Siebel OLTP Transactional' has not been activated by the log reader agent" and schema in shared folder got deleted and snopshat agent started again.
Pls provide resolution
Thanks
Murali
Murali,
you could try increasing the -QUERYTIMEOUT parameter of the distribution
agent's profile. The second error might be resulting from the first, but
just in case it isn't I'd increase the -QUERYTIMEOUT of the logreader also.
I'm not too sure where your post title fits in - "Space is not available in
TempDB" - did you also see this error message? Obviously in this case TempDB
needs increasing in size.
HTH,
Paul Ibison
|||I'd try setting the QueryTimeout parameter in the Snapshot agent.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23tDHzD3YEHA.1356@.TK2MSFTNGP09.phx.gbl...
> Murali,
> you could try increasing the -QUERYTIMEOUT parameter of the distribution
> agent's profile. The second error might be resulting from the first, but
> just in case it isn't I'd increase the -QUERYTIMEOUT of the logreader
also.
> I'm not too sure where your post title fits in - "Space is not available
in
> TempDB" - did you also see this error message? Obviously in this case
TempDB
> needs increasing in size.
> HTH,
> Paul Ibison
>
I have configured transactional replication with one publisher and one subscriber.
after completion of schema and bcp operation , it has given message as "posting commands into the distribution database" after that timedout expired .
Now the error message is
"The concurrent snapshot for publication 'Siebel OLTP Transactional' has not been activated by the log reader agent" and schema in shared folder got deleted and snopshat agent started again.
Pls provide resolution
Thanks
Murali
Murali,
you could try increasing the -QUERYTIMEOUT parameter of the distribution
agent's profile. The second error might be resulting from the first, but
just in case it isn't I'd increase the -QUERYTIMEOUT of the logreader also.
I'm not too sure where your post title fits in - "Space is not available in
TempDB" - did you also see this error message? Obviously in this case TempDB
needs increasing in size.
HTH,
Paul Ibison
|||I'd try setting the QueryTimeout parameter in the Snapshot agent.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23tDHzD3YEHA.1356@.TK2MSFTNGP09.phx.gbl...
> Murali,
> you could try increasing the -QUERYTIMEOUT parameter of the distribution
> agent's profile. The second error might be resulting from the first, but
> just in case it isn't I'd increase the -QUERYTIMEOUT of the logreader
also.
> I'm not too sure where your post title fits in - "Space is not available
in
> TempDB" - did you also see this error message? Obviously in this case
TempDB
> needs increasing in size.
> HTH,
> Paul Ibison
>
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:
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:
Monday, March 26, 2012
Replication does not work after deleting the LDF file manually.
I have maually deleted the Database.LDF file by stopping the SQL Server. When i start the SQL Server, merge replication which was configured for the database does not work. How do i fix this problem.
Thanks in advance.
Regards,
Venu.Reinitialize the replication. It should pick up a new starting LSN. But why did you ever delete the LDF anyway?
Thanks in advance.
Regards,
Venu.Reinitialize the replication. It should pick up a new starting LSN. But why did you ever delete the LDF anyway?
Replication does not start
We would like to make snapshot replicaiton. We use SQL Server 2000
Enterprise Edion with sp3 (over windows 2k advanced server).
We configured the server distributor and publisher correctly. After we
create publication and Publication properties- Run agent Now- we take the
following error message.
" Non-SysAdmins have been denied to permission to run replication jobsteps
without a proxy account.The step failed."
SQL Server and SQL Server agent services are running a domain administrator
account.
Both services use the same startup account and sql server agent's account
has sysadmin role.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:4b4701c490c5$e6de1e50$a301280a@.phx.gbl...
> Can you make the sql server service and the sql server
> agent both use the same startup account. Alternatively
> you could add the sql server agent's service login
> account to the sysadmin role on sql server.
> HTH,
> Paul Ibison
|||Right-click the replication moniotor and select
distributor properties. On the publisher's tab click the
relevant elipsis and check that the agent uses
impersonation to connect to the publisher, then do the
same thing on the subscriber's tab.
HTH,
Paul Ibison
|||i checked it. it same as you said. but still it isnt working.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:4bc701c490cf$0a167350$a301280a@.phx.gbl...
> Right-click the replication moniotor and select
> distributor properties. On the publisher's tab click the
> relevant elipsis and check that the agent uses
> impersonation to connect to the publisher, then do the
> same thing on the subscriber's tab.
> HTH,
> Paul Ibison
>
|||Is the SQL account you are using part of the local admin group on the
Publisher machine?
Can you run this from Query Analyzer on the Subscriber?
master.dbo.xp_cmdshell 'dir \\publisherServerName\c$'
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Digikoray" <kkayisli@.hotmail.com> wrote in message
news:eLu2cJNkEHA.644@.tk2msftngp13.phx.gbl...
> i checked it. it same as you said. but still it isnt working.
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
> news:4bc701c490cf$0a167350$a301280a@.phx.gbl...
>
|||- The SQL account is part of the domain admins group( It's already part
of the Local administrator group.)
- I don't know how I can use Query Analyzer .
- What do you mean with master.dbo.xp_cmdshell.
-
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uxntDZOkEHA.592@.TK2MSFTNGP11.phx.gbl...
> Is the SQL account you are using part of the local admin group on the
> Publisher machine?
> Can you run this from Query Analyzer on the Subscriber?
> master.dbo.xp_cmdshell 'dir \\publisherServerName\c$'
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Digikoray" <kkayisli@.hotmail.com> wrote in message
> news:eLu2cJNkEHA.644@.tk2msftngp13.phx.gbl...
>
|||go to start, run, and type isqlw - that's query analyzer
the extended stored procedure xp_cmdshell will allow you to run command
shell (dos) arguments within query analyzer.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Digikoray" <kkayisli@.hotmail.com> wrote in message
news:%237f3b%23OkEHA.712@.TK2MSFTNGP09.phx.gbl...
> - The SQL account is part of the domain admins group( It's already part
> of the Local administrator group.)
> - I don't know how I can use Query Analyzer .
> - What do you mean with master.dbo.xp_cmdshell.
> -
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:uxntDZOkEHA.592@.TK2MSFTNGP11.phx.gbl...
>
Enterprise Edion with sp3 (over windows 2k advanced server).
We configured the server distributor and publisher correctly. After we
create publication and Publication properties- Run agent Now- we take the
following error message.
" Non-SysAdmins have been denied to permission to run replication jobsteps
without a proxy account.The step failed."
SQL Server and SQL Server agent services are running a domain administrator
account.
Both services use the same startup account and sql server agent's account
has sysadmin role.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:4b4701c490c5$e6de1e50$a301280a@.phx.gbl...
> Can you make the sql server service and the sql server
> agent both use the same startup account. Alternatively
> you could add the sql server agent's service login
> account to the sysadmin role on sql server.
> HTH,
> Paul Ibison
|||Right-click the replication moniotor and select
distributor properties. On the publisher's tab click the
relevant elipsis and check that the agent uses
impersonation to connect to the publisher, then do the
same thing on the subscriber's tab.
HTH,
Paul Ibison
|||i checked it. it same as you said. but still it isnt working.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:4bc701c490cf$0a167350$a301280a@.phx.gbl...
> Right-click the replication moniotor and select
> distributor properties. On the publisher's tab click the
> relevant elipsis and check that the agent uses
> impersonation to connect to the publisher, then do the
> same thing on the subscriber's tab.
> HTH,
> Paul Ibison
>
|||Is the SQL account you are using part of the local admin group on the
Publisher machine?
Can you run this from Query Analyzer on the Subscriber?
master.dbo.xp_cmdshell 'dir \\publisherServerName\c$'
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Digikoray" <kkayisli@.hotmail.com> wrote in message
news:eLu2cJNkEHA.644@.tk2msftngp13.phx.gbl...
> i checked it. it same as you said. but still it isnt working.
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
> news:4bc701c490cf$0a167350$a301280a@.phx.gbl...
>
|||- The SQL account is part of the domain admins group( It's already part
of the Local administrator group.)
- I don't know how I can use Query Analyzer .
- What do you mean with master.dbo.xp_cmdshell.
-
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uxntDZOkEHA.592@.TK2MSFTNGP11.phx.gbl...
> Is the SQL account you are using part of the local admin group on the
> Publisher machine?
> Can you run this from Query Analyzer on the Subscriber?
> master.dbo.xp_cmdshell 'dir \\publisherServerName\c$'
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Digikoray" <kkayisli@.hotmail.com> wrote in message
> news:eLu2cJNkEHA.644@.tk2msftngp13.phx.gbl...
>
|||go to start, run, and type isqlw - that's query analyzer
the extended stored procedure xp_cmdshell will allow you to run command
shell (dos) arguments within query analyzer.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Digikoray" <kkayisli@.hotmail.com> wrote in message
news:%237f3b%23OkEHA.712@.TK2MSFTNGP09.phx.gbl...
> - The SQL account is part of the domain admins group( It's already part
> of the Local administrator group.)
> - I don't know how I can use Query Analyzer .
> - What do you mean with master.dbo.xp_cmdshell.
> -
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:uxntDZOkEHA.592@.TK2MSFTNGP11.phx.gbl...
>
Replication Deadlock
Dear All,
I'm just configured transactional replication.
I have 2 DB Servers, OLTP Server and Reporting Server.
I uses transactional replication to replicate the data from OLTP Server
to Reporting Server.
I configured the replcation to use Push Subcription.
I set the schedule every 3 minutes bcos I need the report to be avaiable
as soon as possible.
Unfortunately, my Reporting Server got deadlock bcos of it.
Did I configure incorrectly?
Pls I need some suggestion for it.
Thanks
Robert Lie
Robert,
perhaps you could use the NOLOCK hint on the reporting server queries.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
I'm just configured transactional replication.
I have 2 DB Servers, OLTP Server and Reporting Server.
I uses transactional replication to replicate the data from OLTP Server
to Reporting Server.
I configured the replcation to use Push Subcription.
I set the schedule every 3 minutes bcos I need the report to be avaiable
as soon as possible.
Unfortunately, my Reporting Server got deadlock bcos of it.
Did I configure incorrectly?
Pls I need some suggestion for it.
Thanks
Robert Lie
Robert,
perhaps you could use the NOLOCK hint on the reporting server queries.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
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 21, 2012
Replication Automation...
My Scenarion is like this.
I have configured replication with a publication database, a distributor database and a few subscriber databases.
The replication model is snapshot + transactional replciation.
Now i want to check using system stored procedures as to whether the replication is configured and running properly.
What are the system stored procedures which can be used and how do use them??
Basically i wanted to automate the check of replciation. How can this be done?
--Sandu.Try MSdistribution_history table in he Distribution database. The "comments" and the "runstatus" columns will give you the status of your replication agents.|||Originally posted by pushistik
Try MSdistribution_history table in he Distribution database. The "comments" and the "runstatus" columns will give you the status of your replication agents.
Is there any other tables or system stored procedures which i can check to see the replciation details?
--Sandu.sql
I have configured replication with a publication database, a distributor database and a few subscriber databases.
The replication model is snapshot + transactional replciation.
Now i want to check using system stored procedures as to whether the replication is configured and running properly.
What are the system stored procedures which can be used and how do use them??
Basically i wanted to automate the check of replciation. How can this be done?
--Sandu.Try MSdistribution_history table in he Distribution database. The "comments" and the "runstatus" columns will give you the status of your replication agents.|||Originally posted by pushistik
Try MSdistribution_history table in he Distribution database. The "comments" and the "runstatus" columns will give you the status of your replication agents.
Is there any other tables or system stored procedures which i can check to see the replciation details?
--Sandu.sql
Tuesday, March 20, 2012
Replication and use of Remote Server
When Replication is configured it creates a remote server connection. Can it
be configured to use Linked Server instead? Linked server seems to have all
the same capability as Remote Server (and more).
LMK
In SQL 2005 they are all linked servers. IIRC it can, you have to give it
the name of distr_admin. Drill down in remote servers to determine what the
name should be.
Why do you want to do this?
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"LMK" <LMK@.discussions.microsoft.com> wrote in message
news:6DD94C8B-7AB8-463D-A4DB-CA42A3C5E7B1@.microsoft.com...
> When Replication is configured it creates a remote server connection. Can
> it
> be configured to use Linked Server instead? Linked server seems to have
> all
> the same capability as Remote Server (and more).
> --
> LMK
|||In this same server, we have a separate true need for a linked server
pointing back to the same master server. I cannot create a linked server with
the same name as a remote server. Therefore if I can change the remote server
for rep to a linked server instead, I have solved both problems. I am on
Win2000. So are you saying that I cannot make this change to Linked Server in
Win2000?
LMK
"Hilary Cotter" wrote:
> In SQL 2005 they are all linked servers. IIRC it can, you have to give it
> the name of distr_admin. Drill down in remote servers to determine what the
> name should be.
> Why do you want to do this?
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "LMK" <LMK@.discussions.microsoft.com> wrote in message
> news:6DD94C8B-7AB8-463D-A4DB-CA42A3C5E7B1@.microsoft.com...
>
>
be configured to use Linked Server instead? Linked server seems to have all
the same capability as Remote Server (and more).
LMK
In SQL 2005 they are all linked servers. IIRC it can, you have to give it
the name of distr_admin. Drill down in remote servers to determine what the
name should be.
Why do you want to do this?
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"LMK" <LMK@.discussions.microsoft.com> wrote in message
news:6DD94C8B-7AB8-463D-A4DB-CA42A3C5E7B1@.microsoft.com...
> When Replication is configured it creates a remote server connection. Can
> it
> be configured to use Linked Server instead? Linked server seems to have
> all
> the same capability as Remote Server (and more).
> --
> LMK
|||In this same server, we have a separate true need for a linked server
pointing back to the same master server. I cannot create a linked server with
the same name as a remote server. Therefore if I can change the remote server
for rep to a linked server instead, I have solved both problems. I am on
Win2000. So are you saying that I cannot make this change to Linked Server in
Win2000?
LMK
"Hilary Cotter" wrote:
> In SQL 2005 they are all linked servers. IIRC it can, you have to give it
> the name of distr_admin. Drill down in remote servers to determine what the
> name should be.
> Why do you want to do this?
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "LMK" <LMK@.discussions.microsoft.com> wrote in message
> news:6DD94C8B-7AB8-463D-A4DB-CA42A3C5E7B1@.microsoft.com...
>
>
Saturday, February 25, 2012
Replication
I have replication configured in an sql 2005 environment. I have
executed the wizard twice but each time the following maintenance jobs
are missing
Reinitialize subscriptions having data validation failures
Agent history clean up: distribution
Replication monitoring refresher for distribution.
Replication agents checkup
Distribution clean up: distribution
Expired subscription clean up
If someone can tell me what most be done to have these jobs created
or why the wizard failed to create them it would be a big help.What do you set up exactly? Distributor, Publisher and Subscriber? Also what
Replication method do you setup? Merge, Transactional, Snapshot?
--
Ekrem Önsoy
"NC3" <ncoleman3@.yahoo.com> wrote in message
news:1191870323.081389.186990@.r29g2000hsg.googlegroups.com...
>I have replication configured in an sql 2005 environment. I have
> executed the wizard twice but each time the following maintenance jobs
> are missing
>
> Reinitialize subscriptions having data validation failures
> Agent history clean up: distribution
> Replication monitoring refresher for distribution.
> Replication agents checkup
> Distribution clean up: distribution
> Expired subscription clean up
> If someone can tell me what most be done to have these jobs created
> or why the wizard failed to create them it would be a big help.
>|||On Oct 8, 4:22 pm, Ekrem =D6nsoy <ek...@.btegitim.com> wrote:
> What do you set up exactly? Distributor, Publisher and Subscriber? Also w=hat
> Replication method do you setup? Merge, Transactional, Snapshot?
> --
> Ekrem =D6nsoy
> "NC3" <ncolem...@.yahoo.com> wrote in message
> news:1191870323.081389.186990@.r29g2000hsg.googlegroups.com...
>
> >I have replication configured in an sql 2005 environment. I have
> > executed the wizard twice but each time the following maintenance jobs
> > are missing
> > Reinitialize subscriptions having data validation failures
> > Agent history clean up: distribution
> > Replication monitoring refresher for distribution.
> > Replication agents checkup
> > Distribution clean up: distribution
> > Expired subscription clean up
> > If someone can tell me what most be done to have these jobs created
> > or why the wizard failed to create them it would be a big help.- Hide q=uoted text -
> - Show quoted text -
I have transactional replication configured using a remote distributor
to 'push' articles to a subscriber with ALL jobs configured to run at
the distributor.|||Hello,
What version of SQL 2005 you are using. As there was bug prior SP1. try
increasing the size of your model db try configuring again.
Thanks
Ajay Rengunthwar
MCDBA,MCTS
"NC3" <ncoleman3@.yahoo.com> wrote in message
news:1191876823.867493.221310@.50g2000hsm.googlegroups.com...
On Oct 8, 4:22 pm, Ekrem Önsoy <ek...@.btegitim.com> wrote:
> What do you set up exactly? Distributor, Publisher and Subscriber? Also
> what
> Replication method do you setup? Merge, Transactional, Snapshot?
> --
> Ekrem Önsoy
> "NC3" <ncolem...@.yahoo.com> wrote in message
> news:1191870323.081389.186990@.r29g2000hsg.googlegroups.com...
>
> >I have replication configured in an sql 2005 environment. I have
> > executed the wizard twice but each time the following maintenance jobs
> > are missing
> > Reinitialize subscriptions having data validation failures
> > Agent history clean up: distribution
> > Replication monitoring refresher for distribution.
> > Replication agents checkup
> > Distribution clean up: distribution
> > Expired subscription clean up
> > If someone can tell me what most be done to have these jobs created
> > or why the wizard failed to create them it would be a big help.- Hide
> > quoted text -
> - Show quoted text -
I have transactional replication configured using a remote distributor
to 'push' articles to a subscriber with ALL jobs configured to run at
the distributor.
executed the wizard twice but each time the following maintenance jobs
are missing
Reinitialize subscriptions having data validation failures
Agent history clean up: distribution
Replication monitoring refresher for distribution.
Replication agents checkup
Distribution clean up: distribution
Expired subscription clean up
If someone can tell me what most be done to have these jobs created
or why the wizard failed to create them it would be a big help.What do you set up exactly? Distributor, Publisher and Subscriber? Also what
Replication method do you setup? Merge, Transactional, Snapshot?
--
Ekrem Önsoy
"NC3" <ncoleman3@.yahoo.com> wrote in message
news:1191870323.081389.186990@.r29g2000hsg.googlegroups.com...
>I have replication configured in an sql 2005 environment. I have
> executed the wizard twice but each time the following maintenance jobs
> are missing
>
> Reinitialize subscriptions having data validation failures
> Agent history clean up: distribution
> Replication monitoring refresher for distribution.
> Replication agents checkup
> Distribution clean up: distribution
> Expired subscription clean up
> If someone can tell me what most be done to have these jobs created
> or why the wizard failed to create them it would be a big help.
>|||On Oct 8, 4:22 pm, Ekrem =D6nsoy <ek...@.btegitim.com> wrote:
> What do you set up exactly? Distributor, Publisher and Subscriber? Also w=hat
> Replication method do you setup? Merge, Transactional, Snapshot?
> --
> Ekrem =D6nsoy
> "NC3" <ncolem...@.yahoo.com> wrote in message
> news:1191870323.081389.186990@.r29g2000hsg.googlegroups.com...
>
> >I have replication configured in an sql 2005 environment. I have
> > executed the wizard twice but each time the following maintenance jobs
> > are missing
> > Reinitialize subscriptions having data validation failures
> > Agent history clean up: distribution
> > Replication monitoring refresher for distribution.
> > Replication agents checkup
> > Distribution clean up: distribution
> > Expired subscription clean up
> > If someone can tell me what most be done to have these jobs created
> > or why the wizard failed to create them it would be a big help.- Hide q=uoted text -
> - Show quoted text -
I have transactional replication configured using a remote distributor
to 'push' articles to a subscriber with ALL jobs configured to run at
the distributor.|||Hello,
What version of SQL 2005 you are using. As there was bug prior SP1. try
increasing the size of your model db try configuring again.
Thanks
Ajay Rengunthwar
MCDBA,MCTS
"NC3" <ncoleman3@.yahoo.com> wrote in message
news:1191876823.867493.221310@.50g2000hsm.googlegroups.com...
On Oct 8, 4:22 pm, Ekrem Önsoy <ek...@.btegitim.com> wrote:
> What do you set up exactly? Distributor, Publisher and Subscriber? Also
> what
> Replication method do you setup? Merge, Transactional, Snapshot?
> --
> Ekrem Önsoy
> "NC3" <ncolem...@.yahoo.com> wrote in message
> news:1191870323.081389.186990@.r29g2000hsg.googlegroups.com...
>
> >I have replication configured in an sql 2005 environment. I have
> > executed the wizard twice but each time the following maintenance jobs
> > are missing
> > Reinitialize subscriptions having data validation failures
> > Agent history clean up: distribution
> > Replication monitoring refresher for distribution.
> > Replication agents checkup
> > Distribution clean up: distribution
> > Expired subscription clean up
> > If someone can tell me what most be done to have these jobs created
> > or why the wizard failed to create them it would be a big help.- Hide
> > quoted text -
> - Show quoted text -
I have transactional replication configured using a remote distributor
to 'push' articles to a subscriber with ALL jobs configured to run at
the distributor.
Monday, February 20, 2012
Replicating Permissions
My reports are currently configured so that only certain users on the
domain can access certain reports. I have installed another server at
a remote location that will need to have the same permissions as the
first one. Is there a way to replicate the security settings without
having to set the permissions manually each time?
Is there a security configuration file somewhere on the first server
that i could move over to the second, since they are pretty much the
same?
Thank you!You may want to check the following tool courtesy of Jasper Smith:
http://www.sqldbatips.com/showarticle.asp?ID=62
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"muris" <rmuris@.hotmail.com> wrote in message
news:1113533808.430998.255460@.f14g2000cwb.googlegroups.com...
> My reports are currently configured so that only certain users on the
> domain can access certain reports. I have installed another server at
> a remote location that will need to have the same permissions as the
> first one. Is there a way to replicate the security settings without
> having to set the permissions manually each time?
> Is there a security configuration file somewhere on the first server
> that i could move over to the second, since they are pretty much the
> same?
> Thank you!
>|||Thanks for your Reply. The app you refered me to helps me replicate
the reports and user roles to multiple servers, but it does not
replicate the security permissions for each folder nor the report. Is
there a script that can accomplish this task?
Thanks!|||Jasper Smith may add this kind of functionality to the tool in a future
release.
On RS 2000 you would have to do this through the SOAP API (ListChildren,
GetProperties, GetPermissions, etc.)
The Management Studio for the upcoming SQL Server 2005 release of Reporting
Services will allow you to generate a script to capture that state and then
apply it to another server.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"muris" <rmuris@.hotmail.com> wrote in message
news:1113572435.510884.55430@.z14g2000cwz.googlegroups.com...
> Thanks for your Reply. The app you refered me to helps me replicate
> the reports and user roles to multiple servers, but it does not
> replicate the security permissions for each folder nor the report. Is
> there a script that can accomplish this task?
> Thanks!
>
domain can access certain reports. I have installed another server at
a remote location that will need to have the same permissions as the
first one. Is there a way to replicate the security settings without
having to set the permissions manually each time?
Is there a security configuration file somewhere on the first server
that i could move over to the second, since they are pretty much the
same?
Thank you!You may want to check the following tool courtesy of Jasper Smith:
http://www.sqldbatips.com/showarticle.asp?ID=62
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"muris" <rmuris@.hotmail.com> wrote in message
news:1113533808.430998.255460@.f14g2000cwb.googlegroups.com...
> My reports are currently configured so that only certain users on the
> domain can access certain reports. I have installed another server at
> a remote location that will need to have the same permissions as the
> first one. Is there a way to replicate the security settings without
> having to set the permissions manually each time?
> Is there a security configuration file somewhere on the first server
> that i could move over to the second, since they are pretty much the
> same?
> Thank you!
>|||Thanks for your Reply. The app you refered me to helps me replicate
the reports and user roles to multiple servers, but it does not
replicate the security permissions for each folder nor the report. Is
there a script that can accomplish this task?
Thanks!|||Jasper Smith may add this kind of functionality to the tool in a future
release.
On RS 2000 you would have to do this through the SOAP API (ListChildren,
GetProperties, GetPermissions, etc.)
The Management Studio for the upcoming SQL Server 2005 release of Reporting
Services will allow you to generate a script to capture that state and then
apply it to another server.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"muris" <rmuris@.hotmail.com> wrote in message
news:1113572435.510884.55430@.z14g2000cwz.googlegroups.com...
> Thanks for your Reply. The app you refered me to helps me replicate
> the reports and user roles to multiple servers, but it does not
> replicate the security permissions for each folder nor the report. Is
> there a script that can accomplish this task?
> Thanks!
>
Subscribe to:
Posts (Atom)