Raid5 and Suspect DB

I have a DB on a Raid 5 of 4 disks. One of the disks failed, freezed the
screen and everything else,
I was obliged to reboot
After reboot, My DB was in suspectmode, First question, if I am not
mistaken, as far as it is raid 5, the DB must not be in suspect mode
Ok, I used the last good full backup, DB came back on line. 2 hours or more
the same thing happened.
I wonder what is the efficiency of RAID 5
Perhaps the database was exactly in the middle of IOs and the Raid did not
cover it...Was the Raid array continuously available?
Asingle disk failure on Raid 5 should not have affected anything.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"SalamElias" <eliassal@.online.nospam> wrote in message
news:C7D83256-BDCA-41D4-A45C-214CF0F47202@.microsoft.com...
> I have a DB on a Raid 5 of 4 disks. One of the disks failed, freezed the
> screen and everything else,
> I was obliged to reboot
> After reboot, My DB was in suspectmode, First question, if I am not
> mistaken, as far as it is raid 5, the DB must not be in suspect mode
> Ok, I used the last good full backup, DB came back on line. 2 hours or
more
> the same thing happened.
> I wonder what is the efficiency of RAID 5
|||Thanks for your response, when you say DB was in the middle of IOs, I
understand when reading Books on line or any other docs regarding DBs
recovery plan should be able to handle these events (rol back or roll forward
in case of disk failure. AmI mistaken?
I confirm it wa a one disk failure. Also one more strange thing happened, I
changed the faulty disk, deleted the database, tried to recreate it, It was
not possible (got error messages). I changed the physical datafile place (on
the raid 0 log disk), DB was created. Any ideas or thoughts.
Thanks again
"Wayne Snyder" wrote:

> Perhaps the database was exactly in the middle of IOs and the Raid did not
> cover it...Was the Raid array continuously available?
> Asingle disk failure on Raid 5 should not have affected anything.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "SalamElias" <eliassal@.online.nospam> wrote in message
> news:C7D83256-BDCA-41D4-A45C-214CF0F47202@.microsoft.com...
> more
>
>

Raid5 and Suspect DB

I have a DB on a Raid 5 of 4 disks. One of the disks failed, freezed the
screen and everything else,
I was obliged to reboot
After reboot, My DB was in suspectmode, First question, if I am not
mistaken, as far as it is raid 5, the DB must not be in suspect mode
Ok, I used the last good full backup, DB came back on line. 2 hours or more
the same thing happened.
I wonder what is the efficiency of RAID 5Perhaps the database was exactly in the middle of IOs and the Raid did not
cover it...Was the Raid array continuously available?
Asingle disk failure on Raid 5 should not have affected anything.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"SalamElias" <eliassal@.online.nospam> wrote in message
news:C7D83256-BDCA-41D4-A45C-214CF0F47202@.microsoft.com...
> I have a DB on a Raid 5 of 4 disks. One of the disks failed, freezed the
> screen and everything else,
> I was obliged to reboot
> After reboot, My DB was in suspectmode, First question, if I am not
> mistaken, as far as it is raid 5, the DB must not be in suspect mode
> Ok, I used the last good full backup, DB came back on line. 2 hours or
more
> the same thing happened.
> I wonder what is the efficiency of RAID 5|||Thanks for your response, when you say DB was in the middle of IOs, I
understand when reading Books on line or any other docs regarding DBs
recovery plan should be able to handle these events (rol back or roll forwar
d
in case of disk failure. AmI mistaken?
I confirm it wa a one disk failure. Also one more strange thing happened, I
changed the faulty disk, deleted the database, tried to recreate it, It was
not possible (got error messages). I changed the physical datafile place (on
the raid 0 log disk), DB was created. Any ideas or thoughts.
Thanks again
"Wayne Snyder" wrote:

> Perhaps the database was exactly in the middle of IOs and the Raid did not
> cover it...Was the Raid array continuously available?
> Asingle disk failure on Raid 5 should not have affected anything.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "SalamElias" <eliassal@.online.nospam> wrote in message
> news:C7D83256-BDCA-41D4-A45C-214CF0F47202@.microsoft.com...
> more
>
>

Raid Array Failure/Rebuild SQL won''t run

Background... Server raid failed, rebuilt raid ran chkdsk but now I am
unable to run SQL service.

I've tried to manually start service but receive the following message

The MSSQLSERVER service on the local computer started and then stopped. Some
services stop automatically if they have no work to do.

Here's all I have in the error logs

2007-08-19 10:56:39.98 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Developer Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

2007-08-19 10:56:39.99 server Copyright (C) 1988-2002 Microsoft
Corporation.
2007-08-19 10:56:39.99 server All rights reserved.
2007-08-19 10:56:39.99 server Server Process ID is 1812.
2007-08-19 10:56:39.99 server Logging SQL Server messages in file
'f:\MSSQL\log\ERRORLOG'.
2007-08-19 10:56:40.01 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2007-08-19 10:56:40.15 server SQL Server configured for thread mode
processing.
2007-08-19 10:56:40.18 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2007-08-19 10:56:40.23 server Attempting to initialize Distributed
Transaction Coordinator.
2007-08-19 10:56:42.29 spid4 Starting up database 'master'.
2007-08-19 10:56:42.31 spid4 Error: 5172, Severity: 16, State: 15.
2007-08-19 10:56:42.31 spid4 Error: 5173, Severity: 16, State: 1.
2007-08-19 10:56:42.31 spid4 Error: 5180, Severity: 22, State: 1.

Is sql server running under a service account and did you change the pwd ? is there any specific info in the event viewer ?

|||

With some assistance I ran rebuildm.exe and was able to get sql up and running.

I have been able to go through the steps to create a new database of same name then copy originals, restart SQL and bring the databases back in suspect mode.

I'm trying to read up on how to set the databases to emergency mode, check for errors and hopefully bring back to working, normal state....

Raid Array Failure/Rebuild SQL won''t run

Background... Server raid failed, rebuilt raid ran chkdsk but now I am
unable to run SQL service.

I've tried to manually start service but receive the following message

The MSSQLSERVER service on the local computer started and then stopped. Some
services stop automatically if they have no work to do.

Here's all I have in the error logs

2007-08-19 10:56:39.98 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Developer Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

2007-08-19 10:56:39.99 server Copyright (C) 1988-2002 Microsoft
Corporation.
2007-08-19 10:56:39.99 server All rights reserved.
2007-08-19 10:56:39.99 server Server Process ID is 1812.
2007-08-19 10:56:39.99 server Logging SQL Server messages in file
'f:\MSSQL\log\ERRORLOG'.
2007-08-19 10:56:40.01 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2007-08-19 10:56:40.15 server SQL Server configured for thread mode
processing.
2007-08-19 10:56:40.18 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2007-08-19 10:56:40.23 server Attempting to initialize Distributed
Transaction Coordinator.
2007-08-19 10:56:42.29 spid4 Starting up database 'master'.
2007-08-19 10:56:42.31 spid4 Error: 5172, Severity: 16, State: 15.
2007-08-19 10:56:42.31 spid4 Error: 5173, Severity: 16, State: 1.
2007-08-19 10:56:42.31 spid4 Error: 5180, Severity: 22, State: 1.

Is sql server running under a service account and did you change the pwd ? is there any specific info in the event viewer ?

|||

With some assistance I ran rebuildm.exe and was able to get sql up and running.

I have been able to go through the steps to create a new database of same name then copy originals, restart SQL and bring the databases back in suspect mode.

I'm trying to read up on how to set the databases to emergency mode, check for errors and hopefully bring back to working, normal state....

Raid Array Failure/Rebuild SQL won''t run

Background... Server raid failed, rebuilt raid ran chkdsk but now I am
unable to run SQL service.

I've tried to manually start service but receive the following message

The MSSQLSERVER service on the local computer started and then stopped. Some
services stop automatically if they have no work to do.

Here's all I have in the error logs

2007-08-19 10:56:39.98 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Developer Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

2007-08-19 10:56:39.99 server Copyright (C) 1988-2002 Microsoft
Corporation.
2007-08-19 10:56:39.99 server All rights reserved.
2007-08-19 10:56:39.99 server Server Process ID is 1812.
2007-08-19 10:56:39.99 server Logging SQL Server messages in file
'f:\MSSQL\log\ERRORLOG'.
2007-08-19 10:56:40.01 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2007-08-19 10:56:40.15 server SQL Server configured for thread mode
processing.
2007-08-19 10:56:40.18 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2007-08-19 10:56:40.23 server Attempting to initialize Distributed
Transaction Coordinator.
2007-08-19 10:56:42.29 spid4 Starting up database 'master'.
2007-08-19 10:56:42.31 spid4 Error: 5172, Severity: 16, State: 15.
2007-08-19 10:56:42.31 spid4 Error: 5173, Severity: 16, State: 1.
2007-08-19 10:56:42.31 spid4 Error: 5180, Severity: 22, State: 1.

Is sql server running under a service account and did you change the pwd ? is there any specific info in the event viewer ?

|||

With some assistance I ran rebuildm.exe and was able to get sql up and running.

I have been able to go through the steps to create a new database of same name then copy originals, restart SQL and bring the databases back in suspect mode.

I'm trying to read up on how to set the databases to emergency mode, check for errors and hopefully bring back to working, normal state....

QUOTED_IDENTIFIER and ARITHABORT for Maintenance plans

Hi,
I would like to setup a maintenance job to 'Rebuild Indexes' as my
'Optimization Job' keeps failing on "DBCC failed because the following set
options have incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
What command do I need to use to rebuild all the indexes on all the tables.
I see DBCC DBREINDEX but that needs table name as a parameter. Any kind of
help is greatly appreciated.
Thank you
Take a look at DBCC SHOWCONTIG in BooksOnLine for the sample near the
bottom. This will rebuild the indexes that actually require it given
certain percentage of fragmentation.
Andrew J. Kelly SQL MVP
"helpplease" <helpplease@.discussions.microsoft.com> wrote in message
news:7DB5F397-1671-4F97-9585-AC7C20382FA1@.microsoft.com...
> Hi,
> I would like to setup a maintenance job to 'Rebuild Indexes' as my
> 'Optimization Job' keeps failing on "DBCC failed because the following set
> options have incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
> What command do I need to use to rebuild all the indexes on all the
> tables.
> I see DBCC DBREINDEX but that needs table name as a parameter. Any kind
> of
> help is greatly appreciated.
> Thank you

QUOTED_IDENTIFIER and ARITHABORT for Maintenance plans

Hi,
I would like to setup a maintenance job to 'Rebuild Indexes' as my
'Optimization Job' keeps failing on "DBCC failed because the following set
options have incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
What command do I need to use to rebuild all the indexes on all the tables.
I see DBCC DBREINDEX but that needs table name as a parameter. Any kind of
help is greatly appreciated.
Thank youTake a look at DBCC SHOWCONTIG in BooksOnLine for the sample near the
bottom. This will rebuild the indexes that actually require it given
certain percentage of fragmentation.
Andrew J. Kelly SQL MVP
"helpplease" <helpplease@.discussions.microsoft.com> wrote in message
news:7DB5F397-1671-4F97-9585-AC7C20382FA1@.microsoft.com...
> Hi,
> I would like to setup a maintenance job to 'Rebuild Indexes' as my
> 'Optimization Job' keeps failing on "DBCC failed because the following set
> options have incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
> What command do I need to use to rebuild all the indexes on all the
> tables.
> I see DBCC DBREINDEX but that needs table name as a parameter. Any kind
> of
> help is greatly appreciated.
> Thank you

QUOTED_IDENTIFIER and ARITHABORT for Maintenance plans

Hi,
I would like to setup a maintenance job to 'Rebuild Indexes' as my
'Optimization Job' keeps failing on "DBCC failed because the following set
options have incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
What command do I need to use to rebuild all the indexes on all the tables.
I see DBCC DBREINDEX but that needs table name as a parameter. Any kind of
help is greatly appreciated.
Thank youTake a look at DBCC SHOWCONTIG in BooksOnLine for the sample near the
bottom. This will rebuild the indexes that actually require it given
certain percentage of fragmentation.
--
Andrew J. Kelly SQL MVP
"helpplease" <helpplease@.discussions.microsoft.com> wrote in message
news:7DB5F397-1671-4F97-9585-AC7C20382FA1@.microsoft.com...
> Hi,
> I would like to setup a maintenance job to 'Rebuild Indexes' as my
> 'Optimization Job' keeps failing on "DBCC failed because the following set
> options have incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
> What command do I need to use to rebuild all the indexes on all the
> tables.
> I see DBCC DBREINDEX but that needs table name as a parameter. Any kind
> of
> help is greatly appreciated.
> Thank you

quoted_identifier

Hi
I am getting this strange error :
Server: Msg 1934, Level 16, State 1, Procedure
dataIntegration_mergeCompanyData_prc, Line 90
UPDATE failed because the following SET options have incorrect settings:
'QUOTED_IDENTIFIER'
the problem seem to be with a table in an update statement in the proc where
it references a table in an index view. if I change the left outer join of
the update statement to an inner join, the error goes away, if I uncomment
the schema_binding in the index view, the error also goes away.
anyone know what is going on?
thanks
PAny time you access an indexed view the connection must have certain SET
settings such as QUOTED_IDENTIFIER set a certain way. Look up Indexed Views
and then Set options that affect results underneath that for details.
Andrew J. Kelly SQL MVP
"alfred" <alfred@.discussions.microsoft.com> wrote in message
news:79578F94-688A-4A17-B8BA-D6418C437AEA@.microsoft.com...
> Hi
> I am getting this strange error :
> Server: Msg 1934, Level 16, State 1, Procedure
> dataIntegration_mergeCompanyData_prc, Line 90
> UPDATE failed because the following SET options have incorrect settings:
> 'QUOTED_IDENTIFIER'
> the problem seem to be with a table in an update statement in the proc
> where
> it references a table in an index view. if I change the left outer join
> of
> the update statement to an inner join, the error goes away, if I uncomment
> the schema_binding in the index view, the error also goes away.
> anyone know what is going on?
> thanks
> P
>|||alfred (alfred@.discussions.microsoft.com) writes:
> I am getting this strange error :
> Server: Msg 1934, Level 16, State 1, Procedure
> dataIntegration_mergeCompanyData_prc, Line 90
> UPDATE failed because the following SET options have incorrect settings:
> 'QUOTED_IDENTIFIER'
> the problem seem to be with a table in an update statement in the proc
> where it references a table in an index view. if I change the left
> outer join of the update statement to an inner join, the error goes
> away, if I uncomment the schema_binding in the index view, the error
> also goes away.
> anyone know what is going on?
As Andrew said, you are performing an update that affects an indexed
view. Whenever the you work with an indexed view, these settings must
be on: ANSI_NULLS, QUOTED_IDENTIFIER, ANSI_WARNINGS, ANSI_PADDNING,
CONCAT_NULL_YIELDS_NULL and ARITHABORT. All but the last option are
on by default when you connect with any API but DB-Library.
However, for the first two settings, what applies when you run a stored
procedure is not the setting for the connection, as these settings are
saved with the stored procedure.
And very unfortunate, there are two tools for which QUOTED_IDENTIFIER
is off by default: OSQL and Enterprise Manager (the latter also has
ANSI_NULLS off by default). Therefore, if you use these tools, you
must take precautions to make sure that this setting is on. If you
use OSQL, use the -I option to turn on QUOTED_IDENFIER. If you use
Enterprise Manager to edit your procedures, simply stop doing that
and use Query Analyzer instead. QA does not have this issue, and is
better editor anyway.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspxsql

Quick DTS import question

I did a DTS import in SQL Server and it said that it failed to copydata between sql server to sql server, but when I do some basicrowchecks and run the application that uses the db, it appears that itdid in fact copy all the data. I noticed that the mdf and ldffiles are smaller than the source db, but I know this is common for anldf? Is it common for an mdf to shrink during dts? Can Idisregard that DTS wizard error since it appears the data was copiedover?

thanks!Run SELECT * against the tables in Query Aanalyzer and click on show results in a grid before execution to verify the move before ignoring the error. Hope this helps.|||Thanks - I'll give it a shot!

Queue Reader ODBC Error: Login failed for user "sa"

After implementing a password for the sa account, I'm getting the error:
ODBC Error: Login failed for user "sa"
I thought that there was stored procedure where I could set the password for
the Queue Reader Agent but I can't find it. Can anyone assist me here or
have any insight into this error?
Thanks in advance.
does this help?
http://support.microsoft.com/default...&Product=sql2k
"Salty Dog" <Salty Dog@.discussions.microsoft.com> wrote in message
news:7B1EB304-FC0E-4495-AB1E-44AC6666634E@.microsoft.com...
> After implementing a password for the sa account, I'm getting the error:
> ODBC Error: Login failed for user "sa"
> I thought that there was stored procedure where I could set the password
> for
> the Queue Reader Agent but I can't find it. Can anyone assist me here or
> have any insight into this error?
> Thanks in advance.
|||This looks like the information that I need. Thank you so much and I will
get back after I apply.
"Hilary Cotter" wrote:

> does this help?
> http://support.microsoft.com/default...&Product=sql2k
> "Salty Dog" <Salty Dog@.discussions.microsoft.com> wrote in message
> news:7B1EB304-FC0E-4495-AB1E-44AC6666634E@.microsoft.com...
>
>
|||Still the same error. I've recreated the Publisher and Subscriptions several
time and still not go. I have Subscription security using sa with password
instead of NT authentication. I'm really stumped or could you tell?
I'm configured for Immediate with Queued for failover. This was working
prior to adding a password. Any other help you can give me?
Another note: Prior to a complete startover of creating the Publisher and
all, I was getting the same error. The crazy thing was that the Red Error Xs
would disappear every once in a while and processing would resume like
everything was OK for just a few seconds. It would stay down longer than
logged on/up and running.
"Salty Dog" wrote:
[vbcol=seagreen]
> This looks like the information that I need. Thank you so much and I will
> get back after I apply.
> "Hilary Cotter" wrote:
|||More info...
The same symptom of it works a bit and then fails is happening again. I
think that this is just indicating that everything else is working except
communication between the subscriber and distributor/publisher so this is
probably not relevant.
The Queue Reader logon is still not passing the password. All other agents
are running fine. Still stumped and still really appreciating your help.
"Salty Dog" wrote:

> After implementing a password for the sa account, I'm getting the error:
> ODBC Error: Login failed for user "sa"
> I thought that there was stored procedure where I could set the password for
> the Queue Reader Agent but I can't find it. Can anyone assist me here or
> have any insight into this error?
> Thanks in advance.
|||authentication is done on a exe level. Can you right click on your queue
reader agent, select agent properties, run steps, and click on the run agent
command. What is your sa password there? It should be something encrypted.
Is there no way you can use trusted authentication to bypass this problem?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Salty Dog" <SaltyDog@.discussions.microsoft.com> wrote in message
news:805E9ECC-CD66-489C-8977-0B2DF77CD4C6@.microsoft.com...
> Still the same error. I've recreated the Publisher and Subscriptions
several
> time and still not go. I have Subscription security using sa with
password
> instead of NT authentication. I'm really stumped or could you tell?
> I'm configured for Immediate with Queued for failover. This was working
> prior to adding a password. Any other help you can give me?
> Another note: Prior to a complete startover of creating the Publisher and
> all, I was getting the same error. The crazy thing was that the Red Error
Xs[vbcol=seagreen]
> would disappear every once in a while and processing would resume like
> everything was OK for just a few seconds. It would stay down longer than
> logged on/up and running.
>
> "Salty Dog" wrote:
will[vbcol=seagreen]
http://support.microsoft.com/default...&Product=sql2k[vbcol=seagreen]
error:[vbcol=seagreen]
password[vbcol=seagreen]
here or[vbcol=seagreen]

QUEUE READER FAILS! Help...

Hi,
We are using transactional replication with queued updating between
SQL2000 Servers (Win 2003).
1) The queue reader has failed with the error message "Queue Reader
aborting. The step failed."
The error details stack shows (from last to first):
Queue Reader aborting. The step failed
Processed 53 queued trans, 105 cmds, 1 conflicts
Failed while applying queued message to publisher
CQueueRdrRowChange: ApplyCommand: Failed to create instance of
pMessage->pParams(ProcParams)
What's causing this? How can I restart the Queue Reader Agent after the
failure?
thanks,
Fabio
I take it that the error repeats next time you run the queue reader. To
restart it after failure I would put it on a schedule of every 5 minutes.
You can have it return to job step 1 on failure.
How many subscribers do you have? Also queued is designed for less than 10
subscribers and where the majority of the DML occurs on the publisher - does
your topology fit into this case?
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
<fabio.pliger@.gmail.com> wrote in message
news:1164187151.581038.182820@.j44g2000cwa.googlegr oups.com...
> Hi,
> We are using transactional replication with queued updating between
> SQL2000 Servers (Win 2003).
> 1) The queue reader has failed with the error message "Queue Reader
> aborting. The step failed."
> The error details stack shows (from last to first):
> Queue Reader aborting. The step failed
> Processed 53 queued trans, 105 cmds, 1 conflicts
> Failed while applying queued message to publisher
> CQueueRdrRowChange: ApplyCommand: Failed to create instance of
> pMessage->pParams(ProcParams)
> What's causing this? How can I restart the Queue Reader Agent after the
> failure?
> thanks,
> Fabio
>
|||Yes, the error repeates everytime i re-run the queue reader.. and it
always returns me those actions:
- Queue reader aborting...
- Processing ## queued trans, ## cmds, ## conflicts
- Failed whiale applying queued message to publisher
- CQueuedRdrRowChange::ApplyCommand: Failed.... bla bla...
- Queue Reader Agent blabla Started
- Starting agent
I do have 5 subscribers. 4 of those have a filter by column on only one
table.
Much DML occurs also at the subscribers...
I see that after the agentes fails... data from 2 of the subscribers is
sent to the publisher (and their Ms_replication_queue table il empty,
but no data from the others subscribers is sent to the publisher and
their replication queue table is unchanged... Can help if i delete all
the records in those tables at the subscribers?
What kind of error is that? Any hint on what i can look at to solve it?
thanks,
Fabio
Hilary Cotter ha scritto:
[vbcol=seagreen]
> I take it that the error repeats next time you run the queue reader. To
> restart it after failure I would put it on a schedule of every 5 minutes.
> You can have it return to job step 1 on failure.
> How many subscribers do you have? Also queued is designed for less than 10
> subscribers and where the majority of the DML occurs on the publisher - does
> your topology fit into this case?
> --
> 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
>
> <fabio.pliger@.gmail.com> wrote in message
> news:1164187151.581038.182820@.j44g2000cwa.googlegr oups.com...
|||Can you enable logging? Follow these steps
http://support.microsoft.com/default.aspx?scid=kb;en-us;312292&sd=tech
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
<fabio.pliger@.gmail.com> wrote in message
news:1164207423.995497.310220@.h48g2000cwc.googlegr oups.com...
> Yes, the error repeates everytime i re-run the queue reader.. and it
> always returns me those actions:
> - Queue reader aborting...
> - Processing ## queued trans, ## cmds, ## conflicts
> - Failed whiale applying queued message to publisher
> - CQueuedRdrRowChange::ApplyCommand: Failed.... bla bla...
> - Queue Reader Agent blabla Started
> - Starting agent
> I do have 5 subscribers. 4 of those have a filter by column on only one
> table.
> Much DML occurs also at the subscribers...
> I see that after the agentes fails... data from 2 of the subscribers is
> sent to the publisher (and their Ms_replication_queue table il empty,
> but no data from the others subscribers is sent to the publisher and
> their replication queue table is unchanged... Can help if i delete all
> the records in those tables at the subscribers?
> What kind of error is that? Any hint on what i can look at to solve it?
> thanks,
> Fabio
>
> Hilary Cotter ha scritto:
>
|||Here's what i get:
Connecting to QueueReader 'WN055.distribution'
Queue Reader Agent [WN055].8 (Id = 5) started
[11/22/2006 4:32:11 PM]WN055.distribution: execute
dbo.sp_MShelp_profile 5, 9, N''
Connecting to WN046 'WN046.FDF'
[11/22/2006 4:32:11 PM]WN055.distribution: exec
dbo.sp_helpdistpublisher @.publisher = N'WN055'
Connecting to WN055 'WN055.FDF'
SQL Command : <exec [dbo].[sp_MSsync_ins_Aut_LogBatch_3] N'WN046',
N'FDF', 250008816, 250000361, N'AUTO', '2006-11-22 16:19:32.000',
N'34B4', '5992D20D-A9E7-40AF-AB71-43F650E4E8AC', 1>
Disconnecting from WN055 'WN055'
Disconnecting from WN046 'WN046'
Connecting to WN030 'WN030.FDF'
[11/22/2006 4:32:26 PM]WN055.distribution: exec
dbo.sp_helpdistpublisher @.publisher = N'WN055'
Connecting to WN055 'WN055.FDF'
CQueueRdrRowChange::ApplyCommand:Failed to create instance of
pMessage->pParams(ProcParams)
Failed while applying queued message to publisher
Disconnecting from WN055 'WN055'
Worker Thread 540 : Task Failed
Disconnecting from WN030 'WN030'
Processed 29 queued trans, 57 cmds, 0 conflicts
Queue Reader aborting
It seem's like the subscriber WN030has some problems comunicating with
publisher-... right? Any hint?
Fabio
Hilary Cotter ha scritto:
[vbcol=seagreen]
> Can you enable logging? Follow these steps
> http://support.microsoft.com/default.aspx?scid=kb;en-us;312292&sd=tech
> --
> 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
>
> <fabio.pliger@.gmail.com> wrote in message
> news:1164207423.995497.310220@.h48g2000cwc.googlegr oups.com...
|||I've shutedown the sqlserveragent at the subscriber WN030 (the one
generating the error...) and the queue reader agent don't fails
anymore... So.. bypassing this subscriber the agent is able to run..
but my goal is to solve the problem and reconnect the subscriber...
Deleting the MS_replicationqueue at tje subscriber can help? I would
prefer to don't loose those transactions... but if it's the only way i
can delete it...
thanks,
Fabio
fabio.pliger@.gmail.com ha scritto:
[vbcol=seagreen]
> Here's what i get:
> Connecting to QueueReader 'WN055.distribution'
> Queue Reader Agent [WN055].8 (Id = 5) started
> [11/22/2006 4:32:11 PM]WN055.distribution: execute
> dbo.sp_MShelp_profile 5, 9, N''
> Connecting to WN046 'WN046.FDF'
> [11/22/2006 4:32:11 PM]WN055.distribution: exec
> dbo.sp_helpdistpublisher @.publisher = N'WN055'
> Connecting to WN055 'WN055.FDF'
> SQL Command : <exec [dbo].[sp_MSsync_ins_Aut_LogBatch_3] N'WN046',
> N'FDF', 250008816, 250000361, N'AUTO', '2006-11-22 16:19:32.000',
> N'34B4', '5992D20D-A9E7-40AF-AB71-43F650E4E8AC', 1>
> Disconnecting from WN055 'WN05
> Disconnecting from WN046 'WN046'
> Connecting to WN030 'WN030.FDF'
> [11/22/2006 4:32:26 PM]WN055.distribution: exec
> dbo.sp_helpdistpublisher @.publisher = N'WN055'
> Connecting to WN055 'WN055.FDF'
> CQueueRdrRowChange::ApplyCommand:Failed to create instance of
> pMessage->pParams(ProcParams)
> Failed while applying queued message to publisher
> Disconnecting from WN055 'WN055'
> Worker Thread 540 : Task Failed
> Disconnecting from WN030 'WN030'
> Processed 29 queued trans, 57 cmds, 0 conflicts
> Queue Reader aborting
>
> It seem's like the subscriber WN030has some problems comunicating with
> publisher-... right? Any hint?
> Fabio
>
>
> Hilary Cotter ha scritto:
|||No, it looks like it is crashing on a single command. Almost like there is a
command in the queue causing it to crash.
Deleting the contents of the queue will cause you to lose work. I would stop
all users working on the subscriber database and try to flush the queue and
see if there is a command stuck in there.
keep logging, and run the queue until one command remains and then I would
consider deleting that one command.
Something is very wrong here. I think you should open a support incident
with Microsoft on this one. Where is Raymond when you really want him?
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
<fabio.pliger@.gmail.com> wrote in message
news:1164210515.241841.233780@.f16g2000cwb.googlegr oups.com...
> Here's what i get:
> Connecting to QueueReader 'WN055.distribution'
> Queue Reader Agent [WN055].8 (Id = 5) started
> [11/22/2006 4:32:11 PM]WN055.distribution: execute
> dbo.sp_MShelp_profile 5, 9, N''
> Connecting to WN046 'WN046.FDF'
> [11/22/2006 4:32:11 PM]WN055.distribution: exec
> dbo.sp_helpdistpublisher @.publisher = N'WN055'
> Connecting to WN055 'WN055.FDF'
> SQL Command : <exec [dbo].[sp_MSsync_ins_Aut_LogBatch_3] N'WN046',
> N'FDF', 250008816, 250000361, N'AUTO', '2006-11-22 16:19:32.000',
> N'34B4', '5992D20D-A9E7-40AF-AB71-43F650E4E8AC', 1>
> Disconnecting from WN055 'WN055'
> Disconnecting from WN046 'WN046'
> Connecting to WN030 'WN030.FDF'
> [11/22/2006 4:32:26 PM]WN055.distribution: exec
> dbo.sp_helpdistpublisher @.publisher = N'WN055'
> Connecting to WN055 'WN055.FDF'
> CQueueRdrRowChange::ApplyCommand:Failed to create instance of
> pMessage->pParams(ProcParams)
> Failed while applying queued message to publisher
> Disconnecting from WN055 'WN055'
> Worker Thread 540 : Task Failed
> Disconnecting from WN030 'WN030'
> Processed 29 queued trans, 57 cmds, 0 conflicts
> Queue Reader aborting
>
> It seem's like the subscriber WN030has some problems comunicating with
> publisher-... right? Any hint?
> Fabio
>
>
> Hilary Cotter ha scritto:
>
|||Sorry for my bad english.. but what do you mean by flushing the
queue? comand queue at the distributor or the queue table at the
subscriber? Do u mean i should delete records one by one?
Hilary Cotter ha scritto:

> No, it looks like it is crashing on a single command. Almost like there is a
> command in the queue causing it to crash.
> Deleting the contents of the queue will cause you to lose work. I would stop
> all users working on the subscriber database and try to flush the queue and
> see if there is a command stuck in there.
> keep logging, and run the queue until one command remains and then I would
> consider deleting that one command.
> Something is very wrong here. I think you should open a support incident
> with Microsoft on this one. Where is Raymond when you really want him?
> --
> 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
>
>

Queue Reader failed for Transactional Repl

Hello,
I have set up queued updating Transactional Repl. The Queue Reader keeps
failing and cannot start up any more. The output shows the following error
"cannot have more than one instance of queue reader agent for the
distribution database". What does this error message mean? Please help.
Thanks in advances
Please can you post up the complete error message, including the error
number?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
Thanks for your reply. Finally I solved by shutting down the queue reader
exe on the task manager. I thought the exe would not run if the Queue Reader
fails. But it is cluster environment and it might be a bug somewhere with the
Queue Reader exe. After I shut down the process, restarting Queue Reader
agent worked fine.
have a good one,
FJY
"Paul Ibison" wrote:

> Please can you post up the complete error message, including the error
> number?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>

Queue reader Agents Failed - SQL 200 replication

Guys,

I get the error message: Queue reader aborting. The steps failed...in queue reader agents of SQL 2000 replication. Could any one give me a hint of how to troubleshoot this problem? Thanks a lot in advance.

Are there any other messages in the history tables? If not, can you modify the queue reader profile by increasing the outputverboselevel and directing the output to a file? Add the following:

-OutputVerboseLevel 2 -Output "c:\somefolder\output.txt"

This will direct the queue agent output to an arbitrary file. It might have more detail with regards to the error being raised.

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

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

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

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 .
>
>

Queue Reader Aborting. The step failed

Hi All,
I have a bi-directional transactional replication between two SQL Server
2000 box. After I reboot the publisher, the Queue Reader kept failing, saying
"Queue Reader Aborting, the step failed, error 14151, state 1". And the worse
thing was that I could not restart it. It would fail immediately after I
restarted it. Any thought?
Thanks in advance,
Hi Franky,
It sounds like SQL Server Agent couldn't start the queue reader job. Could
you also check the job history at Management\SQL Server Agent\jobs\Queue
Reader job\View job history ro see if there is any information there?
Jing Sun
Microsoft SQL server Replication team
"Franky" <Franky@.discussions.microsoft.com> wrote in message
news:C9E1AB14-52EA-4B90-950F-5D2844BDBFC3@.microsoft.com...
> Hi All,
> I have a bi-directional transactional replication between two SQL Server
> 2000 box. After I reboot the publisher, the Queue Reader kept failing,
> saying
> "Queue Reader Aborting, the step failed, error 14151, state 1". And the
> worse
> thing was that I could not restart it. It would fail immediately after I
> restarted it. Any thought?
> Thanks in advance,

Queue Reader - remote procedure call failed

I am running transactional repl with an updateable subscription between two servers running SQL Server 2000 SP3, all agents running on the publisher. Every now and then, the Queue reader fails. I enable logging and attempt restart. The output file looks n
ormal to me; several queries for queued data, but then it seems to timeout. It just sits there for 3 minutes, then fails and retries. I can successfully query the other server, so I know it's not a communications problem. The event viewer simply says "the
remote procedure call failed and did not execute". I can't find any other error messages.
Does anyone have any advice? Thank you.
Microsoft SQL Server Replication Queue Reader Agent 8.00.760
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: [MIALDCS-1].9
Trying to Connect to Local Distributor
Connecting to QueueReader 'MIALDCS-1.distribution'
Server: MIALDCS-1
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
[7/30/2004 12:17:19 PM]MIALDCS-1.distribution: select count(*) from master.dbo.sysprocesses where [program_name] = 'Queue Reader Main (distribution)'
[7/30/2004 12:17:19 PM]MIALDCS-1.distribution: select top 1 id, name from MSqreader_agents
[7/30/2004 12:17:19 PM]MIALDCS-1.distribution: select SERVERPROPERTY('IsClustered')
Queue Reader Agent [MIALDCS-1].9 (Id = 3) started
Repl Agent Status: 1
[7/30/2004 12:17:19 PM]MIALDCS-1.distribution: execute dbo.sp_MShelp_profile 3, 9, N''
Opening SQL based queues
[7/30/2004 12:17:19 PM]MIALDCS-1.distribution: exec master.dbo.sp_MSenum_replsqlqueues N'distribution'
Worker Thread 608 : Starting
The Message Queuing service does not exist[7/30/2004 12:17:19 PM]MIALDCS-1.distribution: exec dbo.sp_MShelp_subscriber_info N'MIALDCS-1', N'MIALDCS-2'
The Message Queuing service is not available
Connecting to MIALDCS-2 'MIALDCS-2.Island'
Server: MIALDCS-2
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
MIALDCS-2.Island: {? = call dbo.sp_getsqlqueueversion (?, ?, ?, ?)}
MIALDCS-2.Island: {? = call dbo.sp_replsqlqgetrows (N'MIALDCS-1', N'Island', N'Island')}
[7/30/2004 12:17:31 PM]MIALDCS-1.distribution: exec dbo.sp_helpdistpublisher @.publisher = N'MIALDCS-1'
Connecting to MIALDCS-1 'MIALDCS-1.Island'
Worker Thread 608 : processing Transaction [2LhOShgh_agC2<T]?LH.h-5--09M--] of [SQL Queue]
Worker Thread 608 : Started Queue Transaction
Worker Thread 608 : Started SQL Tran
MIALDCS-1.Island: {? = call dbo.sp_getqueuedarticlesynctraninfo (N'Island', 44)}
SQL Command : <exec [dbo].[sp_MSsync_del_Leg_Seat_Map_1] N'MIALDCS-2', N'Island', 'F2', '101', '2004-07-24 00:00:00.000', '1', 0, 0, ' ', ' ', 0, 12632256, ' ', 'Y', ' ', 'N', 'N', '', '', '', '', '', '', '', '', ' ', ' ', ' ', 'E8613112-29DC-4563-B3F0-58
665C4967B9', 1>
(hundreds more records follow)
what command is it failing on?
The problem is probably related to the execution of a single proc, which is
locking on the publisher.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"LeeH" <LeeH@.discussions.microsoft.com> wrote in message
news:055E41A9-DA76-403B-8D93-3F4C32BA6DDE@.microsoft.com...
> I am running transactional repl with an updateable subscription between
two servers running SQL Server 2000 SP3, all agents running on the
publisher. Every now and then, the Queue reader fails. I enable logging and
attempt restart. The output file looks normal to me; several queries for
queued data, but then it seems to timeout. It just sits there for 3 minutes,
then fails and retries. I can successfully query the other server, so I know
it's not a communications problem. The event viewer simply says "the remote
procedure call failed and did not execute". I can't find any other error
messages.
> Does anyone have any advice? Thank you.
> Microsoft SQL Server Replication Queue Reader Agent 8.00.760
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: [MIALDCS-1].9
> Trying to Connect to Local Distributor
> Connecting to QueueReader 'MIALDCS-1.distribution'
> Server: MIALDCS-1
> 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
> [7/30/2004 12:17:19 PM]MIALDCS-1.distribution: select count(*) from
master.dbo.sysprocesses where [program_name] = 'Queue Reader Main
(distribution)'
> [7/30/2004 12:17:19 PM]MIALDCS-1.distribution: select top 1 id, name from
MSqreader_agents
> [7/30/2004 12:17:19 PM]MIALDCS-1.distribution: select
SERVERPROPERTY('IsClustered')
> Queue Reader Agent [MIALDCS-1].9 (Id = 3) started
> Repl Agent Status: 1
> [7/30/2004 12:17:19 PM]MIALDCS-1.distribution: execute
dbo.sp_MShelp_profile 3, 9, N''
> Opening SQL based queues
> [7/30/2004 12:17:19 PM]MIALDCS-1.distribution: exec
master.dbo.sp_MSenum_replsqlqueues N'distribution'
> Worker Thread 608 : Starting
> The Message Queuing service does not exist[7/30/2004 12:17:19
PM]MIALDCS-1.distribution: exec dbo.sp_MShelp_subscriber_info N'MIALDCS-1',
N'MIALDCS-2'
> The Message Queuing service is not available
> Connecting to MIALDCS-2 'MIALDCS-2.Island'
> Server: MIALDCS-2
> 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
> MIALDCS-2.Island: {? = call dbo.sp_getsqlqueueversion (?, ?, ?, ?)}
> MIALDCS-2.Island: {? = call dbo.sp_replsqlqgetrows (N'MIALDCS-1',
N'Island', N'Island')}
> [7/30/2004 12:17:31 PM]MIALDCS-1.distribution: exec
dbo.sp_helpdistpublisher @.publisher = N'MIALDCS-1'
> Connecting to MIALDCS-1 'MIALDCS-1.Island'
> Worker Thread 608 : processing Transaction
[2LhOShgh_agC2<T]?LH.h-5--09M--] of [SQL Queue]
> Worker Thread 608 : Started Queue Transaction
> Worker Thread 608 : Started SQL Tran
> MIALDCS-1.Island: {? = call dbo.sp_getqueuedarticlesynctraninfo
(N'Island', 44)}
> SQL Command : <exec [dbo].[sp_MSsync_del_Leg_Seat_Map_1] N'MIALDCS-2',
N'Island', 'F2', '101', '2004-07-24 00:00:00.000', '1', 0, 0, ' ', ' ', 0,
12632256, ' ', 'Y', ' ', 'N', 'N', '', '', '', '', '', '', '', '', ' ', ' ',
' ', 'E8613112-29DC-4563-B3F0-58665C4967B9', 1>
> (hundreds more records follow)
>
|||I don't see anything in the log that indicates failure. It seems that the
agent just restarts. The event viewer simply says "the remote procedure call
failed and did not execute".
"Hilary Cotter" wrote:

> what command is it failing on?
> The problem is probably related to the execution of a single proc, which is
> locking on the publisher.
>
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "LeeH" <LeeH@.discussions.microsoft.com> wrote in message
> news:055E41A9-DA76-403B-8D93-3F4C32BA6DDE@.microsoft.com...
> two servers running SQL Server 2000 SP3, all agents running on the
> publisher. Every now and then, the Queue reader fails. I enable logging and
> attempt restart. The output file looks normal to me; several queries for
> queued data, but then it seems to timeout. It just sits there for 3 minutes,
> then fails and retries. I can successfully query the other server, so I know
> it's not a communications problem. The event viewer simply says "the remote
> procedure call failed and did not execute". I can't find any other error
> messages.
> master.dbo.sysprocesses where [program_name] = 'Queue Reader Main
> (distribution)'
> MSqreader_agents
> SERVERPROPERTY('IsClustered')
> dbo.sp_MShelp_profile 3, 9, N''
> master.dbo.sp_MSenum_replsqlqueues N'distribution'
> PM]MIALDCS-1.distribution: exec dbo.sp_MShelp_subscriber_info N'MIALDCS-1',
> N'MIALDCS-2'
> N'Island', N'Island')}
> dbo.sp_helpdistpublisher @.publisher = N'MIALDCS-1'
> [2LhOShgh_agC2<T]?LH.h-5--09M--] of [SQL Queue]
> (N'Island', 44)}
> N'Island', 'F2', '101', '2004-07-24 00:00:00.000', '1', 0, 0, ' ', ' ', 0,
> 12632256, ' ', 'Y', ' ', 'N', 'N', '', '', '', '', '', '', '', '', ' ', ' ',
> ' ', 'E8613112-29DC-4563-B3F0-58665C4967B9', 1>
>
>