Hi all,
Here is a simple one.
Can I setup SQL mail on a server where the SQL service and agent accounts
are using the local system account? I think I need to set these services to
a domain account, correct?
TIA,
JoeSave yourself some hassle...
http://www.aspfaq.com/2403
"jaylou" <jaylou@.discussions.microsoft.com> wrote in message
news:1AF9ACF1-068E-472E-A547-6A2B30CB25FB@.microsoft.com...
> Hi all,
> Here is a simple one.
> Can I setup SQL mail on a server where the SQL service and agent accounts
> are using the local system account? I think I need to set these services
> to
> a domain account, correct?
> TIA,
> Joe
>
Showing posts with label agent. Show all posts
Showing posts with label agent. Show all posts
Monday, March 12, 2012
Quick SQL Mail Question
Hi all,
Here is a simple one.
Can I setup SQL mail on a server where the SQL service and agent accounts
are using the local system account? I think I need to set these services to
a domain account, correct?
TIA,
Joe
Save yourself some hassle...
http://www.aspfaq.com/2403
"jaylou" <jaylou@.discussions.microsoft.com> wrote in message
news:1AF9ACF1-068E-472E-A547-6A2B30CB25FB@.microsoft.com...
> Hi all,
> Here is a simple one.
> Can I setup SQL mail on a server where the SQL service and agent accounts
> are using the local system account? I think I need to set these services
> to
> a domain account, correct?
> TIA,
> Joe
>
Here is a simple one.
Can I setup SQL mail on a server where the SQL service and agent accounts
are using the local system account? I think I need to set these services to
a domain account, correct?
TIA,
Joe
Save yourself some hassle...
http://www.aspfaq.com/2403
"jaylou" <jaylou@.discussions.microsoft.com> wrote in message
news:1AF9ACF1-068E-472E-A547-6A2B30CB25FB@.microsoft.com...
> Hi all,
> Here is a simple one.
> Can I setup SQL mail on a server where the SQL service and agent accounts
> are using the local system account? I think I need to set these services
> to
> a domain account, correct?
> TIA,
> Joe
>
Saturday, February 25, 2012
QueueSizeMultiplier - Merge Agent Profile Parameter SQL 2005
I see a parameter in the "high volume server-to-server" merge agent profile
named QueueSizeMultiplier.
Can anyone tell me...
The purpose of this paramter
The possible values and their meaning.
Its seems to be undocumented. Default is null, maximum listed seems to be 5.
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
"Pat Clough" <Pat Clough@.discussions.microsoft.com> wrote in message
news:B4E5DBAB-9734-4AC2-BCA3-E85F512F22F0@.microsoft.com...
>I see a parameter in the "high volume server-to-server" merge agent profile
> named QueueSizeMultiplier.
> Can anyone tell me...
> The purpose of this paramter
> The possible values and their meaning.
named QueueSizeMultiplier.
Can anyone tell me...
The purpose of this paramter
The possible values and their meaning.
Its seems to be undocumented. Default is null, maximum listed seems to be 5.
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
"Pat Clough" <Pat Clough@.discussions.microsoft.com> wrote in message
news:B4E5DBAB-9734-4AC2-BCA3-E85F512F22F0@.microsoft.com...
>I see a parameter in the "high volume server-to-server" merge agent profile
> named QueueSizeMultiplier.
> Can anyone tell me...
> The purpose of this paramter
> The possible values and their meaning.
Queue Reader Agent will not start after network failure
Senario
I have a SQL Server 2000 SP4 that is Publisher and distributor plus a SQL
Server 2000 SP3a that is a Publisher.
There replicates to 2 SQL Server 2000 SP4 over the company WAN.
After a roughly 10 min long network failure the queue reader agent will not
start.
Any ideas?
Thanks.
Jonas
Can you enable logging and post the message you get back here?
http://support.microsoft.com/kb/312292
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
"Jonas Larsen" <JonasLarsen@.discussions.microsoft.com> wrote in message
news:7F7768C5-1FF1-4947-8318-9F9A3581A9A3@.microsoft.com...
> Senario
> I have a SQL Server 2000 SP4 that is Publisher and distributor plus a SQL
> Server 2000 SP3a that is a Publisher.
> There replicates to 2 SQL Server 2000 SP4 over the company WAN.
> After a roughly 10 min long network failure the queue reader agent will
> not
> start.
> Any ideas?
> Thanks.
> Jonas
I have a SQL Server 2000 SP4 that is Publisher and distributor plus a SQL
Server 2000 SP3a that is a Publisher.
There replicates to 2 SQL Server 2000 SP4 over the company WAN.
After a roughly 10 min long network failure the queue reader agent will not
start.
Any ideas?
Thanks.
Jonas
Can you enable logging and post the message you get back here?
http://support.microsoft.com/kb/312292
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
"Jonas Larsen" <JonasLarsen@.discussions.microsoft.com> wrote in message
news:7F7768C5-1FF1-4947-8318-9F9A3581A9A3@.microsoft.com...
> Senario
> I have a SQL Server 2000 SP4 that is Publisher and distributor plus a SQL
> Server 2000 SP3a that is a Publisher.
> There replicates to 2 SQL Server 2000 SP4 over the company WAN.
> After a roughly 10 min long network failure the queue reader agent will
> not
> start.
> Any ideas?
> Thanks.
> Jonas
Queue Reader agent fails to start when stopped through Enterprise Menager
I've set up transactional replication with queued updating. If I stop the queue reader agent through EM, I can't start it again. Agent's history says "Queue Reader aborting. The step failed."
All servers are SQL Server 2000 SP3.
Help is greatly appreciated!OK, I found what my problem was (actually not really mine - it's all EM's fault). When you stop the Queue Reader agent through EM, in reality that process is not stoped, but continues to run on the machine. However, the EM doesn't see it and when you try to start it again, of course , it doesn't want to start another instance of Queue Reader agent.
Basically, I had to go and manually stop the process, and only then start it again through EM.
Bad, bad Enterprise Manager!
All servers are SQL Server 2000 SP3.
Help is greatly appreciated!OK, I found what my problem was (actually not really mine - it's all EM's fault). When you stop the Queue Reader agent through EM, in reality that process is not stoped, but continues to run on the machine. However, the EM doesn't see it and when you try to start it again, of course , it doesn't want to start another instance of Queue Reader agent.
Basically, I had to go and manually stop the process, and only then start it again through EM.
Bad, bad Enterprise Manager!
Queue Reader Agent failed
Hi ,
The Queue Reader Agent for my Replication has failed but i am not able to
see the error as there's no Error History details.
1) What does this agent do ?
2) what might cost it to fail ?
It caused the replication to faile but once i start the agent the
replication continues
kindly advise
tks & rdgsThe Queued Reader Agent is used with queued updating (adv feature) with
snapshot and transactional replication.
From the SQL BOL:
Queued updating allows snapshot replication and transactional replication
Subscribers to modify published data without requiring a continuous
connection to the Publisher.
When you create a publication with the queued updating option enabled and a
Subscriber that is enabled for queued updating performs inserts, updates, or
deletes on published data, the changes are stored in a queue. The queued
transactions are applied asynchronously at the Publisher when network
connectivity is restored.
The agent should show up under Agent under Replication in the treeview in
EM. Right-click on the agent in the details pane for history/errors. Also
check the SQL Server and SQL Server Agent error logs for possible errors.
You might also right-click the job associated with the agent in EM for more
details.
HTH
Jerry
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:C8923B13-FDD3-4E66-A628-3236EE80021D@.microsoft.com...
> Hi ,
> The Queue Reader Agent for my Replication has failed but i am not able to
> see the error as there's no Error History details.
> 1) What does this agent do ?
> 2) what might cost it to fail ?
> It caused the replication to faile but once i start the agent the
> replication continues
> kindly advise
> tks & rdgs
The Queue Reader Agent for my Replication has failed but i am not able to
see the error as there's no Error History details.
1) What does this agent do ?
2) what might cost it to fail ?
It caused the replication to faile but once i start the agent the
replication continues
kindly advise
tks & rdgsThe Queued Reader Agent is used with queued updating (adv feature) with
snapshot and transactional replication.
From the SQL BOL:
Queued updating allows snapshot replication and transactional replication
Subscribers to modify published data without requiring a continuous
connection to the Publisher.
When you create a publication with the queued updating option enabled and a
Subscriber that is enabled for queued updating performs inserts, updates, or
deletes on published data, the changes are stored in a queue. The queued
transactions are applied asynchronously at the Publisher when network
connectivity is restored.
The agent should show up under Agent under Replication in the treeview in
EM. Right-click on the agent in the details pane for history/errors. Also
check the SQL Server and SQL Server Agent error logs for possible errors.
You might also right-click the job associated with the agent in EM for more
details.
HTH
Jerry
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:C8923B13-FDD3-4E66-A628-3236EE80021D@.microsoft.com...
> Hi ,
> The Queue Reader Agent for my Replication has failed but i am not able to
> see the error as there's no Error History details.
> 1) What does this agent do ?
> 2) what might cost it to fail ?
> It caused the replication to faile but once i start the agent the
> replication continues
> kindly advise
> tks & rdgs
Queue Reader Agent failed
Hi ,
The Queue Reader Agent for my Replication has failed but i am not able to
see the error as there's no Error History details.
1) What does this agent do ?
2) what might cost it to fail ?
It caused the replication to faile but once i start the agent the
replication continues
kindly advise
tks & rdgsThe Queued Reader Agent is used with queued updating (adv feature) with
snapshot and transactional replication.
From the SQL BOL:
Queued updating allows snapshot replication and transactional replication
Subscribers to modify published data without requiring a continuous
connection to the Publisher.
When you create a publication with the queued updating option enabled and a
Subscriber that is enabled for queued updating performs inserts, updates, or
deletes on published data, the changes are stored in a queue. The queued
transactions are applied asynchronously at the Publisher when network
connectivity is restored.
The agent should show up under Agent under Replication in the treeview in
EM. Right-click on the agent in the details pane for history/errors. Also
check the SQL Server and SQL Server Agent error logs for possible errors.
You might also right-click the job associated with the agent in EM for more
details.
HTH
Jerry
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:C8923B13-FDD3-4E66-A628-3236EE80021D@.microsoft.com...
> Hi ,
> The Queue Reader Agent for my Replication has failed but i am not able to
> see the error as there's no Error History details.
> 1) What does this agent do ?
> 2) what might cost it to fail ?
> It caused the replication to faile but once i start the agent the
> replication continues
> kindly advise
> tks & rdgs
The Queue Reader Agent for my Replication has failed but i am not able to
see the error as there's no Error History details.
1) What does this agent do ?
2) what might cost it to fail ?
It caused the replication to faile but once i start the agent the
replication continues
kindly advise
tks & rdgsThe Queued Reader Agent is used with queued updating (adv feature) with
snapshot and transactional replication.
From the SQL BOL:
Queued updating allows snapshot replication and transactional replication
Subscribers to modify published data without requiring a continuous
connection to the Publisher.
When you create a publication with the queued updating option enabled and a
Subscriber that is enabled for queued updating performs inserts, updates, or
deletes on published data, the changes are stored in a queue. The queued
transactions are applied asynchronously at the Publisher when network
connectivity is restored.
The agent should show up under Agent under Replication in the treeview in
EM. Right-click on the agent in the details pane for history/errors. Also
check the SQL Server and SQL Server Agent error logs for possible errors.
You might also right-click the job associated with the agent in EM for more
details.
HTH
Jerry
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:C8923B13-FDD3-4E66-A628-3236EE80021D@.microsoft.com...
> Hi ,
> The Queue Reader Agent for my Replication has failed but i am not able to
> see the error as there's no Error History details.
> 1) What does this agent do ?
> 2) what might cost it to fail ?
> It caused the replication to faile but once i start the agent the
> replication continues
> kindly advise
> tks & rdgs
Queue Reader Agent failed
Hi ,
The Queue Reader Agent for my Replication has failed but i am not able to
see the error as there's no Error History details.
1) What does this agent do ?
2) what might cost it to fail ?
It caused the replication to faile but once i start the agent the
replication continues
kindly advise
tks & rdgs
The Queued Reader Agent is used with queued updating (adv feature) with
snapshot and transactional replication.
From the SQL BOL:
Queued updating allows snapshot replication and transactional replication
Subscribers to modify published data without requiring a continuous
connection to the Publisher.
When you create a publication with the queued updating option enabled and a
Subscriber that is enabled for queued updating performs inserts, updates, or
deletes on published data, the changes are stored in a queue. The queued
transactions are applied asynchronously at the Publisher when network
connectivity is restored.
The agent should show up under Agent under Replication in the treeview in
EM. Right-click on the agent in the details pane for history/errors. Also
check the SQL Server and SQL Server Agent error logs for possible errors.
You might also right-click the job associated with the agent in EM for more
details.
HTH
Jerry
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:C8923B13-FDD3-4E66-A628-3236EE80021D@.microsoft.com...
> Hi ,
> The Queue Reader Agent for my Replication has failed but i am not able to
> see the error as there's no Error History details.
> 1) What does this agent do ?
> 2) what might cost it to fail ?
> It caused the replication to faile but once i start the agent the
> replication continues
> kindly advise
> tks & rdgs
The Queue Reader Agent for my Replication has failed but i am not able to
see the error as there's no Error History details.
1) What does this agent do ?
2) what might cost it to fail ?
It caused the replication to faile but once i start the agent the
replication continues
kindly advise
tks & rdgs
The Queued Reader Agent is used with queued updating (adv feature) with
snapshot and transactional replication.
From the SQL BOL:
Queued updating allows snapshot replication and transactional replication
Subscribers to modify published data without requiring a continuous
connection to the Publisher.
When you create a publication with the queued updating option enabled and a
Subscriber that is enabled for queued updating performs inserts, updates, or
deletes on published data, the changes are stored in a queue. The queued
transactions are applied asynchronously at the Publisher when network
connectivity is restored.
The agent should show up under Agent under Replication in the treeview in
EM. Right-click on the agent in the details pane for history/errors. Also
check the SQL Server and SQL Server Agent error logs for possible errors.
You might also right-click the job associated with the agent in EM for more
details.
HTH
Jerry
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:C8923B13-FDD3-4E66-A628-3236EE80021D@.microsoft.com...
> Hi ,
> The Queue Reader Agent for my Replication has failed but i am not able to
> see the error as there's no Error History details.
> 1) What does this agent do ?
> 2) what might cost it to fail ?
> It caused the replication to faile but once i start the agent the
> replication continues
> kindly advise
> tks & rdgs
Monday, February 20, 2012
Queue Reader Agent Failed
Hi,
We have set replication between two servers.In subscriber if i update any
row, the transaction is in Msreplication_queue Table.But when it try to push
to publisher it throws a error called "Invalid cursor state". I don't know
where it is going wrong.
what could be the cause of this error.
Thanks in Advance,
Rajesh
Do you have sp4 installed? There was a bug prior to sp4 which gave this
message (http://support.microsoft.com/kb/831997/EN-US/).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Hi
Thanks, Currently we have installed SP3.We have to install it.
"Paul Ibison" wrote:
> Do you have sp4 installed? There was a bug prior to sp4 which gave this
> message (http://support.microsoft.com/kb/831997/EN-US/).
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>
We have set replication between two servers.In subscriber if i update any
row, the transaction is in Msreplication_queue Table.But when it try to push
to publisher it throws a error called "Invalid cursor state". I don't know
where it is going wrong.
what could be the cause of this error.
Thanks in Advance,
Rajesh
Do you have sp4 installed? There was a bug prior to sp4 which gave this
message (http://support.microsoft.com/kb/831997/EN-US/).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Hi
Thanks, Currently we have installed SP3.We have to install it.
"Paul Ibison" wrote:
> Do you have sp4 installed? There was a bug prior to sp4 which gave this
> message (http://support.microsoft.com/kb/831997/EN-US/).
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>
Queue reader agent aborting
Hi,
I'm running transactional replication (SQL Server 2000) with queued updating
between two locations (New Jersey & Arizona). Generally it runs fine, but
about every other week the Queue Reader agent fails with an error message
"Queue reader aborting. The step failed". I can't find any information
regarding the source or nature of the error, and if I try to restart the
agent if fails immediately with the same error. The only way I've been able
to get around the error is to drop the subscription and redo the snapshot.
Does anyone have any suggestions how to determine the source of this error?
Thanks for any help...
Ed
Can you do logging for your queue reader and post the error message you get back here?
Follow the instructions in this kb for more information on how to enable it.
http://support.microsoft.com/default...b;EN-US;312292
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"ed.d@.osgbilling.com" wrote:
> Hi,
> I'm running transactional replication (SQL Server 2000) with queued updating
> between two locations (New Jersey & Arizona). Generally it runs fine, but
> about every other week the Queue Reader agent fails with an error message
> "Queue reader aborting. The step failed". I can't find any information
> regarding the source or nature of the error, and if I try to restart the
> agent if fails immediately with the same error. The only way I've been able
> to get around the error is to drop the subscription and redo the snapshot.
> Does anyone have any suggestions how to determine the source of this error?
> Thanks for any help...
> Ed
>
>
|||Thanks, I'll try adding that logging parameter. What's the best way to stop
the queue reader agent? In the past, I stopped it from enterprise manager by
right clicking and selecting "Stop Agent", but once I do that it often won't
start again...
Ed
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:2AE57792-B5BE-461C-9C5B-347F261FF985@.microsoft.com...
> Can you do logging for your queue reader and post the error message you
get back here?
> Follow the instructions in this kb for more information on how to enable
it.[vbcol=seagreen]
> http://support.microsoft.com/default...b;EN-US;312292
>
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
>
> "ed.d@.osgbilling.com" wrote:
updating[vbcol=seagreen]
but[vbcol=seagreen]
message[vbcol=seagreen]
able[vbcol=seagreen]
snapshot.[vbcol=seagreen]
error?[vbcol=seagreen]
|||For me the only reliable way to stop the queue reader and log reader agents is to stop the SQL Server agent.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"ed.d@.osgbilling.com" wrote:
> Thanks, I'll try adding that logging parameter. What's the best way to stop
> the queue reader agent? In the past, I stopped it from enterprise manager by
> right clicking and selecting "Stop Agent", but once I do that it often won't
> start again...
> Ed
>
>
> "Hilary Cotter" <hilaryk@.att.net> wrote in message
> news:2AE57792-B5BE-461C-9C5B-347F261FF985@.microsoft.com...
> get back here?
> it.
> updating
> but
> message
> able
> snapshot.
> error?
>
>
|||Thanks again. Now I'm just waiting for it to fail...
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:40F318EA-ACF6-4B3A-865D-7B33B00F305E@.microsoft.com...
> For me the only reliable way to stop the queue reader and log reader
agents is to stop the SQL Server agent.[vbcol=seagreen]
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
>
> "ed.d@.osgbilling.com" wrote:
stop[vbcol=seagreen]
manager by[vbcol=seagreen]
won't[vbcol=seagreen]
you[vbcol=seagreen]
enable[vbcol=seagreen]
fine,[vbcol=seagreen]
information[vbcol=seagreen]
the[vbcol=seagreen]
been[vbcol=seagreen]
|||Hi,
The queue reader failed. Below is the output from the log. Any insight you
have would be greatly appreciated.
Ed
Microsoft SQL Server Replication Queue Reader Agent 8.00.760
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: [SLIM].12
Connecting to QueueReader 'SLIM.Billing'
Server: SLIM
DBMS: Microsoft SQL Server
Version: 08.00.0760
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[6/22/2004 12:57:11 PM]SLIM.Billing: select count(*) from
master.dbo.sysprocesses where [program_name] = 'Queue Reader Main (Billing)'
[6/22/2004 12:57:11 PM]SLIM.Billing: select top 1 id, name from
MSqreader_agents
Server: SLIM, Database Billing : ODBC Error:Invalid object name
'MSqreader_agents'.
Unable to connect to Local Distributor
Queue Reader aborting
|||can you check to see if this table exists in your local distribution database?
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"ed.d@.osgbilling.com" wrote:
> Hi,
> The queue reader failed. Below is the output from the log. Any insight you
> have would be greatly appreciated.
> Ed
> Microsoft SQL Server Replication Queue Reader Agent 8.00.760
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: [SLIM].12
> Connecting to QueueReader 'SLIM.Billing'
> Server: SLIM
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [6/22/2004 12:57:11 PM]SLIM.Billing: select count(*) from
> master.dbo.sysprocesses where [program_name] = 'Queue Reader Main (Billing)'
> [6/22/2004 12:57:11 PM]SLIM.Billing: select top 1 id, name from
> MSqreader_agents
> Server: SLIM, Database Billing : ODBC Error:Invalid object name
> 'MSqreader_agents'.
> Unable to connect to Local Distributor
> Queue Reader aborting
>
>
|||The table does exist - but I thought it was odd that the statements
contained references to the "Billing" database. That's a database on the
server, but it's not part of replication. Digging into the job under SQL
Server Agent, I saw that the queue reader step was set to run in the
"Billing" database. I'm guessing someone changed that setting
unintentionally. I changed it to run under the "distribution" database, and
the step restarted fine.
Thanks for the tip on logging the output - it would have been impossible to
figure this out without it
Ed
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:810FBB09-2770-4D9C-A07B-ED917F4B9E32@.microsoft.com...
> can you check to see if this table exists in your local distribution
database?[vbcol=seagreen]
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
>
> "ed.d@.osgbilling.com" wrote:
you[vbcol=seagreen]
(Billing)'[vbcol=seagreen]
I'm running transactional replication (SQL Server 2000) with queued updating
between two locations (New Jersey & Arizona). Generally it runs fine, but
about every other week the Queue Reader agent fails with an error message
"Queue reader aborting. The step failed". I can't find any information
regarding the source or nature of the error, and if I try to restart the
agent if fails immediately with the same error. The only way I've been able
to get around the error is to drop the subscription and redo the snapshot.
Does anyone have any suggestions how to determine the source of this error?
Thanks for any help...
Ed
Can you do logging for your queue reader and post the error message you get back here?
Follow the instructions in this kb for more information on how to enable it.
http://support.microsoft.com/default...b;EN-US;312292
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"ed.d@.osgbilling.com" wrote:
> Hi,
> I'm running transactional replication (SQL Server 2000) with queued updating
> between two locations (New Jersey & Arizona). Generally it runs fine, but
> about every other week the Queue Reader agent fails with an error message
> "Queue reader aborting. The step failed". I can't find any information
> regarding the source or nature of the error, and if I try to restart the
> agent if fails immediately with the same error. The only way I've been able
> to get around the error is to drop the subscription and redo the snapshot.
> Does anyone have any suggestions how to determine the source of this error?
> Thanks for any help...
> Ed
>
>
|||Thanks, I'll try adding that logging parameter. What's the best way to stop
the queue reader agent? In the past, I stopped it from enterprise manager by
right clicking and selecting "Stop Agent", but once I do that it often won't
start again...
Ed
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:2AE57792-B5BE-461C-9C5B-347F261FF985@.microsoft.com...
> Can you do logging for your queue reader and post the error message you
get back here?
> Follow the instructions in this kb for more information on how to enable
it.[vbcol=seagreen]
> http://support.microsoft.com/default...b;EN-US;312292
>
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
>
> "ed.d@.osgbilling.com" wrote:
updating[vbcol=seagreen]
but[vbcol=seagreen]
message[vbcol=seagreen]
able[vbcol=seagreen]
snapshot.[vbcol=seagreen]
error?[vbcol=seagreen]
|||For me the only reliable way to stop the queue reader and log reader agents is to stop the SQL Server agent.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"ed.d@.osgbilling.com" wrote:
> Thanks, I'll try adding that logging parameter. What's the best way to stop
> the queue reader agent? In the past, I stopped it from enterprise manager by
> right clicking and selecting "Stop Agent", but once I do that it often won't
> start again...
> Ed
>
>
> "Hilary Cotter" <hilaryk@.att.net> wrote in message
> news:2AE57792-B5BE-461C-9C5B-347F261FF985@.microsoft.com...
> get back here?
> it.
> updating
> but
> message
> able
> snapshot.
> error?
>
>
|||Thanks again. Now I'm just waiting for it to fail...
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:40F318EA-ACF6-4B3A-865D-7B33B00F305E@.microsoft.com...
> For me the only reliable way to stop the queue reader and log reader
agents is to stop the SQL Server agent.[vbcol=seagreen]
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
>
> "ed.d@.osgbilling.com" wrote:
stop[vbcol=seagreen]
manager by[vbcol=seagreen]
won't[vbcol=seagreen]
you[vbcol=seagreen]
enable[vbcol=seagreen]
fine,[vbcol=seagreen]
information[vbcol=seagreen]
the[vbcol=seagreen]
been[vbcol=seagreen]
|||Hi,
The queue reader failed. Below is the output from the log. Any insight you
have would be greatly appreciated.
Ed
Microsoft SQL Server Replication Queue Reader Agent 8.00.760
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: [SLIM].12
Connecting to QueueReader 'SLIM.Billing'
Server: SLIM
DBMS: Microsoft SQL Server
Version: 08.00.0760
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[6/22/2004 12:57:11 PM]SLIM.Billing: select count(*) from
master.dbo.sysprocesses where [program_name] = 'Queue Reader Main (Billing)'
[6/22/2004 12:57:11 PM]SLIM.Billing: select top 1 id, name from
MSqreader_agents
Server: SLIM, Database Billing : ODBC Error:Invalid object name
'MSqreader_agents'.
Unable to connect to Local Distributor
Queue Reader aborting
|||can you check to see if this table exists in your local distribution database?
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"ed.d@.osgbilling.com" wrote:
> Hi,
> The queue reader failed. Below is the output from the log. Any insight you
> have would be greatly appreciated.
> Ed
> Microsoft SQL Server Replication Queue Reader Agent 8.00.760
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: [SLIM].12
> Connecting to QueueReader 'SLIM.Billing'
> Server: SLIM
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [6/22/2004 12:57:11 PM]SLIM.Billing: select count(*) from
> master.dbo.sysprocesses where [program_name] = 'Queue Reader Main (Billing)'
> [6/22/2004 12:57:11 PM]SLIM.Billing: select top 1 id, name from
> MSqreader_agents
> Server: SLIM, Database Billing : ODBC Error:Invalid object name
> 'MSqreader_agents'.
> Unable to connect to Local Distributor
> Queue Reader aborting
>
>
|||The table does exist - but I thought it was odd that the statements
contained references to the "Billing" database. That's a database on the
server, but it's not part of replication. Digging into the job under SQL
Server Agent, I saw that the queue reader step was set to run in the
"Billing" database. I'm guessing someone changed that setting
unintentionally. I changed it to run under the "distribution" database, and
the step restarted fine.
Thanks for the tip on logging the output - it would have been impossible to
figure this out without it
Ed
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:810FBB09-2770-4D9C-A07B-ED917F4B9E32@.microsoft.com...
> can you check to see if this table exists in your local distribution
database?[vbcol=seagreen]
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
>
> "ed.d@.osgbilling.com" wrote:
you[vbcol=seagreen]
(Billing)'[vbcol=seagreen]
Subscribe to:
Posts (Atom)