Error replication agent is not registered properly

We've been running transactional replication with updatable subscribers for
several months now. his morning we are seeing these errors in the LOG and
QUEUE READER logs.
You Receive Error Message: "The replication agent is not registered
properly. Rerun SQL Server setup.
Any ideas?
SQL Server 2000 SP3
Running the following command would likely resolve the issue:
"%ProgramFiles%\Microsoft SQL Server\80\COM\qrdrsvc.exe" -RegServer
Although I am curious to know if you have installed\uninstalled software
recently on the box that might have caused the problem in the first place.
-Raymond
"CAP" <abraxas1969@.hotmail.com> wrote in message
news:ehtb84P$FHA.740@.TK2MSFTNGP12.phx.gbl...
> We've been running transactional replication with updatable subscribers
> for
> several months now. his morning we are seeing these errors in the LOG and
> QUEUE READER logs.
>
> You Receive Error Message: "The replication agent is not registered
> properly. Rerun SQL Server setup.
>
> Any ideas?
> SQL Server 2000 SP3
>
|||Appreciate the info !
We are investigating if changes to either the OS or SQLServer itself are the
root cause of this problem. We are seeing that in addition to the queue
reader agent, these are also experiencing the same errors:
LOG READER agent
SNAPSHOT agent
DISTRIBUTION agent.
Does this means we also need to run the command below to register the above
agents as well or just 'qrdrsvc.exe' as you indicate?
==============
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
news:O2nEgfS$FHA.140@.TK2MSFTNGP12.phx.gbl...
> Running the following command would likely resolve the issue:
> "%ProgramFiles%\Microsoft SQL Server\80\COM\qrdrsvc.exe" -RegServer
> Although I am curious to know if you have installed\uninstalled software
> recently on the box that might have caused the problem in the first place.
> -Raymond
> "CAP" <abraxas1969@.hotmail.com> wrote in message
> news:ehtb84P$FHA.740@.TK2MSFTNGP12.phx.gbl...
>
|||This seems really strange, is this a clustered SQL Server instance or was
there a registry restore\repair on the box?
In any case, you can probably resolve the issue that you are seeing by
running the agent executables with the -RegServer parameter:
Snapshot agent - snapshot.exe
Logreader agent - logread.exe
Distribution agent - distrib.exe
If the problem is as extensive as it seems to be you may also need to
re-register the support dlls for the replication agents using regsvr32.exe.
Here is a list off the top of my head:
rinitcom.dll
repldp.dll
rdistcom.dll
-Raymond
"GuayacanSQL" <abraxas1969@.hotmail.com> wrote in message
news:eDajBto$FHA.3864@.TK2MSFTNGP12.phx.gbl...
> Appreciate the info !
>
> We are investigating if changes to either the OS or SQLServer itself are
> the root cause of this problem. We are seeing that in addition to the
> queue reader agent, these are also experiencing the same errors:
>
> LOG READER agent
> SNAPSHOT agent
> DISTRIBUTION agent.
>
> Does this means we also need to run the command below to register the
> above agents as well or just 'qrdrsvc.exe' as you indicate?
>
> ==============
> "Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
> news:O2nEgfS$FHA.140@.TK2MSFTNGP12.phx.gbl...
>
|||This is a 2-node clustered SQLServer environment. Word were are getting is
that an attempt to install a new named instance on the cluster failed
(reason unknown) and had to be uninstalled. We are seeing these errors right
after this happened.
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
news:%23wyI2D0$FHA.2736@.TK2MSFTNGP11.phx.gbl...
> This seems really strange, is this a clustered SQL Server instance or was
> there a registry restore\repair on the box?
> In any case, you can probably resolve the issue that you are seeing by
> running the agent executables with the -RegServer parameter:
> Snapshot agent - snapshot.exe
> Logreader agent - logread.exe
> Distribution agent - distrib.exe
> If the problem is as extensive as it seems to be you may also need to
> re-register the support dlls for the replication agents using
regsvr32.exe.[vbcol=seagreen]
> Here is a list off the top of my head:
> rinitcom.dll
> repldp.dll
> rdistcom.dll
> -Raymond
> "GuayacanSQL" <abraxas1969@.hotmail.com> wrote in message
> news:eDajBto$FHA.3864@.TK2MSFTNGP12.phx.gbl...
software[vbcol=seagreen]
subscribers
>
|||It was determined that uninstalling one of the SQL instances on the cluster
caused the replication agents to be unregistered. We executed the commands
below and all went well with the exception of the QUEUE READER agent. When
we attempt to register the queue reader agent with 'qrdrsvc.exe regserver'
we get this error:
===================
Microsoft SQL Server Replication Queue Reader Agent 8.00.760 Copyright (c)
2000 Microsoft Corporation
Server: SERVER1, Database distribution : ODBC Error:SQL Server does not
exist or access denied.
Unable to connect to Local Distributor
Queue Reader aborting
=======================
Is there something special about registering queue reader agent ?
"CAP" <abraxas1969@.hotmail.com> wrote in message
news:OcDiKc0$FHA.140@.TK2MSFTNGP12.phx.gbl...
> This is a 2-node clustered SQLServer environment. Word were are getting is
> that an attempt to install a new named instance on the cluster failed
> (reason unknown) and had to be uninstalled. We are seeing these errors
right[vbcol=seagreen]
> after this happened.
>
> "Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
> news:%23wyI2D0$FHA.2736@.TK2MSFTNGP11.phx.gbl...
was[vbcol=seagreen]
> regsvr32.exe.
are[vbcol=seagreen]
> software
> subscribers
LOG
>
|||That seems kind of strange as I didn't get any messages when I tried the
same on my machine. But if you can start the queue reader agent from
SEM\SQLServerAgent then I wouldn't worry too much about it.
-Raymond
"CAP" <abraxas1969@.hotmail.com> wrote in message
news:eLNoFckAGHA.1312@.TK2MSFTNGP09.phx.gbl...
> It was determined that uninstalling one of the SQL instances on the
> cluster
> caused the replication agents to be unregistered. We executed the commands
> below and all went well with the exception of the QUEUE READER agent.
> When
> we attempt to register the queue reader agent with
> 'qrdrsvc.exe -regserver'
> we get this error:
> ===================
> Microsoft SQL Server Replication Queue Reader Agent 8.00.760 Copyright (c)
> 2000 Microsoft Corporation
> Server: SERVER1, Database distribution : ODBC Error:SQL Server does not
> exist or access denied.
> Unable to connect to Local Distributor
> Queue Reader aborting
> =======================
> Is there something special about registering queue reader agent ?
>
> "CAP" <abraxas1969@.hotmail.com> wrote in message
> news:OcDiKc0$FHA.140@.TK2MSFTNGP12.phx.gbl...
> right
> was
> are
> LOG
>
|||I'm sorry. Can you please elaborate more on what you mean with
SEM\SQLServerAgent ? We are trying to start the queue reader agent from
Enterprise Manager and keep getting the error:
"The replication agent is not registered properly. Rerun SQL Server setup"
===================
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
news:OdN0KTmAGHA.204@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> That seems kind of strange as I didn't get any messages when I tried the
> same on my machine. But if you can start the queue reader agent from
> SEM\SQLServerAgent then I wouldn't worry too much about it.
> -Raymond
> "CAP" <abraxas1969@.hotmail.com> wrote in message
> news:eLNoFckAGHA.1312@.TK2MSFTNGP09.phx.gbl...
commands[vbcol=seagreen]
(c)[vbcol=seagreen]
by[vbcol=seagreen]
to[vbcol=seagreen]
itself[vbcol=seagreen]
the[vbcol=seagreen]
the[vbcol=seagreen]
Server\80\COM\qrdrsvc.exe" -RegServer[vbcol=seagreen]
first[vbcol=seagreen]
registered
>
|||Hi Mark,
When a replication agent is started through a SQL Server Agent job (which is
the same as starting a replication agent from SEM), SQL Server Agent will
activate the replication agent as a COM exe server rather than running it as
a regular executable. That is why I suspect that the COM registration
information for the replication agents was broken when you first reported
the problem. Now from what you have described, your SQL Server installation
was broken due to a clustered instance uninstall so a better course of
action is probably for you to reinstall SQL server rather than trying to fix
bits and pieces of it since nobody knows exactly what pieces are broken.
That said, it is still strange that running 'qrdrsvc.exe -regserver' didn't
return without errors for you (you would want to make sure that Word didn't
mangle the - for you...).
-Raymond
"CAP" <abraxas1969@.hotmail.com> wrote in message
news:u4%234FonAGHA.3872@.TK2MSFTNGP12.phx.gbl...
> I'm sorry. Can you please elaborate more on what you mean with
> SEM\SQLServerAgent ? We are trying to start the queue reader agent from
> Enterprise Manager and keep getting the error:
> "The replication agent is not registered properly. Rerun SQL Server setup"
> ===================
> "Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
> news:OdN0KTmAGHA.204@.TK2MSFTNGP15.phx.gbl...
> commands
> (c)
> by
> to
> itself
> the
> the
> Server\80\COM\qrdrsvc.exe" -RegServer
> first
> registered
>
|||In fact, this is what we are getting when running 'qrdrsvc.exe -regserver'
as a server administrator (with System Administrator role on the SQL server)
Microsoft SQL Server Replication Queue Reader Agent 8.00.760 Copyright (c)
2000 Microsoft Corporation
Server: SERVER1, Database distribution : ODBC Error:SQL Server does not
exist or access denied.
Unable to connect to Local Distributor
Queue Reader aborting
The process finished. Use CTRL+C to close this window.
=========================
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
news:%23USLY0nAGHA.516@.TK2MSFTNGP15.phx.gbl...
> Hi Mark,
> When a replication agent is started through a SQL Server Agent job (which
is
> the same as starting a replication agent from SEM), SQL Server Agent will
> activate the replication agent as a COM exe server rather than running it
as
> a regular executable. That is why I suspect that the COM registration
> information for the replication agents was broken when you first reported
> the problem. Now from what you have described, your SQL Server
installation
> was broken due to a clustered instance uninstall so a better course of
> action is probably for you to reinstall SQL server rather than trying to
fix
> bits and pieces of it since nobody knows exactly what pieces are broken.
> That said, it is still strange that running 'qrdrsvc.exe -regserver'
didn't
> return without errors for you (you would want to make sure that Word
didn't[vbcol=seagreen]
> mangle the - for you...).
> -Raymond
> "CAP" <abraxas1969@.hotmail.com> wrote in message
> news:u4%234FonAGHA.3872@.TK2MSFTNGP12.phx.gbl...
setup"[vbcol=seagreen]
the[vbcol=seagreen]
Copyright[vbcol=seagreen]
not[vbcol=seagreen]
failed[vbcol=seagreen]
errors[vbcol=seagreen]
seeing[vbcol=seagreen]
need[vbcol=seagreen]
to[vbcol=seagreen]
register[vbcol=seagreen]
message
>

Error number: 37000

All,
I've been configuring Transactional replication in accordance with the
'High Availability' standards, and it seems the initial snapshots have been
transferred but when looking at my distribution agent I can see this error:
Last Command:
{CALL sp_MSdel_Alliance UniChem Norge (RBO)$Customer Posting Group ('ALA')}
Transaction sequence number and command ID of last execution batch are
0x0001A7C400002F8C000900000000 and 1.
Error Details:
Syntax error or access violation
(Source: MOSS-KIPPER (ODBC); Error number: 37000)
Anyone have a rough idea of what to look at?
James McM
sounds like your table name has some characters in it which are causing
problems.
What is the underlying table name?
You can work around this by right clicking on your publication, selecting
properties, articles, and then click on the browse button (the three
ellipses to the right of your table name), and click on the command tab.
Enter a proc name that looks like this:
sp_MSdel_Alliance_UniChem_Norge_RBO_Customer_Posti ng_Group
Do this for the update and insert procs as well, so they look like this:
sp_MSupd_Alliance_UniChem_Norge_RBO_Customer_Posti ng_Group
sp_MSins_Alliance_UniChem_Norge_RBO_Customer_Posti ng_Group
Now regenerate and redistribute your snapshot.
You also have the option of doing a no sync subscription, and then doing
validations to determine which tables are out of sync and manually sync
them.
To do a nosync subscription you will need to generate the procs.
To do this change the proc names as illustrated above and then on your
publisher in your publication database.
sp_addpublication 'dummy'
sp_addarticle 'dummy','tablename','tablename'
sp_scriptpublicationcustomprocs 'dummy' and in your results pane you will
find the procs. Copy these procs and run them in your subscription database.
"James McMorrough" <james.mcmorrough@.getrid.sqlpersonnel.com> wrote in
message news:OxNFmtOwEHA.3320@.TK2MSFTNGP14.phx.gbl...
> All,
> I've been configuring Transactional replication in accordance with the
> 'High Availability' standards, and it seems the initial snapshots have
> been
> transferred but when looking at my distribution agent I can see this
> error:
> Last Command:
> {CALL sp_MSdel_Alliance UniChem Norge (RBO)$Customer Posting Group
> ('ALA')}
> Transaction sequence number and command ID of last execution batch are
> 0x0001A7C400002F8C000900000000 and 1.
> Error Details:
> Syntax error or access violation
> (Source: MOSS-KIPPER (ODBC); Error number: 37000)
>
> Anyone have a rough idea of what to look at?
> James McM
>

Error number: 2812 - Transaction Replication

Hi,
I am trying transactional replication between two servers with a remote
distributor. I am getting following error each time I run the distribution
agent
Last Command : {CALL sp_MSupd_Customers (NULL,N'Alfreds Futterkiste -
test',NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL ,N'ALFKI',0x0200)}
Transaction sequence number and command ID of last execution batch are
0x0000001A00000082000900000000 and 1.
Error Message :Could not find stored procedure 'sp_MSupd_Customers'.
Error details : Could not find stored procedure 'sp_MSupd_Customers'.
(Source: L000646\AA03 (Data source); Error number: 2812)
Can some one help please
If you have used @.sync_type = None in sp_addsubscription or in the
subscription wizard, Initialize subscription page, you select 'no, the
subscriber already has the schema and data' you may get this error. The
system tables for replication will be created on the subscriber in either
case but you'll need to manually create the stored procedures on the
subscriber if you use this option otherwise you'll have the above error when
you change a row on the publisher. Use sp_scriptpublicationcustomprocs
(assuming you have >= sp1) to create a script which creates the procedures
and run this script on the subscriber.
HTH,
Paul Ibison
|||Thanks for that Paul. It is all working now.
regards
"Paul Ibison" wrote:

> If you have used @.sync_type = None in sp_addsubscription or in the
> subscription wizard, Initialize subscription page, you select 'no, the
> subscriber already has the schema and data' you may get this error. The
> system tables for replication will be created on the subscriber in either
> case but you'll need to manually create the stored procedures on the
> subscriber if you use this option otherwise you'll have the above error when
> you change a row on the publisher. Use sp_scriptpublicationcustomprocs
> (assuming you have >= sp1) to create a script which creates the procedures
> and run this script on the subscriber.
> HTH,
> Paul Ibison
>
>

Error message from server: The log file is full. Backup transactio

Hi,
I am working on a Access Sql system where I need to put a new release for a
system. This system involves transactional replication. Most of new screens
and code relate to client side sql server and the main server. When I am
trying to test some functionality on the server (main) side I am getting the
above error. Right now the main database file is 1. GB while the transaction
file is 76 GB. The problem is I cannot backup this database on the server as
it tells the log file is full. So I am not sure how to handle this situation
without having the ability to have a backup. Any help is appreciated. ThanksOn Mar 25, 10:12 am, Jack <J...@.discussions.microsoft.com> wrote:
> Hi,
> I am working on a Access Sql system where I need to put a new release for a
> system. This system involves transactional replication. Most of new screens
> and code relate to client side sql server and the main server. When I am
> trying to test some functionality on the server (main) side I am getting the
> above error. Right now the main database file is 1. GB while the transaction
> file is 76 GB. The problem is I cannot backup this database on the server as
> it tells the log file is full. So I am not sure how to handle this situation
> without having the ability to have a backup. Any help is appreciated. Thanks
try using DBCC SHRINKFILE to shrink the log file in conjunction with
the BACKUP LOG command, use sp_helpfile to find the log files logical
name, something like the following
SP_HELPFILE
this will return the logical name of the log file
DBCC SHRINKFILE (<LogicalName>)
I believe this moves all the data to the start of the file
BACKUP LOG <dbname> WITH TRUNCATE_ONLY
this then does the actual shrink. you may need to repeat commands 2 a
3 a couple of times until the filesize stops shrinking.
google or BOL the commands to make sure I have them right, I don't
have a DB handy to check.|||You should learn the basics about backup and restore and based on that set the recovery model for
your database properly. In your case, it seems you have full recover model but you don't perform log
backups. This means that the log is never emptied so the ldf file keeps growing and growing. You can
empty the log file by either setting recover model to simple or by doing:
BACKUP LOG dbname WITH NO_LOG
And then shrink the ldf file (keeping an eye on virtual log file layout, according to
http://www.karaszi.com/SQLServer/info_dont_shrink.asp), to a reasonable size.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jack" <Jack@.discussions.microsoft.com> wrote in message
news:9038A77D-EE8E-4E41-9FEB-335DB2D62834@.microsoft.com...
> Hi,
> I am working on a Access Sql system where I need to put a new release for a
> system. This system involves transactional replication. Most of new screens
> and code relate to client side sql server and the main server. When I am
> trying to test some functionality on the server (main) side I am getting the
> above error. Right now the main database file is 1. GB while the transaction
> file is 76 GB. The problem is I cannot backup this database on the server as
> it tells the log file is full. So I am not sure how to handle this situation
> without having the ability to have a backup. Any help is appreciated. Thanks

Error message from server: The log file is full. Backup transactio

Hi,
I am working on a Access Sql system where I need to put a new release for a
system. This system involves transactional replication. Most of new screens
and code relate to client side sql server and the main server. When I am
trying to test some functionality on the server (main) side I am getting the
above error. Right now the main database file is 1. GB while the transaction
file is 76 GB. The problem is I cannot backup this database on the server as
it tells the log file is full. So I am not sure how to handle this situation
without having the ability to have a backup. Any help is appreciated. Thanks
On Mar 25, 10:12 am, Jack <J...@.discussions.microsoft.com> wrote:
> Hi,
> I am working on a Access Sql system where I need to put a new release for a
> system. This system involves transactional replication. Most of new screens
> and code relate to client side sql server and the main server. When I am
> trying to test some functionality on the server (main) side I am getting the
> above error. Right now the main database file is 1. GB while the transaction
> file is 76 GB. The problem is I cannot backup this database on the server as
> it tells the log file is full. So I am not sure how to handle this situation
> without having the ability to have a backup. Any help is appreciated. Thanks
try using DBCC SHRINKFILE to shrink the log file in conjunction with
the BACKUP LOG command, use sp_helpfile to find the log files logical
name, something like the following
SP_HELPFILE
this will return the logical name of the log file
DBCC SHRINKFILE (<LogicalName>)
I believe this moves all the data to the start of the file
BACKUP LOG <dbname> WITH TRUNCATE_ONLY
this then does the actual shrink. you may need to repeat commands 2 a
3 a couple of times until the filesize stops shrinking.
google or BOL the commands to make sure I have them right, I don't
have a DB handy to check.