|
|
You're in the
sql server replication
group:Queue Reader Agent won't restart
sql server replication:
server 2000 (SP4) system. It has run fine until the other when the network went down. When it came back up, replication came back up successfully except for the queue reader agent. I researched the problem and it was due to the database being changed in the second step of the queue reader job. I wrote to a log and the actual error was: Server: NLECADS01 Database:acuu: ODBC Error: Invalid Object name 'msqreader_agents' I have seen a couple threads on this and it indicated that it should be using the distribution database. The 'msqreader_agents' table exists in the distribution database so this is the problem. My real issue start when I go to change the queue reader agent job. I go to the second step of the job and hit edit. I change the database in the dropdown to 'distribution'. I hit apply and ok. If I go right back in, the change has not taken. I thought this might simply be a display problem so I attempted to start the agent. The same problem occurs. It appears that the change of the database in the queue reader agent is not successful. Any ideas? --
Nobody has any ideas on this one? I am really stuck and could use some help.
-- Tom [quoted text, click to view] "Tom T" wrote:
> I have installed transactional replication with queued updating on a sql > server 2000 (SP4) system. It has run fine until the other when the network > went down. When it came back up, replication came back up successfully except > for the queue reader agent. I researched the problem and it was due to the > database being changed in the second step of the queue reader job. I wrote to > a log and the actual error was: > > Server: NLECADS01 Database:acuu: ODBC Error: Invalid Object name > 'msqreader_agents' > > I have seen a couple threads on this and it indicated that it should be > using the distribution database. The 'msqreader_agents' table exists in the > distribution database so this is the problem. > > My real issue start when I go to change the queue reader agent job. I go to > the second step of the job and hit edit. I change the database in the > dropdown to 'distribution'. I hit apply and ok. > > If I go right back in, the change has not taken. I thought this might simply > be a display problem so I attempted to start the agent. The same problem > occurs. It appears that the change of the database in the queue reader agent > is not successful. > > Any ideas? > --
Please can you enable logging and then post up the full details of this
error. Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com
Can you make the default database that the account the subscription uses to
pulled or pushed with, the distribution database? -- Hilary Cotter Director of Text Mining and Database Strategy RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com [quoted text, click to view] "Tom T" <TomT@discussions.microsoft.com> wrote in message news:F7A45AB5-93D4-478D-B15C-9D9472FA5EAE@microsoft.com... > Nobody has any ideas on this one? I am really stuck and could use some > help. > -- > Tom > > > "Tom T" wrote: > >> I have installed transactional replication with queued updating on a sql >> server 2000 (SP4) system. It has run fine until the other when the >> network >> went down. When it came back up, replication came back up successfully >> except >> for the queue reader agent. I researched the problem and it was due to >> the >> database being changed in the second step of the queue reader job. I >> wrote to >> a log and the actual error was: >> >> Server: NLECADS01 Database:acuu: ODBC Error: Invalid Object name >> 'msqreader_agents' >> >> I have seen a couple threads on this and it indicated that it should be >> using the distribution database. The 'msqreader_agents' table exists in >> the >> distribution database so this is the problem. >> >> My real issue start when I go to change the queue reader agent job. I go >> to >> the second step of the job and hit edit. I change the database in the >> dropdown to 'distribution'. I hit apply and ok. >> >> If I go right back in, the change has not taken. I thought this might >> simply >> be a display problem so I attempted to start the agent. The same problem >> occurs. It appears that the change of the database in the queue reader >> agent >> is not successful. >> >> Any ideas? >> -- >> Tom
I will attach the log first thing Tuesday morning. Thanks for your help.
-- Tom [quoted text, click to view] "Paul Ibison" wrote:
> Please can you enable logging and then post up the full details of this > error. > Cheers, > Paul Ibison SQL Server MVP, www.replicationanswers.com > >
Tom,
you've probably seen this before, but here is the link for logging, just in case: http://support.microsoft.com/?id=312292 Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com
Tom,
can you check that the distributor is visible from the subscriber as a remote server. The queue reader agent will be running as the sql server agent of the subscriber, so log on as this login when testing the connectivity, so you'll be checking the security at the same time. Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com
Here is the output from the log. Since we have many publications, it tries
over and over again. The basic error is the same, Microsoft SQL Server Replication Queue Reader Agent 8.00.2039 Copyright (c) 2000 Microsoft Corporation Microsoft SQL Server Replication Agent: [NLECADS01].8 Connecting to QueueReader 'NLECADS01.acudata' Server: NLECADS01 DBMS: Microsoft SQL Server Version: 08.00.2039 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 [8/24/2006 11:00:31 AM]NLECADS01.acudata: select count(*) from master.dbo.sysprocesses where [program_name] = 'Queue Reader Main (acudata)' [8/24/2006 11:00:31 AM]NLECADS01.acudata: select top 1 id, name from MSqreader_agents Server: NLECADS01, Database acudata : ODBC Error:Invalid object name 'MSqreader_agents'. Unable to connect to Local Distributor Queue Reader aborting Microsoft SQL Server Replication Queue Reader Agent 8.00.2039 Copyright (c) 2000 Microsoft Corporation Microsoft SQL Server Replication Agent: [NLECADS01].8 Connecting to QueueReader 'NLECADS01.acudata' Server: NLECADS01 DBMS: Microsoft SQL Server Version: 08.00.2039 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 [8/25/2006 9:26:10 AM]NLECADS01.acudata: select count(*) from master.dbo.sysprocesses where [program_name] = 'Queue Reader Main (acudata)' [8/25/2006 9:26:11 AM]NLECADS01.acudata: select top 1 id, name from MSqreader_agents Server: NLECADS01, Database acudata : ODBC Error:Invalid object name 'MSqreader_agents'. Unable to connect to Local Distributor Queue Reader aborting Microsoft SQL Server Replication Queue Reader Agent 8.00.2039 Copyright (c) 2000 Microsoft Corporation Microsoft SQL Server Replication Agent: [NLECADS01].8 Connecting to QueueReader 'NLECADS01.acudata' Server: NLECADS01 DBMS: Microsoft SQL Server Version: 08.00.2039 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 [8/25/2006 9:32:30 AM]NLECADS01.acudata: select count(*) from master.dbo.sysprocesses where [program_name] = 'Queue Reader Main (acudata)' [8/25/2006 9:32:30 AM]NLECADS01.acudata: select top 1 id, name from MSqreader_agents Server: NLECADS01, Database acudata : ODBC Error:Invalid object name 'MSqreader_agents'. Unable to connect to Local Distributor Queue Reader aborting Microsoft SQL Server Replication Queue Reader Agent 8.00.2039 Copyright (c) 2000 Microsoft Corporation Microsoft SQL Server Replication Agent: [NLECADS01].8 Connecting to QueueReader 'NLECADS01.acudata' Server: NLECADS01 DBMS: Microsoft SQL Server Version: 08.00.2039 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 [8/25/2006 9:44:04 AM]NLECADS01.acudata: select count(*) from master.dbo.sysprocesses where [program_name] = 'Queue Reader Main (acudata)' [8/25/2006 9:44:04 AM]NLECADS01.acudata: select top 1 id, name from MSqreader_agents Server: NLECADS01, Database acudata : ODBC Error:Invalid object name 'MSqreader_agents'. Unable to connect to Local Distributor Queue Reader aborting Microsoft SQL Server Replication Queue Reader Agent 8.00.2039 Copyright (c) 2000 Microsoft Corporation Microsoft SQL Server Replication Agent: [NLECADS01].8 Connecting to QueueReader 'NLECADS01.acudata' Server: NLECADS01 DBMS: Microsoft SQL Server Version: 08.00.2039 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 [8/25/2006 9:48:52 AM]NLECADS01.acudata: select count(*) from master.dbo.sysprocesses where [program_name] = 'Queue Reader Main (acudata)' [8/25/2006 9:48:52 AM]NLECADS01.acudata: select top 1 id, name from MSqreader_agents Server: NLECADS01, Database acudata : ODBC Error:Invalid object name 'MSqreader_agents'. Unable to connect to Local Distributor Queue Reader aborting Microsoft SQL Server Replication Queue Reader Agent 8.00.2039 Copyright (c) 2000 Microsoft Corporation Microsoft SQL Server Replication Agent: [NLECADS01].8 Connecting to QueueReader 'NLECADS01.acudata' Server: NLECADS01 DBMS: Microsoft SQL Server Version: 08.00.2039 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 [8/25/2006 9:52:42 AM]NLECADS01.acudata: select count(*) from master.dbo.sysprocesses where [program_name] = 'Queue Reader Main (acudata)' [8/25/2006 9:52:42 AM]NLECADS01.acudata: select top 1 id, name from MSqreader_agents Server: NLECADS01, Database acudata : ODBC Error:Invalid object name 'MSqreader_agents'. Unable to connect to Local Distributor Queue Reader aborting Microsoft SQL Server Replication Queue Reader Agent 8.00.2039 Copyright (c) 2000 Microsoft Corporation Microsoft SQL Server Replication Agent: [NLECADS01].8 Connecting to QueueReader 'NLECADS01.acudata' Server: NLECADS01 DBMS: Microsoft SQL Server Version: 08.00.2039 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
Tom
The first series of messages [8/24/2006 11:00:31 AM]NLECADS01.acudata: select count(*) from master.dbo.sysprocesses where [program_name] = 'Queue Reader Main (acudata)' imply that your queue reader cannot logon to your local distributor. Can you verify that the queue reader account runs under the sa account of your subscriber? If it runs under a differen account, ensure that the default database for this account is the distribution database and this account is in the dbo_role in the distribution database. The next series of messages seem to imply that you have more than one queue reader for the database. It is also troubling to me to see that somehow you were down from the 28th at 5:00 pm to the 8/31 at 10:00 am. What occurred during this time period? [8/31/2006 9:59:14 AM]NLECADS01.distribution: select count(*) from master.dbo.sysprocesses where [program_name] = 'Queue Reader Main (distribution)' Cannot have more than one instance of Queue reader agent for the distribution database <distribution> [8/31/2006 10:14:35 AM]NLECADS01.distribution: select count(*) from master.dbo.sysprocesses where [program_name] = 'Queue Reader Main (distribution)' Cannot have more than one instance of Queue reader agent for the distribution database <distribution> Unable to connect to Local Distributor Queue Reader aborting Microsoft SQL Server Replication Queue Reader Agent 8.00.2039 Copyright (c) 2000 Microsoft Corporation Microsoft SQL Server Replication Agent: [NLECADS01].8 -- Hilary Cotter Director of Text Mining and Database Strategy RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com [quoted text, click to view] "Tom T" <TomT@discussions.microsoft.com> wrote in message
news:31ABF75B-06E1-40E1-AE2E-A94C5DA1B3C6@microsoft.com... > Here is the output from the log. Since we have many publications, it tries > over and over again. The basic error is the same, > > Microsoft SQL Server Replication Queue Reader Agent 8.00.2039 > Copyright (c) 2000 Microsoft Corporation > Microsoft SQL Server Replication Agent: [NLECADS01].8 > > Connecting to QueueReader 'NLECADS01.acudata' > > Server: NLECADS01 > DBMS: Microsoft SQL Server > Version: 08.00.2039 > 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 > > [8/24/2006 11:00:31 AM]NLECADS01.acudata: select count(*) from > master.dbo.sysprocesses where [program_name] = 'Queue Reader Main > (acudata)' > [8/24/2006 11:00:31 AM]NLECADS01.acudata: select top 1 id, name from > MSqreader_agents > Server: NLECADS01, Database acudata : ODBC Error:Invalid object name > 'MSqreader_agents'. > Unable to connect to Local Distributor > Queue Reader aborting > Microsoft SQL Server Replication Queue Reader Agent 8.00.2039 > Copyright (c) 2000 Microsoft Corporation > Microsoft SQL Server Replication Agent: [NLECADS01].8 > > Connecting to QueueReader 'NLECADS01.acudata' > > Server: NLECADS01 > DBMS: Microsoft SQL Server > Version: 08.00.2039 > 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 > > [8/25/2006 9:26:10 AM]NLECADS01.acudata: select count(*) from > master.dbo.sysprocesses where [program_name] = 'Queue Reader Main > (acudata)' > [8/25/2006 9:26:11 AM]NLECADS01.acudata: select top 1 id, name from > MSqreader_agents > Server: NLECADS01, Database acudata : ODBC Error:Invalid object name > 'MSqreader_agents'. > Unable to connect to Local Distributor > Queue Reader aborting > Microsoft SQL Server Replication Queue Reader Agent 8.00.2039 > Copyright (c) 2000 Microsoft Corporation > Microsoft SQL Server Replication Agent: [NLECADS01].8 > > Connecting to QueueReader 'NLECADS01.acudata' > > Server: NLECADS01 > DBMS: Microsoft SQL Server > Version: 08.00.2039 > 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 > > [8/25/2006 9:32:30 AM]NLECADS01.acudata: select count(*) from > master.dbo.sysprocesses where [program_name] = 'Queue Reader Main > (acudata)' > [8/25/2006 9:32:30 AM]NLECADS01.acudata: select top 1 id, name from > MSqreader_agents > Server: NLECADS01, Database acudata : ODBC Error:Invalid object name > 'MSqreader_agents'. > Unable to connect to Local Distributor > Queue Reader aborting > Microsoft SQL Server Replication Queue Reader Agent 8.00.2039 > Copyright (c) 2000 Microsoft Corporation > Microsoft SQL Server Replication Agent: [NLECADS01].8 > > Connecting to QueueReader 'NLECADS01.acudata' > > Server: NLECADS01 > DBMS: Microsoft SQL Server > Version: 08.00.2039 > 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 > > [8/25/2006 9:44:04 AM]NLECADS01.acudata: select count(*) from > master.dbo.sysprocesses where [program_name] = 'Queue Reader Main > (acudata)' > [8/25/2006 9:44:04 AM]NLECADS01.acudata: select top 1 id, name from > MSqreader_agents > Server: NLECADS01, Database acudata : ODBC Error:Invalid object name > 'MSqreader_agents'. > Unable to connect to Local Distributor > Queue Reader aborting > Microsoft SQL Server Replication Queue Reader Agent 8.00.2039 > Copyright (c) 2000 Microsoft Corporation > Microsoft SQL Server Replication Agent: [NLECADS01].8 > > Connecting to QueueReader 'NLECADS01.acudata' > > Server: NLECADS01 > DBMS: Microsoft SQL Server > Version: 08.00.2039 > user name: dbo > API conformance: 2 > SQL conformance: 1
The customer did not contact me until the 31st. From the sounds of it,
replication was down for a short amount of time (network issues) during that period. On the 31st, I got a call indicating that the queue reader agent could not be restarted. The techs in the field tried for 3 days. I looked at the log and noticed that it was pointing to the wrong database.I changed the job to look at the distribution database. I then got the second type of error message when I again tried to restart the job. Cannot have more than one instance of Queue reader agent for the distribution database <distribution> I ran the following sql statement in query analyzer on the server where the publishing database and the distribution database reside. select count(*) from master.dbo.sysprocesses where [program_name] = 'Queue Reader Main (distribution)' I get a count(*) of 1 even though the queue reader is not running. Is there a way of clearing this entry out? Should this be 0 when the agent is not running? Thanks. -- Tom [quoted text, click to view] "Hilary Cotter" wrote:
> Tom > > The first series of messages > [8/24/2006 11:00:31 AM]NLECADS01.acudata: select count(*) from > master.dbo.sysprocesses where [program_name] = 'Queue Reader Main (acudata)' > > imply that your queue reader cannot logon to your local distributor. Can you > verify that the queue reader account runs under the sa account of your > subscriber? If it runs under a differen account, ensure that the default > database for this account is the distribution database and this account is > in the dbo_role in the distribution database. > > The next series of messages seem to imply that you have more than one queue > reader for the database. It is also troubling to me to see that somehow you > were down from the 28th at 5:00 pm to the 8/31 at 10:00 am. What occurred > during this time period? > > [8/31/2006 9:59:14 AM]NLECADS01.distribution: select count(*) from > master.dbo.sysprocesses where [program_name] = 'Queue Reader Main > (distribution)' > Cannot have more than one instance of Queue reader agent for the > distribution database <distribution> > > [8/31/2006 10:14:35 AM]NLECADS01.distribution: select count(*) from > master.dbo.sysprocesses where [program_name] = 'Queue Reader Main > (distribution)' > Cannot have more than one instance of Queue reader agent for the > distribution database <distribution> > Unable to connect to Local Distributor > Queue Reader aborting > Microsoft SQL Server Replication Queue Reader Agent 8.00.2039 > Copyright (c) 2000 Microsoft Corporation > Microsoft SQL Server Replication Agent: [NLECADS01].8 > > > > -- > Hilary Cotter > Director of Text Mining and Database Strategy > RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. > > This posting is my own and doesn't necessarily represent RelevantNoise's > positions, strategies or opinions. > > Looking for a SQL Server replication book? > http://www.nwsu.com/0974973602.html > > Looking for a FAQ on Indexing Services/SQL FTS > http://www.indexserverfaq.com > > > > "Tom T" <TomT@discussions.microsoft.com> wrote in message > news:31ABF75B-06E1-40E1-AE2E-A94C5DA1B3C6@microsoft.com... > > Here is the output from the log. Since we have many publications, it tries > > over and over again. The basic error is the same, > > > > Microsoft SQL Server Replication Queue Reader Agent 8.00.2039 > > Copyright (c) 2000 Microsoft Corporation > > Microsoft SQL Server Replication Agent: [NLECADS01].8 > > > > Connecting to QueueReader 'NLECADS01.acudata' > > > > Server: NLECADS01 > > DBMS: Microsoft SQL Server > > Version: 08.00.2039 > > 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 > > > > [8/24/2006 11:00:31 AM]NLECADS01.acudata: select count(*) from > > master.dbo.sysprocesses where [program_name] = 'Queue Reader Main > > (acudata)' > > [8/24/2006 11:00:31 AM]NLECADS01.acudata: select top 1 id, name from > > MSqreader_agents > > Server: NLECADS01, Database acudata : ODBC Error:Invalid object name > > 'MSqreader_agents'. > > Unable to connect to Local Distributor > > Queue Reader aborting > > Microsoft SQL Server Replication Queue Reader Agent 8.00.2039 > > Copyright (c) 2000 Microsoft Corporation > > Microsoft SQL Server Replication Agent: [NLECADS01].8 > > > > Connecting to QueueReader 'NLECADS01.acudata' > > > > Server: NLECADS01 > > DBMS: Microsoft SQL Server > > Version: 08.00.2039 > > 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 > > > > [8/25/2006 9:26:10 AM]NLECADS01.acudata: select count(*) from > > master.dbo.sysprocesses where [program_name] = 'Queue Reader Main > > (acudata)' > > [8/25/2006 9:26:11 AM]NLECADS01.acudata: select top 1 id, name from > > MSqreader_agents > > Server: NLECADS01, Database acudata : ODBC Error:Invalid object name > > 'MSqreader_agents'. > > Unable to connect to Local Distributor > > Queue Reader aborting > > Microsoft SQL Server Replication Queue Reader Agent 8.00.2039 > > Copyright (c) 2000 Microsoft Corporation > > Microsoft SQL Server Replication Agent: [NLECADS01].8 > > > > Connecting to QueueReader 'NLECADS01.acudata' > > > > Server: NLECADS01 > > DBMS: Microsoft SQL Server > > Version: 08.00.2039 > > 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 > > > > [8/25/2006 9:32:30 AM]NLECADS01.acudata: select count(*) from > > master.dbo.sysprocesses where [program_name] = 'Queue Reader Main > > (acudata)' > > [8/25/2006 9:32:30 AM]NLECADS01.acudata: select top 1 id, name from > > MSqreader_agents > > Server: NLECADS01, Database acudata : ODBC Error:Invalid object name > > 'MSqreader_agents'. > > Unable to connect to Local Distributor > > Queue Reader aborting > > Microsoft SQL Server Replication Queue Reader Agent 8.00.2039
It just meant that the queue reader was running when you started the job. I
think everything is working now. -- Hilary Cotter Director of Text Mining and Database Strategy RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com [quoted text, click to view] "Tom T" <TomT@discussions.microsoft.com> wrote in message
news:72D0314A-122E-43F0-8A44-0A680335749B@microsoft.com... > The customer did not contact me until the 31st. From the sounds of it, > replication was down for a short amount of time (network issues) during > that > period. On the 31st, I got a call indicating that the queue reader agent > could not be restarted. The techs in the field tried for 3 days. I looked > at > the log and noticed that it was pointing to the wrong database.I changed > the > job to look at the distribution database. I then got the second type of > error > message when I again tried to restart the job. > > Cannot have more than one instance of Queue reader agent for the > distribution database <distribution> > > I ran the following sql statement in query analyzer on the server where > the > publishing database and the distribution database reside. > > select count(*) from master.dbo.sysprocesses where [program_name] = 'Queue > Reader Main (distribution)' > > I get a count(*) of 1 even though the queue reader is not running. Is > there > a way of clearing this entry out? Should this be 0 when the agent is not > running? > > Thanks. > -- > Tom > > > "Hilary Cotter" wrote: > >> Tom >> >> The first series of messages >> [8/24/2006 11:00:31 AM]NLECADS01.acudata: select count(*) from >> master.dbo.sysprocesses where [program_name] = 'Queue Reader Main >> (acudata)' >> >> imply that your queue reader cannot logon to your local distributor. Can >> you >> verify that the queue reader account runs under the sa account of your >> subscriber? If it runs under a differen account, ensure that the default >> database for this account is the distribution database and this account >> is >> in the dbo_role in the distribution database. >> >> The next series of messages seem to imply that you have more than one >> queue >> reader for the database. It is also troubling to me to see that somehow >> you >> were down from the 28th at 5:00 pm to the 8/31 at 10:00 am. What occurred >> during this time period? >> >> [8/31/2006 9:59:14 AM]NLECADS01.distribution: select count(*) from >> master.dbo.sysprocesses where [program_name] = 'Queue Reader Main >> (distribution)' >> Cannot have more than one instance of Queue reader agent for the >> distribution database <distribution> >> >> [8/31/2006 10:14:35 AM]NLECADS01.distribution: select count(*) from >> master.dbo.sysprocesses where [program_name] = 'Queue Reader Main >> (distribution)' >> Cannot have more than one instance of Queue reader agent for the >> distribution database <distribution> >> Unable to connect to Local Distributor >> Queue Reader aborting >> Microsoft SQL Server Replication Queue Reader Agent 8.00.2039 >> Copyright (c) 2000 Microsoft Corporation >> Microsoft SQL Server Replication Agent: [NLECADS01].8 >> >> >> >> -- >> Hilary Cotter >> Director of Text Mining and Database Strategy >> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. >> >> This posting is my own and doesn't necessarily represent RelevantNoise's >> positions, strategies or opinions. >> >> Looking for a SQL Server replication book? >> http://www.nwsu.com/0974973602.html >> >> Looking for a FAQ on Indexing Services/SQL FTS >> http://www.indexserverfaq.com >> >> >> >> "Tom T" <TomT@discussions.microsoft.com> wrote in message >> news:31ABF75B-06E1-40E1-AE2E-A94C5DA1B3C6@microsoft.com... >> > Here is the output from the log. Since we have many publications, it >> > tries >> > over and over again. The basic error is the same, >> > >> > Microsoft SQL Server Replication Queue Reader Agent 8.00.2039 >> > Copyright (c) 2000 Microsoft Corporation >> > Microsoft SQL Server Replication Agent: [NLECADS01].8 >> > >> > Connecting to QueueReader 'NLECADS01.acudata' >> > >> > Server: NLECADS01 >> > DBMS: Microsoft SQL Server >> > Version: 08.00.2039 >> > 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 >> > >> > [8/24/2006 11:00:31 AM]NLECADS01.acudata: select count(*) from >> > master.dbo.sysprocesses where [program_name] = 'Queue Reader Main >> > (acudata)' >> > [8/24/2006 11:00:31 AM]NLECADS01.acudata: select top 1 id, name from >> > MSqreader_agents >> > Server: NLECADS01, Database acudata : ODBC Error:Invalid object name >> > 'MSqreader_agents'. >> > Unable to connect to Local Distributor >> > Queue Reader aborting >> > Microsoft SQL Server Replication Queue Reader Agent 8.00.2039 >> > Copyright (c) 2000 Microsoft Corporation >> > Microsoft SQL Server Replication Agent: [NLECADS01].8 >> > >> > Connecting to QueueReader 'NLECADS01.acudata' >> > >> > Server: NLECADS01 >> > DBMS: Microsoft SQL Server >> > Version: 08.00.2039 >> > 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 >> > >> > [8/25/2006 9:26:10 AM]NLECADS01.acudata: select count(*) from >> > master.dbo.sysprocesses where [program_name] = 'Queue Reader Main >> > (acudata)' >> > [8/25/2006 9:26:11 AM]NLECADS01.acudata: select top 1 id, name from >> > MSqreader_agents >> > Server: NLECADS01, Database acudata : ODBC Error:Invalid object name >> > 'MSqreader_agents'. >> > Unable to connect to Local Distributor >> > Queue Reader aborting >> > Microsoft SQL Server Replication Queue Reader Agent 8.00.2039 >> > Copyright (c) 2000 Microsoft Corporation >> > Microsoft SQL Server Replication Agent: [NLECADS01].8 >> > >> > Connecting to QueueReader 'NLECADS01.acudata' >> > >> > Server: NLECADS01 >> > DBMS: Microsoft SQL Server >> > Version: 08.00.2039 >> > user name: dbo >> > API conformance: 2
Don't see what you're looking for? Try a search.
|
April 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |