sql login permissions: logreader

Showing posts with label logreader. Show all posts

Wednesday, March 21, 2012

LogReader unable to connect to the publisher

I have a SQL2K box acting as Distributor and SQL7 box as a publisher. The
LogReader on the Distributor is unable to connect to the Publisher. I get the
following Msg from the Log Reader:
The process could not execute 'sp_MSadd_repl_commands27hp' on
'SQL2KServerName\InstanceName'
The two servers are on different untrusted domains. I am however able to
connect both ways through QA.
SQL2K box has SP4 and SQL7 box has SP3. Don't want to go to SP4 on SQL7
unless necessary and because it is a production server.
can you uncheck the Administrative Link Password requirement. Connect to
your distributor in EM, select Tools, Replication, Configure Distributor,
Publishers and Subscribers, and click on the Publishers tab. On the problem
publisher click on the browse button to the right of the publisher and you
will find this option at the bottom of the dialog box.
"Adam" <Adam@.discussions.microsoft.com> wrote in message
news:74DD5392-6B69-43B7-A591-4D80901F97D8@.microsoft.com...
>I have a SQL2K box acting as Distributor and SQL7 box as a publisher. The
> LogReader on the Distributor is unable to connect to the Publisher. I get
> the
> following Msg from the Log Reader:
> The process could not execute 'sp_MSadd_repl_commands27hp' on
> 'SQL2KServerName\InstanceName'
> The two servers are on different untrusted domains. I am however able to
> connect both ways through QA.
> SQL2K box has SP4 and SQL7 box has SP3. Don't want to go to SP4 on SQL7
> unless necessary and because it is a production server.
|||Thank you Hiary for the response. It turned out that the Distributor was
unable to resolve Publisher's IP address by name. Somehow, replacing the IP
address in the parameters for the log reader didn't work either. However,
after modifying the host file (for IP to name lookup) for distributor
resolved the problem.
-A
"Hilary Cotter" wrote:

> can you uncheck the Administrative Link Password requirement. Connect to
> your distributor in EM, select Tools, Replication, Configure Distributor,
> Publishers and Subscribers, and click on the Publishers tab. On the problem
> publisher click on the browse button to the right of the publisher and you
> will find this option at the bottom of the dialog box.
> "Adam" <Adam@.discussions.microsoft.com> wrote in message
> news:74DD5392-6B69-43B7-A591-4D80901F97D8@.microsoft.com...
>
>

LogReader SubSystem

I'm trying to setup a publisher on an msde database and am getting an error
when running my script. The error in the event viewer (and job history)
is -
Step 2 of job 'machine\instance-database-1' cannot be run because the
LogReader subsystem failed to load. The job has been suspended.
The job category is REPL -LogReader. Any ideas what I can do or what I
missed?
TIA,
Dave
on your msde server open a command prompt and go to c:\program
files\Microsoft sql server\80\com and type logread
do you get an error message?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Dave" <dave.golightly@.stgutah.com> wrote in message
news:uZYCJIYpEHA.2304@.TK2MSFTNGP14.phx.gbl...
> I'm trying to setup a publisher on an msde database and am getting an
error
> when running my script. The error in the event viewer (and job history)
> is -
> Step 2 of job 'machine\instance-database-1' cannot be run because the
> LogReader subsystem failed to load. The job has been suspended.
> The job category is REPL -LogReader. Any ideas what I can do or what I
> missed?
> TIA,
> Dave
>
|||I got -
"'logread' is not recognized as an internal or external command, operable
program or batch file"
So the installshield object I'm using to install the msde isn't installing
the logread file. Is there any other files I should be checking for?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uhmT8OZpEHA.744@.TK2MSFTNGP10.phx.gbl...
> on your msde server open a command prompt and go to c:\program
> files\Microsoft sql server\80\com and type logread
> do you get an error message?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Dave" <dave.golightly@.stgutah.com> wrote in message
> news:uZYCJIYpEHA.2304@.TK2MSFTNGP14.phx.gbl...
> error
>
|||Oops, I'm making a huge mistake here. MSDE servers are not enable to be
transactional publishers. You will have to make it a merge publisher.
Sorry about that.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Dave" <dave.golightly@.stgutah.com> wrote in message
news:Os127ZZpEHA.3688@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> I got -
> "'logread' is not recognized as an internal or external command, operable
> program or batch file"
> So the installshield object I'm using to install the msde isn't installing
> the logread file. Is there any other files I should be checking for?
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:uhmT8OZpEHA.744@.TK2MSFTNGP10.phx.gbl...
history)
>
|||I'm trying to create a snapshot publisher. Is there a setting I've got
wrong?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eG0FwfZpEHA.592@.TK2MSFTNGP11.phx.gbl...
> Oops, I'm making a huge mistake here. MSDE servers are not enable to be
> transactional publishers. You will have to make it a merge publisher.
> Sorry about that.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Dave" <dave.golightly@.stgutah.com> wrote in message
> news:Os127ZZpEHA.3688@.TK2MSFTNGP09.phx.gbl...
> history)
>
|||Here's the script -
-- Adding the snapshot publication
exec sp_addpublication @.publication = N'inspPro Snapshot Publication',
@.restricted = N'false', @.sync_method = N'native', @.repl_freq = N'snapshot',
@.description = N'Snapshot publication of inspPro database from Publisher
[workstation]\INSPPRO.', @.status = N'active', @.allow_push = N'true',
@.allow_pull = N'true', @.allow_anonymous = N'true', @.enabled_for_internet =
N'false', @.independent_agent = N'true', @.immediate_sync = N'true',
@.allow_sync_tran = N'false', @.autogen_sync_procs = N'true', @.retention = 0,
@.allow_queued_tran = N'true', @.snapshot_in_defaultfolder = N'true',
@.compress_snapshot = N'false', @.ftp_port = 21, @.ftp_login = N'anonymous',
@.allow_dts = N'false', @.allow_subscription_copy = N'false', @.conflict_policy
= N'sub reinit', @.centralized_conflicts = N'true', @.conflict_retention = 14,
@.queue_type = N'sql', @.add_to_active_directory = N'false',
@.logreader_job_name = N'[workstation]\INSPPRO-inspPro-1'
GO
exec sp_addpublication_snapshot @.publication = N'inspPro Snapshot
Publication',@.frequency_type = 4, @.frequency_interval = 1,
@.frequency_relative_interval = 1, @.frequency_recurrence_factor = 0,
@.frequency_subday = 8, @.frequency_subday_interval = 1, @.active_start_date =
0, @.active_end_date = 0, @.active_start_time_of_day = 0,
@.active_end_time_of_day = 235959, @.snapshot_job_name = N'inspPro Snapshot
Snapshot Agent'
GO
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eG0FwfZpEHA.592@.TK2MSFTNGP11.phx.gbl...
> Oops, I'm making a huge mistake here. MSDE servers are not enable to be
> transactional publishers. You will have to make it a merge publisher.
> Sorry about that.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Dave" <dave.golightly@.stgutah.com> wrote in message
> news:Os127ZZpEHA.3688@.TK2MSFTNGP09.phx.gbl...
> history)
>
|||This looks like a updateable subscription using the queue reader. I don't
believe this is supported on MSDE where MSDE is the publisher.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Dave" <dave.golightly@.stgutah.com> wrote in message
news:e0W6CpZpEHA.3868@.TK2MSFTNGP15.phx.gbl...
> Here's the script -
> -- Adding the snapshot publication
> exec sp_addpublication @.publication = N'inspPro Snapshot Publication',
> @.restricted = N'false', @.sync_method = N'native', @.repl_freq =
N'snapshot',
> @.description = N'Snapshot publication of inspPro database from Publisher
> [workstation]\INSPPRO.', @.status = N'active', @.allow_push = N'true',
> @.allow_pull = N'true', @.allow_anonymous = N'true', @.enabled_for_internet =
> N'false', @.independent_agent = N'true', @.immediate_sync = N'true',
> @.allow_sync_tran = N'false', @.autogen_sync_procs = N'true', @.retention =
0,
> @.allow_queued_tran = N'true', @.snapshot_in_defaultfolder = N'true',
> @.compress_snapshot = N'false', @.ftp_port = 21, @.ftp_login = N'anonymous',
> @.allow_dts = N'false', @.allow_subscription_copy = N'false',
@.conflict_policy
> = N'sub reinit', @.centralized_conflicts = N'true', @.conflict_retention =
14,
> @.queue_type = N'sql', @.add_to_active_directory = N'false',
> @.logreader_job_name = N'[workstation]\INSPPRO-inspPro-1'
> GO
> exec sp_addpublication_snapshot @.publication = N'inspPro Snapshot
> Publication',@.frequency_type = 4, @.frequency_interval = 1,
> @.frequency_relative_interval = 1, @.frequency_recurrence_factor = 0,
> @.frequency_subday = 8, @.frequency_subday_interval = 1, @.active_start_date
=[vbcol=seagreen]
> 0, @.active_end_date = 0, @.active_start_time_of_day = 0,
> @.active_end_time_of_day = 235959, @.snapshot_job_name = N'inspPro Snapshot
> Snapshot Agent'
> GO
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:eG0FwfZpEHA.592@.TK2MSFTNGP11.phx.gbl...
operable[vbcol=seagreen]
an[vbcol=seagreen]
the[vbcol=seagreen]
what
>

LOGREADER NOT START - No body can help?

When I try to start the agent (replication monitor->Agents -> log reader
Agent - with red cross). show me this error :
22022 sqlserveragent error: request to run job svr-personal-origen-1 (from
user personal\alioscha) refused because the job has been suspended.
SO windows 2000. server 2000 sp1
ANY HELP WILL BE APPRECIATED.
right click on this job and start it under sa.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Alioscha Debali" <adebali@.copetel.com.ar> wrote in message
news:%23RpNHcHNFHA.568@.TK2MSFTNGP09.phx.gbl...
> When I try to start the agent (replication monitor->Agents -> log reader
> Agent - with red cross). show me this error :
> 22022 sqlserveragent error: request to run job svr-personal-origen-1 (from
> user personal\alioscha) refused because the job has been suspended.
> SO windows 2000. server 2000 sp1
>
> ANY HELP WILL BE APPRECIATED.
>
>
>
|||Hilary thank you for your answer, But I have tried and it did not work.
"Hilary Cotter" wrote:

> right click on this job and start it under sa.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Alioscha Debali" <adebali@.copetel.com.ar> wrote in message
> news:%23RpNHcHNFHA.568@.TK2MSFTNGP09.phx.gbl...
>
>
|||Hilary. Into folder Admin->Jobs , There is a Job "SVR-PERSONAL-ORIGEN-1"
with red cross ( category REPL-LogReader) YES/ NO (job susp)/YES/SUSP
Right click.->General Label. Owner: sa.
Do I doing something wrong?
Thank again for your help.
"Alioscha Debali" <Alioscha Debali@.discussions.microsoft.com> escribi en el
mensaje news:84FDD7B9-91A9-4635-9174-BA75C3C4AE1A@.microsoft.com...[vbcol=seagreen]
> Hilary thank you for your answer, But I have tried and it did not work.
>
>
> "Hilary Cotter" wrote:
reader[vbcol=seagreen]
(from[vbcol=seagreen]

Logreader failed to construct replicated command from LSN

I have this error coming up 'The process could not execute 'sp_replcmds' on
'VDB1' which always seems to accompany 'Logreader failed to construct
replicated command from LSN {0008e253:00009ddb:0003}.'
I turned on verbose logging and it gave this:
2007-05-04 01:31:16.018 Publisher: {call sp_replcmds (500, 0, 0, , 15,
500000)}
2007-05-04 01:31:16.065 I~0x0008e25300009ddb0005~1:
Looking up that sequence number with:
exec sp_browsereplcmds @.xact_seqno_start = '0x0008e25300009ddb0005'
, @.xact_seqno_end = '0x0008e25300009ddb0005'
Returned nothing.
I also tried:
select * from MSrepl_transactions
where xact_seqno = '0x0008e25300009ddb0005'
It returned nothing also.
This same error is preventing 2 publications, but other 8 are working fine.
I have stopped and started log reader job a couple of times.
Any ideas?
Thanks,
Chuck Lathrope
www.sqlwebpedia.com
I've bumped into this from time to time. What you need to do is to run
profiler with the xactSequence number column.
Next time you get this error, look up the offending statement, for example
it could be a proc which is writing something unexpected to the database.
Last time I got this, it was an update to a text column with a ''.
"Chuck Lathrope" <computerguy_chuck@.fixmehotmail.com> wrote in message
news:5likshd2rlr9.1cei74wrqkxlw$.dlg@.40tude.net...
>I have this error coming up 'The process could not execute 'sp_replcmds' on
> 'VDB1' which always seems to accompany 'Logreader failed to construct
> replicated command from LSN {0008e253:00009ddb:0003}.'
> I turned on verbose logging and it gave this:
> 2007-05-04 01:31:16.018 Publisher: {call sp_replcmds (500, 0, 0, , 15,
> 500000)}
> 2007-05-04 01:31:16.065 I~0x0008e25300009ddb0005~1:
> Looking up that sequence number with:
> exec sp_browsereplcmds @.xact_seqno_start = '0x0008e25300009ddb0005'
> , @.xact_seqno_end = '0x0008e25300009ddb0005'
> Returned nothing.
> I also tried:
> select * from MSrepl_transactions
> where xact_seqno = '0x0008e25300009ddb0005'
> It returned nothing also.
> This same error is preventing 2 publications, but other 8 are working
> fine.
> I have stopped and started log reader job a couple of times.
> Any ideas?
> Thanks,
> Chuck Lathrope
> www.sqlwebpedia.com
|||On Fri, 4 May 2007 08:29:28 -0400, Hilary Cotter wrote:
Thanks, it only seems to be getting worse for me. The replication monitor
can't expand the server nodes now. I restarted sql service on the
distributor and that didn't help. Has anyone seen that?
I am setting the -ReadBatchsize to 1 as Jonathan suggested, hopefully it
can find to correct issue as this command in error reports looks to be
pointed to something already completed.
-Chuck
[vbcol=seagreen]
> I've bumped into this from time to time. What you need to do is to run
> profiler with the xactSequence number column.
> Next time you get this error, look up the offending statement, for example
> it could be a proc which is writing something unexpected to the database.
> Last time I got this, it was an update to a text column with a ''.
>
> "Chuck Lathrope" <computerguy_chuck@.fixmehotmail.com> wrote in message
> news:5likshd2rlr9.1cei74wrqkxlw$.dlg@.40tude.net...
|||Update:
One of the two publications started to work, not sure why or when.
The batchsize to 1 still brought back the same LSN error - which is still
returning nothing when I query it with:
select * from MSrepl_transactions
where xact_seqno = '0x0008e25300009ddb0005'
We are going to kill the publications and recreate them - luckily they are
not super critical like the others.
Still having Replication Monitor issues (Still running SP1 on server; SP2
on my local box).
-Chuck
On Fri, 4 May 2007 08:29:28 -0400, Hilary Cotter wrote:
Thanks, it only seems to be getting worse for me. The replication monitor
can't expand the server nodes now. I restarted sql service on the
distributor and that didn't help. Has anyone seen that?
I am setting the -ReadBatchsize to 1 as Jonathan suggested, hopefully it
can find to correct issue as this command in error reports looks to be
pointed to something already completed.
-Chuck
[vbcol=seagreen]
> I've bumped into this from time to time. What you need to do is to run
> profiler with the xactSequence number column.
> Next time you get this error, look up the offending statement, for example
> it could be a proc which is writing something unexpected to the database.
> Last time I got this, it was an update to a text column with a ''.
>
> "Chuck Lathrope" <computerguy_chuck@.fixmehotmail.com> wrote in message
> news:5likshd2rlr9.1cei74wrqkxlw$.dlg@.40tude.net...
|||While recreating the publications, the snapshot errored because of an
obsolete XSD for an XML table. We have the option set to false to publish
the XSD's, so not sure how this came about.
Now that these are working, the Replication Monitor server nodes can be
expanded now.
-Chuck
On Fri, 4 May 2007 10:15:26 -0700, Chuck Lathrope wrote:
[vbcol=seagreen]
> Update:
> One of the two publications started to work, not sure why or when.
> The batchsize to 1 still brought back the same LSN error - which is still
> returning nothing when I query it with:
> select * from MSrepl_transactions
> where xact_seqno = '0x0008e25300009ddb0005'
> We are going to kill the publications and recreate them - luckily they are
> not super critical like the others.
> Still having Replication Monitor issues (Still running SP1 on server; SP2
> on my local box).
> -Chuck
>
> On Fri, 4 May 2007 08:29:28 -0400, Hilary Cotter wrote:
> Thanks, it only seems to be getting worse for me. The replication monitor
> can't expand the server nodes now. I restarted sql service on the
> distributor and that didn't help. Has anyone seen that?
> I am setting the -ReadBatchsize to 1 as Jonathan suggested, hopefully it
> can find to correct issue as this command in error reports looks to be
> pointed to something already completed.
> -Chuck

Logreader down question

If the logreader stops (separate distributor server from publihser) and
cannot connect to the publisher for - let's say - 4 hours, is that data lost
or will the transactions to be replication still be in the tlog? and
replication will catch up - in total (including the 4 hours down)?
Just to clarify...
The Transaction Retention period is the default 72 hours in the Distribution
properties. ?
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:28c201c51dbe$9111c5e0$a601280a@.phx.gbl...[vbcol=seagreen]
> 4 hours shouldn't be a problem.
> Firstly, the commands won't be removed from the log until
> they have been read by the log reader, so they'll remain
> there.
> The time that this can be an issue is if 4 hours is
> longer than the transaction retention period. If this is
> the case, the distribution cleanup agent can remove
> commands before the distribution agent propagates them,
> in which case you'll end up having to reinitialize to
> recover.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
> publihser) and
> hours, is that data lost
> the tlog? and
> hours down)?
|||Yes - if you have the default of 72 hours, then you're
fine

Rgds,
Paul Ibison
sql

Logreader agent not being created

I'm working with a client on a problem where they setup transactional
replication publications, push out a subscription, the snap shots are
created, the data is initially pushed out to the subscriber but no Logreader
agent is created - So no transactional replication occurs.
The Sql server, agent, and application and system logs show no errors.
If I script out the replication the sp_addpublication is being called
without the @.logreader_job_name parameter. I could try installing the agent
manually using logread.exe but I want to understand why the agent is not
being created the way it normally should.
Any help would be appreciated,
J
can you script out your publication and post it here.
Also sometimes the agent folders get a little scrambled and the agents don't
show up there. Could you perhaps check to see if there aren't any logreader
processes showing up in task manger, or check to see if you can create
another transactional publication in a different database. Make sure you use
a unique name for the publication.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Jim Young" <thorium48@.hotmail.com> wrote in message
news:uKsSQxAqEHA.376@.TK2MSFTNGP14.phx.gbl...
> I'm working with a client on a problem where they setup transactional
> replication publications, push out a subscription, the snap shots are
> created, the data is initially pushed out to the subscriber but no
Logreader
> agent is created - So no transactional replication occurs.
> The Sql server, agent, and application and system logs show no errors.
> If I script out the replication the sp_addpublication is being called
> without the @.logreader_job_name parameter. I could try installing the
agent
> manually using logread.exe but I want to understand why the agent is not
> being created the way it normally should.
> Any help would be appreciated,
> J
>
|||Thank's for the response,
Attached is the replication script with the beginning part that sets up the
distributor and the setup for one of the publications that is failing to
create a Log Reader agent.
As you can see the logreader_job_name parameter is absent. Also I checked in
the server and the logread.exe executable is there in its proper place.
The server is running Sql Server 2000 Standard SP3 on Microsoft Windows
Server 2003 Standard, replicating to a server with the same configuraton
(except 2500 miles away).
This same replication worked just fine on previous servers that the
application was migrated from: Sql Server 7.0 on Windows 2000 Server
Advanced (clustered).
Jim
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ec33qHCqEHA.3464@.TK2MSFTNGP14.phx.gbl...
> can you script out your publication and post it here.
> Also sometimes the agent folders get a little scrambled and the agents
don't
> show up there. Could you perhaps check to see if there aren't any
logreader
> processes showing up in task manger, or check to see if you can create
> another transactional publication in a different database. Make sure you
use
> a unique name for the publication.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Jim Young" <thorium48@.hotmail.com> wrote in message
> news:uKsSQxAqEHA.376@.TK2MSFTNGP14.phx.gbl...
> Logreader
> agent
>
begin 666 Assoc.sql
M+RHJ*BHJ*B!38W)I<'1I;F<@.=&AE(')E<&QI8V%T:6]N('-E='5P(&]F('-E
M<G9E<B!-0E!34TE344PP,2X@.4V-R:7!T($1A=&4Z(#$P+S$O,C P-" S.C0Y
M.C(X(%!-("HJ*BHJ*B\-"B\J*BHJ*BH@.4&QE87-E(&YO=&4Z($%N>2!P87-S
M=V]R9"!P87)A;65T97(@.=V%S('-C<FEP=&5D('=I=&@.@.3E5,3"!O<B!E;7!T
M>2!S=')I;F<@.9F]R('-E8W5R:71Y(')E87-O;BX@.*BHJ*BHJ+PT*#0HO*BHJ
M*BHJ($)E9VEN.B!38W)I<'0@.=&\@.8F4@.<G5N(&%T($1I<W1R: 6)U=&]R.B!-
M0E!34TE344PP,2 J*BHJ*BHO#0HO*BHJ*BHJ($EN<W1A;&QI;F<@.=&AE('-E
M<G9E<B!-0E!34TE344PP,2!A<R!A($1I<W1R:6)U=&]R+B!38W)I<'0@.1&%T
M93H@.,3 O,2\R,# T(#,Z-#DZ,C@.@.4$T@.*BHJ*BHJ+PT*=7-E(&UA<W1E<@.T*
M1T\-"@.T*97AE8R!S<%]A9&1D:7-T<FEB=71O<B @.0&1I<W1R:6)U=&]R(#T@.
M3B=-0E!34TE344PP,2<L($!P87-S=V]R9" ]($XG)PT*1T\-"@.T*+2T@.57!D
M871I;F<@.=&AE(&%G96YT('!R;V9I;&4@.9&5F875L=',-"G-P7TU3=7!D871E
M7V%G96YT='EP95]D969A=6QT($!P<F]F:6QE7VED(#T@.,0T*1T\-"G-P7TU3
M=7!D871E7V%G96YT='EP95]D969A=6QT($!P<F]F:6QE7VED(#T@.,@.T*1T\-
M"G-P7TU3=7!D871E7V%G96YT='EP95]D969A=6QT($!P<F]F:6QE7VED(#T@.
M- T*1T\-"G-P7TU3=7!D871E7V%G96YT='EP95]D969A=6QT($!P<F]F:6QE
M7VED(#T@.-@.T*1T\-"G-P7TU3=7!D871E7V%G96YT='EP95]D969A=6QT($!P
M<F]F:6QE7VED(#T@.,3$-"D=/#0H-"BTM($%D9&EN9R!T:&4@.9&ES=')I8G5T
M:6]N(&1A=&%B87-E#0IE>&5C('-P7V%D9&1I<W1R:6)U=&EO;F1B("! 9&%T
M86)A<V4@./2!.)V1I<W1R:6)U=&EO;B<L($!D871A7V9O;&1E<B ]($XG13I<
M4U%,,DM<35-344Q$051!7$U34U%,7$1A=&$G+"! 9&%T85]F:6QE(#T@.3B=D
M:7-T<FEB=71I;VXN341&)RP@.0&1A=&%?9FEL95]S:7IE(#T@.,S,S+"! ;&]G
M7V9O;&1E<B ]($XG13I<4U%,,DM<35-344Q$051!7$U34U%,7$1A=&$G+"!
M;&]G7V9I;&4@./2!.)V1I<W1R:6)U=&EO;BY,1$8G+"! ;&]G7V9I;&5?<VEZ
M92 ](#4V+"! ;6EN7V1I<W1R971E;G1I;VX@./2 P+"! ;6%X7V1I<W1R971E
M;G1I;VX@./2 W,BP@.0&AI<W1O<GE?<F5T96YT:6]N(#T@.-#@.L($!S96-U<FET
M>5]M;V1E(#T@.,0T*1T\-"@.T*+2T@.061D:6YG('1H92!D:7-T<FEB=71I;VX@.
M<'5B;&ES:&5R#0IE>&5C('-P7V%D9&1I<W1P=6)L:7-H97(@.($!P=6)L:7-H
M97(@./2!.)TU"4%-325-13# Q)RP@.0&1I<W1R:6)U=&EO;E]D8B ]($XG9&ES
M=')I8G5T:6]N)RP@.0'-E8W5R:71Y7VUO9&4@./2 Q+"! =V]R:VEN9U]D:7)E
M8W1O<GD@./2!.)UQ<34)04U-)4U%,,#%<4D503$1!5$$G+"! =')U<W1E9" ]
M($XG9F%L<V4G+"! =&AI<F1P87)T>5]F;&%G(#T@., T*1T\-"@.T*+RHJ*BHJ
M*B!%;F0Z(%-C<FEP="!T;R!B92!R=6X@.870@.1&ES=')I8G5T;W(Z($U"4%-3
M25-13# Q("HJ*BHJ*B\-"@.T*+RHJ*BHJ*B!"96=I;CH@.4V-R:7!T('1O(&)E
M(')U;B!A="!0=6)L:7-H97(Z($U"4%-325-13# Q("HJ*BHJ*B\-"BTM($%D
M9&EN9R!T:&4@.<F5G:7-T97)E9"!S=6)S8W)I8F5R#0IE>&5C('-P7V%D9'-U
M8G-C<FEB97(@.0'-U8G-C<FEB97(@./2!.)TA"4%-325-13# Q)RP@.0'1Y<&4@.
M/2 P+"! <V5C=7)I='E?;6]D92 ](#$L($!F<F5Q=65N8WE?='EP92 ](#8T
M+"! 9G)E<75E;F-Y7VEN=&5R=F%L(#T@.,2P@.0&9R97%U96YC>5]R96QA=&EV
M95]I;G1E<G9A;" ](#(L($!F<F5Q=65N8WE?<F5C=7)R96YC95]F86-T;W(@.
M/2 P+"! 9G)E<75E;F-Y7W-U8F1A>2 ](#@.L($!F<F5Q=65N8WE?<W5B9&%Y
M7VEN=&5R=F%L(#T@.,2P@.0&%C=&EV95]S=&%R=%]D871E(#T@.,"P@.0&%C=&EV
M95]E;F1?9&%T92 ](# L($!A8W1I=F5?<W1A<G1?=&EM95]O9E]D87D@./2 P
M+"! 86-T:79E7V5N9%]T:6UE7V]F7V1A>2 ](#(S-3DP,"P@.0&1E<V-R:7!T
M:6]N(#T@.3B<G#0H@.97AE8R!S<%]C:&%N9V5S=6)S8W)I8F5R7W-C:&5D=6QE
M($!S=6)S8W)I8F5R(#T@.3B=(0E!34TE344PP,2<L($!A9V5N= %]T>7!E(#T@.
M,2P@.0&%C=&EV95]E;F1?9&%T92 ](# -"D=/#0H-"BTM($5N86)L:6YG('1H
M92!R97!L:6-A=&EO;B!D871A8F%S90T*=7-E(&UA<W1E<@.T*1T\-"@.T*97AE
M8R!S<%]R97!L:6-A=&EO;F1B;W!T:6]N($!D8FYA;64@./2!.)T]21$5214Y4
M4EDG+"! ;W!T;F%M92 ]($XG<'5B;&ES:"<L($!V86QU92 ]($XG=')U92<-
M"D=/#0H-"G5S92!;3U)$15)%3E1265T-"D=/#0H-"BTM($%D9&EN9R!T:&4@.
M=')A;G-A8W1I;VYA;"!P=6)L:6-A=&EO;@.T*97AE8R!S<%]A9&1P=6)L:6-A
M=&EO;B! <'5B;&EC871I;VX@./2!.)T%S<V]C7TQO9R<L($!R97-T<FEC=&5D
M(#T@.3B=F86QS92<L($!S>6YC7VUE=&AO9" ]($XG;F%T:79E)RP@.0')E<&Q?
M9G)E<2 ]($XG8V]N=&EN=6]U<R<L($!D97-C<FEP=&EO;B ]($XG5')A;G-A
M8W1I;VYA;"!P=6)L:6-A=&EO;B!O9B!/4D1%4D5.5%)9(&1A=&%B87-E(&9R
M;VT@.4'5B;&ES:&5R($U"4%-325-13# Q+B<L($!S=&%T=7,@./2!.)V%C=&EV
M92<L($!A;&QO=U]P=7-H(#T@.3B=T<G5E)RP@.0&%L;&]W7W!U;&P@./2!.)W1R
M=64G+"! 86QL;W=?86YO;GEM;W5S(#T@.3B=F86QS92<L($!E;F%B;&5D7V 9O
M<E]I;G1E<FYE=" ]($XG9F%L<V4G+"! :6YD97!E;F1E;G1?86=E;G0@./2!.
M)W1R=64G+"! :6UM961I871E7W-Y;F,@./2!.)V9A;'-E)RP@.0&%L;&]W7W-Y
M;F-?=')A;B ]($XG=')U92<L($!A=71O9V5N7W-Y;F-?<')O8W,@./2!.)W1R
M=64G+"! <F5T96YT:6]N(#T@.,S,V+"! 86QL;W=?<75E=65D7W1R86X@./2!.
M)V9A;'-E)RP@.0'-N87!S:&]T7VEN7V1E9F%U;'1F;VQD97(@./2!.)W1R=64G
M+"! 8V]M<')E<W-?<VYA<'-H;W0@./2!.)V9A;'-E)RP@.0&9T<%]P;W)T(#T@.
M,C$L($!F='!?;&]G:6X@./2!.)V%N;VYY;6]U<R<L($!A;&QO=U]D=',@./2!.
M)V9A;'-E)RP@.0&%L;&]W7W-U8G-C<FEP=&EO;E]C;W!Y(#T@.3B=F86QS92<L
M($!A9&1?=&]?86-T:79E7V1I<F5C=&]R>2 ]($XG9F%L<V4G+"! <7)E861E
M<E]J;V)?;F%M92 ]($XG6TU"4%-325-13# Q72XV)PT*97AE8R!S<%]A9&1P
M=6)L:6-A=&EO;E]S;F%P<VAO="! <'5B;&EC871I;VX@./2!.)T%S<V]C7TQO
M9R<L0&9R97%U96YC>5]T>7!E(#T@.-"P@.0&9R97%U96YC>5]I;G1E<G9A;" ]
M(#$L($!F<F5Q=65N8WE?<F5L871I=F5?:6YT97)V86P@./2 Q+"! 9G)E<75E
M;F-Y7W)E8W5R<F5N8V5?9F%C=&]R(#T@.,"P@.0&9R97%U96YC>5]S=6)D87D@.
M/2 X+"! 9G)E<75E;F-Y7W-U8F1A>5]I;G1E<G9A;" ](#$L($!A8W1I=F5?
M<W1A<G1?9&%T92 ](# L($!A8W1I=F5?96YD7V1A=&4@./2 P+"! 86-T:79E
M7W-T87)T7W1I;65?;V9?9&%Y(#T@.,"P@.0&%C=&EV95]E;F1?=&EM95]O9E]D
M87D@./2 R,S4Y-3DL($!S;F%P<VAO=%]J;V)?;F%M92 ]($XG34)04U-)4U%,
M,#$M3U)$15)%3E1262U!<W-O8U],;V<M,34G#0I'3PT*#0IE>&5C('-P7V=R
M86YT7W!U8FQI8V%T:6]N7V%C8V5S<R! <'5B;&EC871I;VX@./2!.)T%S<V]C
M7TQO9R<L($!L;V=I;B ]($XG0E5)3%1)3EQ!9&UI;FES=')A=&]R<R<-"D=/
M#0IE>&5C('-P7V=R86YT7W!U8FQI8V%T:6]N7V%C8V5S<R! <'5B;&EC871I
M;VX@./2!.)T%S<V]C7TQO9R<L($!L;V=I;B ]($XG9&ES=')I8G5T;W)?861M
M:6XG#0I'3PT*97AE8R!S<%]G<F%N=%]P=6)L:6-A=&EO;E]A8V-E<W,@.0'!U
M8FQI8V%T:6]N(#T@.3B=!<W-O8U],;V<G+"! ;&]G:6X@./2!.)W-A)PT*1T\-
M"@.T*+2T@.061D:6YG('1H92!T<F%N<V%C=&EO;F%L(&%R=&EC; &5S#0IE>&5C
M('-P7V%D9&%R=&EC;&4@.0'!U8FQI8V%T:6]N(#T@.3B=!<W-O8U],;V<G+"!
M87)T:6-L92 ]($XG;&]G7V%T=&5N9&%N8V4G+"! <V]U<F-E7V]W;F5R(#T@.
M3B=D8F\G+"! <V]U<F-E7V]B:F5C=" ]($XG;&]G7V%T=&5N9&%N8V4G+"!
M9&5S=&EN871I;VY?=&%B;&4@./2!.)VQO9U]A='1E;F1A;F-E)RP@.0'1Y<&4@.
M/2!.)VQO9V)A<V5D)RP@.0&-R96%T:6]N7W-C<FEP=" ](&YU;&PL($!D97-C
M<FEP=&EO;B ](&YU;&PL($!P<F5?8W)E871I;VY?8VUD(#T@.3B=D<F]P)RP@.
M0'-C:&5M85]O<'1I;VX@./2 P># P,# P,# P,# P,$-%1C,L($!S=&%T=7,@.
M/2 Q-BP@.0'9E<G1I8V%L7W!A<G1I=&EO;B ]($XG9F%L<V4G+"! :6YS7V-M
M9" ]($XG0T%,3"!S<%]-4VEN<U]L;V=?871T96YD86YC92<L($!D96Q?8VUD
M(#T@.3B=#04Q,('-P7TU39&5L7VQO9U]A='1E;F1A;F-E)RP@.0'5P9%]C;60@.
M/2!.)TU#04Q,('-P7TU3=7!D7VQO9U]A='1E;F1A;F-E)RP@.0&9I;'1E6YC7V]B:F5C=" ](&YU;&PL($!A=71O7VED96YT:71Y7W)A
M;F=E(#T@.3B=F86QS92<-"D=/#0IE>&5C('-P7V%D9&%R=&EC;&4@.0'!U8FQI
M8V%T:6]N(#T@.3B=!<W-O8U],;V<G+"! 87)T:6-L92 ]($XG;&]G7V1E<&5N
M9&5N=',G+"! <V]U<F-E7V]W;F5R(#T@.3B=D8F\G+"! <V]U<F-E7V]B:F5C
M=" ]($XG;&]G7V1E<&5N9&5N=',G+"! 9&5S=&EN871I;VY?=&%B;&4@./2!.
M)VQO9U]D97!E;F1E;G1S)RP@.0'1Y<&4@./2!.)VQO9V)A<V5D)RP@.0&-R96%T
M:6]N7W-C<FEP=" ](&YU;&PL($!D97-C<FEP=&EO;B ](&YU;&PL($!P<F5?
M8W)E871I;VY?8VUD(#T@.3B=D<F]P)RP@.0'-C:&5M85]O<'1I;VX@./2 P># P
M,# P,# P,# P,$-%1C,L($!S=&%T=7,@./2 Q-BP@.0'9E<G1I8V%L7W!A<G1I
M=&EO;B ]($XG9F%L<V4G+"! :6YS7V-M9" ]($XG0T%,3"!S<%]-4VEN<U]L
M;V=?9&5P96YD96YT<R<L($!D96Q?8VUD(#T@.3B=#04Q,('-P7TU39&5L7VQO
M9U]D97!E;F1E;G1S)RP@.0'5P9%]C;60@./2!.)TU#04Q,('-P7TU3=7!D7VQO
M9U]D97!E;F1E;G1S)RP@.0&9I;'1E6YC7V]B:F5C=" ]
M(&YU;&PL($!A=71O7VED96YT:71Y7W)A;F=E(#T@.3B=F86QS9 2<-"D=/#0IE
M>&5C('-P7V%D9&%R=&EC;&4@.0'!U8FQI8V%T:6]N(#T@.3B=!<W-O8U],;V<G
M+"! 87)T:6-L92 ]($XG;&]G7V1E=&%I;',G+"! <V]U<F-E7V]W;F5R(#T@.
M3B=D8F\G+"! <V]U<F-E7V]B:F5C=" ]($XG;&]G7V1E=&%I;',G+"! 9&5S
M=&EN871I;VY?=&%B;&4@./2!.)VQO9U]D971A:6QS)RP@.0'1Y<&4@./2!.)VQO
M9V)A<V5D)RP@.0&-R96%T:6]N7W-C<FEP=" ](&YU;&PL($!D97-C<FEP=&EO
M;B ](&YU;&PL($!P<F5?8W)E871I;VY?8VUD(#T@.3B=D<F]P)RP@.0'-C:&5M
M85]O<'1I;VX@./2 P># P,# P,# P,# P,$-%1C,L($!S=&%T=7,@./2 Q-BP@.
M0'9E<G1I8V%L7W!A<G1I=&EO;B ]($XG9F%L<V4G+"! :6YS7V-M9" ]($XG
M0T%,3"!S<%]-4VEN<U]L;V=?9&5T86EL<R<L($!D96Q?8VUD(#T@.3B=#04Q,
M('-P7TU39&5L7VQO9U]D971A:6QS)RP@.0'5P9%]C;60@./2!.)TU#04Q,('-P
M7TU3=7!D7VQO9U]D971A:6QS)RP@.0&9I;'1E6YC7V]B
M:F5C=" ](&YU;&PL($!A=71O7VED96YT:71Y7W)A;F=E(#T@.3B=F86QS92 <-
M"D=/#0IE>&5C('-P7V%D9&%R=&EC;&4@.0'!U8FQI8V%T:6]N(#T@.3B=!<W-O
M8U],;V<G+"! 87)T:6-L92 ]($XG;&]G7VYO4F5H:7)E)RP@.0'-O=7)C95]O
M=VYE<B ]($XG9&)O)RP@.0'-O=7)C95]O8FIE8W0@./2!.)VQO9U]N;U)E:&ER
M92<L($!D97-T:6YA=&EO;E]T86)L92 ]($XG;&]G7VYO4F5H:7)E)RP@.0'1Y
M<&4@./2!.)VQO9V)A<V5D)RP@.0&-R96%T:6]N7W-C<FEP=" ](&YU;&PL($!D
M97-C<FEP=&EO;B ](&YU;&PL($!P<F5?8W)E871I;VY?8VUD(#T@.3B=D<F]P
M)RP@.0'-C:&5M85]O<'1I;VX@./2 P># P,# P,# P,# P,$-%1C,L($!S=&%T
M=7,@./2 Q-BP@.0'9E<G1I8V%L7W!A<G1I=&EO;B ]($XG9F%L<V4G+"! :6YS
M7V-M9" ]($XG0T%,3"!S<%]-4VEN<U]L;V=?;F]296AI<F4G+"! 9&5L7V-M
M9" ]($XG0T%,3"!S<%]-4V1E;%]L;V=?;F]296AI<F4G+"! =7!D7V-M9" ]
M($XG34-!3$P@.<W!?35-U<&1?;&]G7VYO4F5H:7)E)RP@.0&9I;'1E6YC7V]B:F5C=" ](&YU;&PL($!A=71O7VED96YT:71Y7W)A;F=E
M(#T@.3B=F86QS92<-"D=/#0IE>&5C('-P7V%D9&%R=&EC;&4@.0'!U8FQI8V%T
M:6]N(#T@.3B=!<W-O8U],;V<G+"! 87)T:6-L92 ]($XG;&]G7W-E<&%R871I
M;VYS)RP@.0'-O=7)C95]O=VYE<B ]($XG9&)O)RP@.0'-O=7)C95]O8FIE8W0@.
M/2!.)VQO9U]S97!A<F%T:6]N<R<L($!D97-T:6YA=&EO;E]T86)L92 ]($XG
M;&]G7W-E<&%R871I;VYS)RP@.0'1Y<&4@./2!.)VQO9V)A<V5D)RP@.0&-R96%T
M:6]N7W-C<FEP=" ](&YU;&PL($!D97-C<FEP=&EO;B ](&YU;&PL($!P<F5?
M8W)E871I;VY?8VUD(#T@.3B=D<F]P)RP@.0'-C:&5M85]O<'1I;VX@./2 P># P
M,# P,# P,# P,$-%1C,L($!S=&%T=7,@./2 Q-BP@.0'9E<G1I8V%L7W!A<G1I
M=&EO;B ]($XG9F%L<V4G+"! :6YS7V-M9" ]($XG0T%,3"!S<%]-4VEN<U]L
M;V=?<V5P87)A=&EO;G,G+"! 9&5L7V-M9" ]($XG0T%,3"!S<%]-4V1E;%]L
M;V=?<V5P87)A=&EO;G,G+"! =7!D7V-M9" ]($XG34-!3$P@.<W!?35-U<&1?
M;&]G7W-E<&%R871I;VYS)RP@.0&9I;'1E6YC7V]B:F5C
M=" ](&YU;&PL($!A=71O7VED96YT:71Y7W)A;F=E(#T@.3B=F86QS92 <-"D=/
M#0H-"BTM($%D9&EN9R!T:&4@.=')A;G-A8W1I;VYA;"!S=6)S8W)I<'1I;VX-
M"F5X96,@.<W!?861D<W5B<V-R:7!T:6]N($!P=6)L:6-A=&EO;B ]($XG07-S
M;V-?3&]G)RP@.0&%R=&EC;&4@./2!.)V%L;"<L($!S=6)S8W)I8F5R(#T@.3B=(
M0E!34TE344PP,2<L($!D97-T:6YA=&EO;E]D8B ]($XG3U)$15)%3E1262<L
M($!S>6YC7W1Y<&4@./2!.)V%U=&]M871I8R<L($!U<&1A=&5?;6]D92 ]($XG
M<WEN8R!T<F%N)RP@.0&]F9FQO861A9V5N=" ](# L($!D='-?<&%C:V%G95]L
<;V-A=&EO;B ]($XG9&ES=')I8G5T;W(G#0I'3P``
`
end
|||You are using Updateable Subscriptions with Queued Updating.
the log reader agent name should (but doesn't have to be blank). Any value
you put in here will be ignored.
I just want to confirm that the log reader agent is not showing up in the
publisher. It should not show up on the subscriber.
Also can you check your jobs folder (under the management folder) to see if
a log reader agent/job is not created for this job,
Sometimes the agents will not show up in the replication agents folder but
are actually there, and you can only see them in the jobs folder. When this
happens it is difficult to administer your agents, but you will have a
working solution.
"Jim Young" <thorium48@.hotmail.com> wrote in message
news:%238DZmWDqEHA.3668@.TK2MSFTNGP15.phx.gbl...
> Thank's for the response,
> Attached is the replication script with the beginning part that sets up
> the
> distributor and the setup for one of the publications that is failing to
> create a Log Reader agent.
> As you can see the logreader_job_name parameter is absent. Also I checked
> in
> the server and the logread.exe executable is there in its proper place.
> The server is running Sql Server 2000 Standard SP3 on Microsoft Windows
> Server 2003 Standard, replicating to a server with the same configuraton
> (except 2500 miles away).
> This same replication worked just fine on previous servers that the
> application was migrated from: Sql Server 7.0 on Windows 2000 Server
> Advanced (clustered).
> Jim
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ec33qHCqEHA.3464@.TK2MSFTNGP14.phx.gbl...
> don't
> logreader
> use
>
>
|||It was setup for Immediate Updating and Queued Updating as a failover. Even
still, doesn't there need to be a Log Reader agent to pickup any
transactions to replicate?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eZ48JFJqEHA.3244@.tk2msftngp13.phx.gbl...
> You are using Updateable Subscriptions with Queued Updating.
> the log reader agent name should (but doesn't have to be blank). Any value
> you put in here will be ignored.
> I just want to confirm that the log reader agent is not showing up in the
> publisher. It should not show up on the subscriber.
> Also can you check your jobs folder (under the management folder) to see
if
> a log reader agent/job is not created for this job,
> Sometimes the agents will not show up in the replication agents folder but
> are actually there, and you can only see them in the jobs folder. When
this[vbcol=seagreen]
> happens it is difficult to administer your agents, but you will have a
> working solution.
>
> "Jim Young" <thorium48@.hotmail.com> wrote in message
> news:%238DZmWDqEHA.3668@.TK2MSFTNGP15.phx.gbl...
checked[vbcol=seagreen]
you[vbcol=seagreen]
errors.
>
|||The log reader agent is not showing up at the publisher or the subscriber.
There is also no agent job listed.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eZ48JFJqEHA.3244@.tk2msftngp13.phx.gbl...
> You are using Updateable Subscriptions with Queued Updating.
> the log reader agent name should (but doesn't have to be blank). Any value
> you put in here will be ignored.
> I just want to confirm that the log reader agent is not showing up in the
> publisher. It should not show up on the subscriber.
> Also can you check your jobs folder (under the management folder) to see
if
> a log reader agent/job is not created for this job,
> Sometimes the agents will not show up in the replication agents folder but
> are actually there, and you can only see them in the jobs folder. When
this[vbcol=seagreen]
> happens it is difficult to administer your agents, but you will have a
> working solution.
>
> "Jim Young" <thorium48@.hotmail.com> wrote in message
> news:%238DZmWDqEHA.3668@.TK2MSFTNGP15.phx.gbl...
checked[vbcol=seagreen]
you[vbcol=seagreen]
errors.
>
|||yes, there will be a log reader agent on the publisher.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Jim Young" <thorium48@.hotmail.com> wrote in message
news:%23oQdcIKqEHA.1576@.TK2MSFTNGP12.phx.gbl...
> It was setup for Immediate Updating and Queued Updating as a failover.
Even[vbcol=seagreen]
> still, doesn't there need to be a Log Reader agent to pickup any
> transactions to replicate?
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:eZ48JFJqEHA.3244@.tk2msftngp13.phx.gbl...
value[vbcol=seagreen]
the[vbcol=seagreen]
> if
but[vbcol=seagreen]
> this
up[vbcol=seagreen]
to[vbcol=seagreen]
> checked
place.[vbcol=seagreen]
Windows[vbcol=seagreen]
configuraton[vbcol=seagreen]
agents[vbcol=seagreen]
create[vbcol=seagreen]
> you
transactional[vbcol=seagreen]
are[vbcol=seagreen]
> errors.
called[vbcol=seagreen]
the[vbcol=seagreen]
is
>
|||I tried your script. It works on my machine. I think there is something
wrong with your machine. Can you try to disable replication, recreate it,
and then recreate your publication and subscription.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uFdQI6KqEHA.3712@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> yes, there will be a log reader agent on the publisher.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Jim Young" <thorium48@.hotmail.com> wrote in message
> news:%23oQdcIKqEHA.1576@.TK2MSFTNGP12.phx.gbl...
> Even
> value
> the
see[vbcol=seagreen]
> but
[vbcol=seagreen]
> up
failing[vbcol=seagreen]
> to
> place.
> Windows
> configuraton
> agents
> create
sure[vbcol=seagreen]
> transactional
> are
no
> called
> the
> is
>
|||That's what I feared. There is definitely something wrong with the way
replication was installed on this box. Unfortunately I was not the one who
installed Sql Server and replication. I was called in after the fact when it
looked like replication was not working. It may be an issue of permissions
and rights during the setup of replication on the server, as this company
does not want to give the Sql Server DBAs admin rights to their servers.
Thanks for all your help!
Jim
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ejcXuBOqEHA.3244@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> I tried your script. It works on my machine. I think there is something
> wrong with your machine. Can you try to disable replication, recreate it,
> and then recreate your publication and subscription.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:uFdQI6KqEHA.3712@.TK2MSFTNGP15.phx.gbl...
in[vbcol=seagreen]
> see
folder[vbcol=seagreen]
When[vbcol=seagreen]
a[vbcol=seagreen]
sets[vbcol=seagreen]
> failing
the[vbcol=seagreen]
Server[vbcol=seagreen]
> sure
shots[vbcol=seagreen]
> no
installing[vbcol=seagreen]
agent
>
|||I don't think it is a problem with the way the previous dba installed
replication, rather there is something wrong with the SQL Server
environment; ie missing stored procedures, or an inconsistent application of
SP 3. I suggest you reapply SP 3 and try again.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Jim Young" <thorium48@.hotmail.com> wrote in message
news:uiosaiOqEHA.2588@.TK2MSFTNGP12.phx.gbl...
> That's what I feared. There is definitely something wrong with the way
> replication was installed on this box. Unfortunately I was not the one who
> installed Sql Server and replication. I was called in after the fact when
it[vbcol=seagreen]
> looked like replication was not working. It may be an issue of permissions
> and rights during the setup of replication on the server, as this company
> does not want to give the Sql Server DBAs admin rights to their servers.
> Thanks for all your help!
> Jim
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ejcXuBOqEHA.3244@.tk2msftngp13.phx.gbl...
it,[vbcol=seagreen]
failover.[vbcol=seagreen]
Any[vbcol=seagreen]
> in
to[vbcol=seagreen]
> folder
> When
have[vbcol=seagreen]
> a
> sets
I[vbcol=seagreen]
> the
> Server
any[vbcol=seagreen]
> shots
but[vbcol=seagreen]
no[vbcol=seagreen]
being
> installing
> agent
>

Logreader access violation

Hi everyone,
I am setting up Transaction Replication on a MSSQL 2000 8.0.194. Everything
was going fine until the log reader stopped with a "An access violation
occurred" error.
I tried setting up a publication on another test database on the same server
to make sure the problem was not with the database it self and encountered
the same error.
In the ReplExceptLogRdr.log I am getting the following error:
Microsoft SQL Server Replication: Exception Stack Dump
************************************************** *****
Computer type is AT/AT COMPATIBLE.
Bios Version is DELL - 1
Phoenix ROM BIOS PLUS Version 1.10 A10Current local time is Fri Apr 13
15:16:41 2007
4 Intel x86 level 15, 2392 Mhz processor(s).
Windows NT 5.2 Build 3790 CSD .
MemoryLoad 62%TotalPhys 2047 MB
AvailPhys 1481 MBTotalPageFile 4095 MB
************************************************** *****
An exception was caught
in LOGREAD.EXE
* Exception Address = 00000001
* Exception Code = c0000005
*
************************************************** *****
Module NameReturn AddressLocation
[No Module Info]003678f000000001
[No Module Info]0040abd5003678f0
logread0040dec90040abd5
logread0040aa5c0040dec9
logread77e4f38c0040aa5c
kernel3200000000TerminateThread + 113
I have tested setting up replication using the same database on the users
reporting server and everything went fine. I have tried giving the folder
that contains the Distributor database and logfile access to "Everyone".
The Event Viewer show the following error and information:
[SQLSERVERAgent Error]
Microsoft SQL Server Replication : The LOGREAD.EXE executable is terminating
abnormally because it hit an exception. Exception Code c0000005. Check file
ReplExceptLogRdr.log for details.
[Information]
SubSystem Message - Job 'CL-SQL-CLUAT-1'
(0x7A865965F727AB4CA60CC19D5A5EEEA8), step 2 - An access violation occurred.
I tried changing the Logreaders agents verbose level to 3, but nothing extra
appeared in the sqlserver log.
Before I set up replication I had to change the logon the sqlserver agent
was running from the system account to a windows user with Admin rights. The
user also has sql server admin rights.
I am kind of stuck now as I don't know what else I can do to further
investigate the problem.
Any help would really be appreciated.
Thanks,
SQLNewbie
Hi Hillary,
Thanks for your time on this. I did post the contents of the
ReplExceptLogRdr.log in me initial post. It was located in the C:\Program
Files\Microsoft SQL Server\MSSQL\LOG folder. Is this the same log you are
referring to? I am not sure what you mean by (IIRC).
I wasn't sure if this was a bug so I haven't applied any patches.
Is this a user rights problem? That is the user running the SQL Server agent
has insufficient rights, because the user I created has Admin rights for
Windows and System Admin rights for SQL Server.
Thanks,
SQLNEwbie
"Hilary Cotter" wrote:

> I get these from time to time. Did you check ReplExceptLogRdr.log IIRC it
> will be found in windows\system32
> Also does this apply?
> http://support.microsoft.com/kb/872843/EN-US/
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "sqlnewbie" <sqlnewbie@.discussions.microsoft.com> wrote in message
> news:C5CCC218-2858-42BD-97BE-6C0B3AB1054E@.microsoft.com...
>
>
|||Hi,
Just a quick update on this problem. I applied SP4 and that has resolved the
problem.
Thanks
"sqlnewbie" wrote:
[vbcol=seagreen]
> Hi Hillary,
> Thanks for your time on this. I did post the contents of the
> ReplExceptLogRdr.log in me initial post. It was located in the C:\Program
> Files\Microsoft SQL Server\MSSQL\LOG folder. Is this the same log you are
> referring to? I am not sure what you mean by (IIRC).
> I wasn't sure if this was a bug so I haven't applied any patches.
> Is this a user rights problem? That is the user running the SQL Server agent
> has insufficient rights, because the user I created has Admin rights for
> Windows and System Admin rights for SQL Server.
> Thanks,
> SQLNEwbie
> "Hilary Cotter" wrote: